Software Processes

coping with change
1. large software projects.Eg-technologies
2. leads to rework
reducing the cost rework
1. change avoidance
2. change tolerance
software prototyping
1. benefit
  1. improved maintainability
  2. improved design quality
2. def:initial version of a system
  1. process to help requirements
  2. develop a UI design
  3. testing process
3. prototype development
  1. functionality
    1. focus on functional
    2. not include error checking
    3. focus a certain area;not understood
  2. rapid prototyping language
4. throw-away prototypes
  1. discarded as not a good basis
    1. non functional requirements
    2. undocumented
    3. degraded
    4. not organisational standards
5. process of prototype
  1. prototyping plan
  2. outline definition
  3. executable prototype
  4. evaluation report
incremental development
1. develop the system in increments
2. used in agile methods
incremental delivery
1. user requirements as priority
2. realistic evaluation about practical use of software
3. use by end users
4. different to implement for replacement system
5. advantange
  1. lower risk of overall project failure
  2. tend to receive the most testing
  3. system functionality is available ealier
6. problem
  1. the essence of iterative processes is that the specification is developed in conjuction with the software
  2. hard to identify common facilities
Boehm's spiral model
1. spiral vs sequence of activities
2. spiral model sectors
  1. objective setting
  2. risk assessment and reduction
  3. development & validation
  4. planning
3. represents a phase in the process
4. spiral model usage
  1. helping people think about iteration in software processes
RUP
1. RUP iteration
  1. cross phase iteration
    1. loop
  2. inphase iteration
    1. developed incrementally
  3. phase
    1. transition
    2. contruction
    3. inception
    4. elaboration
2. Modern generic process
3. 3 prespective
  1. dynamic
  2. static
  3. practice
4. good practice
  1. use component based architectures
  2. use component based architectures
  3. manage requirements
  4. control changes to software

Next up

Software Processes

Description

Resource summary

Similar

	Created by Nurul Aiman Abdu about 9 years ago