17
Systems Analysis and Design

Systems Analysis and Design. Quality Assurance Quality Assurance Guidelines for Quality Software Guidelines for Quality Software Total Quality Management

Embed Size (px)

Citation preview

Page 1: Systems Analysis and Design.  Quality Assurance Quality Assurance  Guidelines for Quality Software Guidelines for Quality Software  Total Quality Management

Systems Analysis and Design

Page 2: Systems Analysis and Design.  Quality Assurance Quality Assurance  Guidelines for Quality Software Guidelines for Quality Software  Total Quality Management

Quality Assurance Guidelines for Quality Software Total Quality Management Levels or Activities of Quality Assurance Quality Assurance Goals in Systems Life

Cycle Auditing

Page 3: Systems Analysis and Design.  Quality Assurance Quality Assurance  Guidelines for Quality Software Guidelines for Quality Software  Total Quality Management

The main Objective of a software development project is to ensure that the software should be of high quality.In order to maintain the quality of software ,the Project leader must plan for quality activities that are needed to be performed during different phases of SDLC.

BACK

Page 4: Systems Analysis and Design.  Quality Assurance Quality Assurance  Guidelines for Quality Software Guidelines for Quality Software  Total Quality Management

Quality assurance approaches are

◦ Securing total quality assurance through designing systems and software with a top-down and modular approach

◦ Documenting software with appropriate tools◦ Testing, maintaining, and auditing software◦ The user of the information system is the single most

important factor in establishing and evaluating its quality.◦ It is far less costly to correct problems in their early

stages than it is wait until a problem is expressed through user complains or crises.

BACK

Page 5: Systems Analysis and Design.  Quality Assurance Quality Assurance  Guidelines for Quality Software Guidelines for Quality Software  Total Quality Management

Total quality management (TQM) is a conception of quality as an evolutionary process toward perfection instead of conceiving quality as controlling the number of defective products produced

The full organizational support of management and early commitment to quality from the analyst and from the business are necessary

BACK

Page 6: Systems Analysis and Design.  Quality Assurance Quality Assurance  Guidelines for Quality Software Guidelines for Quality Software  Total Quality Management

QUALITY ASSURANCE

CERTIFICATIONTESTINGVALIDATIONVERIFICATION

Page 7: Systems Analysis and Design.  Quality Assurance Quality Assurance  Guidelines for Quality Software Guidelines for Quality Software  Total Quality Management

Verification: Verification is concerned with matching of quality of software at given phase with the specifications.The Developing Software is inspected and reviewed by a agroup of people during different phases of SDLC.

Validation: Validation refers to the process of using the system in the actual live environment in order to find errors.If the results obtained from the system are proper,the System is valid else it is not.

Page 8: Systems Analysis and Design.  Quality Assurance Quality Assurance  Guidelines for Quality Software Guidelines for Quality Software  Total Quality Management

System Testing: In system testing ,the common view is to eliminate program errors.System Testing represents the ultimate review of Specification,Design and Coding.This reviwe may be based on the feedbacks obtained from the users.

Validation: Certification is the Confirmation of the Correctness of the Program.Hence Certification is for providing the authenticity of the system design that is Whether the System is According to what was aimed. BACK

Page 9: Systems Analysis and Design.  Quality Assurance Quality Assurance  Guidelines for Quality Software Guidelines for Quality Software  Total Quality Management

The Software Life Cycle includes various phases of development and each phase has the goal of Quality Assurance.

a) Quality Factor Specifications b)Software Requirement Specifications c) Software Design Specifications d) Software Testing and Implementation e) Maintenance and support

Page 10: Systems Analysis and Design.  Quality Assurance Quality Assurance  Guidelines for Quality Software Guidelines for Quality Software  Total Quality Management

The goal of this phase is to define the quality factors.Software Quality Factors are:

1. Correctness: Correctness is the extent to which a software satisfies its Specifications.

2. Reliability: It is the extent to which a software can be expected to perform its intended function with required precision.

3. Usability:It is the effort required to learn and operate the software properly.

Page 11: Systems Analysis and Design.  Quality Assurance Quality Assurance  Guidelines for Quality Software Guidelines for Quality Software  Total Quality Management

4. Integrity: It is the extent to which access of software or data by unauthorized persons can be controlled.

5. Efficiency:It means lass response time and memory requirement.6. Maintainability:It is the effort required to locate and fix an error

in a program.7. Flexibility:It is the effort required to modify an operational

program.8. Testability:It is the effort required to test to ensure that the

system or a program performs its intended function.9. Portability: It is the effort required to transfer the software from

one hardware /software system environment to another.10. Reusability: It is the extent to which part of software can be

reused in other Software.11. Interoperability:It is the effort required to couple the system with

other system12. Robustness:A Program is robust if it behaves reasonably even in

circumstances that were not anticipated in the requirement specification.

13. Data Abstraction:It is a process where we identify the important aspects of a phenomenon and ignore its details.

Page 12: Systems Analysis and Design.  Quality Assurance Quality Assurance  Guidelines for Quality Software Guidelines for Quality Software  Total Quality Management

The Quality Assurance goal of this phase is to generate the requirements document that provides the technical specifications for the design and development of the software

The SRS document should have the following main characteristics

1. Complete

2. Consistent

3. Understandable by the user

4. Modifiable as per the needs of the user

5. Unambiguous

This document enhances the system’s quality by formalizing communication between the system developer and the user and provides the proper information for accurate documentation.

Page 13: Systems Analysis and Design.  Quality Assurance Quality Assurance  Guidelines for Quality Software Guidelines for Quality Software  Total Quality Management

In this Phase,Software design document defines the overall architecture of the software that provides the functions and features described in the software requirements document.This Document describes the logical subsystems and their respective physical modules.

Page 14: Systems Analysis and Design.  Quality Assurance Quality Assurance  Guidelines for Quality Software Guidelines for Quality Software  Total Quality Management

The Quality assurance goal of the testing phase is to make the System Reliable and error free.

The Quality assurance goal of the Implementation phase is to provide a logical order for the creation of the modules as well as for the creation of the System.

Page 15: Systems Analysis and Design.  Quality Assurance Quality Assurance  Guidelines for Quality Software Guidelines for Quality Software  Total Quality Management

Maintenance is due to◦ Errors or flaws in the system◦ Enhancing the system◦ Feedback procedures must be in place to

communicate suggestions The Quality Assurance goal is to develop a

procedure for correcting errors and enhancing Software.

BACK

Page 16: Systems Analysis and Design.  Quality Assurance Quality Assurance  Guidelines for Quality Software Guidelines for Quality Software  Total Quality Management

There are internal and external auditors Internal auditors study the controls used in

the system to make sure that they are adequate

Internal auditors check security controls External auditors are used when the system

influences a company’s financial statements

BACK

Page 17: Systems Analysis and Design.  Quality Assurance Quality Assurance  Guidelines for Quality Software Guidelines for Quality Software  Total Quality Management