VARDHAMAN COLLEGE OF ENGINEERING

(Autonomous)
Shamshabad - 501 218, Hyderabad
DEPARTMENT OF INFORMATION TECHNOLOGY
Regulations: VCE - R 11 / VCE - R11A
VII Semester
COURSE DESCRIPTION
Course Code

A1524

Course Title

SOFTWARE PROJECT MANAGEMENT

Course Coordinator

Lectur Tutorial Practica

Credits
es
s
ls
4
4
Mr. L. Thirupathi, Asst.prof(Sr.)

Team of Instructors

Mr. A. Bhanu Prasad, Ms. E. R. Aruna

Course Structure

I.

II.

III.

IV.

Course Overview:
The conventional model performance and pitfalls, Software economic parameters,
Software development lifecycle stages and phases, Artifacts and work flows of the
process, Check points of the process(Milestones),Roles and Responsibilities of
Management and Technical people, Tailoring of the project, Monitoring and controlling
of process status using Metrics, Future software project management
Prerequisite(s):
Level

Credits

Periods/ Week

UG

Prerequisites
Software
Engineering

Marks Distribution:

Sessional Marks

Universit
y End
Exam
Marks

Total
Marks

Mid Semester Test

There will be two Mid Semester Tests in theory courses
having a weightage of 20 marks to be answered in two hours
duration each. Marks shall be awarded considering the
average of two Mid Semester Tests in each course. In case a
student does not appear in the Mid Semester Tests due to
any reason whatsoever, will get zero marks(s).
Objective Test
There will be one Objective Test in theory courses for a
maximum of 5 marks to be answered in 20 Minutes duration.
In case a student does not appear in the Objective Test due
to any reason whatsoever, will get zero marks(s).

75

100

Evaluation Scheme:
I Mid Term Examination

20 marks

II Mid Term Examination

20 marks

Online Objective Test

5 marks

End Semester Examination

75 marks

V.

Course Objectives:
I.

Provide cost effective, flexible project management for the software project to
meet current and future demands of a business.
II.
Able to achieve the concurrence among stakeholders at every stage in the life
cycle and synchronize the stakeholders expectations by conducting the
reviews.
III. Ability to incorporate organizational culture into business software to build
employee and workplace morale.
IV.
Able to reach company goals and customer strategic objectives in every
possible way and Work within the customer budgets.
V.
Maintain healthy and ethical strategic business relationships.
VI. Able to support configuration management and change management for a
healthy project and define the roles and Responsibilities of the Management and
Technical people.
VII. Optimize and analyze the software project resources to improve software ROI by
reducing the development cost and State methods to analyze, estimate risks at
early stages to reduce reengineering cost.
VIII. Develop a software product by organizing the software lifecycle such that it will
assure the predictability of the project by taking the crucial decision make/ buy
the product at the end of design phase & extend the knowledge for future
software project management using Modern project profiles.
VI.

to:

Course Outcomes:
After completing this course the student must demonstrate the knowledge and ability
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.

Ability to achieve cost effective management for the software project and
business software.
Develop Strategy to achieve the concurrence among stakeholders at every
stage in the life cycle known by the student.
Provided flexible project management software to meet both current and future
demands of a business.
Ability to incorporate organizational culture into business software to build
employee and workplace morale.
Ability to Work within customer budgets.
Capability to reach company goals and customer strategic objectives in every
possible way.
Ability to maintain healthy and ethical strategic business relationships.
Ability to approval the necessary management and executive review and
approval points and practices per type of project.
Ability to support configuration management and change management for a
healthy project.
Acquired knowledge to optimize the software project resources to improve
software ROI by reducing the development cost.
Gained knowledge on defining the roles and Responsibilities of the Management
and Technical people.
Ability to organize the software lifecycle such that it will assure the predictability
of the project.

VII.

How Course Outcomes are assessed:

Program Outcomes
a

An ability to apply knowledge of mathematics, including

discrete mathematics, probability, statistics, science,
computer science and engineering, electronic engineering
and electrical engineering as it applies to computer
hardware and software (fundamental engineering analysis
skills).

An ability to design and conduct experiments, as well as to

organize, analyzes and interprets data to produce
meaningful conclusions and recommendations (information
retrieval skills).
C An ability to design, implement, and to evaluate a computerbased system, process, component, or program to meet
desired needs, within realistic constraints such as social,
political, health, safety, economic, environmental and
sustainability (Creative Skills)
d An ability to work individually or as a member with
responsibility to function on multi-disciplinary teams
(teamwork).
e An ability to identify, formulates, and solves hardware and
software computing problems, accounting for the interaction
between hardware and software (engineering problem
solving skills).
f An understanding of professional, legal, ethical, security and
social issues and responsibilities (professional integrity).
g An ability to communicate effectively in speech and in
writing, including documentation of hardware and software
systems (speaking / writing skills).
h Able to show the understanding of impact of engineering
solutions in a global on the society, economic, environmental
(engineering impact assessment skills).
i Demonstrate an ability to acquire new knowledge in the
computing discipline and to engage in life-long learning
(continuing education awareness).
j Knowledge of contemporary issues in the social sciences and
the humanities using computational tools (social awareness).
k An ability to use the techniques, skills, and modern
engineering tools necessary for computer engineering
practice (practical engineering analysis skills).
l An ability to apply engineering and management knowledge
and techniques to estimate time and resources needed to
complete a computer engineering project (engineering and
management skills).
m An ability to recognize the importance of professional
development by pursuing postgraduate studies or face
competitive examinations that offer challenging and
rewarding careers in computing (successful career and
immediate employment).

Leve Proficiency
l
assessed by
Lectures
and
problem
H
solving,
Tutorials,
Assignment
s

--

--

--

--

--

Group
discussions

Lectures,
Assignment
s, Exams

--

--

--

Labs,
Tutorials,
Assignment
s

Exams

N = None
VIII.

S = Supportive

H = Highly Related

Syllabus:

UNIT I
SOFTWARE EFFORTS ESTIMATION TECHNIQUES
The waterfall model, conventional software Management performance. Evolution of
Software Economics: Software Economics, pragmatic software cost estimation.
IMPROVING SOFTWARE ECONOMICS
Reducing Software product size, improving software processes, improving team
effectiveness, improving automation, Achieving required quality, peer inspections,
the principles of conventional Software engineering, principles of modern software
management, transitioning to an iterative process.
UNIT II
LIFECYCLE PHASES
Engineering and production stages, inception, Elaboration, construction, transition
phases. Artifacts of the process: The artifact sets, Management artifacts, Engineering
artifacts, programmatic artifacts.
MODEL BASED SOFTWARE ARCHITECTURES
A Management perspective and technical perspective, Work Flows of the process:
Software process workflows, Iteration workflows.
PROJECT ORGANIZATION AND RESPONSIBILITIES
Line-of-Business Organizations, Project Organizations, evolution of Organizations.
Process Automation:
Automation Building blocks, The Project Environment.
UNIT -III
CHECKPOINTS OF THE PROCESS
Major Milestones, Minor Milestones, Periodic status assessments. Iterative Process
Planning:
Work breakdown structures, planning guidelines, cost and
schedule estimating, Iteration planning process, Pragmatic planning.
UNIT - IV
PROJECT CONTROL AND PROCESS INSTUMENTATION
The seven core Metrics, Management indicators, quality indicators, life cycle
expectations, pragmatic
Software Metrics, Metrics
automation. Tailoring the Process: Process discriminants.
UNIT - V
NEXT GENERATION SOFTWARE ECONOMICS
Modern Project Profiles, Next generation Software economics, modern process
transitions. Case Studies: The command Center Processing and Display systemReplacement (CCPDS-R), Process Improvement and mapping to the CMM.
IX.

List of Text Books / References / Websites / Journals / Others

Text Book:
1. Walk Royce (2005), Software Project Management, Pearson Education.
References:
1. Bob Hughes and Mike Cottrell (2006), Software Project Management, Tata
McGraw-Hill Edition.
2. Joel Henry (2003), Software Project Management, Pearson Education.

X.

Course Plan:
The course plan is meant as a guideline. There may probably be changes.

Lectur
e No.
1

3
4-6
7-8

9-11

12-13
14
15-16
17-18
19-20
21-22
23-24
25-27

28-29

30

31-32

33

34
35

Learning Objectives
To understand the
Conventional software
process
To understand the
performance of a
conventional software
management
To understand the
evolution of software
economics
The important trends in
improving software
trends
To understand the
improving automation
software environments
To know the principles of
conventional software
engineering and modern
software management
To understand the lifecycle phases
To understand artifacts
of the process
To understand artifacts
of the process
To understand model
based software
architectures
To understand the work
flows of process
To know the effective
management workflowproject organization and
responsibilities
To understand the
process automation
To know checkpoints of
the process
To know the effective
management workflowiterative process
planning
To know the effective
management workflowiterative process
planning
To understand project
control and process
instrumentation
To understand project
control and process
instrumentation
Able to tailor the process
to the specific needs of
the project
To understand Tailoring
the process with an
example
To understand the

Topics to be covered

Reference

The waterfall model

T1: 1.1

Conventional software
management performance

T1: 1.2

Software economics, pragmatic

software cost estimation

T1: 2.1-2.2

Reducing software product size,

improving software process,
improving team effectiveness
Improving automation through
software environments, achieving
required quality, a pragmatic view
The principles of conventional
software and modern engineering,
the principles of modern software
management, transition to an
iterative process
Engineering and production
stages, inception phase,
elaboration phase, construction
phase

T1: 3.1-3.3
T1: 3.4-3.6

T1: 4.1-4.3

T1: 5.1-5.4

The artifacts sets

T1: 6.1

Management, engineering and

pragmatic artifacts

T1: 6.2-6.4

Architecture: a management and

a technical perspective

T1: 7.1-7.2

Software process workflows,

iteration work flows

T2: 8.1-8.2

Line-of-business organizations,
project organizations, evolution of
organizations

T1:
11.111.3

Tools: automation building blocks,

the project environment
Major milestones, minor
milestones, periodic status
assessments.

T1:
12.112.2
T1: 9.1-9.3

Work breakdown structures,

planning guidelines, the cost and
schedule estimating process

T1:
10.110.3

The iteration planning process,

pragmatic planning

T1:
10.410.5

The seven core metrics,

management indicators, quality
indicators.

T1:
13.113.3

Life cycle expectations, pragmatic

software metrics, metrics
automation.

T1:
13.413.6

Process discriminants

T1: 14.1

Example: small-scale project

versus large scale project

T1: 14.2

XI.
Mapping course objectives leading to the achievement of the program
outcomes:
Course
Objecti
ves

Program Outcomes
b

II

III

IV

H
H

V
VI

H
H

VII

VIII

S
S=Supportive

H=Highly Related

XII.
Mapping course outcomes leading to the achievement of the program
outcomes:

Course
Outcom
es

Program Outcomes
b

10
11

S
H

12

H
S=Supportive

H=Highly Related

Prepared By

E.R. Aruna, Associate Professor Department of IT

Date

2 July, 2014