Mapa mental
Software design and development
Contenido del mapa
Software design and development
Development Methodologies
- Waterfall/traditional
- Client is heavily involved at the start and End points of development
- At the end of the development they will evaluate that it is fit for purpose and meets the specification
- Teams of analysists, programmers, testers and documenters work independently on each phase of development
- A detailed project specification is created at the beginning of a project
- Follows a strict plan, with progress measured against timescales set at the beginning of the project
- A predictive methodology focusing on analyzing and planning the future in detail and catering For known risks
- Testing is carried out when the implementation phase of the project is complete
- A predictive methodology focusing on analyzing and planning the future in detail and catering For known risks
- Follows a strict plan, with progress measured against timescales set at the beginning of the project
- A detailed project specification is created at the beginning of a project
- Teams of analysists, programmers, testers and documenters work independently on each phase of development
- At the end of the development they will evaluate that it is fit for purpose and meets the specification
- Client is heavily involved at the start and End points of development
- Agile
- Client is involved throughout entire process
- Goals can be changed throughout the project
- Teams of developers communicate and collaborate rather than teams operating in isolation
- While modelling solutions remains important, creating large documents that are never updated or referred to again upon completion of the project are not
- Breaks a project down into a series of short development goals
- An adaptive methodology focusing on adapting quickly to changing realities. When the needs of a project change an adaptive team changes as well
- There is no recognised testing phase, as testing is carried out in conjunction with programming
- An adaptive methodology focusing on adapting quickly to changing realities. When the needs of a project change an adaptive team changes as well
- Breaks a project down into a series of short development goals
- While modelling solutions remains important, creating large documents that are never updated or referred to again upon completion of the project are not
- Teams of developers communicate and collaborate rather than teams operating in isolation
- Goals can be changed throughout the project
- Client is involved throughout entire process
- Waterfall/traditional
Software Development Process
- analysis
- design
- implementation
- testing
- documentation
- evaluation
- maintenance
- evaluation
- documentation
- testing
- implementation
- design
- analysis
Información
- Descripción
- Mapa Mental sobre Software design and development, creado por Boyd Harper el 11/01/2022.
- Creado por
- Boyd Harper
- Visitas
- 0
- Valoración