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

SECTION A – Basic Concepts of Software Project Management

Section A contains short conceptual questions related to project planning, testing, configuration management, and project management techniques. These questions test fundamental knowledge of Software Project Management. 

Question (a): Explain the SPM Framework

Answer:
The Software Project Management (SPM) framework provides a structured approach to planning, organizing, executing, and controlling software development projects.

The framework includes several components:

Project Planning – defining goals, resources, schedule, and scope of the project.

Project Monitoring – tracking progress and ensuring work is proceeding according to plan.

Risk Management – identifying possible risks and preparing strategies to handle them.

Quality Management – ensuring the software meets required standards and specifications.

Project Closure – completing the project and delivering the final product.

The SPM framework helps ensure that software projects are completed on time, within budget, and with high quality.

Question (b): Explain Project Scope with Example

Answer:
Project scope defines the boundaries and objectives of a project. It specifies what will be included in the project and what will not be included.

The scope describes:

Project goals

Deliverables

Tasks and responsibilities

Timeline

Resources required

Example:
Suppose a company is developing a mobile banking application.

The project scope may include:

User login and authentication

Account balance viewing

Fund transfer feature

Transaction history

However, the scope may exclude features like loan processing or insurance services.

Clearly defining the scope prevents confusion and helps control project costs and timelines.

Question (c): Authorities of a Project Manager

Answer:
A project manager is responsible for planning, executing, and completing a project successfully.

Key authorities of a project manager include:

Allocating resources for project tasks

Managing the project team

Monitoring project progress

Making decisions regarding scheduling and budgeting

Managing risks and resolving conflicts

The project manager acts as a leader and coordinator who ensures that all team members work together toward the project objectives.

Question (d): Compare PERT and CPM

Answer:

Both techniques are used for project scheduling and identifying critical tasks.

Question (e): Steps of Software Development

Answer:
Software development generally follows the Software Development Life Cycle (SDLC).

The main steps include:

Requirement Analysis – understanding user requirements.

System Design – designing system architecture.

Implementation – coding the software.

Testing – identifying and fixing errors.

Deployment – delivering the software to users.

Maintenance – updating and improving the system.

These steps ensure systematic development of software.

Question (f): Cost Benefit Analysis

Answer:
Cost Benefit Analysis (CBA) is a technique used to evaluate whether a project is financially worthwhile.

It compares:

Costs: development cost, maintenance cost, operational cost

Benefits: revenue, improved productivity, reduced manual work

If the benefits exceed the costs, the project is considered economically feasible.

For example, developing an automated billing system may cost ₹10 lakh but save ₹15 lakh annually in operational expenses.

Question (g): Software Configuration Management (SCM)

Answer:
Software Configuration Management is the process of managing changes in software products during development.

SCM ensures that:

Changes are properly documented

Previous versions of software are preserved

Multiple developers can work simultaneously without conflicts

Key activities of SCM include:

Version control

Change management

Configuration auditing

Release management

SCM helps maintain consistency and stability in software projects.

Question (h): Unit Testing and System Testing

Unit Testing

Unit testing focuses on testing individual components or modules of software.

Example: Testing a login function to ensure it correctly validates username and password.

System Testing

System testing evaluates the complete integrated system to ensure it meets requirements.

Example: Testing the entire application including login, dashboard, and transaction modules together.

Both testing methods help identify errors early in the development process.

Question (i): Code Inspection

Answer:
Code inspection is a formal review process in which developers examine source code to identify errors, improve code quality, and ensure compliance with coding standards.

During code inspection:

Developers analyze code line by line

Errors are documented

Suggestions for improvement are discussed

This process improves software quality before testing begins.

Question (j): Difference Between Change Control and Version Control

Change Control

Change control manages modifications made to project requirements or software components. It ensures that changes are properly evaluated and approved before implementation.

Version Control

Version control tracks different versions of software files. It allows developers to revert to previous versions if needed.

Example tools for version control include Git and SVN.

SECTION B – Intermediate Concepts of Software Project Management

Section B questions focus on project planning, risk management, testing strategies, and estimation models. 

Question: Stepwise Planning of Software Project Development

Answer:
Stepwise planning is a systematic approach used to plan software projects effectively.

The process typically involves:

Identifying project objectives

Identifying project infrastructure

Analyzing project characteristics

Identifying products and activities

Estimating time and resources

Creating project schedule

Allocating resources

Monitoring project progress

Stepwise planning helps ensure that all aspects of the project are carefully considered before development begins.

Question: Work Breakdown Structure (WBS)

Answer:
Work Breakdown Structure is a hierarchical decomposition of a project into smaller manageable tasks.

It divides the project into:

Phases

Deliverables

Activities

Subtasks

Example: Website Development

Project
→ Design
→ Frontend Development
→ Backend Development
→ Testing
→ Deployment

WBS helps in better planning, cost estimation, and task assignment.

Question: Risks in Software Development

Software development projects face several types of risks:

Technical Risks

Problems related to technology or tools.

Project Risks

Issues related to scheduling, budgeting, or team management.

Business Risks

Risks affecting the business value of the project.

Effective risk management involves identifying potential risks early and preparing mitigation strategies.

Question: Verification vs Validation

Verification

Verification ensures that software is developed according to design specifications.

Example: Checking whether code follows design documents.

Validation

Validation ensures that the software satisfies user requirements.

Example: Testing whether the system performs tasks expected by users.

Verification focuses on building the product correctly, while validation focuses on building the correct product.

Question: COCOMO Model

COCOMO (Constructive Cost Model) is used to estimate the cost, effort, and development time required for software projects.

It categorizes projects into three types:

Organic

Semi-detached

Embedded

COCOMO uses mathematical formulas to estimate effort based on the size of the software (usually measured in lines of code).

SECTION C – Advanced Software Project Management

Section C focuses on advanced concepts such as Earned Value Analysis, Software Quality Models, and Project Management Tools. 

Question: Earned Value Analysis (EVA)

Earned Value Analysis is a project management technique used to measure project performance and progress.

Cost Variance (CV)

Cost Variance measures the difference between actual cost and earned value.

CV = EV – AC

If CV is positive → project is under budget
If CV is negative → project is over budget

Schedule Performance Index (SPI)

SPI measures how efficiently the project schedule is being followed.

SPI = EV / PV

SPI greater than 1 indicates the project is ahead of schedule.

Cost Performance Index (CPI)

CPI measures cost efficiency.

CPI = EV / AC

CPI greater than 1 indicates the project is performing well financially.

Question: Software Quality Attributes

Software quality attributes define the characteristics that determine software performance.

Examples include:

Reliability

Usability

Efficiency

Maintainability

Portability

These attributes ensure that the software meets user expectations.

Question: SEI-CMM (Capability Maturity Model)

SEI-CMM is a framework used to improve software development processes.

It consists of five maturity levels:

Initial

Repeatable

Defined

Managed

Optimizing

Organizations progress through these levels to achieve better process control and higher software quality.

Conclusion

Software Project Management is essential for ensuring the successful completion of software projects. By using structured planning techniques, risk management strategies, testing methodologies, and performance evaluation tools such as Earned Value Analysis, organizations can manage complex projects effectively.

Understanding these concepts helps project managers deliver software systems that meet deadlines, budgets, and quality expectations.