Lect 3 by akiwelekar

VIEWS: 52 PAGES: 15

									Software Engineering: Lecture Number 3
Process Model Arvind W. Kiwelekar Assistant Professor Computer Engineering Department, Dr. B. A. Tech. University Lonere-402 103 akiwelekar@gmail.com

January 16, 2009

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department,Number A. Tech. University Lonere-4022009 akiwelekar@gm Software Engineering: Lecture Dr. B. 3 January 16, 103 1 / 15

Life Cycle Models
The Waterfall Model Incremental Model
The incremental model The RAD model

Evolutionary Process Model
Prototyping Spiral Model Concurrent Development Model

Specialized Model
Component-based model The formal methods model Aspect-oriented software model

The Unified Model

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department,Number A. Tech. University Lonere-4022009 akiwelekar@gm Software Engineering: Lecture Dr. B. 3 January 16, 103 2 / 15

Waterfall Model
Communication
Project Initiation Requirements Gathering

Planning
Estimating, Scheduling Tracking

Modeling
Analysis Design

Construction
Coding Testing

Deployment
Delivery Feedback, Support

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department,Number A. Tech. University Lonere-4022009 akiwelekar@gm Software Engineering: Lecture Dr. B. 3 January 16, 103 3 / 15

Waterfall Model

Simple model to follow. Waterfall model is used when requirements are well defined. Inefficient allocation of work to software developers. Rarely requirements are clearly defined. Applicable to scenarios such as porting an existing application to new platform.

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department,Number A. Tech. University Lonere-4022009 akiwelekar@gm Software Engineering: Lecture Dr. B. 3 January 16, 103 4 / 15

Incremental Model
Function/ Feature

Increment n

COM

PLA

MOD

CON

DEP

Increment 2

COM

PLA

MOD

CON

DEP

Increment 1
COM PLA MOD CON DEP

Time

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department,Number A. Tech. University Lonere-4022009 akiwelekar@gm Software Engineering: Lecture Dr. B. 3 January 16, 103 5 / 15

Incremental Model

The model is iterative in nature. It is useful when project staffing is insufficient to deliver a complete product within a stipulated a deadline . Increments are planned to manage technical risk such as underdevelopment hardware.

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department,Number A. Tech. University Lonere-4022009 akiwelekar@gm Software Engineering: Lecture Dr. B. 3 January 16, 103 6 / 15

Rapid Application Development(RAD) Model
Function/ Feature

Team n
MOD CON

Team 2
COM PLA MOD CON DEP

Team 1 Increment 1
MOD CON

Time

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department,Number A. Tech. University Lonere-4022009 akiwelekar@gm Software Engineering: Lecture Dr. B. 3 January 16, 103 7 / 15

Rapid Application Development
Develops application very fast and in a scalable manner. Business modeling, data modeling and process modeling are the main actions in modeling activity. Component reuse, automatic testing and code generation are the main actions in construction. Increments are planned to manage technical risk such as underdevelopment hardware. Drawbacks
1 2 3 4

RAD requires sufficient development teams. Customers and SE both need to agree for rapid development. System need to be properly modularized. Performance of the developed problem is a problem.

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department,Number A. Tech. University Lonere-4022009 akiwelekar@gm Software Engineering: Lecture Dr. B. 3 January 16, 103 8 / 15

Evolutionary Models: Prototyping

Communication

Quick Plan

Deployment Delivery Feedback

Modeling and Quick Design

Construction of Prototype

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department,Number A. Tech. University Lonere-4022009 akiwelekar@gm Software Engineering: Lecture Dr. B. 3 January 16, 103 9 / 15

Prototyping model
1

The objective of the pattern is to build a model that can be assessed iteratively by stakeholders to validate requirements. Initial Context (i) Stakeholders have been identified. (ii) A communication between stakeholders and the software team has been established. (iii) The problem to be solved has been identified. (iv) Initial understanding of project scope, basic business requirements and project constraints has been developed. Problem Requirements are hazy Solution To build a prototype. Resulting Context A Prototype is developed and requirements are validated. A prototype may be evolved to a final product or prototype may be discarded.

2

3 4 5

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department,Number A. Tech. University Lonere-402 103 akiwelekar@gm Software Engineering: Lecture Dr. B. 3 January 16, 2009 10 / 15

Evolutionary Models: Spiral

FIRST
Determine Objective and Identify alternative solutions

SECOND
Identfy and Reolve Risks

Review and Plan for the next Phase

Develop the next level of the product

FOURTH

THIRD

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department,Number A. Tech. University Lonere-402 103 akiwelekar@gm Software Engineering: Lecture Dr. B. 3 January 16, 2009 11 / 15

Rapid Application Development

A realistic approach useful to develop large-scale systems. Uses prototyping as a risk reduction mechanism. The spiral model demands a direct consideration of technical risks at all stages of the project.

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department,Number A. Tech. University Lonere-402 103 akiwelekar@gm Software Engineering: Lecture Dr. B. 3 January 16, 2009 12 / 15

Evolutionary Models: Concurrent Development Model
None

Under Development

awaiting changes under revision

Under Review

Baselined

Done

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department,Number A. Tech. University Lonere-402 103 akiwelekar@gm Software Engineering: Lecture Dr. B. 3 January 16, 2009 13 / 15

Rational Unified Process
Inception

Communication Release of SW Increment

Planning

Production

Elaboration

Deployment

Modeling

Construction

Construction

Transition

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department,Number A. Tech. University Lonere-402 103 akiwelekar@gm Software Engineering: Lecture Dr. B. 3 January 16, 2009 14 / 15

Rational Unified Process: Work Products

Inception Vision Document Initial Use case model Initial Project Glossary Initial Business case Initial Risk Assessment Project Plan phases and Iteration

Elaboration Use case Model Supplementary Requirements(NFR) Analysis Model SA Description Executable Architecture Prototype Preliminary design model

Construction Design Model Software Components Integrated SW Increment Test Plan and Procedure Test cases Support Documentation (i)User Manuals (ii) Installation Manuals (iii) Description Current Increment

Transition Delivered Software Increment Beta Test Report General User Feedback

Business Model

Revised Risk List Project Plan

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department,Number A. Tech. University Lonere-402 103 akiwelekar@gm Software Engineering: Lecture Dr. B. 3 January 16, 2009 15 / 15


								
To top