A Software Quality Assurance and Management System
Er.Ashish Kumar Tripathi, Er. Sachin Kumar Dhar Dwivedi, Mr. Saurabh Upadhyay

Abstract- Software quality objectives covers a variety of techniques and measurements, including gathering code metrics, enforcing coding rules, and proving the absence of run-time errors. The guide also takes into account the origin of the code, its stage in the software life cycle, and the safety aspects of the application. The guide explains how to gradually adapt the code verification process to achieve targeted quality objectives Index Terms- Application and System S/W, System efficiency, testing and good designing tools.

--------------------------------------------------------

1-Introduction
Quality assurance for automotive systems can require different types of verification activities throughout the development process.  Early verification focuses on evaluating intermediate software builds and removing defects at coding time. This represents an emerging trend because performing verification early in the process can improve overall quality and reduce development time.  Post-production verification focuses on evaluating final build quality or finding defect root causes after the product is complete. This is the most common approach to automotive system verification.

3-About Software ProductsSoftware products may be • Custom - developed for a particular customer, according to its specifications Generic (“package”) - developed for a general market, to be sold to a range of different customers

•

Types of software products • Business support software Includes software engineering tools in the software engineering business

•

Personal productivity software spreadsheets, word processing tools, …

2-Objective To introduce the notion of software quality and describe common software quality attributes and quality-factors. To introduce the verification and validation process. To introduce the software quality management process and key quality management activities. To explain the concept of a software metric, predictor metrics and control metrics. •

Embedded software

 

4-Devlopment ProcessThere are several applications to which are necessary to development of software like front end and back end, but when developer develop software, they use



some systematic rule and process for better quality of software. There are some generic activites.

• • •

Portability Reusability Learnability

•

Specification - what the system should do and its development constraints Development - production of the software system Validation - checking that the software is what the customer wants Evolution - changing the software in response to changing demands

7-S/W Quality Principle-

•

•

Development technology Process quality Product quality

•

People quality

5-Some Importance for SoftwareSoftware engineering expenditure (in the development and maintenance of software products) represents a significant fraction of GNP (Gross National Product) in all developed countries like some views as a Including an increasing number of safetycritical and mission-critical systems, with high demands on dependability Software and Information Systems are critical success factors in an increasing number of businesses and organizations

Cost, time and schedule

8-Software Quality Management SystemQuality management should be separate from project management to ensure independence of budget and schedule pressures, ensure that the required level of quality is achieved in software products, namely, that defined standards and procedures are followed. 1-Organization–wide as Quality assurance-



6-Software Quality Attributes- Some attributes are-• • • • • • • Resilience Robustness Understandability Testability Adaptability Modularity Simplicity

Establish organisational procedures and standards for quality in a quality manual 2-Project–wide as a Quality planning Select applicable procedures and standards for a particular project and modify these as required. Produce a quality plan. 3-Project–wide as a Quality controlEnsure that procedures and standards are followed by the software development team. Produce quality review reports

S/W Quality Management and Development ProcessSoftware development process D1 D2 D3 D4 D5

Quality management process

Standards and procedures

Quality plan

Quality review reports
• Usually the responsibility of the component developer (except sometimes for critical systems) Tests are derived from the developer‟s experience

9-Software Testing•  Black-box testing • An approach to testing where the program is considered as a „black-box‟ The program test cases are based on the system specification Test planning can begin early in the software process 

Integration testing • Testing of groups of components integrated to create a system or sub-system The responsibility of an independent testing team Tests are based on a system specification (black-box)

•

•

•

•



White-box testing • Sometime called structural testing Derivation of test cases according to program structure. Knowledge of the program is used to identify additional test cases Objective is to exercise all program statements (not all path combinations)

•

10-Software Product MeasurementSoftware measurement is concerned with deriving a numeric value for an attribute of software product or process. This allows for objective comparisons between techniques and processes. Although some companies have introduced measurement programmed, most organizations still do not make systematic use of software measurement.

•

Test coverage measures ensure that all statements have been executed at least once.  Component testing • Testing of individual program components

Choose measurements to be made Select components to be assessed Measure component characteristics Identify anomalous measurements

Analyse anomalous components

Measurement Process

11-Development Cost and Formal SpecificationCost Validation Design and Implementation

Validation Design and Implementation Specification

Specification

Without formal specification

With formal specification

12-Conclusions Software measurement gathers information about both the software process and the software product  Product quality metrics should be used to identify potentially problematical components



There are no standardised and universally Applicable software metrics

Author1-

ReferencesHarsh, Stephen B., L. J. Connor, and G. D. Schwab. (1981). Managing the Farm Business. Prentice-Hall, Inc., Englewood Cliffs, New Jersey. Knowledge Management, Information Systems, E-Learning, and Sustainability Research: Third World Summit on the Knowledge Society, WSKS 2010, Corfu, in Computer and Information Science) by D. Lytras, Patricia Ordonez De Pablos, Adrian Ziderman and Alan Roulstone (Dec 1, 2010) Study guide for Management Information Systems: Solving Business Problems with Information Technology by Post, ISBN 9780073135731 (Cram101 Textbook Outlines) by Cram101 Textbook Reviews (Oct 25, 2006) Information Systems Project Management: How to Deliver Function and Value in Information Technology Projects by Jolyon Hallows (Feb 21, 2005) Public Management Information Systems by Bruce A. Richelieu (Dec 13, 2005) Imboden, N. (1980). Managing information for rural development projects. Paris: Organization for Economic Co-operation and Development. Sachdeva, R. K. (1990). Management handbook of computer usage. Oxford: NCC Blackwell. Sanders, D. H. (1988). Computers today (3rd ed.). New York: McGraw-Hill.

Er. Ashish Kumar Tripathi (M.Tech in IT), Assistant Professor, Dept of CS, Centre for Management Technology Gr.Noida, India Email- ashish.msa@gmail.com 2-

Er. Sachin Kumar Dhar Dwivedi (M.Tech in IT), Assistant Engineer, NIELIT Aizawl, Ministry of CO & IT Govt of India. E-mail:- Sachin.nielit@gmail.com 3-

Mr.Saurabh Upadhyay Lecturer in Dept. of CS, S.M.S Varanasi affiliated to U.P.Technical University Lucknow, India E-mail:- Saurabh.bac@gmail.com