Class_1_ch1_ch4_ProcessModels

Class_1_ch1_ch4_ProcessModels - CS487 SoftwareEngineering...

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

View Full Document Right Arrow Icon
1   CS487 Software Engineering Omar Aldawud [email protected] http://www.cs.iit.edu/~oaldawud/CS487/index.html http://www.cs.iit.edu/~oaldawud/CS487/index.html
Background image of page 1

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

View Full DocumentRight Arrow Icon
2 Class 1 – Part 2 Prescriptive Process Models
Background image of page 2
3 SW Process Models Prescriptive process models advocate an orderly approach to  software engineering. It is a set of  activities  required to: Define, design, implement, test and maintain a software product. A SW process model is chosen based on the nature of  the project.
Background image of page 3

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

View Full DocumentRight Arrow Icon
4 SW Process Model Phases All models have phases and each phase has 3  components: Set of  activities , this is what you do. Set of  deliverables , this is what you produce. Quality control measures , this is what you use to  evaluate the deliverables. The activities defines the process Framework,  the generic set encompasses: Communication, planning, modeling, construction, and  deployment
Background image of page 4
5 Generic Process Activity  There are 4 fundamental process activities that are  common to all software processes: 1. Software specification 2. Software development 3. Software validation 4. Software evolution
Background image of page 5

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

View Full DocumentRight Arrow Icon
6 The Waterfall Model This Model suggests a systematic, sequential approach to SW development that begins at the system level and progresses through analysis, design, code and testing. Communicat ion  Planning  Modeling Const ruct ion Deployment   analysis  design code  t est project   init iat ion  requirement   gat hering estimating  scheduling  tracking delivery  support   f eedback Pressman, 6th edition
Background image of page 6
7 Waterfall Model Advantages Easy Structured Provide a template into which  methods for analysis, design,  code, testing and maintenance  can be placed. Disadvantages Sequential, does not reflect  reality Does not allow for feedback Does not produce a  prototype User must wait until the end  to see the final program.
Background image of page 7

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

View Full DocumentRight Arrow Icon
8 When to use the Waterfall Model Simple Projects  Limited amount of time Requirements are well understood We can use it for our Class Project.
Background image of page 8
9 Incremental Models Goal to provide quick basic functionality to  the users Process is not linear Requirements are well defined Software is completed in an increments  fashion Will Study 2 models: 1. Incremental Model 2. RAD
Background image of page 9

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

View Full DocumentRight Arrow Icon
10 1. Incremental Model It  combines  characteristics of the waterfall model  and the iterative nature of the prototyping model. 1 st  build is usually the  CORE  product Each increment “deliverable” may  add a new   functionality.
Background image of page 10
Image of page 11
This is the end of the preview. Sign up to access the rest of the document.

This document was uploaded on 04/23/2010.

Page1 / 38

Class_1_ch1_ch4_ProcessModels - CS487 SoftwareEngineering...

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

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