Revision as of 11:19, 15 October 2021 edit Citation bot (talk \| contribs) Bots 5,862,909 edits Alter: title, template type. Add: s2cid, isbn, doi, pages, year, chapter, chapter-url. Removed or converted URL. Formatted dashes. \| Use this bot. Report bugs. \| Suggested by Abductive \| Category:Software development process \| #UCB_Category 70/120 ← Previous edit		Revision as of 15:43, 6 November 2021 edit undo Ineedsomeartwork (talk \| contribs) 1 edit →Collaborative goal identification: Fixed grammar Tags: Mobile edit Mobile web edit Next edit →
Line 51: As closely related to the [[GQM\|Goal-Question-Metric]] paradigm, a '''top-level goal''' is defined as an informal description of what a stakeholder wants to change or improve in his business environment, decomposing itself to more specific '''sub-goals'''. Moreover, a set of questions is linked to every goal, which characterizes the way how software will be tested against defined goals after each [[iterative and incremental development\|iteration]]. Being this the key GDP principle, the collaborative identification of goals brings knowledge of users and software developers together. While goal definition is top-down driven, deciding, if a goal is feasible is bottom-up oriented. === Top-down and bottom-up convergence ===

Goal-Driven Software Development Process: Difference between revisions