Chapter 3 Research Methodology 3.1 Introduction - DSpace@UM

More documents

Recommendations

Info

and supervisor can see their requirements in the prototyped systems, and thereforecan validate the requirements reflected in the prototype. By the iterative nature ofthe prototype’s evolution, a software developer has the opportunity to accept, orchange a requirement.2. Find out unknown requirements.When a researcher starts a project, he /she does not have a clear picture of whatshould be developed. Based on the objectives, the researcher may find additionalfunctions that the prototype must provide. “The key is that prototypes are anexcellent means of eliciting correct, consistent, and complete specifications ofrequirements” (Davis, 1992).3. Requirements Analysis and Design by viewRequirements analysis and design for online systems have two main challenges fora software. First, it is generally difficult to provide a detailed specification for theinterface and the visual components of a web site suck as graphics, layout, etc.Second, there exist functional requirements which customers may take for granted,therefore EP can help a developer to get rid of these challenges.58
4. Flexible to change research assumptions.Evolutionary prototyping is beneficial to the researcher to shift (update) hisassumptions and requirements. Some of these assumptions will be discussed withthe supervisor and some written in documentation. Evolutionary developmentmodels allow these effects and changes.5. Provides a method to communicate about Systems.Evolutionary prototyping is facilitating communication between the researcher andhis supervisor. So when researcher has a new idea, the prototype helps him toexplain what has been done and if there are any suggestion from supervisor he caneasily incorporate the suggestion into the prototype. There is less argument aboutwhat a prototype does, and reduce the misinterpretations from vagueness andequivocalness in natural language specifications.6. Reduce development schedule and minimize costPrototyping minimize development costs and, development schedules, if there isany change in project, the researcher can do that in early phase and this willrequire less time and effort. If there is a wrong in SDLC, the researcher willchange in documentation, design and models. "Many stakeholders are also lessintimidated by the presentation of a prototype than by the paper avalanche ofspecifications, designs, screen layouts, and diagrams found too often in methodssuch as the Waterfall model" (Antón & Carter & Earp & Williams, 2001).59
Page 1 and 2: Chapter 3Research Methodology3.1 In
Page 3 and 4: 6. Is the system able to find which
Page 5 and 6: physical meetings conducted is so d
Page 7: Disadvantages• Very hard to set d
Page 11 and 12: Requirementsanalysis/ Gathering/Int
Page 13 and 14: 3.5.3.b System Design:Initial syste
Page 15 and 16: Figure 3.5. Programming and debuggi
Page 17 and 18: Add a newRequirementsDocumentNot sa
Page 19: Figure 3. 6: User Evaluation Model

Chapter 3 Research Methodology 3.1 Introduction - DSpace@UM

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?