SOFTWARE PROJECT MANAGEMENT (NOE-77)
B.Tech VII Semester – Theory (2017–18)
SECTION A
(Attempt all questions – Descriptive but concise)
a) Scope of a Project
The scope of a project defines the complete boundary of work that must be carried out to deliver a product or service successfully. It clearly specifies what is included in the project and what is excluded, thereby preventing ambiguity and uncontrolled expansion of work, commonly known as scope creep. The scope includes project objectives, deliverables, features, constraints, assumptions, and acceptance criteria. A well-defined scope helps the project manager in planning, scheduling, cost estimation, and resource allocation.
For example, if a software project is developed to build an online examination system, the scope may include user registration, question management, online test conduction, and result generation. Features such as online proctoring or mobile app development may be excluded from the scope unless explicitly mentioned.
b) Types of Project Plans
In software project management, multiple project plans are prepared to ensure smooth execution and control of the project. These plans include the project management plan, quality assurance plan, risk management plan, configuration management plan, staffing plan, and schedule plan. Each plan focuses on a specific aspect of the project and collectively ensures that the project objectives are achieved within constraints.
For instance, a risk management plan identifies potential risks that may affect the project, evaluates their probability and impact, and defines strategies to mitigate or control those risks throughout the project life cycle.
c) Software Project Estimation
Software project estimation is the process of predicting the amount of effort, time, cost, and resources required to develop a software system. Estimation is performed during the early phases of the project and plays a crucial role in decision-making, bidding, scheduling, and budgeting. Accurate estimation helps in setting realistic deadlines and allocating resources effectively, whereas poor estimation may lead to project delays, cost overruns, or failure.
d) Verification and Validation
Verification and validation are two important quality assurance activities in software engineering. Verification focuses on ensuring that the software is being built correctly according to specifications and design documents. It is carried out through reviews, inspections, walkthroughs, and static analysis without executing the code.
Validation, on the other hand, ensures that the developed software meets the user’s actual needs and expectations. It involves executing the software and performing various levels of testing such as system testing and acceptance testing to confirm that the product fulfills its intended purpose.
e) Project Organization Types
Project organization defines how authority, responsibility, and communication are structured within a project. In a functional organization, team members report to functional managers and projects are secondary. In a projectized organization, the project manager has full authority and team members are dedicated solely to the project. A matrix organization combines both functional and projectized structures, allowing shared resources and balanced authority between functional managers and project managers.
f) Results of Major Milestones in a Modern Process
Milestones represent significant events or achievements in a project timeline. In a modern software development process, major milestones typically result in the completion and approval of key phases such as requirements analysis, system design, coding, testing, and deployment. Each milestone acts as a checkpoint that helps management evaluate progress, quality, and readiness to proceed to the next phase.
g) Software Configuration Management (SCM) Activities
Software Configuration Management is a discipline that controls and tracks changes in software artifacts throughout the project life cycle. SCM activities include identifying configuration items, controlling versions, managing changes, maintaining configuration status records, and conducting configuration audits. These activities ensure consistency, traceability, and integrity of software products even when multiple developers are working simultaneously.
h) PERT/CPM Scheduling Concept
PERT (Program Evaluation Review Technique) and CPM (Critical Path Method) are project scheduling techniques used to plan, coordinate, and control complex projects. They represent project activities and dependencies in the form of a network diagram. By analyzing the network, the critical path is identified, which determines the minimum project completion time. Any delay in critical path activities directly affects the project schedule.
i) Waterfall Model and Its Limitations
The Waterfall model is a traditional software development model in which development proceeds sequentially through distinct phases such as requirements analysis, design, implementation, testing, deployment, and maintenance. Each phase must be completed before moving to the next.
However, the Waterfall model has several limitations. It lacks flexibility to accommodate changes once a phase is completed, testing is performed late in the process, and customer feedback is not incorporated early. These limitations make it unsuitable for large and evolving software projects.
j) Change Control Process
The change control process is used to manage modifications in project requirements, design, or implementation. When a change request is raised, it is formally documented and analyzed for its impact on cost, schedule, quality, and resources. After evaluation, the change is either approved or rejected by the change control board. Approved changes are then implemented, tested, and documented to maintain project stability and control.
SECTION B
(Attempt any three – Long answers)
2(a) Software Life Cycle and Manager Activities
The software life cycle begins with the identification of a problem or opportunity and ends when the software is retired or replaced. It includes phases such as feasibility study, requirements analysis, design, coding, testing, deployment, maintenance, and eventually system retirement.
During this life cycle, a software project manager performs several critical activities. These include planning the project scope and schedule, estimating cost and effort, organizing the project team, managing risks, monitoring progress, ensuring quality, communicating with stakeholders, and resolving conflicts. The effectiveness of a software project largely depends on the manager’s ability to coordinate these activities efficiently.
2(b) Role of Project Manager and Organization Structure
Software design cannot be directed by technical experts alone because successful projects require a balance of technical expertise, managerial skills, and human resource management. A project manager plays a central role in integrating these aspects. The project manager is responsible for planning, organizing, leading, and controlling the project to achieve objectives within constraints.
Responsibilities of a project manager include defining project goals, allocating tasks, motivating team members, managing risks, ensuring quality, and maintaining communication with clients and stakeholders. The project organization structure generally consists of a project manager at the top, followed by team leaders and project staff such as developers and testers.
2(d) Function Point Analysis and CAF
Function Point Analysis is a technique used to estimate the size of software based on its functionality rather than lines of code. It evaluates the system by counting external inputs, external outputs, external inquiries, internal logical files, and external interface files. These components are assigned weights based on their complexity to calculate the Unadjusted Function Point (UFP).
The Complexity Adjustment Factor (CAF) is then applied to adjust the UFP based on fourteen general system characteristics such as performance, security, and transaction rates. The final function point value provides a more accurate measure of software size, which can be used for effort and cost estimation.
2(e) Project Scheduling and Agile Benefits
Project scheduling is the process of defining project activities, sequencing them, estimating durations, allocating resources, and developing a timeline. Effective scheduling helps in tracking progress, managing dependencies, and ensuring timely project completion.
Agile project management offers several benefits over traditional approaches. It promotes iterative development, frequent customer feedback, flexibility to change, faster delivery of working software, and improved team collaboration. Agile methodologies are especially useful in dynamic environments where requirements frequently evolve.
SECTION C
(Descriptive answers written in paragraph form)
Project Plan
A project plan is a formal document that describes how a project will be executed, monitored, and controlled. It serves as a roadmap for the project team and stakeholders, outlining objectives, scope, schedule, resources, risks, and quality standards. Different types of project plans focus on specific areas such as risk, quality, configuration, and staffing.
Work Breakdown Structure (WBS)
Work Breakdown Structure is a hierarchical decomposition of the total project work into smaller, manageable components. It helps in better estimation, task assignment, monitoring, and control. WBS ensures that all project activities are identified and organized systematically.
Risk Identification and Categories
Risk identification involves recognizing potential events that may negatively impact the project. During software development, risks may arise due to unclear requirements, technological challenges, staff turnover, or unrealistic schedules. These risks are commonly categorized as project risks, technical risks, and business risks, each requiring appropriate mitigation strategies.
Testing Levels and Strategies
Software testing is performed at multiple levels to ensure quality. Unit testing verifies individual components, integration testing checks interactions between modules, system testing validates the complete system, and acceptance testing confirms that the software meets user requirements. Different testing strategies are applied depending on project complexity and risk.
Project vs Product Life Cycle
The project life cycle refers to the phases a project goes through from initiation to closure and is temporary in nature. The product life cycle, however, spans from product conception to retirement and continues even after the project ends.
COCOMO Development Modes
COCOMO classifies software projects into organic, semi-detached, and embedded modes based on complexity and team experience. It provides mathematical formulas to estimate effort and development time using project size measured in KLOC.
