| 1 | 9 | ||||||||||||||||||||
| 2 | |||||||||||||||||||||
| 3 | |||||||||||||||||||||
| 4 | 10 | ||||||||||||||||||||
| 5 | 8 | ||||||||||||||||||||
| 6 | |||||||||||||||||||||
| 7 | |||||||||||||||||||||
1. A visual representation of a process or algorithm that uses different shapes and arrows to illustrate the sequence of steps and decision points.
2. The total amount of work required to complete a project and the boundaries within which the project must be executed.
3. Refers to the boundaries and limits of a project, including the activities, deliverables, and resources that are considered part of the project.
4. Occurs when the project's boundaries and limits are expanded without proper approval, leading to additional work that was not initially planned.
5. Use cases are descriptions of how users interact with the system to achieve a particular goal, providing a detailed view of the system's functionality.
6. A document that outlines the project's deliverables, objectives, requirements, and constraints, including what is included in scope and what is out of scope.
7. Prototyping involves creating a working model of the system to demonstrate its functionality and gather feedback from stakeholders.
8. The specific metrics or conditions that must be met in order to determine if a project has been successful.
9. Refers to the activities, deliverables, and resources that are not included in the project and are considered beyond the boundaries of the project.
10. A high-level description of a computer program or algorithm using a mixture of natural language and informal programming language syntax.