05 red tweety_innovation_challenge_2013_06_18_iiba_italy_chapter_round1_final


Published on

TEAM RedTweety™
Tool for Brainstorming, Focus Group

Published in: Business, Technology, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

05 red tweety_innovation_challenge_2013_06_18_iiba_italy_chapter_round1_final

  1. 1. RedTweetyTM IIBA® Italy Chapter Innovation Challenge 2013 Electronic Enabled Elicitation Luigi Rega, Riccardo Conturbia
  2. 2. Typical issues during brainstorming sessions and requirements elicitation Distractions, embarrassment, other concurrent work… People often work in different places (at home, on the beach, …) Books are often judged by the cover and ideas by the author… Best ideas come when you’re doing something else… Experience from the past is hardly taken into proper consideration… RedTweety can help you through these issues!
  3. 3. How RedTweety works Clients (hw devices) Clients (smartphones) Users: • Add (record) requirements (ideas) to the server DB by voice recognition or keyboard input. • Vote the requirements (ideas) after they are anonymized with a “like” mechanism, as in social networks. Server: • Suggests other requirements (similar or somehow related), accordingly to a set of keywords, from an historical database. • Combines requirements with logical operators and modifiers, following a defined grammar and presents them to the users to stimulate brainstorming and unexpected connections. Admin: • Defines keywords by experience, starting from sets of standard words and supported by frequency analysis of terms into the historical database. • The grammar and the operators are defined (standard sets).
  4. 4. RedTweety Physical device & smartphone app • All RedTweety client functions can be implemented both into a physical device or a smartphone app. A physical device, like a toy, can be used into common spaces, like office open spaces, or domestic environments. It should be friendly and nice. A smartphone app is the best way to always carry the RedTweety client with you. You never can tell when great ideas cross your mind!
  5. 5. RedTweety feasibility • Text-to-speech and voice recognition capabilities are common on smartphones. • There are no barriers in implementing any I/O task and connections to a server. • There are plenty of open source tools about issue / requirement management that can be used as a base for implementing server-side functionalities. • Redmine (www.redmine.org) is our favourite. • Yes, now you know where the “Red” comes from ☺ • There are no major issues in having a robot or a toy with the RedTweety client functionalities. • Arduino is suitable for prototyping.
  6. 6. Feasibility: text-to-speech and voice recognition on smarthpones • SDKs Frameworks and APIs are widely available: http://avios.org/app_dev.htm Source: Applied Voice Input/Output Society
  7. 7. Feasibility: Robots with Arduino Voice recognition and text-to-speech with Arduino, has been implemented into MiniEric robot. Source: http://www.societyofrobots.com/member _tutorials/book/export/html/346 MiniEric robot by Gabriel “Ro-Bot-X”, Toronto, ON, Canada (2009) Arduino comes in several forms, also wearable. Arduino is widely used for several DYI projects, highly suitable for prototyping. EasyVR Speech Recognition Module
  8. 8. Considerations on formal grammars and languages • Defines a hierarchy of classes of formal grammars (and languages) ranging from “Type 0” (Turing machines) to “Type 3” (programming languages) 1956 Noam Chomsky • Writes “Focault’s Pendulum”, one of his masterpieces, and uses a “Type 2 grammar” to empower the brainstorming about a “global conspiracy theory” 1989 Umberto Eco • Is a meta- language used to generate languages (grammars), mainly for satirical purposes. • (www.polygen.org) 2003-2008 Polygen • Automatically generates a “scientific research document”, submitted to WMSCI 2005 and accepted as a “non reviewed” paper! • (http://pdos.csail. mit.edu/scigen/) 2005 SCIgen
  9. 9. Further development • Better functions – Ideas (requirements) voting could be enabled only after the initial phase is over – Specializing keywords and grammars for specific contexts and processes (e.g. for avionics, automotive, risk or stakeholder identification, etc…) • Requirement management – Adding requirements management functionalities should not be a real problem, because the architecture (standard issue management tool) already enable that feature. • Gamification paradigms – e.g. recognizing the first one to reach the number of 100 requirements , to correct errors, to tag requirements, etc… • Dynamic user ranking – To determine who consistently elicit good requirements. Requirements are “ideas”.. RedTweety could be used, with little customization & configuration for problem solving, creative writing, building an agenda for a meeting in a collaborative way, etc…
  10. 10. Let’s talk about money • Free smartphone app Revenue model Not yet defined • Free “base” account • Monthly subscription for all the features (e.g. unlimited requirements, projects, users, …) Revenues (Business Model) • For an app with the required functionalities, costs may vary from a minimum of 10k to a maximum of 50k. Physical device costs Not yet estimated • Based or our experience in similar projects, customizing or extending Redmine ranges from 40 to 120 days/person http://www.bluecloudsolutions.com/blog/cost-develop-app/ http://appmuse.com/appmusing/how-much-does-it-cost-to- develop-a-mobile-app Costs & Estimations
  11. 11. RedTweety: Current status 1. We gathered the needs (starting from our experience – and frustration!). 2. We explored the RedTweety concept and determined the core and nice-to-have functionalities. 3. We researched for COTS, APIs, Frameworks, .. that could help building RedTweety (and found plenty of them!). 4. We acquired the RedTweety.it domain ☺ 5. We are searching for developers to implement a prototype.