Software Quality Assurance ( Sqa )

A Computer Software Engineer develops software systems to be used by their clients, such as a website used to sell the client’s products. Although software engineers spend the majority of their time programming and testing the software, a key component to the success of a software engineer is the ability to write a thorough Software Requirement Specification (SRS). A SRS documents the requirements and dependencies needed for the software, prior to beginning any programming. Therefore, a Software Engineer must po The SRS is so important because engineers can have a wide scope of clients that they regularly work with.

According to the International Organisation for Standardisation “Quality assurance is a set of activities intended to establish confidence that quality requirements will be met” (Praxiom, 2011)

Quality is therefore not just concerned with what the software does. Rather, it has to include the software’s behavior while it is executing and the structure and organization of the system programs and associated documentation. This is reflected in so-called quality or non-functional software attributes. Examples of these attributes are the software’s response time to a user query and the understandability of the program code.

Project Quality Management| -Cost Benefit Analysis -Cost of Quality -Control Charts -Benchmarking -Design of Experiments -Statistical Sampling -Flowcharting -Proprietary quality manage- ment methodologies -Additional quality planning tools (Brainstorming, Affinity Diagrams, Nominal Group Technique)| -Cost benefit: Looking at how much your quality activities will cost. -Benchmarking: means using the results of quality planning on other projects to set goals for your own. -Design of experiments: is the list of all the kinds of tests you are going to run on your product. -Total Quality Management (TQM): Everyone in the company is responsible for quality and is able to make a difference -Continuous Improvement (Kaizen): constant process improvement in the form of small changes -Just-In-Time(JIT) -ISO 9000: Companies document what they do and they do what they document

Software quality assurance is a very important part of the software development and installation. “The main objective of quality assurance is to avoid problems or to detect them as soon as possible” (Shelly, Cashman & Rosenblatt, 2003, p. 410).

“Perform Quality Assurance (QA)- The process of auditing the quality requirements and the results from quality control measurements to ensure that appropriate quality standards and operational definitions are used” (Project Management Institute, 2013, p. 227). The task begins with development and continues to

Quality assurance program (QA): A plan of action, concern and responsibility to ensure an x-ray image taken in the office is of the highest quality possible.

Keywords—Software Engineering, software process models, Free-Flow Model, Requirement collection, Testing, Activities involved in process models, Comparative analysis of models.

Quality: - Quality means fitness of the product or services to use by the Customer. Quality means competitive cost, Productivity, timely delivery of the services or products and total customer Satisfaction in terms of the product and services and Total services paid by customer to the company.

The third phase of the system development process is the programming phase. During this stage system specifications that were prepared during the design stage are translated into software program code (Laudon, & Laudon, 2016). The business user plays a vital role in this stage because it is in this stage that the software will be either developed or purchased from an outside vendor (Hsu, Lin, Zheng Hung, 2011). Ensuring that the software aligns with the new requirements is vital to the long term success of the information system.

It is typical for developers to spend around 40% of the total project time on testing. For life critical software (e.g. flight control, reactor monitoring), testing can cost 3 to 5 times as much as all other activities combined [1]. The destructive nature of testing requires that the developer discard preconceived notions of the correctness of his/her developed software. This means that testing must be done from an entirely different perspective from that of a developer. Testing must be done by considering the end user in mind, that how

quality is one of the most important attributes in software and a key contributor to its success.

Nick J. Pizzi .2013 Applying approach using a fuzzy classification methodology. The software metrics are automatically calculated to be as (input) to a classifier while the class labels (output) are assigned through an expert’s via assessment of the quality of each software entities.

Though many people interchange system engineering models and software engineering life cycle models, they are defined as two different approaches to software development. System engineering is the technical and technical management process that results in delivered products and systems that exhibit the best balance of cost and performance. As the program progresses from one phase to the next one, so does the system engineering process. It deals with the overall management of engineering project during their life cycle. Its main focus is knowing what the clients and end users wants and needs are satisfied and developing just that all the way through the system’s entire life cycle. Whereas, on the other hand, software engineering focuses on the quality of the product or system, how cost effective it is, is it done within the time-constraints given, whether it is easy to maintain and enhance, and does it work as the requirements defined. Its main focus is on delivering a product that meets the requirement specifications. There are so many models to choose from, as it all depends on what the project needs and entails. Depending on the requirements, allows for the choice of what mode to use.

Software reliability is dynamic & stochastic. Unlike hardware, software does not age, wear out or rust, unreliability of software is mainly due to bugs or design faults in the software. The exact value of product reliability is never precisely known at any point in its lifetime. The study of software reliability can be categorized into three parts: Modeling, Measurement & improvement. Many Models exist, but no single model can capture a necessary amount of software characteristics. Software reliability improvement is necessary & hard to achieve. It can be improved by sufficient understanding of software reliability, characteristics of software & sound software design. Software Reliability is the most important and most measurable aspect