15. System Development Flashcards
(158 cards)
1
Q
CONCEPT OF PROJECT MANAGEMENT
Q: Why is effective management important in IT projects?
A
Because IT projects have many aspects that must be monitored, and failure in one area can affect the project’s quality, deadlines, and costs.
2
Q
Why is project management especially challenging in the IT field?
A
IT is fast-moving with constantly emerging technologies and trends, leading to frequently changing client requirements.
3
Q
MANAGING A PROJECT
What is the role of a project manager regarding stakeholders?
A
To ensure stakeholders are involved at the right time and in the right way.
4
Q
key features of managing a project are
A
Complexity management
Resource allocation
Risk mitigation
Quality assurance
Communication and collaboration
Change management
Scheduling and deadlines
5
Q
Complexity management
What is the goal of complexity management in IT projects?
A
To break down complexity into manageable tasks that can be properly planned, executed, and monitored.
6
Q
Resource allocation
Why is resource allocation important in IT project management?
A
Because proper allocation ensures effective task completion within time, budget, and with the right personnel and equipment.
7
Q
What tasks does a project manager perform during resource allocation?
A
A: Scheduling tasks, assigning responsibilities, and ensuring availability of necessary resources for task completion.
8
Q
Risk mitigation
Q: What are key components of risk mitigation in project management?
A
A: Identifying potential risks, developing mitigation strategies, and implementing contingency plans.
9
Q
Q: What is “feature creep” in IT projects?
A
continual addition of new features to a product in development that affects the team’s ability to complete
the project effectively and negatively affects deadlines and budgets
10
Q
What is mitigation:
A
an action or strategy intended to reduce the seriousness or harm caused by a potential risk
11
Q
Risks in an IT project are
A
Changing requirements
a project manager can handle changing requirements by Keeping the project aligned with the original scope and communicate clearly with stakeholders about any major changes and their impacts.
Technical issues and threats
examples of technical risks in IT projects are Faulty hardware causing delays, or serious issues like data breaches.
Human factors
human factors can pose risks in IT projects are Misconfigured hardware/software, accidental data loss, improper task allocation, and staff illness or absence.
Wider issues
Financial crises, global pandemics, local legislation changes, or political instability.
12
Q
Can project managers control all risks in IT projects?
A
No, but they must analyze and plan for risks even if they are outside of their control.
13
Q
Quality assurance
What is the goal of quality assurance (QA) in IT project management?
A
To ensure the project meets agreed standards and specifications throughout its lifecycle.
14
Q
Communication and collaboration
Why is communication and collaboration essential in IT projects?
A
Because they typically involve diverse teams that need to work together efficiently to achieve project goals.
15
Q
What is the project manager’s role in quality assurance?
A
Oversee QA at all stages and ensure effective systems are in place to maintain quality.
16
Q
How does a project manager ensure effective communication?
A
By clearly communicating project goals, priorities, and expectations to all stakeholders.
17
Q
Change management
Why does change management matter in IT projects?
A
IT requirements evolve due to changing business needs or market conditions, requiring structured approaches to incorporate changes.
18
Q
What should a project manager do when managing change?
A
Assess impacts, prioritise changes, and incorporate them with minimal disruption while supporting staff and stakeholders.
19
Q
Scheduling and deadlines
Why is scheduling important in IT project management?
A
Because IT is fast-paced and meeting deadlines is key to rapid delivery and maintaining a competitive edge.
20
Q
How does effective project management help meet deadlines?
A
By streamlining development, identifying bottlenecks, and prioritising tasks to maintain speed without compromising quality.
21
Q
CHARACTERISTICS OF A SUCCESSFUL IT PROJECT
What are the characteristics that help to ensure an IT project is successful.
A
- Clear objectives
- Effective stakeholder engagement
- Detailed planning
- Skilled team
- Adaptability
- Effective communication
- Quality focus
- Risk management
- Continuous improvement
- On-time and on-budget
22
Q
Clear objectives
Q: Why are clear objectives important in IT projects?
A
A: They help stakeholders understand what is required and guide the planning, execution, and evaluation of tasks.
23
Q
Q: What framework is commonly used to set effective project objectives?
A
A: The SMART framework
24
Q
Effective stakeholder engagement
Q: Who are stakeholders in an IT project?
A
A: Individuals or groups with an interest in the project’s outcome due to potential positive or negative impacts.
25
Q: Why is stakeholder engagement important in IT projects?
A: It ensures stakeholders are informed, supported, and able to provide input and feedback, which contributes to project success.
26
Q: What are internal stakeholders in an IT project?
A: Individuals or groups within the organisations directly involved in the project, such as developers, end-users, managers, and executives.
27
Q: How can stakeholders influence an IT project?
A: Through their feedback, expectations, and reactions to changes, which can shape the direction and success of the project.
28
Q: What are external stakeholders in an IT project?
A: People not directly involved in or employed by the organisation but with a vested interest, such as customers, community members, or regulatory bodies.
29
Detailed planning
Q: Why is detailed planning essential in IT projects?
A: Because IT projects involve many components that must be carefully considered for the project to be feasible and successful.
30
Q: What elements should a detailed project plan include?
A: Scope, deliverables, timelines, resource requirements, risks, and quality standards.
31
Skilled team
Q: Why is having a skilled team important in IT projects?
A: Because team members need the expertise to effectively carry out the tasks assigned to them.
32
Adaptability
Q: Why is adaptability important in IT project management?
A: It allows the project to respond to evolving requirements, technologies, and market conditions while keeping project objectives intact.
33
Q: What is a risk of too much adaptability in a project?
A: Feature creep, which can derail timelines and budgets.
34
Effective communication
Q: Why is effective communication critical in IT projects?
A: It ensures alignment, helps resolve issues, and manages expectations among team members and stakeholders.
35
Quality focus
Q: Why is a quality focus important in project management?
A: To ensure stakeholder expectations are met and that high-quality outcomes are consistently delivered.
36
Risk management
Q: What is the purpose of risk management in IT projects?
A: To identify, analyze, prioritize, and respond to risks in order to minimize their impact on project success.
37
Continuous improvement
Q: What is continuous improvement in the context of IT project management?
A: Regularly reviewing the project to identify successes and areas for improvement to better meet project objectives.
38
On-time and on-budget
Q: How can a project manager ensure a project stays on time and on budget?
A: By using detailed plans to track progress against milestones, monitor spending, and take corrective actions when necessary.
39
SMART TARGETS
Q: What does the acronym SMART stand for in project target setting?
A: Specific, Measurable, Achievable, Relevant, Time-bound.
40
Q: What does "Specific" mean in SMART targets?
A: The goal must be clear and well-defined to make tracking and assessment easier.
41
Q: What does "Measurable" mean in SMART targets?
A: There must be a way to quantify or measure success or progress toward the goal.
42
Q: What does "Achievable" mean in SMART targets?
A: The goal should be realistic and possible to accomplish, possibly broken into manageable subtasks.
43
Q: What does "Relevant" mean in SMART targets?
A: The goal should align with the overall aims of the project.
44
Q: What does "Time-bound" mean in SMART targets?
A: The goal must have a clear deadline to ensure urgency and focus.
45
**PROJECT MANAGEMENT TOOLS**
Q: Why is project management essential throughout a project’s lifecycle?
A: To carefully plan and monitor timings, task progression, budget, and resource usage.
46
Q: What types of aspects does a project manager monitor using project management tools?
A: Timings, task progression, budget, and resource usage.
47
Types of project management tools
Nodes and Gantt charts
Critical path analysis
Precedence tables
48
NODES AND GANTT CHARTS
What is a node in project management?
A node is a point or milestone in a project schedule or network diagram representing significant events, tasks, or deliverables.
49
What does each node in a project relate to?
A specific and measurable target or objective.
50
What is a Gantt chart?
A visual representation of a project schedule that shows the start and end dates of tasks along a timeline.
51
How are tasks displayed in a Gantt chart?
As horizontal bars along a timeline, positioned according to their start and end dates.
52
What does a Gantt chart help identify in a project?
The sequence of tasks, task dependencies, and which tasks can be completed simultaneously.
53
What additional information might a Gantt chart include?
Task dependencies, milestones, resource assignments, and progress tracking indicators.
54
Requirements
What is the purpose of defining project requirements in project management?
To identify, document, and communicate stakeholder needs and the project's deliverables and outcomes.
55
How are project requirements usually categorized in IT systems?
functional and non-functional requirements.
56
What do functional requirements define in an IT system?
They define exactly what the user should be able to do, detailing the specific functions and features available.
57
What do functional requirements provide for a project?
: The scope of the deliverables.
58
Give an example of a functional requirement for user authentication.
The system must allow users to log in with a username and password, followed by authentication via an authenticator app.
59
Give an example of a functional requirement for reporting.
The system must generate reports detailing user interaction rates for management.
60
Give an example of a functional requirement for inventory management.
The system must track the quantity and location of inventory items.
61
What do non-functional requirements specify?
How the system or product should perform, focusing on quality attributes and constraints.
62
What aspects are typically covered by non-functional requirements?
Performance,
The system must respond to user input within two seconds.
security,
The system must use public key encryption to protect transactions.
usability,
The system interface must be intuitive and accessible to users with disabilities.
reliability,
The system should have an availability of 99.9% during business hours.
scalability.
The system must support spikes in the number of concurrent users without performance loss.
63
CRITICAL PATH ANALYSIS
What is the purpose of critical path analysis in project management?
To identify the sequence of tasks that must be completed on time to meet the overall project deadline.
63
What does critical path analysis help project managers prioritize?
Tasks that are critical to the project and cannot be delayed.
63
To perform a critical path analysis, the project manager must follow these steps
What are they
1. Identify all the individual tasks needed to complete the project.
2. Estimate the time it will take to complete each task (duration).
3. Identify any dependencies between tasks (e.g. back-end database must be completed before
integration testing for the e-store can begin).
4. Present the tasks using a suitable diagram (e.g. Gantt chart, arrow diagram method).
5. Work out the longest sequence of tasks that are dependent on each other - this is the critical path.
64
What might a project manager need to do if delays in critical path tasks can't be resolved by internal adjustments?
Negotiate adjusted timelines with the client or change the project scope.
65
PRECEDENCE TABLES
What is a precedence table used for in project management?
Scheduling and sequencing tasks by showing task order and dependencies.
66
What information does a precedence table typically include?
Task name, dependencies (precedence), duration, early start (ES), early finish (EF), late start (LS).
67
What does "precedence" indicate in a precedence table?
Which tasks must be completed before a specific task can begin.
68
What is the "duration" in a precedence table?
: The estimated time required to complete each task, usually in days.
69
What does "Early Start (ES)" mean in a precedence table?
The earliest point a task can start, considering its dependencies.
70
How is "Early Finish (EF)" calculated in a precedence table?
EF = Early Start (ES) + Duration.
71
What does "Late Start (LS)" represent in a precedence table?
The latest point a task can start without delaying the project.
72
Why are precedence tables helpful for project managers?
They help identify critical tasks, understand dependencies, and improve resource allocation.
73
What is one challenge in creating an accurate precedence table?
Accurately estimating task durations and dependencies.
74
**WATERFALL PROJEСТ МЕТНODOLOGY**
What is the Waterfall methodology in project management?
A sequential, linear approach that divides a project into distinct phases where each must be completed before the next begins.
75
What is the key characteristic of the Waterfall methodology?
Each phase must be completed before moving on to the next, with little room for changes.
76
In what type of projects is the Waterfall methodology most effective?
Small or simple projects with few, clearly defined and stable requirements.
77
Give an example of a project that could use the Waterfall methodology effectively.
Upgrading a server and related network infrastructure in an office.
78
What are the phases of waterfall methodology
Requirements gathering/analysis
System design
Implementation:
Testing
Deployment
Maintenance:
79
REQUIREMENT GATHERING/ANALYSIS PHASE
What does this phase involve
this phase involves analysing the problem and communicating with the key project stakeholders to establish the requirements for the project.
It includes identifying what the system needs to do and any constraints it must operate within.
80
What are the parts of the Requirements gathering/analysis phase
Identify stakeholders
Gather requirements
Collate and analyse gathered requirements
Ensuring quality of gathered data
Gather team
81
Identify stakeholders
Who are the typical stakeholders involved in requirements gathering?
Management (for business goals) and potential users (for specific functionality).
82
Why is stakeholder input essential during the requirements phase?
To ensure the system delivers what is needed for the business and end-users.
83
Gather requirements
: What are some common methods of gathering requirements from stakeholders?
Interviews, surveys/questionnaires, focus groups, observations, and document analysis.
84
METHODS FOR REQUIREMENTS GATHERING
Look at pg 98 of textbook
85
Collate and analyse gathered requirements
What is the purpose of analysing gathered stakeholder requirements?
To identify themes, trends, conflicts, and gaps, ensuring data-driven decisions.
86
Why shouldn't missing requirements be ignored during early analysis?
The absence might result from poor methods, wrong stakeholders, or incomplete data—not because they’re unimportant.
87
key principles that should be followed to ensure the quality of data
select the right stakeholders.
Use a mixture of closed and open questions.
Provide structured questions for interviews so you can make comparisons between interviews.
Select the most appropriate collection method for the targeted group.
88
What is the benefit of using both closed and open questions in requirement gathering?
Closed questions yield measurable data; open questions provide deeper insights.
89
Why is choosing the correct data collection method important?
It ensures the method suits the stakeholder group and gathers accurate, usable information.
90
Gather team
When does the team-gathering phase typically occur in an IT project?
After the project requirements have been established.
91
SYSTEM DESIGN PHASE
What is the main goal of the system design phase in an IT project?
To plan the look, content, and functionality of the system.
92
What are the System design phase activities
User experience design
Wireframing and prototyping
Visual design
Accessibility
Network and system diagrams
Flowcharts
Information flow diagrams
93
User experience design
What is the main focus of User Interface (UI) design?
The look and style of the system and how users interact with it.
94
What does User Experience (UX) design aim to achieve?
Meaningful, usable, and enjoyable user experiences that support system functionality.
95
UX design makes use of some key documents and tasks.
Which are
User personas:
Fictional representations of typical users used to guide design decisions based on user expectations and needs.
Information architecture (IA)
The organisation of content and functionality to support intuitive navigation and access to information.
96
What are common components of Information Architecture?
Site maps, navigation menus, and content hierarchies.
97
Wireframing and prototyping
What are wireframes and prototypes in system design?
Low-fidelity versions of a user interface that show layout, structure, and functionality without final visuals.
98
What is the purpose of using wireframes and prototypes?
To explore design options, gather feedback early, and refine interactions before full implementation.
99
Visual design
What does visual design focus on in the system design phase?
The aesthetics and presentation of the interface, including colours, typography, imagery, and final layout.
100
What are the goals of visual design?
To enhance usability, evoke emotional responses, and reflect brand identity through cohesive visuals.
101
Accessibility
Why is accessibility important in system design?
It ensures the system is usable by people of all abilities, including users with disabilities.
102
How can accessibility be achieved in design?
By designing inclusive or alternative interfaces and following accessibility standards and guidelines.
103
Network and system diagrams
What are network and system diagrams used for in IT projects?
To plan the layout and structure of physical systems, including device placement, cabling, and power outlets.
103
Why are network diagrams important during system design?
They ensure all physical components are correctly planned, reducing installation issues and improving efficiency.
104
Flowcharts
Q: What is a flowchart in system design?
A: A visual diagram that shows the sequence of steps or decisions in a process, algorithm, or system.
105
In a system development methodology flowcharts will typically be used for the following activities:
Documenting existing processes:
Communicating complex processes:
Planning and designing algorithms
UX and UI design:
106
How are flowcharts used to document existing processes?
They capture each step in a process visually, helping developers understand and translate business processes into system functions.
107
Why are flowcharts useful for communicating complex processes?
They simplify detailed processes into visual steps, making them easier to understand for non-technical stakeholders.
108
How are flowcharts used in algorithm planning?
They represent decision points and logic sequences, helping developers design and test algorithms effectively.
109
How can flowcharts support UX and UI design?
By mapping the user journey through a system to identify steps, interactions, and potential usability issues.
110
Information flow diagrams
What is an Information Flow Diagram (IFD)?
A visual representation showing how information moves within and between systems or organisations.
111
IMPLEMENTATION PHASE ACTIVITIES
What is the goal of the implementation phase in system development?
To create the actual IT system based on the previously developed designs.
112
What activities does the implementation involve
Coding:
Translating design documents into working code using defined specifications and standards.
Building computer systems and infrastructure:
Assembling hardware components and devices to support the system.
Database creation:
Designing, populating, and integrating databases to support system functions and business goals.
Interface creation:
User interfaces are built, including accessible and responsive versions for different devices.
113
The main types of testing used are
Unit testing
Integration testing:
System testing:
Acceptance testing:
114
TESTING/DEBUGGING PHASE ACTIVITIES
What is the primary goal of the testing/debugging phase?
To identify issues not caught during implementation and ensure the system meets all functional and non-functional requirements.
115
What is unit testing?
: Testing individual modules or units of code to confirm they perform their specific functions correctly.
116
Q: What is the purpose of integration testing?
A: To verify that combined modules work together and correctly exchange data.
117
Q: What key questions are addressed in integration testing?
Does the system function as new units are added?
Do communicating units share data correctly?
Is shared data accurate and reliable?
118
Q: What is system testing?
A: Full testing of the system against predefined requirements and real-world user needs.
119
Q: What is acceptance testing?
A: Final confirmation from stakeholders or end users that the system is ready for deployment.
120
Q: Why is it important to record all test outcomes?
A: For auditing, quality assurance, and root cause analysis in case of future issues.
121
INSTALLATION PHASE
Q: What is the installation phase in system development?
A: It's when the tested system is migrated and deployed to the target environment and handed over to the client.
122
Q: Where does system development usually take place before installation?
A: In isolated systems owned and operated by the development company.
123
What are the activities of the Installation phase
Installation of physical infrastructure
Set up and configuration of cloud-based infrastructure
Installation and deployment of software components
End-user training
124
Installation of physical infrastructure
Q: What is the first major task if the system uses local, on-premises hardware?
A: The installation of the physical infrastructure.
125
Set up and configuration of cloud-based infrastructure
Q: What is a key task involving cloud infrastructure during installation?
A: Set up and configuration of cloud-based infrastructure.
126
Q: Why might cloud services require less setup during installation?
A: Because many of them will have already been set up during the implementation phase.
127
Q: What must be ensured when integrating new hardware with cloud services?
A: That the hardware is correctly configured to connect to third-party cloud services without issues.
128
Installation and deployment of software components
Q: What happens during the installation and deployment of software components?
A: Newly developed software is installed on the target machines for company use.
129
End-user training
Q: Why is end-user training provided before the system goes live?
A: To ensure stakeholders know how to use the system effectively.
130
Q: How is training usually delivered to stakeholders?
A: Stakeholders are trained in groups based on the specific areas of the system they will use.
131
Q: What kind of training do in-house IT support staff receive?
A: Broader training covering overall system functionality and basic troubleshooting.
132
MAINTENANCE PHASE ACTIVITIES
Q: What is the focus of the maintenance phase immediately after deployment?
A: Identifying and resolving any issues or bugs not caught during testing.
133
Q: What is the primary long-term goal of the maintenance phase?
A: Ensuring the system continues to meet user and business needs as they evolve.
134
key activities during maintenance phase
Bug fixing:
involves analysing and prioritising reported issues based on severity and business impact.
Performance optimisation:
Improving system efficiency and productivity even when it is already functioning correctly.
Security updates:
security updates are essential during maintenance To protect the system from new and evolving security threats by applying patches and updates.
New feature implementation:
It saves time and money compared to building a new system and reduces the training burden on users.
Documentation updates:
To reflect changes and new features, ensuring users and technicians have accurate and current information.
135
**AGILE PROJECT METHODOLOGY
Q: What is the Agile project methodology focused on?
A: Continuous and rapid improvements to a system through small, manageable updates.
136
Q: How does Agile differ from Waterfall in terms of delivering systems?
A: Agile delivers usable systems to end users sooner with fewer initial features, whereas Waterfall delivers everything at once at the end.
137
Q: What are the two key concepts that Agile is based on?
A: Iterative and Incremental development.
138
Q: What does iterative development mean in Agile?
A: Constantly reviewing and improving the system’s features, functions, and quality throughout the project.
139
Q: What does incremental development mean in Agile?
A: Adding small improvements and new features gradually over time.
140
Q: What type of projects is Agile best suited for?
A: Large, complex projects that may have changing requirements.
141
What are the Benefits of using an agile approach
1. Faster time to market
working systems are delivered much sooner with fewer features.
2. increased flexibility
by allowing small, frequent changes without restarting the whole project.
3. Improved product quality:
continuous feedback, testing, and refinement, and by limiting the number of changes per iteration.
4. Increased team morale:
encourages collaboration and teamwork, leading to more engaged and motivated teams.
142
What are the Challenges of using an agile approach
1. Requires cultural change
2. uncertain timelines
each iteration's focus depends on real-time feedback, making the future scope unclear.
3. Requires strong communication and collaboration:
143
PHASES OF AN AGILE APPROACH
The main phases of each iteration in agile development are
Requirements:
Plan:
Design
Develop:
Release:
144
Q: What happens during the Requirements phase in Agile?
A: Overall requirements are defined at the start, then revisited and refined at the beginning of each iteration.
145
Q: What is the focus of the Plan phase in each Agile iteration?
A: Specific plans are made for each cycle, detailing features and functionalities to be delivered.
146
Q: How is design handled in Agile?
A: Agile uses just-in-time design based on user-centred principles, only designing what's needed for the next iteration.
147
Q: What is the goal of the Develop phase in Agile?
A: To make small, incremental changes identified in that iteration’s requirements and plans.
148
Q: What happens in the Release phase of Agile?
A: The new iteration is released to users, monitored, reviewed, and then the cycle repeats.
149
KEY ACTIVITIES IN AN AGILE APPROACH
What are they
scrum
sprint
150
Scrum
What is the main purpose of sprint planning in Scrum?
To define the goals, tasks, and deliverables for the upcoming sprint and commit to specific backlog items.
151
A scrum typically covers the following four key events/activities that inform the development.
What are they
1. Sprint planning
defines the goals and tasks for the upcoming sprint.
2. Daily scrum
Team members share what they did yesterday, what they'll do today, and any blockers they face. It promotes communication and collaboration.
3. Sprint review
To demonstrate the work completed during the sprint, gather stakeholder feedback, and assess whether sprint goals were met.
4. Sprint retrospective
to reflect on the past sprint and identify areas of improvement for future sprints.
152
Sprints
What is a sprint in Agill
sprint is a short, time-boxed development cycle in Agile, usually lasting between 1 and 4 weeks.
It focuses on delivering small, incremental improvements.
While it allows rapid deployment of high-quality systems, it requires careful management and can be demanding for developers.
153
INFORMATION FLOW DIAGRAMS
What is an Information Flow Diagram (IFD) used for?
Information flow diagrams (IFDs) are visual representations that show how information travels
within and between systems, organisations and processes.
154
What are the four main components of an IFD?
Entities – Data sources or destinations (e.g. customers, databases).
Flows – Arrows showing the direction of information.
Processes – Boxes showing data transformations.
Decisions – Diamonds representing conditional logic in data flow.
155
What are the three levels of IFDs and what do they represent?
Context (Level 0): High-level overview showing the system and external interactions.
Level 1: Detailed view focusing on major subsystems and flows.
Level 2: Highly detailed view of specific processes and data handling.
