 A life cycle of product development is commonly referred as the “model”  A simple model contains five phases  Requirement analysis  Design  Development.

Slides:



Advertisements
Similar presentations
Prescriptive Process models
Advertisements

Conquering Complex and Changing Systems Object-Oriented Software Engineering Chapter 12, Software Life Cycle.
Lecture # 2 : Process Models
Software Development Life Cycle
MIS 2000 Class 20 System Development Process Updated 2014.
CS487 Software Engineering Omar Aldawud
CSE 470 : Software Engineering The Software Process.
CHAPTER 1 SOFTWARE DEVELOPMENT. 2 Goals of software development Aspects of software quality Development life cycle models Basic concepts of algorithm.
Waterfall Model H.M.Shahzad MS(CS) from COMSATS Institute of Information Technology, Lahore.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Alternative Software Life Cycle Models By Edward R. Corner vol. 2, chapter 8, pp Presented by: Gleyner Garden EEL6883 Software Engineering II.
Alternate Software Development Methodologies
Gu & Maher University of Sydney, October 2004 DECO2005 Monitoring Team Process.
CS 5150 Software Engineering
Developing safety critical systems
1 CS 501 Spring 2003 CS 501: Software Engineering Lecture 2 Software Processes.
CS 501: Software Engineering
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Problem with Software Requirements are complex The client does not know the functional requirements in advance Requirements may be changing Technology.
Introduction to Software Design Chapter 1. Chapter 1: Introduction to Software Design2 Chapter Objectives To become familiar with the software challenge.
Software Life Cycle Model
Carnegie Mellon University © Robert T. Monroe Management Information Systems Software Development Lifecycles (SDLC’s) Management.
CIS 321—IS Analysis & Design
Extreme Programming Software Development Written by Sanjay Kumar.
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.
Understand Application Lifecycle Management
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
CS CS 5150 Software Engineering Lecture 3 Software Processes 2.
Software Engineering Management Lecture 1 The Software Process.
Testing Workflow In the Unified Process and Agile/Scrum processes.
The Systems Development Life Cycle
Software Engineering MCS-2 Lecture # 6
Systems Analysis and Design in a Changing World, Fourth Edition
Software Engineering II Lecture 3 Fakhar Lodhi. Software Life-Cycle Steps Life-cycle model (formerly, process model) –Requirements phase –Specification.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 1: Introduction to Systems Analysis and Design Alan.
1 CS 501 Spring 2004 CS 501: Software Engineering Lecture 2 Software Processes.
Introduction to Software Development (Software Engineering - I)
Software Testing Process By: M. Muzaffar Hameed.
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 43 Introduction to Software Engineering.
Software Project Management Iterative Model & Spiral Model.
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
Modelling the Process and Life Cycle. The Meaning of Process A process: a series of steps involving activities, constrains, and resources that produce.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Chapter 1: Introduction Omar Meqdadi SE 3860 Lecture 1 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Waterfall Model Software project Management. Waterfall Model  The Waterfall Model was first Process Model to be introduced. It is also referred to as.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Lectures 2 & 3: Software Process Models Neelam Gupta.
WATERFALL METHOD Robbie Campbell WHAT IS IT  Considered the classic approach to the SDLC.  It is a linear method with goals for each development phase.
V-Shaped Software Development Life Cycle Model. Introduction: Variation of water fall model. Same sequence structure as water fall model. Strong emphasis.
Introduction to Systems Analysis and Design
Unit 6 Application Design KLB Assignment.
Methodologies and Algorithms
Software Engineering Management
Software Life Cycle “What happens in the ‘life’ of software”
Chapter :Software Process Model
Models of Software Development Life Cycle (SDLC)
Software Life Cycle Models
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
Introduction to Software Engineering
Software Engineering Lecture 18.
Software life cycle models
Systems Development Life Cycle
Lesson 1 Understanding Software Quality Assurance
Baisc Of Software Testing
CS310 Software Engineering Lecturer Dr.Doaa Sami
UNIT 5 EMBEDDED SYSTEM DEVELOPMENT
UNIT 5 EMBEDDED SYSTEM DEVELOPMENT
Software Engineering Lecture 17.
Presentation transcript:

 A life cycle of product development is commonly referred as the “model”  A simple model contains five phases  Requirement analysis  Design  Development and test  Deployment and maintenance  The no of phases involved in EDLC model depends on the complexity of the product Classic Embedded product development life cycle model

NEED:  Any embedded product may evolves as an output of a need.  Need may come from an individual/from public/from company(generally speaking from an end user/client)  New/custom product development  Product re-engineering  Product maintenance CONCEPTUALIZATION:

ANALYSIS: Analyze and document functional and non-functional requirements Interface definition and documentation Define test plan and procedure Requirement specification document Document review Rework on requirements and documents

: DESIGN : Deals with the entire design of the product taking the requirements into consideration and focuses on how the functionalities can be delivered. Only i/p & o/p are defined here Product will look like a black box Sent for approval from client Generates detailed architecture Detailed architecture also needs approval

DEVELOPMENT AND TESTING:  Development phase transforms the design into realizable product  Design is transformed into hardware and firmware  Look and feel of the device is very important Testing phase can be divided into  Unit testing – independent testing of hardware and firmware  Integration testing – testing after integrating hardware and firmware  System testing – testing of whole system on functionality and non-functionality basis  User acceptance testing – testing of the product against the criteria mentioned by the end-user/client  Test reports

DEPLOYMENT:  A process of launching fully functional model into the marketSUPPORT:  Deals with the operation and maintenance of the product  Support should be provide to the end user/client to fix the bugs of the productUPGRADES:  Releasing of new version for the product which is already exists in the market  Releasing of major bug fixes.RETIREMENT/DISPOSAL:  Everything changes, the technology you feel as the most advanced and best today may not be the same tomorrow  Due to this the product cannot sustain in the market for long  It has to be disposed on right time before it causes the loss.

EDLC APPROACHES: Linear/Waterfall Model: Conceptualization Need Analysis Design Development & testing Deployment Support Upgrades Retirement  Each phase of EDLC is executed in sequence  Flow is unidirectional  Output of one phase serving as input of other

Iterative/Incremental/Fountain EDLC Model:  Cascaded series of linear models  Do some analysis, follow some design, then some implementation in cycles  Repeat the cycles until the requirements are met

Prototyping/evolutionary model:  Similar to iterative model, product is developed in multiple cycles  The only difference is the model produces more refined prototype of the product at each cycle instead of just adding the functionality at each cycle like in iterative model.

Spiral model:  Spiral model is best suited for the development of complex embedded products and situations where the requirements are changing from customer side.  Risk evaluation in each stage helps in reducing risk

Conclusion In order to make best profit out of product what you do, development life cycle is very important. To build a reliable product, of best quality, functionality and to release your product in right time. EDLC will make things easy for sure!!.

REFERENCES:  Introduction to Embedded System by Shibu K.V  development/product-life-cycle/ development/product-life-cycle/  life-cycle-of.html