CS-724 Software Process Improvement
Mcqs
Q & A
Video
Online Test
Foram
Short Question & Answers
Q1: Steps of Project Planning. Explain software scope. 5marks
Fall 2016 – Mid
Steps of Project Planning:
• Software scope • Estimation • Risk • Schedule • Control strategy

Software Scope:
• Understand the problem and the work that must be done – in a nutshell
• Software scope describes the data and control to be processed, function, performance, constraints, interfaces, and reliability
• Project scope must be unambiguous and understandable at the management and technical levels
• A statement of software scope must be bounded – in other words
• At the beginning of a project, things are very hazy and nothing is clear
• Good and open communication is required between developers and customer to define the scope of the project
• Who is behind the request for this work?
• Who will use the solution?
• What will be the economic benefit of a successful solution?
• Is there another source for the solution?
Q2: KPA of "Software Quality Management" of CMM Level-4. 5 Marks
Fall 2016 – Mid
Purpose:
• Purpose is to develop a quantitative understanding of the quality of the project’s software products and achieve specific quality goals
• Involves
    - Defining quality goals for the software products,
    - Establishing plans to achieve these goals
    - Monitoring and adjusting software plans and work products

Building High-Quality Products:
• Software Quality Management Focuses on the product.
• Measurable quality goals for the product are defined.
• The product is ready when the goals are achieved.

Quality Evolves:
• At level 2 the focus of quality is conformance to requirement
• By level 4 there is emphasis on understanding needs of the
    - Customer
    - End users
    - Organization (supplier)
• Ultimately customer determines what quality is or is not
• TQM revolves around customer satisfaction
Q3: Explain process area "Supplier agreement management" of CMM level 2. 10 Marks Fall 2016 – Mid
 
Q4: Explain process area "Technical Solution" of CMM level 3. 5 Marks
Fall 2016 – Mid
 
Q5: explain W and A process models. 5 Marks
Fall 2016 – Mid
 
Q6: What is KPA process definition of CMMI? 5 marks
Fall 2016 – Mid
 
Q7: What is project tracking and oversight of CMM. 5 Marks
Fall 2016 – Mid
 
Q8: Explain KPA “Organizational training”. 10 Marks
Fall 2016 – Mid
 
Q9: Give EVTX model of Rework Activity in Inspection. 5 Marks
Fall 2016 – Mid
 
Q10: Explain organization focus.
Fall 2016 – Mid
 
Q11: What is continuous and staged representations and their advantages.
Fall 2016 – Mid
 
Q12: Explain casual analysis and resolution. 10 Marks
Fall 2016 – Mid
 
Q13: Explain KPA “Software product engineering”. 5 Marks
Fall 2016 – Mid
 
Q14: Explain “Data recording and report” in inspection activity with ETVX model. 5 Marks
Fall 2016 – Mid
 
Q15: What are attributes of process to choose or satisfy the CMMI model? 5 marks
Fall 2016 – Mid
 
Q16: Explain "Verification" process area in CMMI 3. 10 marks
Fall 2016 – Mid
 
Q17: Explain Software Quality Management CMMI 4. 5 Marks
Fall 2016 – Mid
 
Q18: What are the attributes of processes according to CMMI?
Fall 2016 – Mid
 
Q19: PSP measurements.
Spring 2016 – Final
 
Q20: Lack of management support and user involvement.
Spring 2016 – Final
 
Q21: Principles of teambuilding.
Spring 2016 – Final
 
Q22: absolute scale with example.
Spring 2016 – Final
 
Q23: Standard 12207
Spring 2016 – Final
 
Q24: SPR approach
Spring 2016 – Final
 
Q25: Backlog management and fix response time
Spring 2016 – Final
 
Q26: TSP launching project step
Spring 2016 – Final
 
Q27: Given a diagram of data collection and we have to explain
Spring 2016 – Final
 
Q28: Explain estimation step of planning and organization
Spring 2016 – Final
 
Q29: Explain TSP BOX competency area
Spring 2016 – Final
 
Q30: Explain level 5 of people CMM
Spring 2016 – Final
 
Q31: Explain software measurement
Spring 2016 – Final
 
Q32: How was GQM used by AT&T to help determine which matrices were appropriate for assessing their inspection processes 10 marks
Spring 2016 – Final
 
Q33: Briefly explain “act” step of Shevart’s cycle 10 marks
Spring 2016 – Final
 
Q34: Define the levels of people CMM 10 marks
Spring 2016 – Final
 
Q35: Explain the process matric “ defect arrival rate” 5 marks
Spring 2016 – Final
 
Q36: Explain component of planning and organization “ effective communication” & “steering committee” 5 marks
Spring 2016 – Final
 
Q37: Explain team building principles in TSP 5 marks
Spring 2016 – Final
 
Q38: Briefly explain 4 organizational paradigm for software engineering
Spring 2016 – Final
 
Q39: What are the types of process pattern 5
Spring 2016 – Final
 
Q40: What are process area of people CMM level 3
Spring 2016 – Final
 
Q41: Explain one classification example of interval scan and ratio scale 10
Spring 2016 – Final
 
Q42: Explain SPR assessment approach 10
Spring 2016 – Final
 
Q43: Explain the level 1 of people CMM 10
Spring 2016 – Final
 
Q44: What are the various PSP measures 10
Spring 2016 – Final
 
Q45: Brief explain process assurance 5 marks
Spring 2016 – Final
 
Q46: What are various measurements scales and explain also 10 marks
Spring 2016 – Final
 
Q47: Explain team foundation 10 marks
Spring 2016 – Final
 
Q48: Explain project team and project standard 10 marks
Spring 2016 – Final
 
Q49: Workforce principles
Spring 2016 – Final
 
Q50: GQM approach
Spring 2016 – Final
 
Q51: CMM maturity levels
Spring 2016 – Final
 
Q52: Explain the Benchmarks
Spring 2016 – Final
 
Q53: Quality management
Spring 2016 – Final
 
Q54: Defects measures.
Spring 2016 – Final
 
Q55: Explain the PSP process level “ personal quality management” 10 marks
Spring 2016 – Final
 
Course Instructor

Dr. Ghulam Ahmad Farrukh Ph.D Software Engineering George Mason University, USA
Books

Managing the Software Process by Watts Humphrey

Requirements Engineering by Gerald Kotonya and Ian Sommervillephrey

Software Engineering by Roger Pressman

Inroads to Software Quality by Alka Jarvis and Vern Crandal

A Handbook of Software Quality Assurance by G. Gordon Schulmeyer and James L. McManus

Measuring the Software Process by William Florac and Anita Carleton

The Capability Maturity Model, Guidelines for Improving Software Process

Interpreting the CMMI: A Process Improvement Approach by Margaret K. Kulpa and Kent A. Johnson

Introduction to the Personal Software Process by Watts Humphrey

Introduction to the Team Software Process by Watts Humphrey

Software Assessments, Benchmarks, and Best Practices by Capers Jones

People CMM: A Framework for Human Capital Management by Bill Curtis, William E. Hefley, and Sally A. Miller, Addison-Wesley

Software Metrics: A Rigorous & Practical Approach, by Norman E. Fenton and Shari L. Pleeger

Metrics and Models in Software Quality Engineering by Stephan H. Kan

Practical Software Metrics for Project Management and Process Improvement by Robert Grady