INTRODUCTION

QUALITY MANAGEMENT STANDARDS

ITS 473 SOFTWARE IMPROVEMENT

Lecture 2

1

What do you learn?Quality management activitiesScope of Quality Management StandardsSoftware Engineering Institute (SEI) and its rolesWhy Software Process should be managedCommon process problems

Scope of quality managementQuality management is particularly important for large, complex systems. The quality documentation is a record of progress and supports continuity of development as the development team changes.For smaller systems, quality management needs less documentation and should focus on establishing a quality culture.

Quality management activitiesQuality assuranceEstablish organisational procedures and standards for quality.Quality planningSelect applicable procedures and standards for a particular project and modify these as required.Quality controlEnsure that procedures and standards are followed by the software development team.Quality management should be separate from project management to ensure independence.

Quality management and software development

The Scope of Quality Management StandardsThe scope of certification standards is determined by the aims of the certification, which are to:

Enable a software development organization to demonstrate consistent ability to assure that its software products or maintenance services comply with acceptable quality requirement

Serve as an agreed basis for customer and supplier evaluation of the suppliers quality management system

Support the software development organizations efforts

6

How to Manage the Quality??Practicing some standards or model such as:

7

Software Engineering Institute (SEI)Federally funded research and development center (FFRDC) established 1984Awarded to Carnegie Mellon UniversitySponsored by the Office of the Secretary of Defense/Acquisition, Technology, and Logistics (OSD/AT&L)

8

SEI Mission and VisionMission: to provide leadership in advancing the state of the practice of software engineering to improve the quality of systems that depend on software.Vision: to bring engineering discipline to the development and maintenance of software.

9

Definition Of ProcessA process is defined as the logical organization of people, materials, energy, equipment and procedures into work activities designed to produce a specific end result.

Process orientation contributes to a better understanding of the ultimate goal and output of the company and the individuals role in it.

Modeling and analyzing business processes enables one to develop the organization and improve its effectiveness and quality of work.

10

Process What holds everything together? It is the process used in organization that align the way you do business, address scalability and provide a way to incorporate knowledge of how to do things better.

11

Process FrameworkWhat holds everything together? It is the process used in organization that align the way you do business, address scalability and provide a way to incorporate knowledge of how to do things better.

12

ProcessWhy do you need a process?"If you don't know where you are going, any road will do." Chinese Proverb"If you dont know where you are, a map won't help." Watts Humphrey"If you don't know where you are going, a map won't get you there any faster." Anonymous "You can't expect to be a functional employee in a dysfunctional environment" Watts Humphrey(Humphrey, S.W Managing the Software Process)Express the need to appraise the software process to know where you are and the need for a vision, or model, for where you want to goDocumented processes are the basis for consistent performance and improvement

13

Why Should We Manage the Software Process?

15Individuals, Teams, and ArmiesHistory of software is one of increasing scaleInitially a few people could craft small programsToday large projects require the coordinated work of many teamsThe increase in scale requires a more structured approach to software process management

16People and the Software ProcessTalented people are the most important element in a software organizationSuccessful organizations provide a structured and disciplined environment to do cooperative workAlternativeEndless hours of repetitively solving technically trivial problemsTime is consumed by mountains of uncontrolled detailIf the details are not managed, the best people cannot be productiveFirst class people need the support of an orderly process to do first-class work

17Myth of the Super ProgrammersCommon view: First-class people intuitively know how to do first-class workImplication: No orderly process framework is neededConclusion: Organizations with the best people should not suffer from software quality and productivity problemsHowever, studies show that companies with top graduates from leading universities are still plagued with the same problemsNew Conclusion: The best people need to be supported with an effectively managed software process

18Myth of Tools and TechnologyCommon View: Some technically advanced tool or method will provide a magic answer to the software crisisReality: Technology is vital, but unthinking reliance on an undefined "silver bullet" will divert attention from the need for better process management

19Major Concerns of Software ProfessionalsOpen-ended requirementsUncontrolled changeArbitrary schedulesInsufficient test timeInadequate trainingUnmanaged system standardsVery few even mention technology as a key problem

20Limiting Factors in using Software TechnologyPoorly-defined processInconsistent implementationPoor process management

21Focusing on Software Process ManagementSoftware process: the set of actions required to efficiently transform a user's need into an effective software solutionMany software organizations have trouble defining and controlling this processEven though this is where they have the greatest potential for improvementThis is the focus of the book "Managing the Software Process"

The Role of ProcessEveryone realizes the importanceof having a motivated, quality work forceand the latest technology, but even the finest people cant perform at their bestwhen the process is not understoodor operating at its best

22

Common Process Problem Symptoms of Process FailureCommitments consistently missedLate deliveryLast minute crunchesSpiraling costsNo management visibility into progressYoure always being surprised (eg. No project tracking)Quality problemsToo much reworkFunctions do not work correctlyCustomer complaints after deliveryPoor moralePeople frustratedIs anyone in charge?

23

The Process Management PremiseThe quality of a product is largely governed by the quality of the process used to build it

The quality of a software product is largely governed by the quality of the software process used to develop and maintain it

*premise : assumption that something is true

The Software Process Improvement Principle

The process to develop and maintain software can be defined, managed, measured, and continuously improved