AKTU

B.Tech 3rd year

Software
Project
Management
+ Free notes

Most important PYQ solutions

 Questions

ing
Describe the different types, levels and strategies of testing.

rn
Outline COSMIC full function points for software cost estimation.

lea
What do you understand by Verification and validation? Explain

i
their difference with an example.

ev
Write COCOMO model in detail.

br
Discuss and differentiate Project Life Cycle and Product Life Cycle

@
with example.
Discuss Rapid Application Model for software development.
Discuss Agile methodologies for software development.
Describe the different types, levels User Acceptance Testing (UAT): Involves
and strategies of testing. end-users testing the application to
Types of Testing in Software Project confirm it meets their needs and

g
Management: requirements before final deployment.

g in
1. Manual Testing:
in 2.Automated Testing:
rn
r n e a
e a
Exploratory Testing: Allows testers to
li to ensure new changes
Regression Testing: Automates the

i l
explore the application based on their
don’t disruptv
process of re-testing

e
e v
knowledge, helping to identify unexpected
essentialrfor maintaining project timelines
existing functionality,
issues.
r b
b
Usability Testing: Ensures the application
@ Testing: Evaluates the
and quality.

@
meets user expectations and provides a
good user experience, which is critical for
Performance
system’s performance under load,
project acceptance. ensuring it meets performance criteria
outlined in the project plan.
 Integration Testing: Automates the 2.Integration Testing:
testing of combined components to Focuses on the interaction between
ensure they work together as expected, integrated units or components,
crucial for identifying integration issues ensuring they work together as
n g
early.
n g intended.
n i
n i r
Helps in identifying interface defects,
Levels of Testing in Software
r Project
e a
which can be crucial for maintaining
Management :
e a li
project schedules.

il e v
e v r
b
1.Unit Testing: 3.System Testing:

functionb
Ensures
r individual components Conducted on a complete, integrated
@
@
correctly, reducing the risk of system to ensure it meets the specified
defects in later stages. requirements.
Typically integrated into the Validates the system’s compliance with
development phase, promoting early functional and non-functional
detection of issues and reducing project requirements, aligning with project
risk. scope and goals.
4.Acceptance Testing: 2.White-Box Testing:
The final level of testing before
deployment, ensuring the software Involves testing internal structures or
workings of an application.
g
meets business requirements and is

n
ready for release.
g
Helps in thorough testing of complex
Involves stakeholders and end-users,
n n i
algorithms and critical sections of the
i r
providing a final verification step

n a
code, ensuring high-quality

r
before project closure.

a le
deliverables.

li e
Strategies of Testing in Software Project
v i
e
Management :

v
3.Gray-Box Testing:

e the software’s
Focuses onrtesting
1.Black-Box Testing: Combinesr
btechniques, providing a balanced
black-box and white-box

b @
testing

@ the software meets user

functionality without looking at the approach to testing.
internal code structure.
Ensures both functional and structural
Ensures
expectations and requirements, aspects are tested, enhancing overall
aligning with project goals. project quality.
4.Static Testing: 7.Regression Testing:
Involves reviewing the code, requirements,
and design documents without executing Re-tests previously tested
the code.

n g
functionalities after changes to ensure

g i
Helps in early detection of defects, they still work as expected.

i n
reducing rework and project delays.
r n
Critical for maintaining stability and
5.Dynamic Testing:
r n a
reliability throughout the project
e
the software behavior. a li
e
Involves executing the code and checking lifecycle.

il v
8.Model-BasedeTesting:
v r
Ensures the application behaves as

r e
expected in real-world scenarios, validating
b
Uses models to represent the desired

b
project deliverables.
@
behavior of the system and generates

@
6.Risk-Based Testing:
Prioritizes testing based on the risk of
failure and its impact on the project.
test cases based on these models.
Ensures comprehensive testing
Ensures critical functionalities are tested coverage, aligning with project
thoroughly, reducing project risk and requirements and objectives.
increasing confidence in the software’s
reliability.
Outline COSMIC full function points Identify Functional Users: Recognize the
for software cost estimation. entities interacting with the software (e.g.,
users, external systems).

g
COSMIC (Common Software Measurement

g
International Consortium) Full Function
in
2. Identify the Functional Processes

i n
Points is a method used for estimating the size
rn
Functional Processes: Identify and

r n
and complexity of software projects, which document
ea the functional user

a l
helps in cost estimation.

e i
requirements, including all functional

li COSMIC Full v
processes the software must perform.
e
Function Points: v r
Key steps involved in using

e
A functional process is a set of data

r b movements necessary to achieve a

bScope of the Software @ specific goal.

@the Boundary: Determine the

1. Identify the
Define 3. Measure Data Movements
boundary between the software being Entry (E): Data entering the system from a
measured and the external environment. functional user.
 Exit (X): Data leaving the system to a 5. Apply Complexity Factors
functional user. Complexity Adjustment: Optionally,

ng
g
Read (R): Data being read from a adjust the CFP based on the
persistent storage by the system.
n n i
i
complexity of the software's

n
Write (W): Data being written to persistent
a r
environment and specific requirements.
storage by the system.
a r li e
Consider factors like performance

il e v
requirements, processing complexity,

v e
4.Calculate COSMIC Function Points (CFP) data communications, etc.

e
For each functional process, count the
r
bfor Cost Estimation
b r
@ Model: Use the total CFP
number of each type of data movement (E, 6. Use CFP

Sum@
X, R, W). Estimation
the data movements to get the total as an input to a cost estimation model
CFP for each functional process. to predict effort, time, and resources
Add the CFPs of all functional processes required.
to get the total CFP for the software.
What do you understand by Activities in Verification:
Verification and validation? Explain
Reviews: Examining documents and code
their difference with an example
to ensure standards and guidelines are

g
Verification: followed.

g
Verification is the process of checking
in
Walkthroughs: Step-by-step presentations

in
whether the software product meets the
rn
of the software process or product.

rn
specified requirements and design
a
Inspections: Formal evaluations of work

e
a li
specifications. products by a team.

lie
It is concerned with the correctness of the
v
Static Analysis: Analyzing the code

v
development process and involves
re
without executing it to find defects or

re
activities that ensure the product is being
b
ensure adherence to coding standards.

b
built correctly.
@ Example:
@
Focuses on ensuring the product is built Verification
according to specifications and standards During the verification phase, the team
Verification answers the question: "Are conducts reviews and inspections of the design
we building the product right?" documents and source code. They ensure that:
 The design document accurately reflects Validation answers the question: "Are we
the library's inventory management building the right product?"
requirements. Focuses on ensuring the product fulfills
The code follows coding standards and its intended purpose and meets user
n g
guidelines.
ng requirements.
n i
i
All specified functions (e.g., adding,

n r
r
updating, and deleting books) are correctly Activities in Validation:
e a
e
implemented in the code.
a i l
Alpha Testing: Executing the software to

il e
find defects and
v ensure it meets user
v
Validation isethe process of checking
Validation
r
requirements (e.g., unit testing,

whether ther software product meets the

b
b
integration testing, system testing,

@
acceptance testing).
@
user's needs and requirements.
It ensures the final product behaves as
Beta Testing: Releasing the software to a
limited audience outside of the
expected in a real-world scenario and development team for real-world testing
satisfies the intended use and requirements. and feedback.
Validation Example: Write COCOMO model in detail.
During the validation phase, the team performs
various tests to ensure the software works The COCOMO (Constructive Cost Model)
correctly in practice.
ng
is a software cost estimation model
They:
ng ni
developed by Barry W. Boehm in 1981.

ni
Execute unit tests to verify individual
r
It is used to estimate the cost, effort, and

r
functions work as intended.
ea
schedule when planning new software

ea
Conduct integration tests to ensure different
li
development activities.
li
modules (e.g., the database and user
ev
The model uses basic project characteristics

ev r
b
interface) work together seamlessly. to compute cost estimations and is divided

br
Perform system tests to check the entire into three levels of detail:
application functions correctly in a
@
1. Basic
@
simulated library environment. 2. Intermediate
3. Detailed
Through these tests, they ensure the software
meets the actual needs of the library and
1.Basic COCOMO Model:
performs well in real-world scenarios.
The Basic COCOMO model provides a rough
estimate of project cost and duration based Effort Estimation Formula:
on the size of the software project in terms of Effort:
KLOC (thousands of lines of code). (person-months)=a×(KLOC)^b
n g
n g i
a and b are coefficients that vary based on
n
Types of Software Projects:
n i the project type.
r
small teams and relativelyr
1. Organic: Small, simple projects with
e a
e a flexible
Development Time: i
l
Time Estimation Formula:
requirements.
il e v
e v
2. Semi-Detached: Medium-sized projects
r
(months)=c×(Effort)^d

r b
b
with mixed characteristics of organic c and d are coefficients that vary based on
and embedded types.
@
the project type.
@
3. Embedded: Large, complex projects
with tight hardware, software, and
operational constraints.
2.Intermediate COCOMO Model: Cost Drivers and Their Range:
The Intermediate COCOMO model Product Attributes: Required software
refines the Basic model by considering a set reliability, database size, product
of cost drivers that affect the software
ng
g
complexity, etc.
development effort.
n ni
Hardware Attributes: Execution time

n
These cost drivers include product
i r
a
constraint, main storage constraint, etc.

a r
attributes, hardware attributes, personnel
lie
Personnel Attributes: Analyst capability,

le
attributes, and project attributes.
v
programmer capability, application

v i e
experience, etc.
r
e b
Effort Estimation Formula:

r
Project Attributes: Use of software tools,

b @
Effort: required development schedule, etc.

@
(person-months)=Effort(basic)×EAF
Effort(basic) is calculated using the Basic 3.Detailed COCOMO Model:
COCOMO model. The Detailed COCOMO model extends
EAF (Effort Adjustment Factor) is the the Intermediate model by incorporating
product of all cost driver multipliers. the effect of individual project phases.
 It considers the influence of cost drivers Calculate Basic Effort: Use the Basic
on each phase of the software development COCOMO model formula with the
lifecycle (e.g., design, coding, testing). appropriate coefficients.

g
Identify Cost Drivers: For the
Phase-Based Effort Distribution:
g in
Intermediate and Detailed models,

in
Effort is divided among various phases, and
rn
evaluate the cost drivers and determine

r n
each phase may have different multipliers for
a
their multipliers.

e
a li
cost drivers. This approach provides a more Compute Effort Adjustment Factor
accurate estimation.
ile v
(EAF): Multiply the cost driver

v re
multipliers.

e Size (KLOC): Estimate

DeterminerProject
Steps to Use COCOMO Model:
b
Calculate Adjusted Effort: Multiply the

the size b @
basic effort by the EAF.

@of code.
of the software in thousands of Estimate Development Time: Use the
lines time estimation formula with the
Select Project Type: Identify if the project appropriate coefficients.
is Organic, Semi-Detached, or Embedded.
 Discuss and differentiate Project Life Cycle and
Product Life Cycle with example.

Project Life Cycle :

Initiation: Define goals, scope, n

g
ng n i and

ni Planning: Create detailedrdevelopment

stakeholders; conduct feasibility study.

r e a
ea il
plans, timelines, budgets.
li e v
Execution: Develop software, manage

ev r
b
team, ensure specifications are met.

br Monitoring and Controlling: Track

@
progress, manage changes, ensure
@ 0.334
quality.
Closure: Finalize software, obtain
acceptance, conduct post-project review.
Project Life Cycle Example: made as needed to ensure everything runs
Project: Organizing a Company Event smoothly.

g
Initiation: The company decides to host Closure: After the event, feedback is

g
a networking event to promote its brand
in
collected, expenses are reconciled, and a
and products.
in r
post-event report is prepared.
n
rn
Planning: Event coordinators create a

e a
a
detailed plan including venue selection,

e
Product Life Cycle :
li
li
budgeting, scheduling, and marketing

e v
ev
strategies.
r
Introduction: Launch with marketing

r Growth: b
Execution: The event is carried out efforts, target early adopters.

b
according to the plan, with tasks such as
@ enhance features.
Increase sales, expand

@
setting up booths, arranging
presentations, and managing
distribution,
Maturity: Stabilize sales, optimize costs,
registrations. maintain market position.
Monitoring and Controlling: Event Decline: Decline in sales, discounting, or
progress is tracked, and adjustments are discontinuation.
Product Life Cycle Example:

n g
n g n i
i r
Product: Smartphone Model XYZ Decline: Sales start to decline due to

rn
Introduction: The company launches the
e a
market saturation and the emergence of
new smartphone model
e a XYZ with
li to discontinue the
newer models, prompting the company

i
extensive marketing
l campaigns and
v
to decide whether

e
promotions.
e v r
XYZ model or introduce upgrades to

rapidly asr it gains popularity among

Growth: Sales of the XYZ model increase
b
prolong its lifespan.

b @
@
consumers, leading to market expansion
and feature enhancements through
software updates.
Maturity: Sales stabilize as the product
reaches its peak market penetration, and
the company focuses on maintaining
market share and optimizing costs.
Discuss Rapid Application Model for
Prototyping: Rapid development of
software development
prototypes allows quick feedback and
validation of requirements.
The Rapid Application Development
g
User Involvement: Stakeholders, including

n
g
(RAD) model is an iterative and
i
end-users and clients, play an active role

in n
incremental approach to software

r
throughout the development process,

n a
development that prioritizes rapid

r
providing feedback and validation to

a lie
prototyping and quick feedback cycles.
ensure the final product meets their needs.

l e
It aims to accelerate the development

i v
Reusable Components: RAD encourages

v e
process by focusing on user involvement,
r
the use of reusable components and pre-
e b
prototyping, and iterative development.

Key Features b
r built frameworks to expedite development

@
and improve productivity.

@
of RAD Model:
Focus on Quality: Despite the emphasis on
Iterative and Incremental: RAD breaks
speed, RAD maintains a focus on quality
down the project into small, manageable
through continuous testing, feedback, and
increments or iterations, allowing for
refinement.
continuous refinement and improvement.
 Requirement Analysis: In this initial phase,
Requirement
Analysis the development team gathers information

g
from stakeholders to comprehend the

g in
Planning project's goals and functionalities. This

in n
might involve interviews, workshops, or

n
Analyze

ar
document reviews.
r e
Team 1 Team 2 Team N

a li
Design
Develop Develop Develop Planning: Following gathering

e
module 1 module 2 module N

l v
Code requirements, the team breaks down the

vi Test

re
project into smaller, more manageable

e
Integrate all

r b
the modules
modules. Each module should address a

b @
specific set of functionalities.
Test the final

@
product and Design and Develop: Here, multiple teams
deliver
are assigned to develop the segregated
modules concurrently. This parallel
Rapid-Application Development Architecture
approach significantly reduces
development time.
 Integrate and Test: Once the modules Enhanced User Involvement: Early and
are developed, they are combined and continuous user feedback ensures the

g
integrated into a cohesive system. This application aligns with their needs, leading

g in
to higher user satisfaction.

n
stage also involves rigorous testing to

i
ensure the application functions as
rn
Reduced Risk: By creating functional

rn
intended and identify and rectify any
a
prototypes early , RAD allows for
e
bugs.
e a li
identifying potential issues before

il
Deliver: Upon successful testing, the
v
significant development effort is invested.
e
e v
final product is delivered to the
r
Improved Maintainability: Module based

r b
development ensures easier maintenance

b
stakeholders.
@
and modifications in the project.

@
Advantages:
Faster Development: Concurrent Disadvantages:
development of modules reduces the Limited Scope: RAD might not be ideal
overall development time. for projects with constantly evolving
requirements.
Need for Clear Requirements: A well- Discuss Agile methodologies for
defined understanding of project goals is software development.
crucial for the success of RAD. Unclear

g
requirements can lead to rework and Agile methodology is an iterative and
delays.
g in
incremental approach to software

in
Potential for Incompleteness: The focus
rn
development that emphasizes flexibility,

rn
on rapid delivery may sometimes result in
a
customer collaboration, and rapid

e
a li
applications lacking some functionalities delivery of functional software in small,

lie
compared to a more traditional
v
frequent releases.

v
development approach.
re
It adapts to changing requirements and

re
Requires Skilled Team: Effective RAD
b
focuses on continuous improvement

b
implementation necessitates a team with
@
through regular feedback and reflection.

@
strong communication, collaboration,
and prototyping skills. Key Features of Agile:
Iterative Development: Projects are
broken down into small, manageable
units called iterations or sprints.
Customer Collaboration: Continuous
involvement of the customer or client

g
to provide feedback and guide
development.
g in
in
Flexibility: Ability to adapt to
r n
rn
changing requirements.
e a
a
Incremental Delivery: Software is
e li
li
developed and delivered in increments.
e v
v
Self-Organizing Teams: Teams are
e
Plan:
r
r
empowered to organize their work and
b
Define goals, gather requirements,

b
make decisions to achieve project
Design:@
prioritize tasks.

@
goals.
Continuous Improvement: Regular Create wireframes, prototypes, and
reflection and adaptation of processes system architecture.
to enhance efficiency and effectiveness. Develop:
Code and integrate software features.
Test: Flexibility: Adaptable to changing
Conduct unit, integration, and system requirements.
testing. Early Delivery: Regular releases of
Deploy: functional software.
n g
ng
Release software to production or
n i
Improved Quality: Ongoing testing and

ni r
a
staging environments. integration.
Review:
ar li e
Team Morale: Empowered and motivated

lie v
Evaluate output, gather feedback, and teams.

v e
make adjustments.

e Scope b
r
r
Launch: Disadvantages of Agile

b @
Final release to end users, support, and Creep: Potential for uncontrolled

@
training. changes.
Resource Intensive: Requires significant
Advantages of Agile time and effort.
Customer Satisfaction: Frequent Limited Documentation: Focus on
delivery and continuous feedback. software over documentation.
Inconsistent Deliverables: Initial
releases may be incomplete.
Team Dependency: Success relies
heavily on team performance.

@brevilearning