Explain throw-away prototyping, Software Engineering

Assignment Help:

Throw-away prototyping

Objective:

The principal objective of this model is to validate or to derive the system requirements.
It is developed to reduce requirement risks.

Advantages

Requirement risks are very less.

Problems

It can be undocumented.
Changes made during the software development proceed may degrade the system

structure.
• Sometimes organizational quality standard may not be strictly applied.

Related Discussions:- Explain throw-away prototyping

Determine the system integration the life cycle process, Determine the Syst...

Determine the System Integration the life cycle process. It is the process of putting hardware, software and user together to prepare a system. System Installation I

Define verification, Define Verification ?

Define Verification ?

Salient features of ISO 9001 certification, Q. Salient features of ISO 9001...

Q. Salient features of ISO 9001 certification? Ans) Salient(noticeable) features of ISO 9001 certification are :- All documents concerned with the development of a softw

Define the quality control, Quality Control Quality control is a method...

Quality Control Quality control is a method in which the product's quality is compared with standards and corrective actions taken if needed. Quality control activities focus o

What are the objectives of analysis modelling, What are the objectives of A...

What are the objectives of Analysis modelling? i. To explain what the customer requires. ii. To establish a basis for the creation of software design. iii. To devise a se

What is internal interrupt, Internal Interrupt Cause because of illegal...

Internal Interrupt Cause because of illegal or erroneous use of an instruction or data. Internal interrupts are also known as traps. Internal interrupts are initiated because o

What are the different rapid prototyping techniques, What are the different...

What are the different Rapid prototyping techniques? i. Dynamic high level language development. ii. Database programming. iii. Component and application assembly.

Explain storage testing, This is a explanation of whether or not certain pr...

This is a explanation of whether or not certain processing conditions use many storage [memory] than estimated.

Software testing, Discuss the limitations of software testing. How do we sa...

Discuss the limitations of software testing. How do we say that complete testing is impossible?.

Explain bottom up design, Bottom up design: This design leads to a style o...

Bottom up design: This design leads to a style of design where we decide how to join these modules to give larger ones; to combine those to give even larger ones, and so on, till

Write Your Message!

Name

Email id

Message

Verfication Code

User Account

All Pages