Requirement Try not work only in Stealth

Requirement Elicitation for IT StartupsAbdulRahman, Ayaz Ishaq and Mozam AliSchool ofSystems and TechnologyUniversityof Management and Technology [email protected],[email protected], [email protected]  ABSTRACTRequirements engineering process in Startup development is not clearlyunderstood, hindering the development of reliable practices and processes forthis field of requirement engineering. An investigation of factors leading tosuccess or failure in startups development suggests that many failures can betraced to problems with the transition from preproduction to production.

Thisshows that the problem is in the requirements elicitation phase. Suppose youare an IT startup and interested in illustrating the requirements for youproject and you are unable in elicitation of the requirements what will you dothen? This paper is going to present you the ways for the elicitation of therequirements. Requirements engineering is the key area andmost of the projects fail due to the poor elicitation of requirements.

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

For thepurpose of elicitation of requirements we are going to use the technique ofIterative Model and Agile Model throughoutthe IT Startups. One of the Main reasons why the startups are failing isbecause of its working in “Stealth Mode”. Try not work only in Stealth mode.

Share your idea with others and get feedbacks but be aware of Market Monkeysbecause some senior market people steal your idea and showing the help of theIT startups as a mentor. Anotherthing that is very important in the documentation of the projects. Startdocumentation from the beginning of the startup. Keep on improving thedocumentation until the whole product is developed.

1.  INTRODUCTIONA startup canalso be defined as Research & Development Company whose primary focus is ondiscovering and gathering knowledge for a new product or service. A startup isa company that may represent a new idea.

But the main thing about the startup’ssuccess depends on its ability to “pivot”,a term that is associated with the changing of the product, strategy or engineof growth. Pivot may be defined as the agility in a specific product or an ideaof the startup. A startup company may seem like a traditional company but thestartups are very different from the traditional companies.Startup plays avery important role in the economy of a country and researchers in economicsciences have realized that existing processes cannot simply be applied tostartups because they may look alike like traditional companies but they arevery different in every aspect. There is a lot of work done in the area ofrequirements engineering but in this area of                                                          startups the work done is not of muchsignificance. Therefore, the requirements engineering in startups is a specialtype of Research and Development, but somehow it is not gaining as muchattention it should have. 1.1  STARTUPS,REQUIREMENTS ENGINEERING AND CHALLENGES Many thingshave been written about Requirements Elicitation in within small companies andlarge organizations.

Surprisingly, the organization type plays a very smallrole in the software engineering literature and therefore startups, a specialtype of Research & Development environment, did not receive the attentionthey deserve in researches. People think that the models and techniques thatare being used in the traditional software engineering can be used for thestartup too but the results have shown that the way a startup work is verydifferent from the tradition software companies and hence a new way or methodbut be introduced for the running of startup companies. Results have shown thatthe main reason for the failure of startup companies is the elicitation ofrequirements as well as properly documenting those requirements.

The main problem is that there is no exactmethod for Elicitation of requirements for new IT startups. So many IT startupsfail due to lack of requirements gathering from right stakeholders of theproduct, Requirements from the stakeholders and using those requirements toimplement the product and as well as documenting those requirements for futureversions of the product.Anothermain reason why there are issues are because many IT startups work in “stealthmode” because they wont to share own innovative idea to anyone and they have nouser feedback on innovative idea that is very beneficial for any new innovativeidea holders to launch idea in market at right time. These two are the mainreason for the research on this are. 1.

2 DOMAIN AND SOLUTIONS  Requirementengineering is the main domain of the any IT startups to gather rightrequirements related to our innovative and publically beneficial idea.Requirement engineering tells us how to gather requirements from rightstakeholders and define main stakeholders of the product.Followthe Iterative Model with Prototyping throughoutthe IT Startups will be a great solution for this problem.Secondthing that will add to our method is to try not work in “Stealth mode”. Share your ideas with other for their feedback butbe aware of Market Monkeys.

Thirdthing is to start Documentation from the beginning of the startup. Documentationplays a very important role for any kind of business especially for IT startupsbecause of their changing versions and customer needs and as well as newtechnology Keep on improving until the whole product is developed.               1.3  PAPER STRUCTUREWeprovide an overview of related work in section 2; section 3 covers the proposedmethodology for the problems and results shows in section 4 and conclusion ofthe study is in section 5. Future research directions and references are insection 6 and section 7 respectively.                 2.     RELATEDWORKThere isa lot of work done in the area of requirements engineering but in the area ofrequirements engineering for startups the work done is not of muchsignificance. Therefore, the requirements engineering in startups is a specialtype of Research and Development, but somehow it is not gaining as muchattention it should have.

Startups are thought to be as small companies butstartups are very different from the traditional companies and hence require adifferent way and model for the elicitation of requirements. Thereare some practices that are happening right now which are being used instartups for requirement elicitation. There are two existing solutions Traditional requirement Elicitationtechniques and the other one is leansoftware developments. Lean Software development may also be said as AgileDevelopment which is related to eliminate waste, amplify learning, decide aslate as possible, and deliver as fast as possible, empower the team, buildingintegrity in, and see the Whole. 2.1 COMPARISON There isa great difference between the traditional way of elicitation of requirementsand the agile development. The given table below describes the differenceproperly, efficiently and neatly.

TABLE 1TRADITIONAL VERSUS AGILE DEVELOPMENT The difference between both the methods areeasily visible in this table, they are different in many aspects like itsplanning, Primary focus of development, Documentation, Customer Involvement andmany more.2.2  LIMITATIONS AND GAPSThe Traditional way will not work for thestartup companies because the working of startup is very different from theworking of a traditional software house as well as the requirements are alsovery different from a traditional software company.While on the other hand there is the agiledevelopment method which is near to customers and as well as adaptive to changebut is very costly, time consuming and is evolving with time. In the case ofagile development the documentation is also less or may be no documentation                3.     PROPOSEDMETHODTheMethod that is being suggested for the elicitation of requirements in ITStartups Are as follows:1.      Followthe ITERATIVE MODEL WITH PROTOTYPING throughoutthe IT Startups.

  2.      Try notwork in Stealth mode. Share youridea but be aware of Market Monkeys because some senior market people stealyour idea and showing the help of the IT startups as a mentor. 3.

      Start Documentation from the beginning of thestartup. Keep on improving the documentation until the whole product isdeveloped.   Requirementengineering is the main domain of the any IT startups to gather rightrequirements related to our innovative, publically beneficial and businessgrowing idea. Requirement engineering tells us how to gather requirements fromright stakeholders and define main stakeholders of the product and makingdocumentation of the requirements elicitation process.

4.    RESULTS/ CASE STUDY/ ANALYSISAfterstudying many cases we found out that our method will be a great model for theIT startup companies. The following give below table shows us different wellknown cases of IT startups and hence why the startup failed.TABLE 2STARTUPS AND THEIR REASONS TO FAILURETheAbove table shows different startups their date and their reason to failure.

The failure of all these startup is related to the failure in the field ofrequirements elicitation. This table indicates us that the main reason behindthese failures is either because of no documentation, wrong requirements, nocustomer satisfaction and so on.Agiledevelopment is not providing the any method of requirement elicitation ascompared to our proposed solutions. Iterative model provides the proper way ofrequirement gathering from taking survey of our product target market. Anditerate this process until the desired product is developed and hence using itwith prototyping make it more near to the customer hence the startup gets itsfeedback and customer satisfaction. A properdocumentation of requirements and the made system will also come out from theproposed model which will help us not in just the testing phase but also forfuture references if new versions of the systems has to build. 5.      CONCLUSION / DISCUSSIONWe concludethat Iterative Method with prototyping is good as compared to lean agiledevelopment.

Agile development is not giving any method of requirementelicitation. Iterative methodology gives the proper way to requirementsgathering and defines our best stakeholders of the desired product and iteratesthe requirements elicitation process until the end of desired product. With ourmethod we will also be able to the documentation of the requirements and thesystem working hence the system will also be ready for future versions.Themethod used will also use the user feedback hence will guarantee success 6.      FUTURE RESEARCH DIRECTIONSThere isnot much Work done in the area of the Requirements Engineering for theStartups. There are a few researchers who are actually working for the problemsof requirements gathering, elicitation and analysis. But yet no significantwork has been done.7.

      REFERENCESØ  Trustexamination in the startups.Examining Trust within the Team in IT Startup Companiesby Oechslein, O. ; Munich Sch. of Management. Ø  Causes ofstartup product failuresWhy software product startups fail and what to do about it.by Crowne, M Ø  Success factorsin Startups IndustryA Success Factor of a Digital Material Startup Companyby Hayashida, H.

 ; Osaka Univ., Suita Ø  The innovativestartup ideas from academia to Industry The View from Silicon Valley: FromAcademe to Innovative Startups by Harris, J.; Stanford Univ., Stanford.Ø Agile andTraditional Requirements Engineering: A Survey Heba Elshandidy, Sherif MazenØ  iThink : Agame-based approach towards improving collaboration and participation inrequirement elicitation Jo˜ao Fernandesa,?, Diogo Duarteb, Claudia Ribeiroa, CarlaFarinhab, Jo˜ao Madeiras Pereiraa, Miguel Mira da SilvabØ  Requirements Engineering and the Creative Process in the Video Game Industry Ø  DavidCallele, Eric Neufeld, Kevin SchneiderØ  RequirementsElicitation in Startup CompaniesØ  Jan-MartenAhrendØ  http://agile.csc.ncsu.edu/SEMaterials/AgileRE.pdfØ  http://autopsy.io/  

x

Hi!
I'm Mary!

Would you like to get a custom essay? How about receiving a customized one?

Check it out