1/12 | |||||||||||||||||||||||||
2/16 | |||||||||||||||||||||||||
3 | |||||||||||||||||||||||||
17 | |||||||||||||||||||||||||
4 | |||||||||||||||||||||||||
14 | 18 | ||||||||||||||||||||||||
15 | |||||||||||||||||||||||||
13 | 5 | ||||||||||||||||||||||||
6 | |||||||||||||||||||||||||
7 | |||||||||||||||||||||||||
8 | |||||||||||||||||||||||||
9 | |||||||||||||||||||||||||
10 | |||||||||||||||||||||||||
11 | |||||||||||||||||||||||||
1. A research method that involves in-depth exploration of a single individual, group, or event to analyze its effects and implications.
2. Individuals or businesses that purchase goods or services from a company.
3. A high-level description of a computer program or algorithm using a mixture of natural language and informal programming language syntax.
4. A method of obtaining stakeholder requirements by holding one-on-one discussions to gather insights and information.
5. An internal stakeholder that ensures the functionality and performance of technology systems meet established standards and requirements.
6. A software development methodology that prioritizes flexibility, collaboration, and customer feedback through iterative and incremental development.
7. An internal stakeholder that plays a role in hiring, training, and managing employees who use technology within the organization.
8. Internal stakeholders who oversee the planning, execution, and monitoring of technology projects to ensure successful implementation.
9. The phase where the system is released for its intended users.
10. The ability of a development team or project to adjust to changes in requirements, technology, or other factors during the software development lifecycle.
11. Internal stakeholders in ICT systems who use technology on a daily basis to perform their tasks and contribute to the overall functioning of the organization.
12. A loss of competitive edge in the market due to inferior product or service design.
13. An iterative software development approach that emphasizes risk management through multiple cycles of development
14. The total amount of work required to complete a project and the boundaries within which the project must be executed.
15. 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.
16. The existing framework or system in place that is being used in a particular context, subject to evaluation and potential improvement.
17. A group of internal stakeholders who provide assistance and troubleshooting for technology users within the organization.
18. An internal stakeholder that oversees the budgeting and financial aspects related to the acquisition and maintenance of technology.