SE422 Software Quality AssuranceCH-6 Development and quality plans

Software EngineeringCollege of Arts, Media and Technology ,CMU.

Kittitouch S.1.1-12-12-11

Topics

Development plan and quality plan objectives

Elements of the development plan Elements of the quality plan Development and quality plans for

small projects and for internal projects

Development plan and quality plan in ISO29110

The project needs development and quality plans that:

Are based on proposal materials that have been re-examined and thoroughly updated.

Are more comprehensive than the approved proposal, especially with respect to schedules, resource estimates, and development risk evaluations.

The project needs development and quality plans that:

Include additional subjects, absent from the approved proposal.

Were prepared at the beginning of the project to sound alerts regarding scheduling difficulties potential staff shortages problems with meeting contractual

milestones modified development risks

Development and quality plan-software standard

Development and quality plans are major elements needed for project compliance ISO9000.3 ISO730 ISO12207 ISO29110 CMMi

Development plan and quality plan objectives

1. Scheduling development activities that will lead to the successful and timely completion of the project, and estimating the required manpower resources and budget.

2. Recruiting team members and allocating development resources (according to activity schedules and manpower resource requirement estimates).

Development plan and quality plan objectives (cont)

3. Resolving development risks.

4. Implementing required SQA activities.

5. Providing management with data needed for project control.

Elements of the development plan

1. Project products, specifying “deliverables”2. Project interfaces3. Project methodology and development tools4. Software development standards and

procedures5. Map of the development process6. Project milestones7. Project staff organization8. Required development facilities9. Development risks and risk management actions10. Control methods11. Project cost estimates

1. Project products

The development plan includes the following products: Design documents specifying dates of

completion, indicating those items to be delivered to the customer (“deliverables”)

Software products (specifying completion date and installation site)

Training tasks (specifying dates, participants and sites).

Deliverables

No. Deliverables/Release

Media Qty Due date

1 Proposal Hard copy 4 12-12-2011

2 SRS Hard copy 1 20-12-2011

3 Acceptance test report

Hard copy 1 30-01-2012

4 Software DVD 10 1-02-2012

Example of Deliverables table

2. Project interfaces

Project interfaces include: Interfaces with existing software

packages (software interface) Interfaces with other software and/or

hardware development teams that are working on the same system or project (i.e., cooperation and coordination links)

Interfaces with existing hardware (hardware interface)

4. Project methodology and development tools

Software development model Waterfall Agile V-Model and so forth

Development tools Hardware and Software Management tool

4. Software development standards and procedures

Software development standards ISO CMMi TQS

Procedures Processes Tasks WBS:Work breakdown structure

5.The mapping of the development process

An estimate of the activity’s duration. These estimates are highly dependent on the experience gained in previous projects.

The logical sequence in which each activity is to be performed ,including a description of each activity’s dependence on previouslycompleted activities.

5.The mapping of the development process (cont)

The type of professional resources required and estimates of how much of these resources are necessary for each activity.

Gantt chart

6. Project milestones

For each milestone, its completion time and project products (documents and code) are to be defined.

7. Project staff organization

The organization plan comprises: Organizational structure Professional requirements Number of team members required

for each period of time Names of team leaders and team

members.

8. Development facilities

Required development facilities include hardware, software and hardware development tools, office space, and other items. For each facility, the period required for its use should be indicated on the timetable.

9. Development risks

Development risks are inherent in any project. To understand their pervasiveness, and how they can be controlled,

A development risk is “a state or property of a development task or environment, which, if ignored, will increase the likelihood of project failure”

Typical development risks are:

Technological gaps Staff shortages Interdependence of organizational

elements

The top 10 major software risk items are shown in the Appendix to this chapter in Table 6A.1.

10. Control methods

In order to control project implementation, the project manager and the department management apply a series of monitoring practices when preparing progress reports and coordinating meetings.

11. Project cost estimation

Project cost estimates are based on proposal costs estimates.

based on updated human resource estimates, contracts negotiated with subcontractorsand suppliers, and so forth.

Development plan approval

Development plan review and approval is to be completed according to the procedures applied within the organization.

Elements of the quality plan

1. List of quality goals2. Review activities3. Software tests4. Acceptance tests for software

externally developed5. Configuration management tools

and procedures

1. List of quality goals

The term “quality goals” refers to the developed software system’s substantive quality requirements.

Quantitative measures are usually preferred to qualitative measures when choosing quality

Example

HDS qualitative requirement The HDS should be user friendly

Related quantitative quality goalsA new help desk operator should be able

to learn the details of the HDS following a course lasting less than 8 hours, and to master operation of the HDS in less than 5 working days.

2. Review activities

The quality plan should provide a complete listing of all planned review activities: design reviews (DRs) design inspections code inspections

2. Review activities(cont)

The scope of the review activity The type of the review activity The schedule of review activities (as

defined by its priority and the succeeding activities of the project process)

The specific procedures to be applied Who is responsible for carrying out

the review activity?

ExampleStage Exit Review

No Stage Review Item Responsibility

1 Preliminary Planning

Preliminary Planning Doc

PL

2 Web site Structure Study

Web site Structure Doc

PL

3 Requirement Specification

WSRS Document PL

4 Project Planning WPMP Document Senior Manager

5 Design 3 Style Home Pages

3 Style Home Pages (Picture Layout)

CD

6 Design Next Web Pages

All Web Pages CD

7 Arrangement and Translate Text

Text Arrangement and Translation

WCDM

3. Planned software tests The quality plan should provide a

complete list of planned software tests, with the following designated for each test:

The unit, integration or the complete system to be tested

The type of testing activities to be carried out, including specification of computerized software tests to be applied

3. Planned software tests(cont)

The planned test schedule (as defined by its priority and the succeeding activities of the project process)

The specific procedures to be applied Who is responsible for carrying out

the test.

4. Planned acceptance tests for externally developed software

A complete list of the acceptance tests planned for externally developed software should be provided within the quality plan.

items to be included are.. (a) purchased software, (b) software developed by

subcontractors, (c) customer-supplied software.

5. Configuration management

Who make changes?

What changes are made?

When are changes made?

Why are changes made?

Source of Changes

Requirements Changes in funding. Technology advancements. Solutions to problems. Scheduling constraints. Customer expectations. Unexpected opportunities for an

improved system.

The quality plan document, its format and approval

The quality plan may be prepared as part of the development plan or as an independent document.

Review and approval of the quality plan should be conducted according to the organization’s standard procedures for such plans.

Development and quality plans for small projects and for internal projects

The development plan: Project products, indicating

“deliverables” Project benchmarks Development risks Estimates of project costs

The quality plan: Quality goals

Development plan and quality plan in ISO29110

Project plan(+ quality goal) is major element needed for ISO29110 standard.

Activities relate to ISO29110 (example) The Project Plan for the execution of the

project is developed according to the Statement of Work and reviewed and accepted by the Customer. The tasks and resources necessary to complete the work are sized and estimated.

Example of tasksProject Management (PM) Process

ISO29110 VSE Certification Preparation

Training

PM PM.1.8 Calculate and document the project Estimated Effort and Cost.

Schedule of the Project TasksResources

Estimated Effort and Cost

PMTL

PM.1.9 Identify and document the risks which may affect the project.

All elements previously defined

Identification of Project Risks

PMTL

PM.1.10 Document the Version Control Strategy in the Project Plan.

Version Control Strategy

PM PM.1.11 Generate the Project Plan integrating the elements previously identified and documented.

TasksEstimated DurationResources Composition of Work TeamSchedule of the Project TaskEstimated Effort and CostIdentification of Project RisksVersion Control Strategy Delivery Instructions

Project Plan

Referrence

Chapter 6:Daniel Galin. SOFTWARE QUALITY ASSURANCE From theory to implementation. Pearson Education Limited,2004.