Abstract
Prototyping has been recognized as being a powerful and indeed essential tool in many branches of engineering. Although software prototyping is often considered too expensive, correcting ambiguities and misunderstandings at the requirements specification stage is significantly cheaper than correcting a system after it has gone into production. This paper describes how rapid prototyping impacts the Requirements Analysis and Specification phase of the software life cycle. This is illustrated by describing the experience gained from a prototype used to assist in the requirements specification of a system to manage and control an integrated circuit fabrication facility. The cost of the prototype was less than 10 percent of the total software development cost.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
