Lecuture 3 Software Process

Lecuture 3 Software Process - Lecture 2: Software Process...

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

View Full Document Right Arrow Icon
CUHK, Spring 2007 Lecture 2: Software Process Teresa Xia Cai
Background image of page 1

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

View Full DocumentRight Arrow Icon
CUHK, Spring 2007 Software Engineering / 1 - 2 Outline 1. Three generic software process models 1. Two methods of process iteration 1. Software process activities 1. CASE technology to support software process activities
Background image of page 2
CUHK, Spring 2007 Software Engineering / 1 - 3 The software process A structured set of activities required to develop a software system Complex, no ideal process, varied according to system features: U Critical systems: very structured U Business systems: flexible, agile process Fundamental activities involved: U Specification - The functionality of the software and constraints on its operation must be defined. U Design and implementation - The software to meet the specification must be produced. U Validation - The software must be validated to ensure that it does what the customer wants. U Evolution - The software must evolve to meet changing customer needs.
Background image of page 3

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

View Full DocumentRight Arrow Icon
CUHK, Spring 2007 Software Engineering / 1 - 4 Software process models A software process model U an abstract representation of a process U a description of a process from some particular perspective. Software process models are not mutually exclusive, but are often used together
Background image of page 4
CUHK, Spring 2007 Software Engineering / 1 - 5 Outline 1. Three generic software process models U Waterfall model U Evolutionary development U Component-based software engineering 1. Two methods of process iteration 1. Software process activities 1. CASE technology to support software process activities
Background image of page 5

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

View Full DocumentRight Arrow Icon
CUHK, Spring 2007 Software Engineering / 1 - 6 1. Generic software process models The waterfall model U Separate and distinct phases of specification, design, implementation and testing. Evolutionary development U Specification, development and validation are interleaved. Component-based software engineering U The system is assembled from existing components. These models are often combined in software systems, together with their variants.
Background image of page 6
CUHK, Spring 2007 Software Engineering / 1 - 7 1A. Waterfall model Service/ Constraints/ goals specification Customer /User specification Software abstraction Software design A set of program units Programs Software system ready for release Failure report & new requirements New version
Background image of page 7

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

View Full DocumentRight Arrow Icon
CUHK, Spring 2007 Software Engineering / 1 - 8 Waterfall model Advantages U Clear, easy to control U Documentation is produced at each stage, fitting with other engineering discipline Problems U Inflexible partitioning of the project into distinct stages makes it difficult to respond to changing customer requirements. U This model is only appropriate when the requirements are well-understood and changes will be fairly limited during the design process. U
Background image of page 8
Image of page 9
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 37

Lecuture 3 Software Process - Lecture 2: Software Process...

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

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