类别 全部 - requirements - prototyping - waterfall - testing

作者:Ibrahim Ibrahim 7 年以前

705

Software engineering

Software development processes utilize various models and activities to ensure the efficient creation and maintenance of software. The waterfall model involves sequential phases such as system design, implementation, and testing.

Software engineering

Software Processes

Process improvement

The process improvement cycle
analyze
change
Measure

Coping with change

Software prototyping
Benefits of prototyping

Reduced development effort.

Improved maintainability

Improved design quality

A closer match to users’ real needs

Improved system usability

Coping with changing requirements
Reducing the costs of rework

Process activities

Software validation
Stages of testing

Customer testing

System testing

Component testing

Software design and implementation
System implementation
Design activities
Software specification
Requirements engineering process

Requirements validation

Requirements specification

Requirements elicitation and analysis

Many different software processes

Evolution
Validation
Design and implementation
Specification

Incremental development

Throw-away prototyping
Exploratory development

Types of reusable software

Integration and configuration

Product specification
Software products
Customized products
Generic products

Software process models

The waterfall model
integration and system testing
operation and maintenance
implementation and unit testing
system and system design
requirement definition
Spiral Model
When to use Spiral Model

Significant changes are expected

Requirements are complex.

Users are unsure of their needs.

For medium to high-risk projects.

When costs and risk evaluation is important.

Phases in spiral model

Customer evaluation

Engineering

Plan

Risk Analysis

Applications

Disadvantages

Risk assessment expertise is required.

Spiral may go indefinitely.

Process is complex

Not suitable for small or low risk projects and could be expensive for small projects

End of project may not be known early.

Advantages

Early and frequent feedback from users.

Users see the system early

Requirements can be captured more accurately.

Allows for extensive use of prototypes

Changing requirements can be accommodated