THEORY EXAMINATION (SEM–VI) 2016-17 SOFTWARE PROJECT MANAGEMENT

SOFTWARE PROJECT MANAGEMENT (EIT601)

Section-wise Solved Answers & Notes

SECTION – A (10 × 2 = 20 Marks)

Very short & precise answers

(a) SPM Framework

The Software Project Management framework includes planning, scheduling, risk management, quality assurance, monitoring, and control to ensure successful project completion.

(b) Project Scope (with example)

Project scope defines boundaries, deliverables, features, and limitations of a project.
Example: Developing an online examination system excluding mobile app support.

(c) Authorities of a Project Manager

• Resource allocation                                       • Task assignment
• Decision making                                            • Schedule control
• Risk handling                                                 • Client coordination

(d) PERT vs CPM

(e) Steps of software development

Requirement analysis                                        Design

Coding                                                               Testing

Deployment                                                       Maintenance

(f) Cost Benefit Analysis

Cost Benefit Analysis compares total expected costs with expected benefits to determine project feasibility.

(g) Software Configuration Management (SCM)

SCM is the process of tracking, controlling, and managing changes in software artifacts throughout the project life cycle.

(h) Unit testing vs System testing

(i) Code Inspection

Code inspection is a formal review process to detect errors, improve quality, and ensure standards compliance without executing the code.

(j) Change control vs Version control

SECTION – B (Attempt Any Five) (5 × 10 = 50 Marks)

(a) Stepwise Planning of Software Project          Stepwise planning includes:

Define project objectives                                    Identify deliverables

Estimate size & effort                                         Identify risks

Create schedule                                                  Allocate resources

Review & refine plan

It ensures controlled and systematic development.

(b) Work Breakdown Structure (WBS)

WBS is a hierarchical decomposition of project work into manageable components.

Example:     Software Project
→ Requirement Analysis                                         → Design
→ Coding                                                                → Testing
→ Deployment

Benefits:                                                                • Better planning
• Accurate estimation                                             • Clear responsibility

(c) Types of Risks in Software Development          • Project Risks: Schedule delay, cost overrun
• Technical Risks: New technology, performance issues
• Business Risks: Market failure, client changes

(d) Testing Strategies (with examples)                    • Unit Testing – testing login module
• Integration Testing – testing login + database  • System Testing – full application testing
• Acceptance Testing – client approval testing

(e) Verification vs Validation

(f) COCOMO Model                                               COCOMO estimates effort, cost, and schedule.

Types:
• Basic COCOMO                                                   • Intermediate COCOMO
• Detailed COCOMO

Effort equation:

Effort=a×(KLOC)bEffort = a \times (KLOC)^bEffort=a×(KLOC)b 

(g) Project Monitoring & Control

Monitoring ensures project is on track, while control involves corrective actions.

Dimensions:
• Cost control                                                         • Schedule control
• Quality control                                                     • Scope control

(h) Preparing Project Schedule

Steps:                                                                     Identify activities

Estimate duration                                                   Sequence activities

Assign resources                                                     Develop schedule

Inputs:
• WBS                                                                     • Resource availability

Outputs:
• Project timeline                                                   • Milestones

SECTION – C (Attempt Any Two) (2 × 15 = 30 Marks)

Q3. Earned Value Analysis (EVA)

EVA measures project performance using cost and schedule.

(i) Cost Variance (CV)                                             CV=EV−ACCV = EV - ACCV=EV−AC

Positive → Under budget                                       Negative → Over budget

(ii) Schedule Performance Index (SPI)                    SPI=EVPVSPI = \frac{EV}{PV}SPI=PVEV​

SPI < 1 → Behind schedule

(iii) Cost Performance Index (CPI)                          CPI=EVACCPI = \frac{EV}{AC}CPI=ACEV​

CPI < 1 → Cost overrun

Q4.

(i) Software Quality Attributes

• Reliability                                                             • Maintainability
• Efficiency                                                              • Usability
• Portability                                                             • Security

(ii) SEI-CMM

Capability Maturity Model evaluates process maturity.

Levels:                                                                       Initial

Repeatable                                                                Defined

Managed                                                                   Optimizing

Q5. Software Project Management Tools

• Project Planning Tools: MS Project                   • Scheduling Tools: Gantt charts, PERT
• Risk Management Tools: Risk register              • Configuration Tools: Git, SVN
• Quality Tools: Review checklists                         • Monitoring Tools: EVA dashboards

These tools improve planning, control, and quality.