Latest Activity In Study Groups

Join Your Study Groups

VU Past Papers, MCQs and More

We non-commercial site working hard since 2009 to facilitate learning Read More. We can't keep up without your support. Donate.

The topic is as under
A part of Software Engineering community claims that a “Prototype” is part of requirements elicitation as it helps to refine the requirements further. On the other hand, in second stance, some people claim it to be part of the design process as it provides a base (e.g. interface design etc.) for developing an operational product.
What is your stance; please provide your opinion with logical reasons?

Views: 628

Replies to This Discussion

Please Discuss here about this GDB.Thanks

prototype is more related to requirement elicitation then design. design comes much before then making a prototype
bhai is ko more deeply explain ker du thanks alot
vu **** .com

In requirements engineering, requirements elicitation is the practice of obtaining the requirements of a system from users, customers and other stakeholders. [1] The practice is also sometimes referred to as requirements gathering.

The term elicitation is used in books and research to raise the fact that good requirements can not just be collected from the customer, as would be indicated by the name requirements gathering. Requirements elicitation is non-trivial because you can never be sure you get all requirements from the user and customer by just asking them what the system should do. Requirements elicitation practices include interviews, questionnaires, user observation, workshops, brain storming, use cases, role playing and prototyping.

Before requirements can be analyzed, modeled, or specified they must be gathered through an elicitation process. Requirements elicitation is a part of the requirements engineering process, usually followed by analysis and specification of the requirements.

A prototype is often used as part of the product design process to allow engineers and designers the ability to explore design alternatives, test theories and confirm performance prior to starting production of a new product. Engineers use their experience to tailor the prototype according to the specific unknowns still present in the intended design. For example, some prototypes are used to confirm and verify consumer interest in a proposed design whereas other prototypes will attempt to verify the performance or suitability of a specific design approach.

In general, an iterative series of prototypes will be designed, constructed and tested as the final design emerges and is prepared for production. With rare exceptions, multiple iterations of prototypes are used to progressively refine the design. A common strategy is to design, test, evaluate and then modify the design based on analysis of the prototype.

thanks fajar     
now that is cool
vu ****.com
I will go with the first choice because.....
• Prototypes may be easily changed or even discarded.
• Prototyping may improve communication between and among developers and customers
• Users may be more satisfied with systems developed using prototyping.
• A prototype may provide the proof of concept necessary to attract funding.
• Early visibility of the prototype may help management assess progress.
• Prototypes may demonstrate progress at an early stage of development.


© 2021   Created by + M.Tariq Malik.   Powered by

Promote Us  |  Report an Issue  |  Privacy Policy  |  Terms of Service