Texas College of Management and IT

Software Project
Management
Explore, Learn and Excel

Assignment 2

Submitted By: Submitted To:

Name: Smith Yando Department Of IT

Program: BIT
Sections: A
Date: 9/9/2024
1. List three main types of risk. Explain Boehm’s risk engineering task breakdown structure.

Three main types of risk:

1. Technical risks – These arise from technology-related issues. For example, the software
might not function as planned, or the technology used could be outdated or not well understood.

2. Cost risks – This happens when the project goes over budget. Unexpected expenses, poor
estimation of costs, or delays in the project can lead to higher costs.

3. Schedule risks – These occur when the project doesn’t meet its deadlines. Delays could
happen due to technical issues, team unavailability, or scope changes.

Boehm’s Risk Engineering Task Breakdown Structure:

Barry Boehm created a framework for managing risks in software development. Here’s how it
works:

- Risk Identification: First, the team needs to figure out what could go wrong in the
project. For example, risks related to technology, time, or resources.

- Risk Analysis: After identifying risks, the next step is to assess how likely they are to
happen and how serious their impact will be.

- Risk Management Planning: The team then comes up with a plan to manage or reduce the
risks. For example, using alternative technologies if the chosen one doesn’t work.

- Risk Resolution: The team takes action to prevent risks or minimize their impact when
they occur.

- Risk Monitoring: The team continuously watches for risks throughout the project,
making sure any new risks are addressed.

2. What is the importance of software quality? Explain EMM.

Software quality is crucial because it directly affects how well the software performs and how
satisfied users will be. High-quality software has fewer bugs, performs better, and is more
secure. It ensures that the software meets the user's needs, which leads to happier customers,
fewer complaints, and fewer costly fixes down the road. For businesses, maintaining highquality
software also means staying competitive.

EMM (Execution Maturity Model):

The Execution Maturity Model (EMM) is a tool that helps organizations evaluate how mature
their processes are in software development. It helps them understand their current capabilities
and what they need to improve. The EMM defines different levels of maturity:

- Level 1: Initial, where processes are chaotic or unstructured.

- Level 2: Managed, where processes are more organized and planned.

- Level 3: Defined, where processes are standardized and documented.

- Level 4: Quantitatively Managed, where the company measures and monitors processes.

- Level 5: Optimizing, where the company continuously improves its processes for better results.

3. Draw a precedence network diagram for the following and identify the critical path.

Activity Duration (weeks) Precedence

B 3 A

C 5 A

D 10 B, C

Precedence Network Diagram:

The network diagram shows the sequence in which activities should be completed. In this case:

- Activity A has no preceding activities, so it starts first.

- Once A is completed, B and C can start.

- Activity D can only begin after both B and C are done.

Critical Path: The critical path is the longest path through the network, representing the shortest
time in which the project can be completed. The critical path for this project is A → C → D,
which takes 5 + 5 + 10 = 20 weeks. Any delay on this path will delay the whole project.

4. Suppose you have been assigned to develop an online voting system. List four risks that
might affect the success of the system.

1. Security risks – Online voting systems are vulnerable to cyberattacks, such as hacking or data
breaches, which could compromise the voting process.
2. Data loss – If the system crashes or the data storage fails, votes could be lost, which would
undermine the entire election.

3. User errors – Voters might not be familiar with the online system and could make mistakes
during voting, such as casting the wrong vote or not completing their vote correctly.

4. System downtime – The system could experience technical issues or overload due to high
traffic on voting day, preventing people from voting on time.

5. Calculate ROI for the following project.

Year Project Cost/Income

0 -50,000 (Initial Investment)

1 5,000

2 5,000

3 20,000

4 40,000

5 50,000

ROI (Return on Investment) is a measure of how much profit is made compared to the initial
investment. The formula is:

ROI= (Total Gains−Initial Investment)/ Initial Investment ×100

- Total Gains over 5 years = 5,000 + 5,000 + 20,000 + 40,000 + 50,000 = 120,000

- Initial Investment = 50,000

Now, applying the formula:

ROI= ((120,000−50,000)/ 50,000)×100=140%

This means the project returned 140% of the initial investment.

6. Why PERT chart is a technique? Explain the estimated time, standard deviation, and z value
for a PERT chart.

Why PERT is a technique?

The PERT (Program Evaluation Review Technique) chart is a project management tool that
helps to estimate the time needed to complete a project. It is useful for projects where the time
required to complete different tasks is uncertain. PERT allows you to calculate the probability of
completing a project on time by factoring in various time estimates.

Estimated Time: PERT uses three time estimates:

- Optimistic Time (O): The best-case scenario, where everything goes smoothly.

- Pessimistic Time (P): The worst-case scenario, where everything goes wrong.
- Most Likely Time (M): The most realistic estimate.

The formula to calculate the estimated time is:

Estimated Time=(O+4M+P)/6

Standard Deviation: This measures the uncertainty in the time estimates. It tells you how much
variation there is from the estimated time.

Z-value: The z-value is used in PERT to calculate the probability of completing the project
within a given time frame. It helps project managers understand the risk of delays.

7. Explain the difference between verification and validation in the context of software testing.

- Verification: This is the process of ensuring that the software is being built correctly
according to the design and specifications. It's like asking, “Are we building the product right?”
Verification involves activities like code reviews, inspections, and testing during development to
ensure everything is done according to the plan.

- Validation: This ensures that the right software is being built to meet the user’s needs. It’s
like asking, “Are we building the right product?” Validation is done after the software is
developed, usually through testing with actual users or stakeholders, to make sure it does what
they expect.

8. Explain the concept of software estimation technique and their role in project management.

Software Estimation Techniques help project managers predict how long and how much effort a
software project will take. These techniques are vital because they allow teams to plan
resources, budget, and timelines. Without good estimates, projects might run over budget or take
much longer than expected.

Common estimation techniques include:

- Expert Judgment: Experienced team members give their best guess on how long a task
will take based on their previous experiences.

- Analogous Estimation: Using data from past similar projects to estimate the time and cost
for the new project.

- Function Point Analysis: A more formal method where the complexity of the software’s
functionality is measured to estimate effort.

9. Which model of cost estimation technique is most appropriate to use?

The COCOMO (Constructive Cost Model) is one of the most popular cost estimation techniques
for software projects. It’s appropriate because it uses different factors like project size,
complexity, and team experience to estimate how much effort and time will be required.
COCOMO adjusts the cost based on various project attributes, making it flexible for different
kinds of software projects.
10. Explain the relationship between software quality and customer satisfaction.

There is a strong relationship between software quality and customer satisfaction. When
software is of high quality, it:

- Works efficiently and performs as expected.

- Has fewer bugs and issues, leading to a smoother experience for users.

- Is secure, meaning users trust the software to protect their data.

- Is user-friendly, so customers can easily use it without confusion.

When software quality is poor, users may experience crashes, slow performance, or security
issues, which can lead to frustration. High-quality software leads to higher customer satisfaction
because users are more likely to have a positive experience.