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

Step 1: Given Data

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}$

Project duration (EF of E) = 13 weeks

Step 4: Backward Pass (LF, LS)

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

Step 5: Slack / Float

$\text{Slack} = LS - ES$

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.

Model Answer: Contract and Contract Management Process

What is a Contract?

A contract is a legally binding agreement between two or more parties that establishes mutual obligations and rights. In the context of software engineering and IT projects, a contract specifies:

• Deliverables: What products or services will be provided
• Terms and conditions: Payment, timeline, and performance standards
• Responsibilities: Duties of each party
• Legal enforceability: Consequences for breach or non-compliance

Contracts form the foundation of formal agreements between clients and service providers, ensuring clarity and protection for all parties involved.

Contract Management Process

The contract management process typically involves the following phases:

1. Contract Planning

• Identify the need for a contract
• Define scope, objectives, and requirements
• Determine contract type (fixed-price, time-and-materials, etc.)
• Establish success criteria and performance metrics

2. Contract Development

• Draft contract terms and conditions
• Include detailed specifications and deliverables
• Define payment schedules and milestones
• Specify roles, responsibilities, and timelines
• Include risk allocation and dispute resolution clauses

3. Contract Review and Negotiation

• Review contract by legal and technical teams
• Negotiate terms with the other party
• Resolve conflicts and ambiguities
• Obtain necessary approvals from stakeholders

4. Contract Execution

• Finalize and sign the contract by authorized representatives
• Distribute copies to all relevant parties
• Establish baseline documentation and records

5. Contract Monitoring and Control

• Track deliverables against agreed specifications
• Monitor timelines and milestones
• Manage changes through formal change control procedures
• Ensure compliance with contract terms
• Document performance metrics and issues

6. Contract Closure

• Verify all deliverables have been completed
• Conduct final acceptance testing
• Process final payments
• Archive contract documentation
• Conduct post-project review and lessons learned

Key Point: Effective contract management ensures mutual understanding, reduces disputes, and facilitates successful project completion.