| 1 | 15 | ||||||||||||||||||||||||
| 19 | |||||||||||||||||||||||||
| 2 | 3 | ||||||||||||||||||||||||
| 4 | |||||||||||||||||||||||||
| 5 | |||||||||||||||||||||||||
| 17 | |||||||||||||||||||||||||
| 6 | |||||||||||||||||||||||||
| 16 | |||||||||||||||||||||||||
| 7 | |||||||||||||||||||||||||
| 18 | |||||||||||||||||||||||||
| 8 | |||||||||||||||||||||||||
| 10 | 9 | ||||||||||||||||||||||||
| 11 | |||||||||||||||||||||||||
| 12 | |||||||||||||||||||||||||
| 13 | |||||||||||||||||||||||||
| 14 |
1. A facilitated discussion with a small group of stakeholders to gather diverse perspectives and insights on the project requirements.
2. A research method that involves in-depth exploration of a single individual, group, or event to analyze its effects and implications.
3. The total amount of work required to complete a project and the boundaries within which the project must be executed.
4. The phase where the system is released for its intended users.
5. Individuals or businesses that purchase goods or services from a company.
6. A software development model in which progress is seen as flowing steadily downwards through the phases of conception, initiation, analysis, design, construction, testing, production/implementation, and maintenance.
7. The existing framework or system in place that is being used in a particular context, subject to evaluation and potential improvement.
8. Harm to the brand or image of a company resulting from dissatisfied end users.
9. A high-level description of a computer program or algorithm using a mixture of natural language and informal programming language syntax.
10. Individuals or entities that own shares of a company and have a financial interest in its performance.
11. A software development process where a subset of the software is developed and released, with subsequent iterations adding more features and improving quality based on user feedback.
12. The series of steps and activities involved in creating a product or service.
13. The high-level structure of a system that defines its components, interfaces, and data.
14. A group of internal stakeholders responsible for managing and maintaining the organization's information technology infrastructure.
15. The specific metrics or conditions that must be met in order to determine if a project has been successful.
16. The systematic process of designing and developing a system from its conception to implementation.
17. An iterative software development approach that emphasizes risk management through multiple cycles of development
18. Creating a working model or prototype of the project to gather feedback and refine requirements based on stakeholder input.
19. A loss of competitive edge in the market due to inferior product or service design.