Software Quality Management 2 mark Unit II,

Unit II

1. What is software quality?

            Software quality measures how well software is designed (quality of design), and how well the software conforms to that design ( quality of conformance), although there are several different definitions.

2. Define software quality assurance?

            Software Quality Assurance (SQA) is defined as a planned and systematic approach to the evaluation of the quality and adherence to software product standards of processes and procedures.

3.  What are the processes of SQA in software development process?

            Software design

            Source code coding

            Source code control

Code reviews

Change management

Configuration management

Release management.

4. What is known as documentation standards?

            Documentation Standards specify form and content for planning, control and product documentation and provide consistency throughout a project.

5. What are design standards?

            Design standards specify the form and content of the design product. They provide rules and methods for translating the software requirements into the software design and for representing it in the design documentation.

6. What are code standards?

            Code standards specify the language in which the code is to be written and define any restrictions on use of language features. They define legal language structures,style conventions, rules for data structures and interfaces and internal code documentation.

7. How are verification and validation done in SQA?

            SQA assures Verification and Validation (V & V) activities by monitoring technical reviews, inspections and walkthroughs.

8. What are the testing process documentation?

Ø  Test plans

Ø  Test specifications

Ø  Test procedures

Ø  Test reports.

9. What are the different types of documentation?

Ø  Software requirements

Ø  User documentation

Ø  Analysis documentation

Ø  Architectural and implementation documentation

Ø  Marketing documentation

Ø  Technical documentation

Ø  Design and Implementation documentation

Ø  Design documentation

Ø  Operation and Maintenance Documentation

Ø  Test Documentation

Ø  Installation and Checkout Documentation

Ø  Source code documentation

Ø  Project management documentation

10. What is a SQA Status Reports Report?

            SQA status is reported monthly. The content of this report will identify:

            1) Items produced by the SQA functions

            2) Significant software development compliance problems, if any, along with

                their agreed to and recommended corrective actions.

            3) Audits, reviews and tests accomplished during the reporting period.

11. What is a software review?

            A software review is “ A process or meeting during which a software product is  [examined by] project personnel, managers, users, customers, user representatives or other interested parties for comment or approval.

12. What are the types of software reviews?

            Software reviews may be divided into three categories:

            Software peer reviews

            Software management reviews

            Software audit reviews

13. What is a software peer review?

            They are conducted by the author of the work product, or by one or more colleagues of the author, to evaluate the technical content and quality of the work.

14. What is a pair programming review?

            Pair programming is a type of code review where two persons develop code together at the same workstation. While reviewing, the observer also considers the strategic directions of the work, coming up with ideas for improvements and likely future problems to address.

15.  What is known as Inspection review?

            Inspection is a very formal type of peer review where the reviewers are following  a well-defined process to find defects.

16. What are the processes in Inspection review?

Ø  Planning

Ø  Overview meeting

Ø  Preparation

Ø  Inspection meeting

Ø  Rework

Ø  Follow-up

17. What are the roles in Inspection review?

            Moderator

            Reader

            Writer

18. What are walkthrough reviews?

Walkthrough is a form of peer review where the author leads members of the development team and other interested parties through a software product and the participants ask questions and make comments about defects.

19. Who is a Author?

            The author, who presents the software product in step-by step manner at the walk-  through meeting and is probably responsible for completing most action items.

20. What are the roles in walkthroughs?

            Author

            Walkthrough Leader

            Recorder

Software Quality Management 2 mark Unit I,

Unit I

1.      Name some of the insights of quality?

Ø  Quality is not absolute.

Ø  Quality is multidimensional.

Ø  Quality is subject to constrain.

Ø  Quality is about acceptable compromises.

Ø  Quality criteria are not independent, but interact with each other causing conflicts.

2.      Quality is not absolute? Prove it?

   Quality is not absolute. It means different things in different situations with respect to solution. Quality cannot be measured upon a quantifiable scale as physical objects.

3.  Give the formal definition of quality given by the ISO?

            The formal definition of quality is defined by the International Standards  

      Organization (ISO)

            The totality of features and characteristics of products or service that bear on the  

       ability to satisfy specified or implied needs.

4.      What is software quality?

Software Quality is ‘fitness to needs’ when referred by Kitchenham and claims

       that quality involves matching expectations.

5. What are the different views of Quality?

Ø  Transcendent views.

Ø  Product based view.

Ø  Manufacturing View.

Ø  Value based view.

6. Give the role of a Project manager?

            A project manager has responsibility for the project on the supply side. He is keen   to produce a product that is reliable and maintainable and will keep the customer satisfied.

7. What are the roles of a Business analyst?

            Business analyst is the clients found in the developer’s camp. He will tend to defend the pressures exerted by the external constraints.

8. What does an Implementation programmer do?

            This is the person who writes the software and is highly defensive of the product  

    of the labors and may be hard to convince that their codes do not meet technical or user requirements.

9. Give the role of a quality auditor in the aspect of quality?

            He detects the departures from a quality  solution, whether it its technical defects  or a poor match to requirements.

10. Who is an end user? What is his role in software quality?

He is a junior person who often has very little input onto the development  process, but has to use the system till the end.

11. Who is a Project sponsor?

            The sponsor is the one who pays the bill. They will often be remote from the day-to-day implementation issue and want a successful outcome to boost their prestige and justify the expenditure.

12. What is called to be transcendent view?

            This view relates quality to excellence. An attempt to build software in a high excellence is likely to be constrained by resources.

13. Give brief answers: Product based view?

            The main basis of this view is that it costs money to build quality software that is the  higher the quality, higher the cost.

14. What does manufacturing view means?

            The manufacturing view measure quality in terms of conformance to requirements. This view of quality is the most common amongst software engineers

      and lies at the sequential development methodologies of the traditional waterfall type.It is aided through the use of methodologies, computer aided software engineering

      case tools and total quality management. With manufacturing zero defect approach to quality is growing.

15. Why is quality determined by the people?

Ø  It is the people and human organizations who have problems to be tackled by computer software.

Ø  It is the people who define the problems and specify the solutions.

Ø  It is the people who implement the design and produce code.

Ø  It is the people who test the code.

Ø  It is the people who make the final judgments about the overall quality of the solution.

16. What is a hierarchical model?

            A hierarchical model of software quality is based upon a set of quality criteria,

       each of which has a set of measures or metrics associated with it.

     

18. What are the different hierarchical models that were proposed?

Ø  GE Model( by Mc Call, 1977 and 1980)

Ø  Boehm Model ( 1978)

19. What are the metrics associated with reliability?

Ø  Accuracy

Ø  Consistency

Ø  Error tolerance

Ø  Simplicity

Ø   

20. What were the areas addressed by McCall?

            1. Product operation

            2. Product revision

            3. Product transition

22. Give the common characteristics shared by the two models?

Ø  Based on user view

Ø  The models focus on the parts that designers can more readily analyze.

Ø  Can be tested or validated.

Ø  The overall Quality is achieved by a weighted summarization.

23. How are quality measured?

            Quality measurements are usually expressed in terms of metrics.

24. What is software metric?

            Software metric is used to predict the about the software later in the life cycle.

25. What are the three conditions that a software quality must meet?

Ø  It must be clearly linked to the quality criterion that it seeks to measure.

Ø  Be sensitive to the different degrees of the criterion

Ø  Provide objective determination of the criterion that can be mapped onto a

            suitable scale.

26. How do you define structured ness?

            Structured ness may be simply calculated in the terms of the average lines of code    modules within the program. Structured ness α modularity α lines of code / Number of modules.

27. What are the types of metrics?

            Metrics are classified into two types according to whether they are

1.      Predictive

2.      Descriptive

28. What are the questions by which the structured ness is measured?

Ø  Have the rules for the transfer of control between modules been followed?

Ø  Are modules limited in size(Y/N)?

Ø  Do all modules have only one exit point?

Ø  Do all modules have only one entry point?

29. Give the equations to calculate the McCall Structured ness?

            McCall’s approach is more quantitative, using scores derived from equation such

       as,

            McCall structured ness metric = n ₀₁ / n _tot

         Where n ₀₁ = number of modules containing one or zero exit points only

                   n _tot     = total number of modules

            In this approach the scores range between 0 and 1, to allow for easier combination

      and comparison.

30. Give the seven criteria of a good metric?

            Objectivity: The results should be free subjective influences. It should not matter

                                who the measurer is.

            Reliability: The results should be precise and repeatable.

            Validity: The metric must measure the correct characteristic.

            Standardization: The metric must be unambiguous and allow for comparison.

            Comparability: The metric must be comparable with other measures of the same

                                      criterion.

            Economy: The simpler and therefore the cheaper the measure is to use the better.

            Usefulness: The measure must address the need, not simply measure a property

                                for its own sake. Another important measure is consistency.

31. What are the metrics cited according to the fundamental properties?

Ø  Readability as the measure of usability

Ø  Error prediction as the measure of correctness

Ø  Error deduction as the measure of correctness

Ø  Mean Time To Failure( MTTF) as the measure of reliability

Ø  Complexity as the measure of reliability

Ø  Complexity as the measure of maintainability

Ø  Readability of code as a measure of maintainability

Ø  Modularity as a measure of maintainability

Ø  Testability as the measure of maintainability

32. Why the metrics are available from literature are less effective?

            They cannot be validated

            They are not generally objective

            Quality is relative, not an absolute, quantity

            They depend upon the small set of measurable units.

            They do not measure the complete set of quality criteria

            Metrics measure more than one criterion.

33. What are the problems in Gilbs approach?

Gilb himself highlights five problem areas with implementation of the method ,

The simple fact that the method is different.

The need for training and re-training and associated costs.

The need for effective management.

The need to measure progress towards the ultimate goal.

Picking up errors may be very frustrating to the progress.

 34.              Give Gilbs quality attributes?

Gilb proposed four quality attributes,

Ø  Workability

Ø  Adaptability

Ø  Usability

Ø  Availability  

35. Gilb suggested range of measures to quality the resource attributes? What are 

       they?

            Gilb proposed some measures to quantify the attributes. They are not transactional metrics.

Ø  Transaction per second

Ø  Records per Minute

Ø  Bytes per line

Ø  Bits per node per second

36. What are the resources attributes given by Glib?

Ø  Time

Ø  Money

Ø  People

Ø  Tools

37. What is a GQM model?

            A goal-driven method for developing and maintaining a meaningful metrics

        program that is based on three levels, Goals, Questions and Metrics. The Goal- 

        Question-Metric( GQM) approach is a paradigm for developing and maintaining  

        a meaningful metrics program.