More terms¶
- V-Model
The famous V-Model shows the relations between development-lifecycle activities. There are several definitions and origins of the model, as well as a lot of misunderstanding. All model-derivations have multiple hierarchical levels and are based on three kind of activities: design (or definition), integration (or test) and validation (or feedback). The model itself is non-linear, but most implementations of the V-Model are more or less sequential in time, however.
The V-Model is an extension to the older Waterfall model; which is linear. But many people regard them as the same; probably due the typical sequential execution of the V-Model. That sequential execution is often seen as a drawback of the V-Model. And used to advocate ‘modern’ agile software development methods; like scrum.
See also
- http://en.wikipedia.org/wiki/V-Model
This wikipedia article describes the generic system engineering V-Model and variations.
- http://en.wikipedia.org/wiki/V-Model_(software_development)
There is a separate wikipedia article on the software engineering variation of the V-Model
- Agile
- Scrum
- Geïntegreerd Agile
- Integrated Agile
The is the mix of Lean, Agile and Scrum advocated by Albert Mietus
- Lean
Todo
DocMe (Lean) XXX
- Pathways
A concept and (reference) implementation to execute (system/user) tests to approve the (developing) product is working correctly.