Development Approach: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
The Development Approach is a strategic, emergent, agile approach towards building a certain prototype determined by the product owner. Depending on the available resources, scheduling, timelines, dogfooding needs, development of other prototypes, product ecologies, features of OSE Specifications, and other situational factors, a certain approach is favored over another. | The Development Approach is a strategic, emergent, agile approach towards building a certain prototype determined by the product owner. Depending on the available resources, scheduling, timelines, dogfooding needs, development of other prototypes, product ecologies, features of OSE Specifications, and other situational factors, a certain approach is favored over another. | ||
The development approach should include decisions on the types of components used and a specific implementation pathway - to be tested according to [[Test-Driven Design]]. | |||
Revision as of 03:47, 2 August 2013
The Development Approach is a strategic, emergent, agile approach towards building a certain prototype determined by the product owner. Depending on the available resources, scheduling, timelines, dogfooding needs, development of other prototypes, product ecologies, features of OSE Specifications, and other situational factors, a certain approach is favored over another.
The development approach should include decisions on the types of components used and a specific implementation pathway - to be tested according to Test-Driven Design.