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

State the coding standards, State the Coding standards Coding standar...

State the Coding standards Coding standards normally give the guidelines about following: i) Name of the module ii) External and Internal documentation of source code

Type of organizational behaviour, what is type of organizational behaviour ...

what is type of organizational behaviour like classical,neo and morden?

Data Dictionary, The University needs to develop an online student registra...

The University needs to develop an online student registration system for new CAO entrants. This system will allow new students to enroll in their university course. Each student i

Describe software measure, Describe software measure ?

Describe software measure ?

What is fault-based testing, 1. Testing that employs a test data selection ...

1. Testing that employs a test data selection method designed to obtain test data capable of demonstrating the absence of a set of pre-specified faults, typically, frequently happe

What is a user friendly document, What is a user friendly document? Ans)...

What is a user friendly document? Ans) A document is user friendly, when it is designed and written with simple of use, as single of the primary objectives of its design.

Resource usage with reference to software reliability models, Q. Resource u...

Q. Resource usage with reference to software reliability models? Resource usage: It is linearly proportional to implementation time t and mean failures experienced μ. Let Xr

Explain the test case, Test Case A test case is a unit level document d...

Test Case A test case is a unit level document describing the inputs, steps of implementation and the expected result of each test condition for each requirement from the BRD.

Case study - conference management system, This case study looks at the req...

This case study looks at the requirements for an information system to manage the organisation of an international academic conference. An academic conference consists of presenta

Requirements analysis and specification, What are functional and non-functi...

What are functional and non-functional requirements?

Write Your Message!

Name

Email id

Message

Verfication Code

User Account

All Pages