The Software Quality Life Cycle

Published Date: 02 Nov 2017

Contents

Introduction

Nowadays, there are many factories in the world that they face many problems such as Involve all the software product of the organization and covered from requirement until deployment stage in the software quality life cycle. Software quality Engineering gives us powerful benefit, since people are more and more place trust in many of information systems. Therefore, an important issues for end –user this is that how to set up an estimation model to choose a better software quality suitable. This document show think over questions of what software process appraisal should concern it with, how it help to cause to improve software quality, how software metrics characterize and before process estimation what work is needed that become a reality. In this assignment we want firstly at the supervision in which design such as ISO 9001 and Tick IT and Improve IT are taking us. In process analyses the relationships between process quality product quality, process improvement, process metric and analysis, in order that we understand what process estimation we should do if it is really to help an organization improve the quality of its software. It concludes that a change in emphasis away from conformance testing and towards process assessment is to be welcomed and liable to lead to better quality management systems that take into account the process improvement and customer-orientation of total quality management.

Over view:

Hi Tech Co is a well-known software company since 2001. The product this company is (GPS ship)

I am Software Engineering that working in the company the tech . we will want to increase Quality Company .

The first we must over View Company that include main product is a generic software control system for a class of digital devices. There are a number of major clients for this product. This is a very large system involving over 20 development and maintenance staff. It is delivered to the customers in phased releases, typically 9-12 months apart. New releases often contain significant chunks of new functionality to take account of rapidly evolving technological advances.

Problem statement

The customers often report defects such as loss of availability, loss of specific services, or erroneous services. Defects discovered in each of this phases are expected (where relevant) to be traced to a specific module and fixed. An attempt must be made to fix all defects in the subsequent release.

Recently the system has gained a bad reputation for being "unreliable". This is an obvious concern that the management of Hi Tech wants to get to the bottom of. There are also concerns that major defects are not being fixed quickly enough. Because of these, the management realizes that they need to set up a quality system in the company to ensure all future releases are of sufficient high quality.

Aims and objectives

We must be known that a software quality system including four main components.

How does the quality of each component contribute to the quality of the developed software and quality of the software maintenance?

Define software error, software fault and software failure. Explain the different between these undesirable software statuses.

List and briefly describe the various causes of software errors.

Classify the causes of error according to the groups responsible for the error: the client’s staff, the systems analysts, the programmers, the testing staff – or is it a shared responsibility belonging to more than one group

Aim: assuaging software quality within software development process

Objectives:

CMM LEVEL 3

Hire SQE team

Produce SQAP

get an international quality standard (CMM) in the near future

Project planning

Engineering with use Project planning can have an overview of Software Development Quality Plan as belonging to an organization assignment in the direction of the project referring to non-technical necessity on work product connected to the quality, measurements and processes. The foundational rules of the project quality management, particularly quality planning phase are described. One of the most important of organizational participation in quality requirements interpretation that Engineering are discussed, activity and control. On top of that, one instance of the Software Development Quality Plan is given. Some proposals and future directions in the area of software product quality and development process improvements are given.

â– Contract review

â–  Development and quality plans

â– Risk management

Quality plan and development plan objectives

Planning, like a process. It has separate objectives, which each of them meant to pre- pare sufficient substructure for the following:

We should make timetable 0f development activities that will goes to the successful and timely finishing of the project, and approximate the demanded total number of people available for service wealth and budget.

We should enlist or draft new members’ team and allot development resources (according to activity timetable and total number of people available for system resource requirement estimates).

We should solve development risks.

We should executing demanded SQA activities.

We should arranging a person or group of people that manages a business or other enterprise with data needed for project control.

This chapter, we want to survey of the wide spectrum point of view of software use that may be efficient in every part the life cycle of software systems. Some SQA models propose to us that classified requirements into 11 to 15 factors (subject area) that can be combine into three or four division.

SQA activities: quality factor

There are several models of software quality factors and their classifications in factor division have been proposed over the years. McCall proposed the classic model of software quality factors that comprise of 11 factors (McCall et al., 1977). Following models, be composed of 12 to 15 factors, were proposed by Deutsch and Willis (1988) and by Evans and Marciniak (1987). The optional models do not differ considerably from McCall’s model. The McCall factor model, in spite of divide into 4 equal parts of a century of its "maturation", keep doing something to supply an applicable, up-to-date method for arrange systematically software requirements (Pressman, 2000)

McCall’s factor model

McCall classify all software requirements into 11 software quality factors, which The 11 cause are assembled into three divisions – product operation, product revision and product transition – as follows:

â–  Product operation factors: Usability, Integrity, Reliability, Efficiency, Correctness

â–  Product revision factors: Testability, Maintainability, Flexibility.

â–  Product transition factors: Interoperability, Reusability, Portability.

Product operation software quality factors:

In accord with McCall’s model, there are five software quality factors that comprise in the product operation division, all of they handle with requirements that frankly influence the day by day operation of the software. These factors are as follows.

Correctness

We with use factor of correctness, we can define a list of the system required output. Outputs Characteristic is usually having many dimensions; some common dimensions include:

â– .The demanded preciseness of those outputs that can be unfavorably influenced by inaccurate calculation or inaccurate data.

â– .The wholeness of the output information that can be unfavorably, influenced by imperfect data.

â– . The up-to-date oldness of the information that defines such as the time between the event and it is compensation by the software system.

â– . The accessibility of the information (delineated like the time essential to acquire the requested information, reaction time).

â– .The standards for coding and documenting the software system.

Example: in our product (GPS ship) user or customer should can see location, which include air, sea and height

Reliability

Reliability requirements can take care of inability to succeed to supply service. They decide the maximum permitted software system downfall rate, and can direct attention to the whole system or to one or more of its segregate duty

Example: our product (GPS ship) should be has warranty that only once face with problem during one.

Efficiency

Efficiency requirements can take care of the hardware ability essential to carry out all the duty of the software system in adaptation to all other something that is needed. The principal duty in a hardware system be measured are the computer’s processing ability (deliberate in MIPS – million guidelines per second, MHz or megahertz – million cycles per second, etc.), its data storage capability in terms of memory and disk capacity (measured in MBs – megabytes, GBs – gigabytes, TBs – terabytes, etc.) and the data communication capability of the communication lines (usually measured in KBPS – kilobits per second, MBPS – megabits per second, and GBPS – gigabits per second). The requirements may include the maximum values at which the hardware resources will be applied in the developed software system or the firmware. Another type of efficiency requirement deals with the time between recharging of the system’s portable units, such as, information systems units located in portable computers, or meteorological units placed outdoors.

Example: in our product (GPS ship) for has the best efficiency, we should characterize that our system what it does need to carry out such as RAM, CPU and monitor.

RAM=1GB

CPU=2Gb Hz

Hard=SATA 100GB

Usability

Usability requirements deal with the scope of staff resources needed to train a new employee and to operate the software system

Product revision software quality factor:

In accord with McCall model of software quality factors, there are three quality factors be composed of the product revision division. These factors take care of something that is needed that influence the whole determine the range of a target of software upkeep activities: remedial upkeep (making right of software defect and inability to succeed), capable of adapting upkeep (conforming the prevalent software to supplemental modifying condition and client without changing the software). These are as follows.

Maintainability

Maintainability necessity decide the attempt that will be essential by users and upkeep personnel to recognize the support a claim with reasons for software inability to succeed, to accurate the downfall, and to validate the success of making right. This factor’s necessity direct attention to relating to a module building of software, the interior program documentation, among other items.

Example: in our product (GPS ship), if product has Defect the software should be reinstalled in 60 sec

Testability

Testability prerequisite take care of the testing of an information system. Testability necessities for the comfort of testing are connected to special quality in the programs, which help the examiner, for example by supplying determined ahead of time intervene outcome and write a log files. Testability essential related to software operation, which contain automatic science of identifying problem through signs and symptoms carry out by the software system before to starting the system, to discover whether all ingredient of the software system are in working arrangement and to acquire a report about the discern defect. Other type of these stipulation take care of automatic relating to or used in diagnosis verify practical by the upkeep technicians to discover the factor of software inability to succeed.

Example: when we test product system can report all detail.

Product transition software quality factors:

In accord with McCall, there are three quality factors be composed of in the product transition division, a class that be connected to the adjustment of software to other surroundings and its reciprocal action with other software systems.

Portability

Portability necessity protects of the process of making of a software system to other surroundings comprise of not the same hardware, not the same operating systems, and so on. These essential accomplished it might be to keep doing applying the same fundamental software in various condition or to utilize it concurrently in various operating systems and hardware condition.

Example: our product must be enable install on different ship.

Reusability

Reusability necessity take care of utilize of software component in an original manner make plans for one scheme in a new software project most recently existence advanced.in addition, They can make possible that will happen projects to derive benefit from a granted component or a group of component of the most lately developed software. The use again of software is anticipated to save development supply, make shorter the development length of time, and make arrangements loftier quality modules. These be useful of loftier quality are establish under the supposition that majority of the software defect have previously been discovered by checking the quality of the product before it carried out on the original software, by one who uses the original software, and throughout its earlier use again. The problems within a company of software reutilize be suitable a subordinate of software manufacturing standards.

Example: we must constitute a team when write module of (GPS ship) team can recognize reusable module to use them in future project.

SQA activities: reviews

A usual product (GPS ship) of the process software development, particularly in its make plans for stage and analysis, is a model document in that the headway of the development work carried out is inscribe onto storage.one person that profession is in the establishment of computerized technological systems and maintenance of document will check it repetitively it is to be supposed, in arrangement to discover any might be error that strength have recorded. Development group heads are also anticipated to inspect this document and its item in order to discover any abiding errors previous fulfilling their confirmation. "A procedure or rendezvousing while something that is produced, or fixed of result of manufacturing, is displayed to project staff, director, client, user, or other interested parties for write an explanatory note or confirmation. similar to these documents are result of manufacturing of the project’s first stage, reviews obtain specific significance in the SQA procedure because they supply discovery of something before the expected and impede the going by of model and examination errors "down- stream", to perform where error finding out and amendment are vastly greater complicated, burdensome, and so expensive. Various methodologies may be executed when reviewing documents. In this particular section, we want to explain to methods reviews:

â–  Formal design reviews

â–  Peer reviews (inspections and walkthroughs)

â–  Expert opinions

It must be take note of having achieved success execution of review and walkthroughs. In addition, discover imperfection in the coding stage, where the suitable for document reviewed is the code printed output. A detailed study or analysis of a particular of the donation of formal model reviews and official examination to software quality is exhibited by McFarland (2001). After finishing this stage, we will be able to:

â–  .we can explain the straight and devious purpose of survey methodologies.

â– .we can explain the act of donating of exterior specialist to the execution of survey obligation.

â–  .we can consider to be similar the three serious survey methodologies

Reviews objectives

Some objectives provide inspiration reviews. The review’s straight purposes take care of the prevalent project, since its devious purposes, further inclusive in universe, handle with the act of donating of the review suitable to the advancement of group members’ specialist understanding and act of improving of the gradual growth methodologies practical by the arrangement.

The principal review objectives are:

C:\Users\Shervin\Desktop\review.PNG

Figure ,\

The several review methods be different in the importance that is attached to the distinctive purposes and in the measure of prosperity able to be achieved for each purpose. And so, for enhance "filtering out" of mistake and of more importance long-term influence, a twofold or even threefold "net", build from within the area of survey methods ready for use, must be practical. Reviews are not state of being active to be directed randomly. Routine request and working in a group extend at the heart of ceremonious model survey, review and inspections. Each member is anticipated to show the importance of duty or specific action when write an explanatory note. At each survey meeting, one characteristic is allocated the mission of write on a surface reciprocally accepted observe. The succeeding make a list of object should comprise entirely list of deficiency situation and depiction, the development group can will later retrieval documented in a way. However, These symbolize a encourage donation of reviews to increase in product quality.

Formal design reviews

Formal design reviews, in various ways called "design reviews", "DRs" and "formal technical reviews (FTR)", be different from all other survey implement by entity the only survey that are essential for confirmation of the design product. With none this confirmation, the development group cannot keep doing to the next stage of the software development project. Formal designs reviews may be directed at any development landmark necessitate finalization of an examination or model document, whether that document is a necessity act of specifying or an putting in plan. A list of common formal design reviews are:

Some common formal design reviews

DPR – Development Plan Review

SRSR – Software Requirement Specification Review

PDR – Preliminary Design Review

DDR – Detailed Design Review

DBDR – Data Base Design Review

TPR – Test Plan Review

STPR – Software Test Procedure Review

VDR – Version Description Review

OMR – Operator Manual Review

SMR – Support Manual Review

TRR – Test Readiness Review

PRR – Product Release Review

IPR – Installation Plan Review

The participants in a design reviews

All design review is directed by a review group and a review leader. The select of suitable participator is of exceptional significance due to their power to ability or disagree a design product.

The review leader

Have different opinions the interview of a suitable survey leader is a great factor influencing the design review prosperity, certain distinguishing quality are to be searched for in a applicant for this viewpoint:

â– . We should understand and knowledge obtained in evolvement of assignment of the model reviewed.

â– .we should have an excellent connection between project leader and project team.

â– . We should have a viewpoint exterior to the project group.

The review team

Including every part of review group should be chosen from within the older individual belonging to an organization of the project group together with suitable senior specialist allocated to other district and projects, client–user delegate, and in some situation, software development counselor. It is worthwhile for non-plan personnel to construct the greater part of the review group. A significant, of forsaken distribute is the extent of the review group. A review group should have three or five staff is anticipated to be an effective group. An immoderately enormous group be inclined to make accord problems, squander review meeting time and reduce the rank of preparation,

Preparation for a design review

despite the fact that getting ready for a design review meeting are to be perfected by all three principal participator in the review – the review head, the review group and the development group – each participator is necessitate to concentrated upon clear point of view of the process.

Review leader preparations

The main tasks of the review leader in the preparation stage are:

â–  To appoint the team members

â–  To schedule the review sessions

â–  To distribute the design document among the team members (hard copy, electronic file, etc.)

Team members are expected to review the design document and list their comments prior to the review session.

SQA activities: testing

The principal problems within to be elevated with regards to testing execution are test productivity and efficiency. This means that, continuous attempt are to be guided to decreasing of the proportion of not detected mistake continue in the system or software tested from a certain point of view, and to presentation of those tests with less capability on the other. in spite of the large capability expended for imperfection recognition in future, it is usually approved that freely software of imperfection is as yet an impracticable obligation. This condition has motivated testing specialist to emphasize the problem of efficiency and impressiveness at every occasion. The two principal tracks understood for improvement include raise the quality of the impressiveness of the test pack practical during testing, and evolution of operate software testing. The procedure of sketching, planning and performing tests at the several levels – piece tests, system test and merging test – are discussed in down:

â– . We should explain to the procedure of programming and sketching tests.

â– .we should explain to the origin for test situation, with their utilities and problematic condition.

â– .we should List the principal types of mechanized software tests.

â– .we should explain to the utilities and problematic condition of mechanized computerized testing as contrasted to physical testing.

The testing process

Programming, design and execution of testing are performed in every part of the software evolution procedure. These pursuits are separated into sections; start in the design step and ending whereas the software is set up at customer’s site. The testing process is illustrated in Figure.

Deciding the test methodology stage:

The principal subject that testing methodology has to argue with are:

The suitable necessitated software quality criterion

The software testing strategic planning

Determination about these two subjects is basic and should be prepared before programming begins.

Figure testing process

Planning the tests:

The tests to be schemed comprise:

â–  Unit tests

â–  Integration tests

â–  System tests.

While piece tests take care of into little pieces of software or component, merging tests handle with various piece that join into a subsidiary system. System tests direct attention to the whole software package/system. It is responsible to programmer to think over problems before launching a special test plan:

What to test?

Which sources to use for test cases?

Who is to execute the tests?

Where to execute the tests?

When to conclude the tests?

Test design

The products of the test design stage are:

â–  Detailed design and procedures for each test

â–  Test case database/file.

The software test plan (STP) – template

1 Scope of the tests

2 Testing environment

3 Test details (for each test)

4 Test schedule (for each test or test group) including time estimates for the following

preparation

testing

error correction

regression test

Test implementation

Prevalently, the testing execution stage activities are composed of a sequence of tests, making right of discovered mistake and retrogression tests. Testing is concluded while the retrogression tests consequence gratify the developers. The execution stage procedure is demonstrated in Figure 10.2. The tests are performed by Carry out the test matter in accord with the test process. Collecting of documents of the test process and the test matter database/file include the "software test descriptive" (STD). Retrogression tests is directed to confirm that the mistake discovered in earlier test Carry Out have been fittingly amendment, and that no new mistake have inscribe as a consequence of defective amendment

Test case design

A test case is a recorded as evidence fixed of operating situation necessitated and the data inputs to carry out a test object simultaneously with the anticipated results of the carry out. The tester is anticipated to carry out the project for the test object in accord with the test case collection of documents, and then consider to be similar the real consequence with the anticipated consequence important in the documents. If the acquire consequence totally concur with the anticipated consequence, no mistake is display or at least has been recognized. While quantity or all of the consequence do not concur with the anticipated consequence, a possible mistake is recognized. The equality of value class segment method,

SQA activities: configuration management

A unit of software code, a document or piece of hardware is defined as an SCI if it is assumed that it may be needed for further development of the software system and/or its maintenance. In other words, the main criterion governing a non-code item’s classification as an SCI and its inclusion in a software configuration version is its potential contribution to the software development and maintenance process. A software configuration is composed of as many SCIs as the developers assume will be needed in the future, with each SCI approved, identified and registered. The SCIs aggregated in each software configuration version naturally correspond to the software components and software definitions reviewed in Section 2.1. The SCIs are generally placed into four classes, as follows:

â–  Design documents

â–  Software code

â–  Data files, including files of test cases and test scripts

â–  Software development tools

A list of common types of SCIs is presented in down

Common types of software configuration items

Design documents

â–  Software development plan (SDP)

â–  System requirements document

â–  Software requirements document (SRD)

â–  Interface design specifications

â–  Preliminary design document (PDD)

â–  Critical design document (CDD)

â–  Database description

â–  Software test plan (STP)

â–  Software test procedure (STPR)

â–  Software test report (STR)

â–  Software user manuals

â–  Software maintenance manuals

â–  Software installation plan (SIP)

â–  Software maintenance requests (including problem reports)

â–  Software change requests (SCRs) and software change orders (SCOs)

â–  Version description document (VDD)

Software code

â–  Source code

â–  Object code

â–  Prototype software

Data files

â–  Test cases and test scripts

â–  Parameters, codes, etc.

Software development tools

(The versions applied in the development and maintenance stages)

â–  Compilers and debuggers

â–  Application generators

â–  CASE tools

Documentation control

Software development and maintenance processes involve production and use of a multitude of documents; some are vital immediately while others may become vital for software quality assurance over the life cycle of the sys- tem. Special procedures for documentation control (usually called documentation procedures, documentation control procedures or control of documents procedures) are therefore introduced to indicate which documents are indeed expected to be vital at some point and to assure their appropriate preparation and availability. Documents that display these characteristics and that are treated according to these procedures are called controlled documents. One type of controlled document – quality records – is aimed mainly to provide evidence that the development and maintenance processes were performed in conformity to requirements and that the soft- ware quality system is operating fully and effectively. The issues of documentation control together with the characteristics of controlled documents and quality records are the subject of this section Documentation control, controlled documents and quality records are important components of the SQA system.

Controlled documents and quality records

In this section, we present a detailed definition of controlled documents and quality records, the objectives of their management, the authority established for this purpose and the compliance required.

Controlled document

A document that is currently vital or may become vital for the development and maintenance of software systems as well as for the management of current and future relationships with the customer. Hence, its preparation, storage, retrieval and disposal are controlled by documentation procedures. The main objectives for managing controlled documents are:

â–  To assure the quality of the document.

â–  To assure its technical completeness and compliance with document structure procedures and instructions (use of templates, proper signing, etc.).

■ To assure the future availability of documents that may be required for software system maintenance, further development, or responses to the customer’s (tentative) future complaints.

â–  To support investigation of software failure causes and to assign responsibility as part of corrective and other actions.

Quality record

A quality record is a special type of controlled document. It is a customer- targeted document that may be required to demonstrate full compliance with customer requirements and effective operation of the software quality assurance system throughout the development and maintenance processes.

Frame 19.2 presents an overview of the types of documents that may be categorized as controlled documents. An examination of the document list reveals that a good number of the controlled documents may be classified as quality records. The magnitude of the list and its composition vary between organizations and depend on the characteristics of the customers in addition to those of the software packages. Contracts for large-scale "custom-made" software projects usually require quite different lists of controlled documents than do COTS software packages.

The document types listed in table up are produced during the implementation of a variety of SQA processes, to mention but a few:

â–  Contract and negotiation process

â–  Development process

â–  Software change process

â–  Maintenance services

â–  Software quality metrics

â–  internal quality audits

The controlled documents list

The key to management of controlled documents (including quality records) is the controlled document types list. Proper construction of the list is based on the establishment of an authority to implement the concept, whether embodied in a person or a committee. Specifically, this authority is responsible for:

â–  Deciding which document type is to be categorized as a controlled document and which controlled document types are to be classified as quality records.

â–  Deciding whether the level of control is adequate for each document type categorized as a controlled document.

â–  Following up of compliance with the controlled document types list. This subject can be incorporated in the internal quality audits plan .

â–  Analyzing follow-up findings and initiating the required updates, changes, removals and additions to the controlled documents types list.

Most controlled document types are documents created internally by the organization itself. Nonetheless, a substantial number of external document types, such as contract documents and minutes of joint committee meetings, also fall into this category.

Controlled document preparation

The documentation requirements involved in the creation of a new docu- ment or the revision of an existing document focus on completeness, improved readability and availability. These requirements are realized in the documents:

â–  Structure

â–  Identification method

â–  Standard orientation and reference information.

The document’s structure may be free or defined by a template. An identification method is devised to provide each document, version and revision with a unique identity. The method usually entails notation of (a) the software system or product name or number, (b) the document (type) code and (c) the version and revision number. The method can vary for different types of documents. The document’s orientation and reference information may be required as well. Orientation and reference information support future access of required documents by supplying information about the content of the document and its suitability to the needs of the future user. Depending on the document type, a greater or smaller proportion of the following information items is commonly required:

■ The document’s author(s)

â–  Date of completion

â–  Person(s) who approved the document, including position(s) held

â–  Date of approval

â–  Signature(s) of the author(s) and person(s) who approved it

â–  Descriptions of the changes introduced in the new release

â–  List of former versions and revisions

â–  Circulation list

â–  Confidentiality restrictions.

Staff training and certification

It goes without saying that keeping staff abreast of the latest professional knowledge available is the key to achieving quality in development and maintenance. Moreover, it is generally accepted that regular professional training, retraining and updating are mandatory if the gap between required and current professional knowledge is to be kept as narrow as possible. Internal certification (hereinafter just "certification") of staff members assigned to key software development and maintenance positions is another, complementary tool for assuring professional quality. Internal certification of staff should not, however, be confused with the certification awarded by the American Society for Quality (ASQ), which confers CSQE status (see below) in addition to other types of certification, or the professional certifi- cation granted by commercial organizations such as Microsoft or Novell. The importance of professional training as a vital component of any SQA system is stressed in ISO 9000-3 as well as the CMM Guidelines (see ISO, 1997; ISO/IEC, 2001; Paulk et al., 1995). Job descriptions and training program development for SQA personnel are discussed by Mendis (1999)

Also of interest is the program for certified software quality engineers (CSQE) delivered by the American Society for Quality (ASQ), described by Hamilton (1999) and an ASQ brochure (ASQ, 1999). The training and certification process and the activities that comprise it are dealt with in the different sections of this chapter. After completing this chapter, you will be able to:

â–  Explain the main objectives of training and certification. â–  Discuss what is needed to prepare a training and updating program. â–  List the main components of a certification program. â–  Explain the objectives of follow-up of trained and certified staff per- formance and the main sources of the follow-up data.

Elements of the development plan:

Based on the proposal materials, the project’s development plan is prepared to fulfill the above objectives. The following elements, each applicable to different project components, comprise a project development plan.

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)

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).

3. Project methodology and development tools to be applied at each phase of the project.