| 1 | 14 | 16 | 17 | ||||||||||||||||||||||
| 2 | |||||||||||||||||||||||||
| 3 | |||||||||||||||||||||||||
| 18 | |||||||||||||||||||||||||
| 4 | |||||||||||||||||||||||||
| 12 | |||||||||||||||||||||||||
| 5 | 13 | ||||||||||||||||||||||||
| 6 | |||||||||||||||||||||||||
| 15 | |||||||||||||||||||||||||
| 7 | |||||||||||||||||||||||||
| 8 | |||||||||||||||||||||||||
| 9 | |||||||||||||||||||||||||
| 10 | |||||||||||||||||||||||||
| 11 | |||||||||||||||||||||||||
1. Low uptake or acceptance of a product or service by end users due to design flaws.
2. A group of internal stakeholders responsible for managing and maintaining the organization's information technology infrastructure.
3. A visual representation of a process or algorithm that uses different shapes and arrows to illustrate the sequence of steps and decision points.
4. The specific metrics or conditions that must be met in order to determine if a project has been successful.
5. A loss of competitive edge in the market due to inferior product or service design.
6. A facilitated discussion with a small group of stakeholders to gather diverse perspectives and insights on the project requirements.
7. The ongoing process of updating, monitoring, and supporting the system post-deployment.
8. The individuals who will ultimately use the product or service being designed.
9. Companies or businesses that offer similar goods or services in the same market.
10. A technique that involves directly observing stakeholders in their natural environment to understand their behaviors and interactions.
11. The existing framework or system in place that is being used in a particular context, subject to evaluation and potential improvement.
12. A document that outlines the project's deliverables, objectives, requirements, and constraints, including what is included in scope and what is out of scope.
13. High-level internal stakeholders in ICT systems who make decisions regarding the adoption and utilization of technology to achieve business goals.
14. The phase where the system is released for its intended users.
15. The total amount of work required to complete a project and the boundaries within which the project must be executed.
16. The process of gathering and documenting requirements from stakeholders through various techniques such as interviews, surveys, and workshops.
17. 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.
18. Assessing and evaluating the strengths and weaknesses of competitors within a specific market or industry to gain strategic insights and advantages.