| 1 | 15 | ||||||||||||||||||||||||
| 17 | |||||||||||||||||||||||||
| 14 | 2 | ||||||||||||||||||||||||
| 3 | |||||||||||||||||||||||||
| 4 | |||||||||||||||||||||||||
| 5 | |||||||||||||||||||||||||
| 16 | |||||||||||||||||||||||||
| 13 | 6 | ||||||||||||||||||||||||
| 18 | |||||||||||||||||||||||||
| 7 | |||||||||||||||||||||||||
| 8 | |||||||||||||||||||||||||
| 9 | |||||||||||||||||||||||||
| 10 | |||||||||||||||||||||||||
| 11 | |||||||||||||||||||||||||
| 12 |
1. Occurs when the project's boundaries and limits are expanded without proper approval, leading to additional work that was not initially planned.
2. Refers to the activities, deliverables, and resources that are not included in the project and are considered beyond the boundaries of the project.
3. The high-level structure of a system that defines its components, interfaces, and data.
4. Low uptake or acceptance of a product or service by end users due to design flaws.
5. A creative technique used to generate ideas and solutions for project requirements through a collaborative and structured group session.
6. The existing framework or system in place that is being used in a particular context, subject to evaluation and potential improvement.
7. A method of obtaining stakeholder requirements by holding one-on-one discussions to gather insights and information.
8. A critical analysis of existing literature on a specific topic, highlighting gaps, trends, and contributions to the field.
9. The ongoing process of updating, monitoring, and supporting the system post-deployment.
10. A software development approach where the project is divided into smaller parts, with each part delivered and tested in stages, adding new functionality with each iteration.
11. An iterative software development approach that emphasizes risk management through multiple cycles of development
12. A facilitated discussion with a small group of stakeholders to gather diverse perspectives and insights on the project requirements.
13. A technique that involves directly observing stakeholders in their natural environment to understand their behaviors and interactions.
14. Members of an organization who are directly involved in the use and implementation of ICT systems.
15. Government agencies or bodies responsible for overseeing and enforcing laws and regulations in a specific industry.
16. Creating a working model or prototype of the project to gather feedback and refine requirements based on stakeholder input.
17. Companies or businesses that offer similar goods or services in the same market.
18. The series of steps and activities involved in creating a product or service.