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

Software availability, Software Availability: In the present day conte...

Software Availability: In the present day context, software suppliers have realised the potential demand and also the special requirements of library and information professio

TRANSFORM FLOW, WHAT IS TRANSFORM FLOW

WHAT IS TRANSFORM FLOW

Explain cost drivers and eaf of intermediate cocomo model, Q. Explain the c...

Q. Explain the cost drivers and EAF of the intermediate COCOMO model? Ans. There are 15 different attributes described as cost drivers' attributes that determine the multiply

Phosphate conditiong, what is meant by phosphate conditiong

what is meant by phosphate conditiong

What are the causes behind to perform white box testing, What are the cause...

What are the causes behind to perform white box testing? There are three main reasons behind performing the white box testing. 1. Programmers may have some incorrect assumpt

Classify the techniques into dynamic or static, Classify the below techniqu...

Classify the below techniques into dynamic or static. i. Data Flow Analysis. ii. Use Case Testing. iii. Equivalence Partitioning. iv. Exploratory Testing. v. Inspec

Explain cocomo model with its applicable equations, Q. Explain COCOMO model...

Q. Explain COCOMO model with its applicable equations. Describe various attributes of cost drivers used in COCOMO model. Ans. COCOMO denotes for constructive cost model -

What are decision tables, What are decision tables? Why do we use them? ...

What are decision tables? Why do we use them? - Decision tables are specification-based techniques that are more focused on business rules or business logic. - A decision ta

Difference between module coupling and module collection, Q. What is the di...

Q. What is the difference between module coupling and module collection? List different types of coupling and cohesion. Ans : Cohesion is the property of a single module as we

Illustrate iterative waterfall model, Iterative waterfall model The ite...

Iterative waterfall model The iterative waterfall model is as shown in the following figure. Requirement gathering phase in which all needs are identified. The design

Write Your Message!

Name

Email id

Message

Verfication Code

User Account

All Pages