Mindmap
software design and development
Inhalt der Mindmap
software design and development
development methodologies
- traditional method
- client interaction
- - The client is heavily at the start and end points of development.
- They evaluate at the end to see if it's fit for purpose and their feedback can be used to redesign
- Teamwork
- Teams of analysts, programmers, testers and documenters work independently of each phase of development
- Team will only when require between phases.
- documentation
- Team will only when require between phases.
- Teams of analysts, programmers, testers and documenters work independently of each phase of development
- Teamwork
- They evaluate at the end to see if it's fit for purpose and their feedback can be used to redesign
- - The client is heavily at the start and end points of development.
- client interaction
- agile method
- client interaction
- The client is involved throughout the entire process
- They will give feedback on each prototype as it is produced.
- Teamwork
- Teams of developers communicate and collaborate, rather than work on their own. There are regular meeting between individuals with different skills
- documentation
- Teams of developers communicate and collaborate, rather than work on their own. There are regular meeting between individuals with different skills
- Teamwork
- They will give feedback on each prototype as it is produced.
- The client is involved throughout the entire process
- client interaction
- traditional method
coding
- Modularity and parameter
- Modularity
- Procedures/subroutines
- functions
- Formal parameters
- form
- actual parameters
- Procedures/subroutines
- Modularity
- Modularity and parameter
Informationen
- Beschreibung
- Mindmap am software design and development, erstellt von Niamh Horton am 11/01/2022.
- Erstellt von
- Niamh Horton
- Aufrufe
- 0
- Bewertung