Intent |
The intent sub-process deals with how to channel the intent of stakeholders to the rest of the development team, to ensure that validated builds with incremental capabilities reflect stakeholder intents.
Relationships
Contents | Balance competing priorities to maximize stakeholder value Requirements Configuration & Change Management Requirements Manage Requirements Ongoing Tasks
Main Description
The intent sub-process deals with how to channel the intent of stakeholders to the rest of the development team, to ensure that validated builds with incremental capabilities reflect stakeholder intents. This is done by capturing and communicating the vision to all team members, and by translating the vision into test cases and requirements of different types to allow the team to understand what capabilities needs to be delivered to address stakeholder intent. You find the most tasks for the intent sub-process in the Requirements discipline, and the task Create Test Cases in the Test discipline. The corresponding work products are found under Requirements and Test domains. The intent sub-process is built upon the foundational Collaboration and Communication layer. That layer constitutes the backbone of OpenUP in order to reflect the following: all roles in OpenUP are involved in intent development to ensure that as a minimum, all team members properly understand stakeholders’ intent. make sure that the best practices for collaborative development provided in the collaboration layer guides any work related to intent. The intent sub-process is written in such a way that your organization can modify it to fit your style of development and stakeholder collaboration, without necessarily impacting how you deal with the other sub-processes of Management and Solution development .
This program and the accompanying materials are made available under the Eclipse Public License v1.0 which accompanies this distribution. View copyright information here: OpenUP Copyright