April3 - SoftwarePrototyping q q...

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 1 Software Prototyping Rapid software development to validate requirements Objectives To describe the use of prototypes in different types of development project To discuss evolutionary and throw-away prototyping To introduce three rapid prototyping techniques - high-level language development, database programming and component reuse To explain the need for user interface prototyping
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 2 System prototyping Prototyping is the rapid development of a system The principal use is to help customers and developers understand the requirements for the system Requirements elicitation – Users can experiment with a prototype to see how the system supports their work Requirements validation – The prototype can reveal errors and omissions in the requirements Prototyping can be considered as a risk reduction activity
Background image of page 2
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 3 Prototyping benefits Misunderstandings between software users and developers are exposed Missing services may be detected and confusing services may be identified A working system is available early in the process The prototype may serve as a basis for deriving a system specification The system can support user training and system testing
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 4 Prototyping in the software process Evolutionary prototyping An initial prototype is produced and refined through a number of stages to the final system Throw-away prototyping A prototype is produced to help discover requirements problems and then discarded The system is then developed using some other development process
Background image of page 4
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 5 Prototyping objectives The objective of evolutionary prototyping is to deliver a working system to end-users The development starts with those requirements which are best understood. The objective of throw-away prototyping is to validate or derive the system requirements The prototyping process starts with those requirements which are poorly understood
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 6 Approaches to prototyping Evolutionary prototyping Throw-away Prototyping Delivered system Executable Prototype + System Specification Outline Requirements
Background image of page 6
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 7 Evolutionary prototyping Must be used for systems where the specification cannot be developed in advance E.g., AI systems and user interface systems Based on techniques which allow rapid system iterations Verification is impossible as there is no specification Validation means demonstrating the adequacy of the system
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 8
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 28

April3 - SoftwarePrototyping q q...

This preview shows document pages 1 - 8. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online