Prototype Model Lecture-4.

Slides:



Advertisements
Similar presentations
Information technology solutions development Fundamentals of Information Technology Session 3.
Advertisements

1 Life Cycle Models (Lecture 2) Prof. R. Mall Dept. of CSE, IIT, Kharagpur.
Lecture # 2 : Process Models
Software Process Models
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 المحاضرة الثانية.
Software Project Management
Chapter 4 Design Approaches and Methods
CS 5150 Software Engineering
Software project management (intro ) Project approaches.
Chapter 8 Prototyping and Rapid Application Development
Software Engineering Incorporating Interface Design Into Software Engineering.
Software Life Cycle Model
Rapid Prototyping Model
1 CMPT 275 Software Engineering Software life cycle.
 Software Models.  A software life-cycle model is a descriptive and diagrammatic representation of the software life-cycle. This includes a series of.
Mohammad Amin Kuhail M.Sc. (York, UK) University of Palestine Faculty of Engineering and Urban planning Software Engineering department Requirements Engineering.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
SOFTWARE PROTOTYPING Anil Kumar.Arikepudi.
CS 5150 Software Engineering Lecture 3 Software Processes 2.
Prof. Aiken CS 169 Lecture 21 Software Process CS169 Lecture 2.
Introduction to Software Development (Software Engineering - I)
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology.
Software Project Management
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Topic:- At the end we will be able to explain:- Why it is called Meta Model ?? Spiral Model Its Advantages & Disadvantages… Phases of Spiral Model...
Systems Development Life Cycle
1 Chapter 2 SW Process Models. 2 Objectives  Understand various process models  Understand the pros and cons of each model  Evaluate the applicability.
Building Information Systems
Prototype 3 Prototype 2 Prototype What is prototyping? Types of prototyping: – Evolutionary – Throw-away Good and Bad points to prototyping.
Rekayasa Perangkat Lunak Part-6
Methodologies and Algorithms
IL Marking Get out your CPU / Memory answers Swap with someone else
Software Engineering Management
User-centred system design process
Software Life Cycle “What happens in the ‘life’ of software”
INTRODUCTION TO SOFTWARE DEVELOPMENT
PROJECT LIFE CYCLE AND EFFORT ESTIMATION
CS 5150 Software Engineering
SOFTWARE LIFE-CYCLES Beyond the Waterfall.
Methodologies By Akinola Soyinka.
Software Processes (a)
Systems Analysis and Design
Chapter :Software Process Model
Software development life cycle models
Software Process Models
Models of Software Development Life Cycle (SDLC)
Chapter 2 SW Process Models
Software Process Models
Prototyping.
Object oriented system development life cycle
Life Cycle Models PPT By :Dr. R. Mall.
CHAPTER 2 Testing Throughout the Software Life Cycle
The Prototyping Paradigm
Software Prototyping Animating and demonstrating system requirements.
Classical Waterfall Model
Requirements and the Software Lifecycle
Life Cycle Models (Lecture 2)
Software Development Process
Computer Science Life Cycle Models.
Software life cycle models
Incremental Waterfall
CS310 Software Engineering Lecturer Dr.Doaa Sami
Software Engineering Lecture 17.
Rapid software development
Chapter 8 Prototyping and Rapid Application Development
Software Development Process
Information system analysis and design
Presentation transcript:

Prototype Model Lecture-4

4.1 What is Prototyping? Prototyping is the process of quickly putting together a working model (a prototype) in order to test various aspects of a design, illustrate ideas or features and gather early user feedback. Prototyping is often treated as an integral part of the system design process, where it is believed to reduce project risk and cost. The Prototyping model suggests that before carrying out development of actual software, a working prototype of the system is built.

4.2 Prototyping Model Often one or more prototypes are made in a process of incremental development where each prototype is influenced by the performance of previous designs, in this way problems or deficiencies in design can be corrected. When the prototype is sufficiently refined and meets the functionality, robustness, manufacturability and other design goals, the product is ready for production.

4.3 What is a Prototype? A prototype is a toy implementation of a system having: limited functional capabilities, low reliability, inefficient performance. An important purpose for the use of prototype is: To illustrate the input data formats, messages, reports, and The interactive dialog to the customer

4.4 Why Prototyping? A developed prototype can help engineers: To critically examine technical issues associated with product development: response time of a hardware controller, efficiency of a sorting algorithm, etc. The next reason for developing a prototype is: it is impossible to ``get it right'' the first time, we must plan to throw away the first product if we want to develop a good product.

4.5 How prototyping model is built? Start with approximate requirements. Carry out a quick design. Built a prototype: The developed prototype is submitted to the customer for his evaluation: Based on the user feedback, requirements are refined. This cycle continues until the user approves the prototype. The actual system is developed using the iterative waterfall approach.

4.6 Prototyping Process Req. gathering Quick design Iterative waterfall model Refine Req. Built prototype Evaluate prototype Accepted by the customer Design Implementation Test Maintenance

4.7 Advantages of prototyping Reduced time and costs: changes cost exponentially more to implement as they are detected later in development, the early determination of what the user really wants can result in faster and less expensive software Improved and increased user involvement Prototyping requires user involvement and allows them to see and interact with a prototype allowing them to provide better and more complete feedback and specifications

4.8 Disadvantages of prototyping Insufficient analysis Excessive development time of the prototype Expense of implementing prototyping User confusion of prototype and finished system

4.9 When to use Prototype Model? The prototyping model is suitable for: Projects for which either the user requirements or the underlying technical aspects are not well understood. Especially popular for development of the user- interface part of the project.