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

Define the computer based system, Define the computer based system. The...

Define the computer based system. The computer based system can be explained as "a set or an arrangement of elements that are organized to accomplish some predefined goal by pr

Describe software measure, Describe software measure ?

Describe software measure ?

Explain the iterative model, Explain the Iterative Model Every release ...

Explain the Iterative Model Every release of Iterative Model is developed in a specific, fixed time period known as iteration. Each iteration focuses on a certain set of requir

Explain lines of code - software metrics, Q. Explain Lines of code - Softwa...

Q. Explain Lines of code - Software Metrics? Lines of code (LOC) is a software metric used to measure the size of a software program by counting the number of lines in the te

Determine the problems of software maintenance, Determine the problems of s...

Determine the problems of software maintenance Software maintenance has the below problems: i) It is very cumbersome to analyse and understand code written by somebody.

Applicability with reference to software reliability models, Q. Applicabili...

Q. Applicability with reference to software reliability models? Applicability : It is another important characteristic of a model. The model must be judged by its degree of a

Explain the software life cycle model, Q. Explain the software life cycle m...

Q. Explain the software life cycle model that incorporates risk factor. Ans. The problem with traditional software process models is that they don't deal sufficiently with th

Coupling, explain coupling

explain coupling

Software requirements specification, A Software Requirements Specification...

A Software Requirements Specification (SRS) is a complete description of the behavior of the system to be developed. It includes a set of use cases, describing the interactions

Explain the cardinality and optionally, Cardinality & Optionally Card...

Cardinality & Optionally Cardinality represents the relationship between two entities. Consider one to many relationship between two entities -student andclass. Here cardinal

Write Your Message!

Name

Email id

Message

Verfication Code

User Account

All Pages