Draw activity-on-arrow diagram for the above scenario and find the critical path. Project Activities Duration (Week) Precedence --------- A 2 B 3 A C 4 A D 5 B, C E 2 D [10]

Activity Duration (weeks) Predecessor ----------------------------------------- A 2 - B 3 A C 4 A D 5 B, C E 2 D Nodes (events) are numbered; arrows are activities. - Node 1: Start - A runs from Node 1 → Node 2 - After A, both B and C start from Node 2 - B and C both must finish before D. So B: 2...

BIT402 · Exam intelligence

Software Project Management important questions

From 4 past TU papers: which questions keep coming back, how much they carry, and what is most likely to show up next. Every question links to a model answer.

Most likely Most repeated

Most likely in the next examStatistical

Ranked by how often a topic is asked, its marks weight, and whether it is due after skipping the 2082 paper. No guarantees; study the whole syllabus.

1asked 3xavg 5 marks · due (skipped 2082) · Software quality enhancement techniques

Answer

How software quality can be enhanced? Explain. [5]

Model Answer: How Software Quality Can Be Enhanced

Software quality can be enhanced through systematic approaches and practices applied throughout the software development lifecycle. Here are the key methods:

1. Requirements Analysis and Specification

Clearly define and document all functional and non-functional requirements
Ensure requirements are complete, unambiguous, and testable
Validate requirements with stakeholders to prevent misunderstandings that lead to defects

2. Design Quality

Follow established design principles and patterns
Create modular, maintainable architecture
Conduct design reviews before implementation begins
Ensure proper separation of concerns and low coupling

3. Code Quality Practices

Follow coding standards and conventions
Write clean, readable, and well-documented code
Conduct code reviews by peers
Use static analysis tools to detect potential issues early

4. Testing and Verification

Implement comprehensive testing at multiple levels:
- Unit testing (individual components)
- Integration testing (component interactions)
- System testing (complete system)
- User acceptance testing (UAT)
Automate test cases for regression testing
Achieve adequate code coverage

5. Quality Assurance (QA) Activities

Establish QA processes and standards
Perform inspections and walkthroughs
Use metrics to measure quality attributes
Monitor defect rates and trends

6. Configuration Management

Maintain version control of all artifacts
Track changes systematically
Manage releases properly

7. Continuous Improvement

Collect and analyze defect data
Implement lessons learned
Refine processes based on feedback

These combined approaches ensure software meets user expectations, performs reliably, and is maintainable throughout its lifecycle.

2asked 2xavg 10 marks · due (skipped 2082) · Critical path and critical activities

Answer

Draw activity-on-arrow diagram for the above scenario and find the critical path.

Project Activities	Duration (Week)	Precedence
A	2
B	3	A
C	4	A
D	5	B, C
E	2	D

[10]

Activity-on-Arrow (AOA) Diagram and Critical Path

Step 1: Given Data

Activity	Duration (weeks)	Predecessor
A	2	-
B	3	A
C	4	A
D	5	B, C
E	2	D

Step 2: Build the AOA Network

Nodes (events) are numbered; arrows are activities.

Node 1: Start
A runs from Node 1 → Node 2
After A, both B and C start from Node 2
B and C both must finish before D. So B: 2 → 3 and C: 2 → 3 (both merge at Node 3)
D runs from Node 3 → Node 4
E runs from Node 4 → Node 5 (End)

            B(3)
        ┌──────────┐
        ↓          │
(1)──A(2)──►(2)     ├──►(3)──D(5)──►(4)──E(2)──►(5)
        │          ↑
        └──────────┘
            C(4)

Since B and C share the same start (Node 2) and end (Node 3), a dummy activity is technically required to keep unique identification in strict AOA notation:

(1) --A(2)--> (2) --B(3)--> (3)
                 \          ^
                  C(4)      | dummy(0)
                   \        |
                    v       |
                    (3')----+
                    |
                    D(5)
                    v
                   (4) --E(2)--> (5)

For simplicity the merge is shown at Node 3.

Step 3: Forward Pass (ES, EF)

$EF = ES + \text{Duration}$

Activity	Duration	ES	EF
A	2	0	2
B	3	2	5
C	4	2	6
D	5	$\max(5,6)=6$	11
E	2	11	13

Project duration (EF of E) = 13 weeks

Step 4: Backward Pass (LF, LS)

$LS = LF - \text{Duration}$ , starting from $LF_E = 13$

Activity	Duration	LF	LS
E	2	13	11
D	5	11	6
B	3	6	3
C	4	6	2
A	2	2	0

Step 5: Slack / Float

$\text{Slack} = LS - ES$

Activity	ES	LS	Slack	Critical?
A	0	0	0	Yes
B	2	3	1	No
C	2	2	0	Yes
D	6	6	0	Yes
E	11	11	0	Yes

Step 6: Critical Path

Activities with zero slack: A, C, D, E

$\boxed{\text{Critical Path: } A \to C \to D \to E}$

Total Project Duration $= 2 + 4 + 5 + 2 = 13$ weeks

Any delay in A, C, D, or E delays the whole project. Activity B has 1 week of float.

Activity-on-Arrow (AOA) Diagram and Critical Path

Step 1: Given Data

Activity	Duration (weeks)	Predecessor
A	2	-
B	3	A
C	4	A
D	5	B, C
E	2	D

Step 2: Build the AOA Network

Nodes (events) are numbered; arrows are activities.

Node 1: Start
A runs from Node 1 → Node 2
After A, both B and C start from Node 2
B and C both must finish before D. So B: 2 → 3 and C: 2 → 3 (both merge at Node 3)
D runs from Node 3 → Node 4
E runs from Node 4 → Node 5 (End)

            B(3)
        ┌──────────┐
        ↓          │
(1)──A(2)──►(2)     ├──►(3)──D(5)──►(4)──E(2)──►(5)
        │          ↑
        └──────────┘
            C(4)

Since B and C share the same start (Node 2) and end (Node 3), a dummy activity is technically required to keep unique identification in strict AOA notation:

(1) --A(2)--> (2) --B(3)--> (3)
                 \          ^
                  C(4)      | dummy(0)
                   \        |
                    v       |
                    (3')----+
                    |
                    D(5)
                    v
                   (4) --E(2)--> (5)

For simplicity the merge is shown at Node 3.

Step 3: Forward Pass (ES, EF)

$EF = ES + \text{Duration}$

Activity	Duration	ES	EF
A	2	0	2
B	3	2	5
C	4	2	6
D	5	$\max(5,6)=6$	11
E	2	11	13

Project duration (EF of E) = 13 weeks

Step 4: Backward Pass (LF, LS)

$LS = LF - \text{Duration}$, starting from $LF_E = 13$

Activity	Duration	LF	LS
E	2	13	11
D	5	11	6
B	3	6	3
C	4	6	2
A	2	2	0

Step 5: Slack / Float

$\text{Slack} = LS - ES$

Activity	ES	LS	Slack	Critical?
A	0	0	0	Yes
B	2	3	1	No
C	2	2	0	Yes
D	6	6	0	Yes
E	11	11	0	Yes

Step 6: Critical Path

Activities with zero slack: A, C, D, E

$$\boxed{\text{Critical Path: } A \to C \to D \to E}$$

Total Project Duration $= 2 + 4 + 5 + 2 = 13$ weeks

Any delay in A, C, D, or E delays the whole project. Activity B has 1 week of float.

3asked 2xavg 5 marks · due (skipped 2082) · Leadership importance and styles

Answer

Explain different leadership styles. [5]

Leader makes decisions unilaterally without consulting team members - Strict control over work processes and outcomes - Clear rules and procedures are established - Suitable for: Urgent situations, routine tasks, inexperienced teams - ...

4asked 2xavg 10 marks · COCOMO II model and stages

Answer

Why estimation has to be carried out? Describe different stages of COCOMO II model.[10]

Estimation is a critical activity in software project management for the following reasons: 1. Project Planning & Scheduling - Determines realistic timelines and milestones - Helps allocate resources effectively across project phases - E...

5asked 2xavg 8 marks · Estimation models overview

Answer

List estimation models. Explain estimation by analogy with example. [5]

Estimation Models - Model Answer

List of Estimation Models

The main estimation models used in software project estimation are:

Algorithmic/Parametric Models
- COCOMO (Constructive Cost Model)
- SLIM (Software Lifecycle Management)
- Function Point Analysis
Expert Judgment Models
- Delphi Technique
- Planning Poker
- Expert Opinion
Analogy-Based Models
- Estimation by Analogy
- Case-Based Reasoning
Machine Learning Models
- Neural Networks
- Regression Analysis
Hybrid Models
- Combination of multiple approaches

Estimation by Analogy - Explanation with Example

Definition

Estimation by analogy is a technique where project effort/cost is estimated by comparing the current project with similar completed projects from historical data. The estimation is based on the assumption that similar projects will require similar effort and resources.

Process

Identify completed projects with similar characteristics
Find the closest match(es) from historical records
Adjust estimates based on differences between current and past projects
Use the adjusted values as estimates for the current project

Example

Scenario: Estimating effort for a new e-commerce website project.

Historical Project (Completed):

Similar e-commerce website built 6 months ago
Size: 50,000 lines of code
Team: 5 developers
Effort: 2,000 person-hours
Duration: 4 months

Current Project:

New e-commerce website
Estimated Size: 60,000 lines of code (20% larger)
Similar technology stack
Similar complexity

Estimation:

Base estimate from analogy: 2,000 person-hours
Adjustment factor for 20% larger size: 1.2
Estimated effort = 2,000 × 1.2 = 2,400 person-hours
Estimated duration ≈ 4.8 months (approximately 5 months)

Advantages

Simple and intuitive
Based on real project data
Quick estimation process

Limitations

Requires good historical data
Difficult to find truly similar projects
Subjective adjustment factors

Most repeated questions

Topics asked at least twice, most-asked first.

asked 3xavg 5 marks · 2081, 2080, 0

Answer

How software quality can be enhanced? Explain. [5]

Model Answer: How Software Quality Can Be Enhanced

Software quality can be enhanced through systematic approaches and practices applied throughout the software development lifecycle. Here are the key methods:

1. Requirements Analysis and Specification

Clearly define and document all functional and non-functional requirements
Ensure requirements are complete, unambiguous, and testable
Validate requirements with stakeholders to prevent misunderstandings that lead to defects

2. Design Quality

Follow established design principles and patterns
Create modular, maintainable architecture
Conduct design reviews before implementation begins
Ensure proper separation of concerns and low coupling

3. Code Quality Practices

Follow coding standards and conventions
Write clean, readable, and well-documented code
Conduct code reviews by peers
Use static analysis tools to detect potential issues early

4. Testing and Verification

Implement comprehensive testing at multiple levels:
- Unit testing (individual components)
- Integration testing (component interactions)
- System testing (complete system)
- User acceptance testing (UAT)
Automate test cases for regression testing
Achieve adequate code coverage

5. Quality Assurance (QA) Activities

Establish QA processes and standards
Perform inspections and walkthroughs
Use metrics to measure quality attributes
Monitor defect rates and trends

6. Configuration Management

Maintain version control of all artifacts
Track changes systematically
Manage releases properly

7. Continuous Improvement

Collect and analyze defect data
Implement lessons learned
Refine processes based on feedback

These combined approaches ensure software meets user expectations, performs reliably, and is maintainable throughout its lifecycle.

asked 2xavg 10 marks · 2080, 0

Answer

Draw activity-on-arrow diagram for the above scenario and find the critical path.

Project Activities	Duration (Week)	Precedence
A	2
B	3	A
C	4	A
D	5	B, C
E	2	D

[10]

Activity-on-Arrow (AOA) Diagram and Critical Path

Step 1: Given Data

Activity	Duration (weeks)	Predecessor
A	2	-
B	3	A
C	4	A
D	5	B, C
E	2	D

Step 2: Build the AOA Network

Nodes (events) are numbered; arrows are activities.

Node 1: Start
A runs from Node 1 → Node 2
After A, both B and C start from Node 2
B and C both must finish before D. So B: 2 → 3 and C: 2 → 3 (both merge at Node 3)
D runs from Node 3 → Node 4
E runs from Node 4 → Node 5 (End)

            B(3)
        ┌──────────┐
        ↓          │
(1)──A(2)──►(2)     ├──►(3)──D(5)──►(4)──E(2)──►(5)
        │          ↑
        └──────────┘
            C(4)

Since B and C share the same start (Node 2) and end (Node 3), a dummy activity is technically required to keep unique identification in strict AOA notation:

(1) --A(2)--> (2) --B(3)--> (3)
                 \          ^
                  C(4)      | dummy(0)
                   \        |
                    v       |
                    (3')----+
                    |
                    D(5)
                    v
                   (4) --E(2)--> (5)

For simplicity the merge is shown at Node 3.

Step 3: Forward Pass (ES, EF)

$EF = ES + \text{Duration}$

Activity	Duration	ES	EF
A	2	0	2
B	3	2	5
C	4	2	6
D	5	$\max(5,6)=6$	11
E	2	11	13

Project duration (EF of E) = 13 weeks

Step 4: Backward Pass (LF, LS)

$LS = LF - \text{Duration}$ , starting from $LF_E = 13$

Activity	Duration	LF	LS
E	2	13	11
D	5	11	6
B	3	6	3
C	4	6	2
A	2	2	0

Step 5: Slack / Float

$\text{Slack} = LS - ES$

Activity	ES	LS	Slack	Critical?
A	0	0	0	Yes
B	2	3	1	No
C	2	2	0	Yes
D	6	6	0	Yes
E	11	11	0	Yes

Step 6: Critical Path

Activities with zero slack: A, C, D, E

$\boxed{\text{Critical Path: } A \to C \to D \to E}$

Total Project Duration $= 2 + 4 + 5 + 2 = 13$ weeks

Any delay in A, C, D, or E delays the whole project. Activity B has 1 week of float.

Activity-on-Arrow (AOA) Diagram and Critical Path

Step 1: Given Data

Activity	Duration (weeks)	Predecessor
A	2	-
B	3	A
C	4	A
D	5	B, C
E	2	D

Step 2: Build the AOA Network

Nodes (events) are numbered; arrows are activities.

Node 1: Start
A runs from Node 1 → Node 2
After A, both B and C start from Node 2
B and C both must finish before D. So B: 2 → 3 and C: 2 → 3 (both merge at Node 3)
D runs from Node 3 → Node 4
E runs from Node 4 → Node 5 (End)

            B(3)
        ┌──────────┐
        ↓          │
(1)──A(2)──►(2)     ├──►(3)──D(5)──►(4)──E(2)──►(5)
        │          ↑
        └──────────┘
            C(4)

Since B and C share the same start (Node 2) and end (Node 3), a dummy activity is technically required to keep unique identification in strict AOA notation:

(1) --A(2)--> (2) --B(3)--> (3)
                 \          ^
                  C(4)      | dummy(0)
                   \        |
                    v       |
                    (3')----+
                    |
                    D(5)
                    v
                   (4) --E(2)--> (5)

For simplicity the merge is shown at Node 3.

Step 3: Forward Pass (ES, EF)

$EF = ES + \text{Duration}$

Activity	Duration	ES	EF
A	2	0	2
B	3	2	5
C	4	2	6
D	5	$\max(5,6)=6$	11
E	2	11	13

Project duration (EF of E) = 13 weeks

Step 4: Backward Pass (LF, LS)

$LS = LF - \text{Duration}$, starting from $LF_E = 13$

Activity	Duration	LF	LS
E	2	13	11
D	5	11	6
B	3	6	3
C	4	6	2
A	2	2	0

Step 5: Slack / Float

$\text{Slack} = LS - ES$

Activity	ES	LS	Slack	Critical?
A	0	0	0	Yes
B	2	3	1	No
C	2	2	0	Yes
D	6	6	0	Yes
E	11	11	0	Yes

Step 6: Critical Path

Activities with zero slack: A, C, D, E

$$\boxed{\text{Critical Path: } A \to C \to D \to E}$$

Total Project Duration $= 2 + 4 + 5 + 2 = 13$ weeks

Any delay in A, C, D, or E delays the whole project. Activity B has 1 week of float.

asked 2xavg 5 marks · 2081, 0

Answer

Explain different leadership styles. [5]

Leader makes decisions unilaterally without consulting team members - Strict control over work processes and outcomes - Clear rules and procedures are established - Suitable for: Urgent situations, routine tasks, inexperienced teams - ...

asked 2xavg 10 marks · 2082, 2080

Answer

Why estimation has to be carried out? Describe different stages of COCOMO II model.[10]

asked 2xavg 8 marks · 2082, 0

Answer

List estimation models. Explain estimation by analogy with example. [5]

Estimation Models - Model Answer

List of Estimation Models

The main estimation models used in software project estimation are:

Algorithmic/Parametric Models
- COCOMO (Constructive Cost Model)
- SLIM (Software Lifecycle Management)
- Function Point Analysis
Expert Judgment Models
- Delphi Technique
- Planning Poker
- Expert Opinion
Analogy-Based Models
- Estimation by Analogy
- Case-Based Reasoning
Machine Learning Models
- Neural Networks
- Regression Analysis
Hybrid Models
- Combination of multiple approaches

Estimation by Analogy - Explanation with Example

Definition

Process

Identify completed projects with similar characteristics
Find the closest match(es) from historical records
Adjust estimates based on differences between current and past projects
Use the adjusted values as estimates for the current project

Example

Scenario: Estimating effort for a new e-commerce website project.

Historical Project (Completed):

Similar e-commerce website built 6 months ago
Size: 50,000 lines of code
Team: 5 developers
Effort: 2,000 person-hours
Duration: 4 months

Current Project:

New e-commerce website
Estimated Size: 60,000 lines of code (20% larger)
Similar technology stack
Similar complexity

Estimation:

Base estimate from analogy: 2,000 person-hours
Adjustment factor for 20% larger size: 1.2
Estimated effort = 2,000 × 1.2 = 2,400 person-hours
Estimated duration ≈ 4.8 months (approximately 5 months)

Advantages

Simple and intuitive
Based on real project data
Quick estimation process

Limitations

Requires good historical data
Difficult to find truly similar projects
Subjective adjustment factors

asked 2xavg 5 marks · 2082, 2081

Answer

Why do you think resource histogram equalization is necessary? Explain with example. [5]

Resource histogram equalization is necessary for the following reasons: Resource histograms reveal periods where resource demand exceeds availability. Equalization helps identify these critical bottlenecks early in project planning, allo...

Shortcuts

Study BIT402 Past questions Full syllabus Your progress

Keep studying

Study BIT402

Answers, flashcards and MCQs

Past papers

Solved papers by year

NoteTok feed

Quick video explainers

Study every one of these with model answers, flashcards, and MCQs.

Open BIT402 study modes