Software Quality Assurance

1. Software Quality Assurance By Adnan Khan

2. Software Configuration Management (SCM) The process of identifying, organizing, and controlling changes to the software during development and maintenance. • SCM is a support activity that makes technical and managerial activities more effective • SCM operates throughout the SW life-cycle

3. Causes of Change • Evolutionary changes • the system evolves as it passes through various stages in the development cycle • Revolutionary changes • such change is caused by the system being unable to satisfy the user’s requirements or the customers or producers expectations

4. Why Products change ? • Requirements change during and after development • Errors are found and need correction • Variants are needed

5. Problems of Change Which component ? Which version ? • Double (or multiple) maintenance • Updates to shared data • Simultaneous update

6. SCM Functions • Identification of software items and products • Definition of Baselines • Access controls • Progressing defect reports • Progressing change requests • Recording item status • Controlling releases (versions and variants) • Reporting

7. SCM Tasks • Configuration identification • Configuration control • Configuration audit

8. Typical SW Configuration Items (CIs) • Management plans • Specifications (requirements, design) • User documentation • Test design, case and procedure specifications • Test data and test generation procedures • Data dictionaries and databases • Source code, executable code • Libraries • Maintenance documentation • Support software

9. Milestones and Baselines • Milestone • A milestone is the end of a stage or phase of a project at which one or more deliverables are actually delivered. • Baselines • A baseline is that collection of items which when complete indicates that a milestone in the development process has been reached.

10. Baselines • Baselines serve as the basis for further development • Baselines can be changed only through formal change control procedures • Only items that have been approved and obtained through a formal technical review are accepted into the baseline.

11. Configuration Identification • Identify what the different baselines will consist of • Set labelling and identification conventions for the CIs

12. SCM Terminology • Version • A SW CI having a defined set of functional capabilities. • Revisions • Changes to a version to correct only errors in design logic but does not affect documented functional capabilities since none of the requirements have changed. • Variants • A variation of a version developed to run on different types of HW, or to provide slightly different facilities for different users.

13. 1.1 1.2 1.3 1.4 1.1 1.2 1.3 1.4 Examples successive versions branching versions (variants) 1.3.1.1 1.3.1.2

14. Merging • Two diverging versions may be merged to create a single new version combining both set of change requests. • Merge operations are typically done interactively with tool assistance

15. SCM Terminology • Promotion of a CI • A CI may be promoted from one developmental baseline to another to signify a change in a CI’s internal development state. • Release • A Release is used to designate certain promotions of CI’s that are distributed outside the development organization.

16. Configuration Control • Enforces a rigorous change control mechanism • Requires formal procedures to • request changes • carry out impact analysis • approve changes • carry out changes

17. Change Management Methodology • Submission of Change Request (CR) • Technical and business evaluation and impact analysis • Approval by Change Control Board • Engineering Change Order (ECO) is generated stating • changes to be made • criteria for reviewing the changed CI • CI’s checked out • Changes made and reviewed • CI’s checked in

18. Change Control Board • A group consisting of representatives of user, customer, producer. • Responsibilities: • to approve, monitor and control baselines • to approve, monitor, and control changes • to authorise changes • CCB concerns in change approval • technically ok solution, cost, schedule, configuration of the whole system, user satisfaction

19. Organising for SCM Roles: • Configuration manager • Change Control Board • includes representatives of • user • customer • developer

20. SCM Plan • The SCM Plan is prepared in Project Initiation phase. It documents • what SCM activities are to be done • how they are to be done • who is responsible for doing specific activities • when they are to happen • what resources are required

21. SCM Tools • Popular PC-based tools • PVCS, MS Visual SourceSafe, Subversion, Rational Clearcase • Common Features • Support for controlling all types of files (source code as well as binary) • Supporting branching and merging • Identifying and re-creating releases • Providing a project view

22. Rational Clearcase • VOB (Versioned Object Base) • Configuration Record • Build Avoidance • Unix/Windows Interoperability • Integration With Other Products

23. SW Configuration Management Plan -- IEEE Standard 828-1990 for SCM Plan 1. Introduction 2. SCM Management 2.1 Organization 2.2 SCM Responsibilities 2.3 Applicable policies, directives and procedures

24. SW Configuration Management Plan -- IEEE Standard 828-1990 for SCM Plan 3. SCM Activities 3.1 Configuration identification 3.1.1 Identifying configuration items 3.1.2 Naming configuration items 3.1.3 Acquiring configuration items 3.2 Configuration control 3.2.1 Requesting changes 3.2.2 Evaluating changes 3.2.3 Approving or disapproving changes 3.2.4 Implementing changes

25. SW Configuration Management Plan -- IEEE Standard 828-1990 for SCM Plan (3. SCM Activities) 3.3 Configuration Status Accounting 3.4 Configuration Audits and Reviews 3.5 Interface control 4. SCM Schedules 5. SCM Resources 6. SCM Plan maintenance