User:Marek.dusek/Goal-Driven Software Development Process: Difference between revisions
Content deleted Content added
Marek.dusek (talk | contribs) Initial version |
nowiki'd categories - user pages should not be categorized in main page space |
||
(One intermediate revision by one other user not shown) | |||
Line 22:
Secondly, while established [[Software development process|software processes]] refine requirements down to an implementation, the Goal-driven Development Process recommends trying to find an optimal mapping between business objectives and capabilities of
the technical platform in an ''iterative'' process, equally considering and adjusting business goals and technical aspects to come to an optimal, ''convergent'' solution.
Goal-driven development process allows stakeholders to <ref name="CASE">{{cite web
| url = http://www.jot.fm/issues/issues%202006_03/column9
| title = How to align IT with the Changes using UML and according to BMM
| accessdate = 2008-12-30
| last = Berkem
| first = Birol
| publisher = Journal of Object Technology, vol. 5, no. 2, March-April 2006, pp. 85-102
}}</ref>:
* Discover use cases that are tailored to the requirements according to business goals
* Establish a bridge between goals and IT architecture
== Key principles ==
Line 75 ⟶ 87:
The core activities are:
These activities can be also divided into six main steps <ref name="CASE" />:
# '''Group requirements by goals'''
# '''Formalize behaviors inside processes'''
# '''Monitor advancement in the realization of the goals (optional)'''
# '''Assign responsibilities to participants'''
# '''Plug behaviors in the architectural and play'''
# '''Integrate application constraints of the actors'''
== References ==
<references/>
== External links ==
Line 88 ⟶ 109:
{{Software Engineering}}
<nowiki>
[[Category:Software development process]]
</nowiki>
|