Sponsored by

Lavu Educational Society

(Approved by AICTE and Affiliated to JNTUniversity, Hyderabad)

Course File

A.Y 2023-2024

SOFTWARE PROCESS & PROJECT MANAGEMENT

For

IV Year B.Tech I Sem (R18)

By

D. Chaithanya
Asst Prof., IT Department

Department Of Information Technology

 CONTENTS

Sl. No. PARTICULARS

1 Vision & Mission of the College

2 Vision & Mission of the Department

3 Programme Educational Objectives(PEOs)

4 Program Outcomes

5 Program Specific Outcomes

6 Academic Calender

7 Time Table

8 Roll List

Syllabus Copy with Information of

9 a. Text books
b. Reference books
c. Online resources
10 Course Objectives

11 Course Outcomes (COs)

12 Lecture Plan

13 Question bank( Descriptive & Objective)

14 Unit Wise Learning Objectives

15 Assignment Test Question Papers

16 Mid -I , Mid -II Question Paper( Descriptive & Objective )

17 Mid -I , Mid -II Scheme of Evaluation

18 Mid -I, Mid-II Marks

19 Model papers( if it is new subject)

20 Previous Year University Question Papers

21 Subject Hand Written Notes

22 Unit Wise PPT

 1.1. VISION OF THE COLLEGE

To evolve into a Center of excellence in Science & Technology through creative and innovative

practices in teaching-learning, promoting academic achievement & research excellence to produce

internationally accepted competitive and world class professionals who are psychologically strong

and emotionally balanced imbued with social consciousness and ethical values.

1.2. MISSION OF THE COLLEGE

To provide high quality academic programmes, training activities, research facilities and

opportunities supported by continuous industry-institute interaction aimed at employability,

entrepreneurship, leadership and research aptitude among students and contribute to the economic

and technological development of the region, state and nation.

 2.1. DEPARTMENT (IT) VISION
The department aims to produce globally competent graduates to meet the ever changing needs of IT
industry through contemporary knowledge and moral values..

2.2. DEPARTMENT (IT) MISSION

1. To provide a holistic learning environment to students for professional development and ethical

practices.

2. To train students to be industry ready and to have multidisciplinary skills as an individual and as a

team.

3. To impart skills beyond university prescribed to transform students into a well- rounded IT

professional.

4. To continuously engage in research and projects development, use of emerging technologies to attain

self-sustainability.
 3. PROGRAM EDUCATIONAL OBJECTIVES (PEOs)

PEO1: To create and sustain a community of learning in which students acquire knowledge and
apply in their concerned fields with due consideration for ethical, ecological, and economic issues.

PEO2: To provide knowledge based services so as to meet the needs of the society and industry.

PEO3: To make the students understand, design and implement the concepts in multiple arenas.

PEO4: Graduates with leadership skills, Lifelong learning ability for a successful professional
Career. To educate the students in disseminating the research findings with good soft skills so as to
become successful entrepreneurs.
 4. PROGRAM OUTCOMES (POs)
Engineering Graduates will be able to:

1. Engineering knowledge: Apply the knowledge of mathematics, science, engineering fundamentals,

and an engineering specialization to the solution of complex engineering problems.
2. Problem analysis: Identify, formulate review research literature and analyze complex engineering
problems reaching substantiated conclusions using first principle of mathematics, natural science and
engineering science.
3. Design/development of solutions: Design solutions for complex engineering problems and design
system components or processes that meet the specified needs with appropriate consideration for the
public health and safety, and the cultural, societal, and environmental considerations.
4. Conduct investigations of complex problems: Use research-based knowledge and research methods
including design of experiments, analysis and interpretation of data, and synthesis of the information
to provide valid conclusions.
5. Modern tool usage: Create, select, and apply appropriate techniques, resources, and modern
engineering and IT tools including prediction and modeling to complex engineering activities with an
understanding of the limitations.
6. The engineer and society: Apply reasoning informed by the contextual knowledge to assess societal,
health, safety, legal and cultural issues and the consequent responsibilities relevant to the professional
engineering practice.
7. Environment and sustainability: Understand the impact of the professional engineering solutions in
societal and environmental contexts, and demonstrate the knowledge of, and need for sustainable
development.
8. Ethics: Apply ethical principles and commit to professional ethics and responsibilities and norms of
the engineering practice.
9. Individual and team work: Function effectively as an individual, and as a member or leader in
diverse teams, and in multidisciplinary settings.
10. Communication: Communicate effectively on complex engineering activities with the engineering
community and with society at large, such as, being able to comprehend and write effective reports
and design documentation, make effective presentations, and give and receive clear instructions.
11. Project management and finance: Demonstrate knowledge and understanding of the engineering
and management principles and apply these to one's own work, as a member and leader in a team, to
manage projects and in multidisciplinary environments.
12. Life-long learning: Recognize the need for, and have the preparation and ability to engage in
independent and life-long learning in the broadest context of technological change.
 5. PROGRAM SPECIFIC OUTCOMES (PSOs)

PSO-1 Students were enabled to apply the core engineering subjects related to Digital signal
processing, Signal and Systems also Electrical circuits, Manufacturing knowledge in analysis and to
conduct experimental investigation of complex mechanical products / systems.

PSO-2 Graduates were enabled to use the modern modeling and finite element analysis software’s
in developing the new mechanical products and also demonstrates the social responsibility,
professional ethics and environmental safety in their professional and personal life.

PSO-3 Co-curricular activities in collaboration with industries, R&D centers and professional
bodies and also extra-curricular activities enable the students to acquire organizing abilities, team &
competitive spirit, communication & management skills and knowledge of emerging technologies.
6.ACADEMIC CALENDER
 7.TIME TABLE

FACULTY NAME : D. Chaithanya

1 2 3 4 5 6 7

8:45 – 09:35– 10:40 – 11:30- 1:00 – 1:50 – 2:40 –

09:35 10:25 11:30 12:20 1:50 2:40 3:30

MON

LUNCH
TUE

WED

THU

FRI

SAT
 8.ROLL LIST

B.TECH IV IT ROLL LIST ACADEMIC YEAR - 2022-23/SEMESTER-I

S.No. H.T.NO. Name of the Student

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
 9.SYLLABUS

UNIT - I
Software Process Maturity
Software maturity Framework, Principles of Software Process Change, Software Process Assessment, The
Initial Process, The Repeatable Process, The Defined Process, The Managed Process, The Optimizing
Process.
Process Reference Models
Capability Maturity Model (CMM), CMMI, PCMM, PSP, TSP).

UNIT - II
Software Project Management Renaissance
Conventional Software Management, Evolution of Software Economics, Improving Software
Economics, The old way and the new way. Life-Cycle Phases and Process artifacts
Engineering and Production stages, inception phase, elaboration phase, construction phase, transition
phase, artifact sets, management artifacts, engineering artifacts and pragmatic artifacts, model-based
software architectures.

UNIT - III
Workflows and Checkpoints of process
Software process workflows, Iteration workflows, Major milestones, minor milestones, periodic status
assessments.
Process Planning
Work breakdown structures, Planning guidelines, cost and schedule estimating process, iteration planning
process, Pragmatic planning.

UNIT - IV
Project Organizations
Line-of- business organizations, project organizations, evolution of organizations, process automation.
Project Control and process instrumentation
The seven-core metrics, management indicators, quality indicators, life-cycle expectations, Pragmatic
software metrics, metrics automation.

UNIT - V
CCPDS-R Case Study and Future Software Project Management Practices
Modern Project Profiles, Next-Generation software Economics, Modern Process Transitions.

TEXT BOOKS:
1. Managing the Software Process, Watts S. Humphrey, Pearson Education
2. Software Project Management, Walker Royce, Pearson Education

REFERENCE BOOKS:
1. An Introduction to the Team Software Process, Watts S. Humphrey, Pearson Education, 2000
2. Process Improvement essentials, James R. Persse, O’Reilly, 2006
3. Software Project Management, Bob Hughes & Mike Cotterell, fourth edition, TMH, 2006
4. Applied Software Project Management, Andrew Stellman & Jennifer Greene, O’Reilly, 2006.
5. Head First PMP, Jennifer Greene & Andrew Stellman, O’Reilly, 2007
6. Software Engineering Project Management, Richard H. Thayer & Edward Yourdon,
2nd edition, Wiley India, 2004.
 10.COURSE OBJECTIVES

• To acquire knowledge on software process management

• To acquire managerial skills for software project development
• To understand software economics

11.COURSE OUTCOMES

• Gain knowledge of software economics, phases in the life cycle of software development, project
organization, project control and process instrumentation
• Analyze the major and minor milestones, artifacts and metrics from management and technical
perspective
• Design and develop software product using conventional and modern principles of software
project management

PO1 PO2 PO3 PO4 PO5 PO6 PO7 PO8 PO9 PO10 PO11 PO12 PSO1 PSO2 PSO3

C404.1 3 3 3 3 3 3 3 3 3 3 3 3 3

C404.2 3 3 3 3 3 3 3 2 3 2 3 3 2

C404.3 3 3 3 3 3 3 3 3 3 3 3 3 3
 12.LECTURE PLAN

No. of
S.No. TOPIC Teaching Methodologies Resources
Hours

1 UNIT-1: Introduction Software 1

Process Maturity BLACK BOARD, PPT T1,T2
T1,T2
2 2
Software maturity Framework BLACK BOARD, PPT
Principles of Software Process T1,T2
3 2
Change BLACK BOARD, PPT
T1,T2
4 2
Software Process Assessment BLACK BOARD, PPT
T1,T2
5 1
The Initial Process BLACK BOARD, PPT
T1,T2
6 1
The Repeatable Process BLACK BOARD, PPT
T1,T2
7 1
The Defined Process BLACK BOARD, PPT
T1,T2
8 1
The Managed Process BLACK BOARD, PPT
T1,T2
9 1
The Optimizing Process BLACK BOARD, PPT
Process Reference T1,T2
10 modelsCapability Maturity Model 3
(CMM), CMMI, PCMM, PSP,
BLACK BOARD, PPT
TSP)
Unit-2: Software Project
11 1
Management Renaissance BLACK BOARD, PPT T2

12 Conventional Software 1
Management BLACK BOARD, PPT T2

13 Evolution of Software 2
Economics BLACK BOARD, PPT T2
14 Improving Software Economics 1 BLACK BOARD, PPT T2
Life-Cycle Phases and Process
15 2
artifacts BLACK BOARD, PPT T2
Engineering and Production
16 1
stages BLACK BOARD, PPT T2
inception phase, elaboration
17 2
phase BLACK BOARD, PPT T2
construction phase, transition
18 1
phase, artifact sets BLACK BOARD, PPT T2
19 1
management artifacts BLACK BOARD, PPT T2
20 engineering artifacts and 1
pragmatic artifacts BLACK BOARD, PPT T2
model-based software
21 1
architectures BLACK BOARD, PPT T2

22 Unit-3: Workflows and 1

Checkpoints of process BLACK BOARD, PPT T2
23 1
Software process workflows BLACK BOARD, PPT T2
24 1
Iteration workflows BLACK BOARD, PPT T2
Major milestones, minor
25 2
milestones BLACK BOARD, PPT T2
26 1
periodic status assessments BLACK BOARD, PPT T2
27 Process Planning 1 BLACK BOARD, PPT T2
28 1
Work breakdown structures BLACK BOARD, PPT T2
Planning guidelines, cost and
29 1
schedule estimating process BLACK BOARD, PPT T2
iteration planning process,
30 2
Pragmatic planning BLACK BOARD, PPT T2
31 1
Unit-4: Project Organizations BLACK BOARD, PPT T2
Line-of- business organizations,
32 2
project organizations BLACK BOARD, PPT T2

33 evolution of organizations, 1
process automation BLACK BOARD, PPT T2

34 Project Control and process 1

instrumentation BLACK BOARD, PPT T2
35
The seven-core metrics,
1
management indicators BLACK BOARD, PPT T2

36 quality indicators, life-cycle 2

expectations BLACK BOARD, PPT T2
37 2
Pragmatic software metrics BLACK BOARD, PPT T2
38 metrics automation 1 BLACK BOARD, PPT T2
39 2
Unit-5 : CCPDS-R Case Study BLACK BOARD, PPT T2
Future Software Project
40 1
Management Practices BLACK BOARD, PPT T2
41 2
Modern Project Profiles BLACK BOARD, PPT T2
 Next-Generation software
42 2
Economics BLACK BOARD, PPT T2
43 2
Modern Process Transitions BLACK BOARD, PPT T2
Total No. Of Lectures: 60

TEXT BOOKS:
1. Managing the Software Process, Watts S. Humphrey, Pearson Education
2. Software Project Management, Walker Royce, Pearson Education
13. Question Bank:

S.No Descriptive Questions Marks CO PO BTL

UNIT-I

1. 1a. Explain Principles of Software Process Change? 2M 1 1 1

1b. Describe about Level 4 of CMM Model. 3M 1 1 2

1c. Distinguish between software process and 10M 1 1 2

software project.

2. 2a. Describe about Software Process Assessment? 2M 1 1 1

2b. Explain PSP Reference Model. 3M 1 1 2

2c. Discuss in detail the Initial process, the 10M 1 2 2

repeatable process and the managed process?

3. 3a. Define Initial Process? 2M 1 2 2

3b. Explain about the TSP Reference Model. 3M 1 1 2

3c. What are process reference models? Explain 10M 1 2 2

any two of them?

4. 4a. Describe about Repeatable Process? 2M 1 1 1

4b. Explain why a software needs to be levelled up? 3M 1 2 2

 4c. Explain about the Optimizing Process in 10M 1 1 2
details?

5. 5a. Explain about Managed Process? 2M 1 1 1

5b. Distinguish between a stable process and an 3M 1 2 2

unstable process?

5c. Explain about the PCMM Process Reference 10M 1 1 2

Model in details?

6. 6a. Define Optimizing Process? 2M 1 1 2

6b. Describe ISO 9001 Certification principles 3M 1 1 2

required for a software evolution?

6c. Explain about the various Certifications used for 10M 1 1 2

Software Assessment?

UNIT-II

1. 1a. Explain about the Evolution of Software 2M 1 1 2

Economics?

1b. Describe Conventional Software Management 3M 1 1,2,3 2

Performance?

1c. Explain the risk profile of a conventional 10M 1 1,2,3 4

software project across its life cycle?

2. 2a. Describe about Life-Cycle Phases? 2M 1 1,2,3 2

2b. Explain about Inception and Elaboration 3M 1 1,2,3 2

phases?

2c. What is meant by Elaboration phase? Discuss 10M 1 1,2,3 3

the primary objectives and essential activities of
Elaboration phase?

3. 3a. Describe about inception phase? 2M 1 1 2

3b. Explain about the improving Software 3M 1 1,2,3 2

Economics in the old way?

3c. Discuss briefly the Engineering artifact sets? 10M 1 1,2,3 3

4. 4a. Explain about elaboration phase? 2M 1 1 2

4b. Describe the Life cycle phases of a software 3M 1 1,2,3 2

development?

4c. Explain with a neat diagram how various 10M 1 1,2,3 2

artifacts evolved over the life Understand cycle?

5. 5a. Describe about transition phase? 2M 1 1 2

5b. Explain about Transition and Elaboration 3M 1 1,2,3 2

Phases?

5c. Explain the pragmatic software metrics? 10M 1 1,2,3 2

6. 6a. Define management artifacts? 2M 1 1 4

6b. Explain about the improving Software 3M 1 1,2,3 2

Economics in the new way?

Briefly Explain about the evolution of Software 10M 1 1 4

Economics?

UNIT-III

1. 1a. Explain about Iteration workflows? 2M 2 1 2

1b. Explain why Periodic Status assessments are 3M 2 1,2,3 2

conducted regularly?

1c. What are major milestone that occur at the 10M 2 3 2

transition points between life - cycle phases? Explain
them?

2. 2a. Describe about Major milestones? 2M 2 1,2,3,12 1

2b. Explain about Life-cycle phase emphasis of 3M 2 3 4

Management Workflow?

2c. Discuss about typical minor milestones in the 10M 2 3 2

life cycle of an iteration?

3. 3a. Describe about Minor milestones? 2M 2 1 2

 3b. Explain about Planning Guidelines for a 3M 2 3 3
Software Development?

3c. Explain in detail about periodic status 10M 2 3 2

assessments?

4. 4a. Explain congestion control? 2M 2 1 1

4b. Explain why process planning is necessary? 3M 2 1,2,3 2

4c. Explain about iteration planning process? 10M 2 3 2

5. 5a. Describe about Work breakdown structures? 2M 2 1 1

5b. Explain about Life-cycle phase emphasis of 3M 2 3 4

Deployment Workflow?

5c. Describe about Process Planning in details? 10M 2 3 2

6. 6a. Define Pragmatic planning? 2M 2 1 2

6b. Describe the three fundamental flaws of 3M 2 1,2,3,12 3

Conventional WBS Issues?

6c. Explain about Conventional Work Breakdown 10M 2 3 2

Structures and Evolutionary Work Breakdown
Structures?

UNIT-IV

1. 1a. Explain about evolution of organizations? 2M 2 1,5,6 1

1b. Explain about Process Instrumentation? 3M 2 1,5,6 3

1c. What are the key practices that improve overall 10M 2 1,5,6 2
software quality?

2. 2a. Describe about process automation? 2M 2 1,5,6 4

2b. Describe quality indicators of a process 3M 2 1,5,6 2

instrumentation?

2c. Describe about Pragmatic software metrics? 10M 2 1,5,6 2

3. 3a. Define about core metrics? 2M 2 1,5,6 1

 3b. Explain about Project Control? 3M 2 1,5,6 2

3c. Illustrate the congestion control in details? 10M 2 1,5,6 2

4. 4a. Explain about management indicators? 2M 2 1 1

4b. Explain about Software Engineering Process 3M 2 1 2

Authority (SEPA)?

4c. Explain in detail about metrics automation? 10M 2 1 2

5. 5a. Describe about life-cycle expectations? 2M 2 1 1

5b. Illustrate the working of a Configuration 3M 2 1 2

Control Board (CCB)?

5c. Explain Project Control and process 10M 2 1 2

instrumentation in detail?

6. 6a. Explain about Line-of-Business Organizations? 2M 2 1 1

6b. Describe the Management Indicators of a 3M 2 1 2

Process Instrumentation?

6c. Explain about Round-Trip Engineering in 10M 2 1 2

Detail?

UNIT-V

1. 1a. State advantages Next-Generation Software 2M 3 1 1

Economics?

1b. Describe the activities of Software Architecture 3M 3 1 4

team?

1c. Discuss clearly the software management team 10M 3 1 2

activities, software architecture team activities and
also software development team activities?

2. 2a. Explain about Modern Process Transitions? 2M 3 1 1

2b. Explain about the key points of a Modern 3M 3 1,5,6 2

process transition?
 2c. Explain about the Next generation software 10M 3 1 2
economics?

3. 3a. Describe about Future Software Project 2M 3 1 1

Management Practices?

3b. Describe the activities of a Software 3M 3 1,5,6 2

Development Team?

3c. Explain about the Modern process transitions? 10M 3 1 2

4. 4a. Describe the CCPDS-R Case Study? 2M 3 1 1

4b. Describe the Future Software Management 3M 3 1 2

Practices?

4c. Explain in details about Modern Project 10M 3 1 2

Profiles?

5. 5a. Define Modern Project Profiles? 2M 3 1,8,9 2

5b. Describe the activities of a Software 3M 3 1 3

Management Team?

5c. Discuss about CCPDS-R Case Study? 10M 3 1,5,6 2

6. 6a. What are the Major points CCPDS-R Case 2M 3 1,5,6 1

Study?

6b. Write short notes on the Next – Generation 3M 3 1,5,6 2

software economics? Understand

6c. Explain about the Future Software Project 10M 3 1,5,6 2

Management Practices?
Objective Questions

UNIT I
Choose The Correct Answers

1. Capability level in which process area is either not performed or doesn't achieve all goals
and objectives defined by CMMI respective level
a.) Level 0: Incomplete b.) Level 0: Complete c.) Level 1: Performed d.) Level2:
Managed

2. Process area in which organizational innovation and deployment casual analysis

and resolution is present has level of

a.) Optimizing b.) defined c.) managed d.) performed

3. In PSP, component level design is refined and reviewed by

a.) postmortem b.) planning c.) high level design d.) Development

4. Which of the following is not a maturity level in CMM

a). Design b) Repeatable c) Managed d) Optimizing

5. TSP recognizes that best software teams are

a.) user-directed b.) manager-directed c.) engineer-directed d.) self-directed

6. Which of the following risks are derived from the organizational environment where
the software is being developed?
a.) People Risks b.) Organizational risks c.) Estimation risks d.)
Technology risks

7. Identify the sub-process of process improvement. Select anyone:

a.) Process Distribution b.) De-Processification c.) Process Introduction d.)
Process Analysis

8. Project has uncertainties on some functionalities at the beginning which will improve
over time. Which software development model is suitable?
Select one:
a. None of the above b. Waterfall c. Iterative d. Incremental

9. Object point method best suited for

a. Designing b. Testing c. Coding d. Estimation

10. This term is least critical from customer view point

a. UAT b. Unit testing c. Delivery timeliness d. Milestones
Fill in the Blanks:

11. There are types of work breakdown structures.

12. Model is not suitable for not accommodating any change.

13. Percentage of Defect Free modules at Entrance to compile time must be

14. Percentage of Defects at the Unit Testing must be

15. Percentage of Defects at the System Testing must be

16. AOSD stands for

17. Framework that encompasses a process, set of methods and an array of tools is

termed as

18. According to , the causes of nonconforming product should be eliminated

and Identified.

19. At higher recovery distillate is produced.

20. COTS stands for

 UNIT II
Choose The Correct Answers

1. Quality planning is the process of developing a quality plan for

a) Team b) project c) customers d) project manager

2. Which of the following is incorrect activity for the configuration management of

a software system?

a) Internship management b) Change management c) Version management d) System

3. An independent relationship must exist between the attribute that can be measured by

the External quality attribute.

a)True b) False

4. Which one of the following models is not suitable for accommodating any change?

a) Build & Fix Model b) Prototyping Model c) RAD Model d) Waterfall Model

5. Which model can be selected if user is involved in all the phases of SDLC?

a)Waterfall Model b) Prototyping Model c) RAD Model d) both B &C

6. Which of the following is a people-intensive activity?

a. Project management b. Organization c. Motivation d. Problem solving

7. What are the signs that a software project is in trouble?

a. Changes are managed poorly. b. Deadlines are unrealistic
c. The product scope is poorly defined d. All of the given options.

8. The project life cycle consists of

a. Objectives of the project b. All of the above

c. Formulation and planning various activities d. Understanding the scope of the project

9. An estimation technique measure the size of the functionality to be developed.

a. Analogy b. Function Point c. WBS d. ISO 9001

10. Which of the following is not generally considered a stakeholder in the software process?
a. end users b. project team c. sales team d. customer
Fill in The Blanks:

11. is the simplest model of Software Development Paradigm.

12. A proven methodical life cycle is necessary to

projects successfully.

13. A 66.6% risk is considered as .

14. —————— is the modern software development lifecycle methodology.

15. A is the sequence of processing steps that completely handles one business transaction
or customer request

16. A 66.6% risk is considered as

17.SDLC stands for

18. RAD stands for

19.Build & Fix Model is suitable for programming exercises of

20.RAD Model has phases

 UNIT III
Choose The Correct Answers

1. Which of the following are parameters involved in computing the total cost of a
software development project?
a)Hardware and software costs b) Effort costs c) Travel and training costs d) All of the
mentioned

2. Which of the following costs is not part of the total effort cost?
a)Costs of networking and communications b) Costs of providing lighting office space
c) Costs of lunch time food d) Costs of support staff

3. What is related to the overall functionality of the delivered

software? a)Function-related b) Product-related metrics
c)size related metrics d) None of the mentioned

4. It is often difficult to estimate size at an early stage in a project when only

a specification is available

a)True b) False

5. Which model is used to compute the effort required to integrate reusable

components or program code that is automatically generated by design or program
translation tools?
a) An application-composition model b) A post-architecture model
c) A reuse model d) An early design model

6. Project management (PM) is the application of to meet project

requirements. a.) skills, tools and techniques b.) knowledge, skills, tools
and techniques
c.) knowledge, tools and techniques d.) knowledge, skills, tools

7. Which of the following is not achieved by an automated estimation

tools? a.) Predicting clients demands. b.) Predicting software
schedules.
c.) Predicting software cost. d.) Predicting staffing levels.

8. Following method is not used for project planning

a.) Activity Diagram b.) CPM c.) Timesheet d.) Gantt chart

9. The project life cycle consists of

a.) Objectives of the project b.) All of the above
c.) Formulation and planning various activities d.) Understanding the scope of the project

10. Which of the following is not a commonly used technique for schedule compression
a.) quality reduction b.) use of overtime c.) scope reduction d.) resource
reduction
Fill in the Blanks:

11. is used to detect fraudulent usage of credit cards. A:Outlier Analysis

12. is not considered a risk in project management. A: Testing

13. Quality planning is the process of developing a quality plan for A: Project

14. is the sub process of process improvement.A: Process Analysis

15. The project usually provides the direction and funding for the project. A: Sponsor

16. A is developed using historical cost information that

relates some software metric to the project cost. A: Algorithmic cost modeling

17. The limitations of scope, time, and cost goals are sometimes referred to
as the .A: Triple Constraint

18. Function-related metrics related to the overall functionality of the delivered software?

19. Estimation by analogy technique is applicable when other projects in the same

analogy application domain have been completed?

20. Parkinson’s Law states that work expands to fill the time available
 UNIT IV
Choose The Correct Answers
1.Which of the following is not considered as a risk in project management?

a) Specification delays b) Product competition c) Testing d) Staff turnover 2.The

process each manager follows during the life of a project is known as

a) Project Management b) Manager life cycle

c) Project Management Life Cycle d) All of the mentioned 3.Inspections and

testing are what kinds of Quality Costs?

a) Prevention b) Internal Failure c) External Failure d) Appraisal

4. Which of the following is not a core step of Six Sigma?

a) Define b) Control c) Measure d) Analyze 5.Software

safety is equivalent to software reliability.

a) True b) False

6. In the example of the project of building a house, the would normally be the
general contractor responsible for building the house.
a.) project sponsors b.) project team c.) project manager d.) support staff

7. Project management ensures that the project will satisfy the stated or
implied needs for which it was undertaken.
a.) cost b.) time c.) scope d.) quality

8. Achieving high performance on projects requires , otherwise called human

relations skills.
a.) capital skills b.) soft skills c.) light skills d.) hard skills

9. Most people agree that the modern concept of project management began with the ?.
a.) Great Wall of China b.) first space shuttle c.) Egyptian pyramids d.) Manhattan Project

10. In which year Henry Gantt developed the famous Gantt chart as a tool for scheduling work
in factories.
a.) 1897 b.) 1917 c.) 1927 d.) 1957
Fill in the Blanks:

11. serves as an excellent training ground for future senior executives in

most organizations.

12. The stages in a projects development are known as the .

13. Detailed specifications, schematics, and schedules are all developed during the
stage.

14. Creativity is at its zenith during the stage of the project life cycle.

15. The degree of risk associated with the project is at its highest during the stage.

16. examine program systematically & automatically

17. Test Archiving Systems testing tool is responsible for

18.Beta Testing is done by_

19.Execution Verifier is a dynamic tool that is also known as

20.Percentage of modules that were inspected is a part of

 UNIT V
Choose The Correct Answers

1. Standard Enforcer is a

a) Static b) Dynamic Testing

c) Static & Dynamic Testing d) None of the mentioned

2. Which testing tool does a simple job of enforcing standards in a uniform way of
many programs?
a) Static Analyzer b) Code Inspector
c) Standard Enforcer d) Both Code Inspector & Standard Enforcer

3. Which metric gives the idea about the contents on a web page ?
a) Word Token b) Word Count c) Word Size d) Word Length

4. Which of the following is not a classification of the web engineering metric, Web Page
Similarity ?
a) Content based b) Link based c) Usage based d) Traffic based

5. Which of the following is not a web engineering project metric ?

a) Number of Static Content Objects b) Number of Dynamic Content Objects
c) Number of Inherited Objects d) Word Count

6. Just as passing the CPA exam is a standard for accountants, passing the exam is
becoming a standard for project managers.
a.) PMI b.) PM c.) PMP d.) PMO

7. The Project Management , a Web site for people involved in project management,
provides an alphabetical directory of more than 300 project management software
solutions. a.) Center b.) Alliance c.) Consortium d.) Facility

8. tools are often recommended for small projects and single

users. a.) Low-end b.) Mid Range c.) High-end
d.) Expensive

9. tools, sometimes referred to as enterprise project management software, provide

robust capabilities to handle very large projects.
a.) Low-end b.) Mid range c.) High-end d.) Inexpensive

10. Which management involves defining and managing all the work required to complete
the project successfully?
a.) scope b.) quality c.) time d.) cost
Fill in the Blanks:

11. A refers to ongoing, day-to-day activities in which an

organization engages while producing goods and services.

12. The goals of a project are sometimes called . 13.Projects are -focused.

14. Project management entails crossing and boundaries.

15. In general, product life cycles are becoming and product launch
windows are becoming

16. Link based measures rely on _ of a web graph to obtain related pages

17. is the process of deriving the system design and

specification from its Source code

18. Transformation of a system from one representational form to another is known as

and

19. Extracting data items and objects, to get information on data flow, and to understand
the existing data structures that have been implemented is sometimes called _

20. Software mistakes during coding are known as

 14. Unit wise Learning objectives

UNIT- I
1. Prescribe the conventional and evolution of software.
2. Analyze the importance of improving software economics.
3. Evaluate budget for any small scale projects.
4. Describe the evolution of software economics.
5. Formulate various cost estimation models.

UNIT-II
1. Comprehend the process of managing software from conventional to modern.
2. Catagorize different life cycle phases.
3. Analyse engineering and production stages.
4. Describe various artifact sets.
5. Apply, design & develop the software system process.

UNIT-III
1. Analyse the architecture of a model based software and the process flow
2. Describe various workflows.
3. Summerize the check points of the process.
4. Develop the WBS structure of any project.
5. Illustrate different process planning strategies.

UNIT-IV
1. Analyse the process automation, process management, and its discrminants.
2. Identify seven core metrics.
3. Formulate metric automation.
4. Describe the evolution of organization

UNIT-V
1. Establish modern project profile.
2. Plan and manage projects at each stage of the SDLC.
3. Estimate future technologies of managing software projects.
4. Analyse next generation software economics.
15. Assignment Test Question papers
16.MID-I and MID-II Question papers
 17. MID-I ,MID-II Scheme of Evolution

MID-1 Scheme of Evolution of SPPM

1. A)Define Initial Process?

Initial processing means taking applications for medical assistance, assisting applicants in
completing the application, providing information and referrals, obtaining required documentation
needed to complete processing of the application, and assuring completeness of the information
contained on the application. Initial processing does not include evaluating the information on the
application and supporting documentation, or making a determination of eligibility.

B)Explain about the TSP Reference Model.

The team software process (TSP) provides a defined operational process framework that is
designed to help teams of managers and engineers organize projects and produce software the
principles products that range in size from small projects of several thousand lines of code
(KLOC) to very large projects greater than half a million lines of code. The TSP is intended to
improve the levels of quality and productivity of a team's software development project, in order
to help them better meet the cost and schedule commitments of developing a software system
Some properties: General, domain specific, Client specific and project specific

C) What are process reference model? Explain any two of them?

The process framework or reference model acts as an interface between the way the content is
organized and the way work is performed. A uniform process model organized under a process
reference model makes business modeling and systems designing much easier.
Capability Maturity Model (CMM)
Broadly refers to a process improvement approach that is based on a process model. CMM also
refers specifically to the first such model, developed by the Software Engineering Institute (SEI)
in the mid-1980s, as well as the family of process models that followed.
The Software Engineering Institute (SEI) Capability Maturity Model (CMM) specifies an
increasing series of levels of a software development organization. The higher the level, the better
the software development process, hence reaching each level is an expensive and time consuming
process.

Levels of CMM
• Level One :Initial - The software process is characterized as inconsistent, and occasionally
even chaotic. Defined processes and standard practices that exist are abandoned during a crisis.
Success of the organization majorly depends on an individual effort, talent, and heroics. The
heroes eventually move on to other organizations taking their wealth of knowledge or lessons
learnt with them.
• Level Two: Repeatable - This level of Software Development Organization has a basic
and consistent project management processes to track cost, schedule, and functionality. The
process is in place to repeat the earlier successes on projects with similar applications. Program
management is a key characteristic of a level two organization.
• Level Three: Defined - The software process for both management and engineering
activities are documented, standardized, and integrated into a standard software process for the
entire organization and all projects across the organization use an approved, tailored version of the
organization's standard software process for developing,testing and maintaining the application.
• Level Four: Managed - Management can effectively control the software development
effort using precise measurements. At this level, organization set a quantitative quality goal for
both software process and software maintenance. At this

maturity level, the performance of processes is controlled using statistical and other quantitative
techniques, and is quantitatively predictable.
• Level Five: Optimizing - The Key characteristic of this level is focusing on continually
improving process performance through both incremental and innovative technological
improvements. At this level, changes to the process are to improve the process performance and at
the same time maintaining statistical probability to achieve the established quantitative process-
improvement objectives.
2. A)Explain about elaboration phase?
It is a pre-development stage of the project's creation. It involves numerous investigations and
helps to define the project's scope and clarify all the requirements
B)Describe the Life cycle phases of a software development?

Software Development Life Cycle is the application of standard business practices to building
software applications. It's typically divided into six to eight steps: Planning, Requirements,
Design, Build, Document, Test, Deploy, Maintain.

C) Explain with a neat diagram how various artifacts evolved over the life Understand
cycle?
Artifact is generally used to represent cohesive information that is created and reviewed as a
single entity.
In an artifact, some amount of precision in description of the final system description is
represented at each stage of development. The precision is very low and representation is also
high early in the life cycle process.
Eventually, precision of representation is high and everything is explained even specifies in a
full detailed manner. Each state of development generally focuses on a specific artifact set. The
overall state of a system will also have progressed on all sets at the end of every state or phase.
It is shown in the below diagram.

• Inception Phase: This phase mainly focuses on requirements that are critical usually
with a secondary focus on an initial view of deployment. To achieve concurrence among all
stakeholders on the objectives of lifecycle for project is the overriding target or goal of this
phase. It also focuses on estimating potential risks, estimating the cost and schedule for the
overall project.
• Elaboration Phase: There is a very larger depth in requirements or needs, even more
breadth in the design set, and further focus on the issues of implementation and deployment
during this phase. The activities of elaboration phase must be able to ensure and confirm that
architecture, requirements or needs, and plans are stable enough, and sufficiently mitigation of
the risks, that cost and schedule for completeness of the establishment and development can be
predicted within a range that can be acceptable.
• Construction Phase: Design and implementation are the main and primary goal of this
phase. At this phase, software that is developed newly is integrated and inserted where and
whenever required. The primary goal and objectives of this phase are to minimize or reduce
costs of development by optimizing resources and even avoiding unnecessary scrap, achieve
high quality fastly, and even to achieve versions that are useful as fast as possible.

• Transition Phase: Achieving consistency and completeness of deployment set in the

context of other sets is the primary goal of this phase. This phase must include some of
activities like beta testing to validate system that is new, beta testing, and parallel operation that
are similar or relative to a legacy system, it is replacing, etc.

3. A) Define Optimizing Process?

Process optimization is the discipline of adjusting a process so as to optimize some specified set
of parameters without violating some constraint.

B) Describe ISO 9001 Certification principles required for a software evolution?

Quality system of an organization means the various activities related to its products or services.
Standard of ISO addresses to both aspects i.e. operational and organizational aspects which
includes responsibilities, reporting etc. An ISO 9000 standard contains set of guidelines of
production process without considering product itself.

ISO 9000 Certification

Why ISO Certification required by Software Industry?
There are several reasons why software industry must get an ISO certification. Some of reasons
are as follows :
• This certification has become a standards for international bidding.
• It helps in designing high-quality repeatable software products.
• It emphasis need for proper documentation.
• It facilitates development of optimal processes and totally quality measurements.
Features of ISO 9001 Requirements :
• Document control– All documents concerned with the development of a software
product should be properly managed and controlled.
• Planning–Proper plans should be prepared and monitored.
• Review–For effectiveness and correctness all important documents across all phases
should be independently checked and reviewed .
• Testing–The product should be tested against specification.
• Organizational Aspects– Various organizational aspects should be addressed e.g.,
management reporting of the quality team.
Advantages of ISO 9000 Certification: Some of the advantages of the ISO 9000 certification
process are following :
• Business ISO-9000 certification forces a corporation to specialize in “how they are
doing business”. Each procedure and work instruction must be documented and thus becomes a
springboard for continuous improvement.
• Employees morale is increased as they’re asked to require control of their processes and
document their work processes
• Better products and services result from continuous improvement process.
• Increased employee participation, involvement, awareness and systematic employee
training are reduced problems.
C) Explain about the various Certifications used for Software Assessment?
Several national and international standards institutes, professional and industry-oriented
organizations have been involved in the development of SQA standards.
The following institutes and organizations are the main developers of SQA and software
engineering standards −
• IEEE (Institute of Electrical and Electronics Engineers) Computer Society
• ISO (International Organization for Standardization)
• DOD (US Department of Defense)
• ANSI (American National Standards Institute)
• IEC (International Electro Technical Commission)
• EIA (Electronic Industries Association)
These organizations provide updated international standards to the quality of professional and
managerial activities performed in software development and maintenance organizations.
They also provide SQA certification through independent professional quality audits. These
external audits assess achievements in the development of SQA systems and their
implementation. Certification, which is granted after the periodic audits, will be valid only until
the next audit, and therefore must be renewed. At present, the ISO 9000 Certification Service is
the most prominent provider of SQA certification in Europe and other countries.
They also provide the tools for self-assessment of an organization’s SQA system and its
operation. The Capacity Maturity Model (CMM) developed by the Software Engineering Institute
(SEI), Carnegie Mellon University, and ISO/IEC Std 15504 are the examples of this approach.
SQA Standards
Software quality assurance standards can be classified into two main classes −
• Software quality assurance management standards, including certification and assessment
methodologies (quality management standards)
• Software project development process standards (project process standards)
Quality Management Standards
These focus on the organization’s SQA system, infrastructure and requirements, while leaving the
choice of methods and tools to the organization. With quality management standards,
organizations can steadily assure that their software products achieve an acceptable level of
quality.
Example − ISO 9000-3 and the Capability Maturity Model (CMM)
Project Process Standards
These focus on the methodologies for implementing the software development and maintenance
projects. These standards include the following −
• The steps to be taken
• Design documentation requirements
• Contents of design documents
• Design reviews and review issues
• Software testing to be performed
• Testing topics
Naturally, due to their characteristics, many SQA standards in this class can serve as software
engineering standards and vice versa.
The characteristics of these two classes of standards are summarized in the following table.

Characteristics Quality Management Standards Project Process Standards

Management of software A software development and

The target unit development, maintenance and the maintenance project team
specific SQA units

Methodologies for carrying out

Organization of SQA systems,
The main focus software development and
infrastructure and requirements
maintenance projects
The standard’s
“What” to achieve “How” to perform
objective

Assuring the supplier’s software

Assuring the supplier’s software
The standard’s quality and assessing its software
quality and assessing its software
goal process capability Assuring the
process capability
quality of a specific software project.

Examples ISO 9000-3 SEI’s CMM ISO/IEC 12207 IEEEStd 1012-1998

ISO 9001 Certification

ISO (the International Organization for Standardization) is a worldwide federation of national
standards bodies. ISO technical committees prepare the International Standards. ISO collaborates
closely with the International Electro-technical Commission (IEC) on all matters of electro-
technical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives,
Part 2. Draft of the International Standards adopted by the technical committees is circulated to
the member bodies for voting. ISO 9001 was prepared by Technical Committee ISO/TC 176,
Quality management and quality assurance, Subcommittee SC 2, Quality systems.
Process Approach
This International Standard promotes the adoption of a process approach when developing,
implementing, and improving the effectiveness of a quality management system, to enhance
customer satisfaction by meeting the customer requirements. For an organization to function
effectively, it has to determine and manage numerous linked activities. An activity or set of
activities using resources, and managed in order to enable the transformation of inputs into
outputs, can be considered as a process.
Often the output from one process directly forms the input to the next. The application of a system
of processes within an organization, together with the identification and interactions of these
processes, and their management to produce the desired outcome, can be referred to as
the “process approach”.
An advantage of the process approach is the ongoing control that it provides over the linkage
between the individual processes within the system of processes, as well as over their combination
and interaction. When used within a quality management system, such an approach emphasizes
the importance of the following −
• Understanding and meeting the requirements
• Need to consider the processes in terms of added value
• Obtain the results of process performance and effectiveness
• Continual improvement of processes based on objective measurement
ISO 9001 - Application to Software: the TickIT Initiative
TickIT was launched in the late 1980s by the UK software industry in cooperation with the UK
Department for Trade and Industry to promote the development of a methodology for adapting
ISO 9001 to the characteristics of the software industry known as the TickIT initiative.
TickIT is, additionally, specializing in information technology (IT). It covers the entire range of
commercial software development and maintenance services. TickIT, now managed and
maintained by the DISC Department of BSI (the British Standards Institute), is accredited for the
certification of IT organizations in the UK and Sweden.
Its activities include −
• Publication of the TickIT Guide, which supports the software industry’s efforts to spread
ISO 9001 certification. The current guide (edition 5.0, TickIT, 2001), which includes references
to ISO/IEC 12207 and ISO/IEC 15504, is distributed to all TickIT customers.
• Performance of audit-based assessments of software quality systems and consultation to
organizations on the improvement of software development and maintenance processes in
addition to their management.
• Conduct ISO 9000 certification audits.
TickIT auditors who conduct audit-based assessments and certification audits are registered by the
International Register of Certificated Auditors (IRCA). Registered IRCA auditors are required,
among other things, to have experience in management and software development; they must also
successfully complete an auditor's course.
Registered lead auditors are required to have a demonstrated experience in conducting and
directing TickIT audits.
4. A) Define management artifacts?
Management Artifacts includes overseeing whole condition or situation to confirm and ensure that
instructional technology project gets done.
B) Explain about the improving Software Economics in the new way?
Software estimation is needed to be based on very careful analysis and should be supported by
all. Software economics improvements should come from reducing size, improving software
processes, improving team effectiveness, improving automation through software environments,
and achieving the required quality.
Improving Team Effectiveness :No matter how productive the team is, there are always some
ways available with the help of which we can be incorporated to take the productivity of the
workplace to a whole new level. Efficiency generally represents a level of performance that
explains and describes the process that just uses the lowest amount of inputs to develop or
create the greatest or highest amount of outputs. Rather than the sum of the individuals,
teamwork is much more efficient and important nowadays. A team is vulnerable whenever it is
out of balance. Some of the true statements of team management are given below:

• With the help of the engineering team that is nominal or are not expert, a project that is
well and carefully managed can succeed in achieving their purpose.
• Even if the team of engineers is highly expert, a project that is not carefully managed
can never succeed in achieving its purpose.
• With the help of a team of software builders or developers that are not experts or are
nominal, a system that is well-architected can be developed or built.
• Even with the help of a team of software builders or developers that are experts, a
system that is poorly architected will experience many difficulties.
Boehm (1981) have suggested and offered five staffing principles generally to examine how to
staff a software project. These principles are given below:

1. The principle of Top Talent –This principle simply suggests using fewer or fewer
people that are better. The quality of people is very essential and important. So, it is highly
suggested to use a smaller number of peoples with more skills and talent.
2. The Principle of Job Matching –This principle simply suggests to fit and adjust and
task to the skills and the motivation of the people that are available. The skillset of the pe ople
usually varies from one to another. The best programmer might not be suitable as an architect or
a manager. In the same way, an architect or manager is not suitable as a programmer. So, it is
highly suggested to motive them to do their jobs.
3. The Principle of Career Progression – This principle states that an organization does
best and better in the long run just be providing help to its people to self-actualize. All the
training programs of the organization that are having educational value and project training
programs are very helpful and essential for all of the individuals to develop their careers.
4. The Principle of Team Balance – This principle simply suggests to use and select the
people who will complement and harmonize with one other. The psychology of all the team
members will help in balancing the team. All of them should be friendly and should be quickly
mingle with their co-member of the team.
5. The Principle of Phaseout – This principle suggests that keeping a misfit on the team
won’t be going to benefit anyone.

C) Briefly explain about the evolution of Software Economics?

Software Economics in Software Engineering is mature research area that generally deals with
most difficult and challenging problems and issues of valuing software and determining or
estimation costs usually involved in its production. Boehm and Sullivan outline these difficulties
and challenges and also presented how software economics principles can be applied to improve
software design, development, and evolution.
Software economics is basically situated at intersection of information economics and even
software design and engineering. Most of software cost models are generally abstracted into
function of five basic parameters. These parameters are given below :
• Size –Size is generally measured or qualified in term of number of source instructions or in
SLOC (Source line of code) or number of function points required to realize desired capabilities.
The size of end product or result is required to develop or create required functionality.
• Process –The process is steps that are used to guide all of activities and produce end
products, in particular ability and capability of process to avoid or ignore activities that are not
adding any value. It also supports heading towards the target or goal and eliminate activities that
are not essential or important.
• Personnel –The capabilities of personnel of software engineering in general, and
particularly their experience with issues or problems regarding computer science and issues
regarding application domain of project. It emphasizes on team and responsibilities of team.
• Environment –It is simply made of various tools and techniques and automated procedures
that are available and used to support software development and effort in an efficient way.
• Quality –The required quality along with its features, performance, reliability, scalability,
portability, usability, user interface utility, adaptability, and many more.
Between these parameters, relationship and estimated cost can be written in following way :
Effort = (Personnel) (Environment) (Quality) (Size Process)
Generations of Software Development –There are three generations of software development as
described below :
• Conventional Development (1960s and 1970s) –During this generation, organizations used
various custom tools, custom processes, and all components of custom that are built or developed
in primitive languages. The size is 100 % custom. At this generation, conventional development is
generally considered bad. It is because it was always costly and over budget and schedule. It also
does not fulfill requirements that are necessary such as some components, symbolic languages,
other languages like Fortran, PL/1, etc. The quality of performance was always poor and less than
great.
• Transition (1980s and 1990s) –During this generation, organizations used various
repeatable processes and off-the-shelf tools, and more likely to use custom components) that are
generally developed in high-level languages. The size is 30 % component-based and 70 %
custom. It is not predictable to decide whether it is bad or good. Transition development is
infrequently on budget and schedule. Some of commercial components were simply available
such as databases, networking along with operating system, database management system, and
graphical user interface. But due to an increase in complexity, all languages and technologies
available were not enough for desired business performance.
• Modern (2000 and later) –Modern development processes are generally measured and
managed, integrated automated environments, 70% off-the-shelf components. The size is 70 %
component-based and 30 %custom. Modern development is usually in budget and in schedule.
Improved “process” requires “tools” that are improved. The improved process requires
environmental support. Various technologies other for environment automation, size reduction,
and process improvement are not independent of each other. In the new era, main key is only
complementary growth in all these technologies
20. Previous Year University Question Papers