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

Nature and types of softare packages, NATURE AND TYPES OF SOFTARE PACKAGES:...

NATURE AND TYPES OF SOFTARE PACKAGES: Software packages are commercially supplied products which typically provide solutions to a particular range of software development or a

Define the prototyping model, Define the Prototyping Model In this mod...

Define the Prototyping Model In this model, a working model of actual software is developed originally. Prototype is just like a sample software having low reliability and les

What is the work product of software design process, What is the work produ...

What is the work product of software design process and who does this? A design model that encompasses architectural, interface, component level and their representations is th

What is top-down strategy, What is Top-Down Strategy? Ans) Top down inte...

What is Top-Down Strategy? Ans) Top down integration is basically an approach where modules are produced and tested starting at the top level of the programming hierarchy and re

Determine the sanity testing, Determine the Sanity testing - Sanity te...

Determine the Sanity testing - Sanity testing is used to ensure that conflicting or multiple functions or variables don't exist in system. - It verifies that components of

Process models, Ask question what is abstraction ?#Minimum 100 words accept...

Ask question what is abstraction ?#Minimum 100 words accepted#

What is bottom-up approach, What is bottom-up approach? System develop...

What is bottom-up approach? System developed starting from detailed modules. Testing begins from the detailed modules and proceeds up to the higher levels of hierarchy.

Describe component testing, Describe component testing. - Component tes...

Describe component testing. - Component testing is also called as module, unit or program testing. - It looks for defects in software and verifies its functioning. - It c

Describe bottom-up and top-down approaches, How do you develop a test plan ...

How do you develop a test plan and schedule? Describe bottom-up and top-down approaches. A test plan is contract among the testers and the project team explaining the role of t

Data dictionary, describe process

describe process

Write Your Message!

Name

Email id

Message

Verfication Code

User Account

All Pages