End Users Design Process
User Requirements Feedback
Usability Issues Poor Adoption Rate
Wasted Resources Competitive Disadvantage

 

The series of steps and activities involved in creating a product or service. The individuals who will ultimately use the product or service being designed.
Input provided by end users on the design of a product or service. The specific needs, preferences, and expectations of end users that must be considered during design.
Low uptake or acceptance of a product or service by end users due to design flaws. Problems related to the ease of use, functionality, and overall user experience of a product or service.
A loss of competitive edge in the market due to inferior product or service design. Resources, such as time and money, that are expended on a poorly designed product or service.

 

Negative Reputation Stakeholder
Requirement Elicitation Interviews
Surveys Observations
Prototyping Focus Groups

 

A person or organization with a vested interest or concern in the project and its outcomes. Harm to the brand or image of a company resulting from dissatisfied end users.
A method of obtaining stakeholder requirements by holding one-on-one discussions to gather insights and information. The process of gathering and documenting requirements from stakeholders through various techniques such as interviews, surveys, and workshops.
A technique that involves directly observing stakeholders in their natural environment to understand their behaviors and interactions. A tool used to collect feedback and preferences from a large group of stakeholders to understand their needs and expectations.
A facilitated discussion with a small group of stakeholders to gather diverse perspectives and insights on the project requirements. Creating a working model or prototype of the project to gather feedback and refine requirements based on stakeholder input.

 

Document Analysis Brainstorming
Workshops Internal Stakeholders
Managers Employees
IT Department Executives

 

A creative technique used to generate ideas and solutions for project requirements through a collaborative and structured group session. Reviewing existing documentation such as project charters, business cases, and user manuals to extract requirements and insights from stakeholders.
Members of an organization who are directly involved in the use and implementation of ICT systems. Interactive sessions with stakeholders to discuss and prioritize project requirements, facilitate collaboration, and reach consensus on key priorities.
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. Internal stakeholders in ICT systems responsible for overseeing the strategizing, planning, and implementation of technology within an organization.
High-level internal stakeholders in ICT systems who make decisions regarding the adoption and utilization of technology to achieve business goals. A group of internal stakeholders responsible for managing and maintaining the organization's information technology infrastructure.

 

Finance Department Human Resources
Project Managers Technical Support
Quality Assurance Shareholders
Customers Suppliers

 

An internal stakeholder that plays a role in hiring, training, and managing employees who use technology within the organization. An internal stakeholder that oversees the budgeting and financial aspects related to the acquisition and maintenance of technology.
A group of internal stakeholders who provide assistance and troubleshooting for technology users within the organization. Internal stakeholders who oversee the planning, execution, and monitoring of technology projects to ensure successful implementation.
Individuals or entities that own shares of a company and have a financial interest in its performance. An internal stakeholder that ensures the functionality and performance of technology systems meet established standards and requirements.
Companies or individuals that provide goods or services to another company. Individuals or businesses that purchase goods or services from a company.

 

Government Creditors
Competitors Media
Regulators Trade Unions
Literature Review Technical Research

 

Entities that lend money to a company in exchange for repayment with interest. The governing body of a country or region that enforces laws and regulations affecting businesses.
Organizations or platforms that distribute news and information to the public. Companies or businesses that offer similar goods or services in the same market.
Organizations that represent workers in negotiations with employers regarding wages, working conditions, and other employment-related issues. Government agencies or bodies responsible for overseeing and enforcing laws and regulations in a specific industry.
Conducting in-depth research to develop new technologies or improve existing ones, based on scientific principles and methodologies. A critical analysis of existing literature on a specific topic, highlighting gaps, trends, and contributions to the field.

 

Current System Competitor Analysis
Case Study Use Cases
Entity Relationship Diagram System Architecture Diagram
Pseudocode Mockup

 

Assessing and evaluating the strengths and weaknesses of competitors within a specific market or industry to gain strategic insights and advantages. The existing framework or system in place that is being used in a particular context, subject to evaluation and potential improvement.
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. A research method that involves in-depth exploration of a single individual, group, or event to analyze its effects and implications.
A diagram that shows the structure of a system, including its components and how they interact. A visual representation of the relationships between entities in a database.
A visual representation or model of a design, used to showcase the layout and functionality of a product. A high-level description of a computer program or algorithm using a mixture of natural language and informal programming language syntax.

 

Flowchart In Scope
Out Of Scope Success Criteria
Scope Statement Project Scope
Scope Creep System Design Cycle

 

Refers to the boundaries and limits of a project, including the activities, deliverables, and resources that are considered part of the project. A visual representation of a process or algorithm that uses different shapes and arrows to illustrate the sequence of steps and decision points.
The specific metrics or conditions that must be met in order to determine if a project has been successful. Refers to the activities, deliverables, and resources that are not included in the project and are considered beyond the boundaries of the project.
The total amount of work required to complete a project and the boundaries within which the project must be executed. A document that outlines the project's deliverables, objectives, requirements, and constraints, including what is included in scope and what is out of scope.
The systematic process of designing and developing a system from its conception to implementation. Occurs when the project's boundaries and limits are expanded without proper approval, leading to additional work that was not initially planned.

 

Requirements Analysis System Architecture
Implementation Testing
Deployment Maintenance
Iteration Waterfall Model

 

The high-level structure of a system that defines its components, interfaces, and data. The stage in the system design cycle where the needs and constraints of the system are identified and documented.
The process of evaluating the system to ensure that it meets the specified requirements. The stage in the system design cycle where the system is built and put into use.
The ongoing process of updating, monitoring, and supporting the system post-deployment. The phase where the system is released for its intended users.
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. The process of repeating the system design cycle to refine and enhance the system over time.

 

Agile Model Spiral Model
Iterative Model Incremental Model
Models Incremental
Iterative Adaptability

 

An iterative software development approach that emphasizes risk management through multiple cycles of development A software development methodology that prioritizes flexibility, collaboration, and customer feedback through iterative and incremental development.
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. 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.
A development approach where the software product is delivered in small, manageable increments or iterations rather than all at once. Different approaches or frameworks used in software development to guide the processes involved in building software applications.
The ability of a development team or project to adjust to changes in requirements, technology, or other factors during the software development lifecycle. A development approach that involves repeating a process or set of activities in cycles or iterations.

 

Collaboration

 

Working together with stakeholders, team members, and other parties involved in the software development process to achieve common goals.