SOFTWARE QUALITY MANAGEMENT. Unit I Part A

SOFTWARE QUALITY MANAGEMENT Unit I Part A 1) Define software quality? (Dec 2011) (or) What is software quality (Dec 2012) definition OED,1990 source Degree of excellence Crosby,1979 Zero defects The totality of features and characteristics of a product or ISO,1986 service that bear on its ability to satisfy specified or implied needs. Fruhauf Quality is when the customer comes back, not the product. 2) What is view of quality? The framework for the specification of software quality processing requirements called view of quality. The different quality views are the transcendent view, the product based view, the value based view, the manufacturing view and the user based view. 3) List the three areas addressed by McCall s model? (Dec 2012) McCall identified three main perspectives for characterizing the quality attributes of a software product. These perspectives are 1. Product revision (ability to change). 2. Product transition (adaptability to new environments). 3. Product operations (basic operational characteristics). 4) Define McCall s quality criteria Usability, Integrity, Efficiency, Correctness, reliability, Maintainability, Flexibility, Testability, Portability, Reusability, Interoperability 5) How the quality criteria interrelated? The individual measures of software quality such as Integrity, efficiency, usability etc provided do not provide an overall measure of software quality. The individual measures must be combined. The individual measures of software quality may conflict with each other. Some of the relationships are described as Inverse, Neutral, and Direct. Integrity Vs efficiency (Inverse), Maintainability Vs Flexibility (Direct), Correctness Vs Efficiency (Neutral) 6) Give the conditions that quality metrics should meet? Be clearly linked to the quality criterion. Be sensitive to the different degrees of the criterion. Provide objective determination of criterion. 7) How the Structured ness of the program is calculated? Structured ness as it simplest may be calculated in terms of the average length of code modules within the programs. Structured ness α modularity lines of code α = lines of code / Number of modules 8) What are the two types of software quality metrics? Predictive Metrics is used to Make Better Decisions Faster Descriptive Metrics is used to illustrate a condition measured at a certain point 9) Give the characteristics of quality of software? Quality is not absolute and independent. Quality is multidimensional, subject to constraints, acceptable compromises. 10) Why software is considered to be problematical?

Software has no physical existence, the lack of knowledge of client needs, the rapid change in hardware and software, High expectation of customers 11) What does software development methodology mean? A software development methodology or system development methodology in software engineering is a framework that is used to structure, plan, and control the process of developing an information system. 12) Write down the features of software development methodology? A software development methodology is a framework which includes the pre-definition of specific deliverables and artifacts that are created and completed by a project team to develop or maintain an application. It can be taught, scheduled, measured, compared and modified. 13) What is the problem areas associated with implementation of the method? The method is different. The need for training, retraining, effective management, measure progress and Picking up errors earlier may cause frustration. 14) Define workability? Workability is defined as the raw ability of the system to do work. Workability may consider in terms of: 1.Process capacity-it s the ability to process transactions within a given unit of time. 2. Storage capacity-it s the ability of the system to store things such as information. 3. Responsiveness-It s the measure of the response to single event. 15) Define Availability? Availability is concerned with the proportion of elapsed time that a system is able to be used. The sub attributes are reliability, maintainability, integrity 16) Define Adaptability? Adaptability may consider in terms of improvability, extendibility and Portability. Improvability-the time taken to make minor changes to the system where the term system is taken to include items such as documentation. Extendibility-It s the ease of adding new functionality to system. Portability-It s the ease of moving a system from one environment to another. 17). Write down the principles behind the quality management? The best scenario is to prevent errors being injected into the development process. When errors are introduced, improve the front end of the development process to remove as many of them as early as possible. If the project is beyond the design and code phases, unit tests and any additional tests by the developers serve as gate keepers for defects to escape the front end process before the code is integrated into the configuration management system. 18) What are the activities involved in Quality Improvement Program (QIP)? Blitz testing the technique, concurrently interviewed in a single session. Customer evaluation Allow customers to quickly and easily provide feedback to service provider managers. Code inspections, in which the team examines a sample of code and fixes any defects in it. Design review Process is a mechanism for ensuring design standards, alignment, and diligence throughout the course of the product design process. Extension of system tests provides system test features to simplify and speed up system test cases 19) Write down the product quality attributes? Technical solution, Support and service, Marketing, Administration, Delivery, Company image. 20) What is a software reliability model? Software reliability model is used to assess software products reliability or to estimate the number of latent defects when it is available to the customers.

UNIT II 1) Write down the five methods suggested by WAATS for measuring quality? Simple Scoring, Weighted Scoring, Phased Weighting factor method, the Kepner-Tregoe method and the Cologne combination method. 2) Gilb s approach becomes obsolete. State reason. Use of a template rather than rigid model. Explicit recognition of constraints upon quality. Recognition of critical resources, Use of locally defined measures. Close links with the development process. 3) Write down the gilb s quality attributes? Workability, Availability, Adaptability, Usability 4) Write down the limitations of metrics? They cannot be validated. They are not generally objective. Quality is relative, not an absolute quantity. They depend upon a small set of measurable properties. The do not measure the complete set of quality criteria. The metrics measure more than one criterion. 5) How the metrics are classified? Readability is a measure of usability, Error prediction as a measure of correctness, Error detection as a measure of correctness, MTTF as a measure of reliability, Complexity as a measure of reliability. 6) What are the seven criteria suggested by watts for a good metric? Objectivity, Reliability, Validity, Standardization, Comparability, Economy, Usefulness 7) Define SSADM. Write down the principle behind SSADM. SSADM-Structured System and Design Methodology. The aim of SSADM is to ensure that user requirements are reflected in the design of the system. The three principles behind SSADM are User Involvement, Quality Assurance, and Separation of logical and Physical design. 8) What are the stages involved in SSADM? Analysis of current system, Requirement specification, Selection of technical options. Data design, Process design, Physical design. 9) What are techniques used in SSADM? SSADM make use of a number of techniques, both diagrammatic and non diagrammatic. Diagrammatic Techniques Non-Diagrammatic Techniques 1)Data Flow Diagram 1) Relational Data Analysis 2)Logical data structures 2) First-cut rules. 3)Entity life histories 3) Physical design control. 4)Logical dialogue outlines 4) Project Estimation. 5)QA Reviews 10) Write down the seven phases involved in IEM? Information Strategy Planning. Business Area Analysis. Business System Design. Technical Design. Construction. Transition and Production. 11) Write down the advantages of IEM? It links system development to business needs. It covers the whole life cycle and it facilitates the use of a case tool. 12) Define CASE tool? CASE-Computer Aided Software Engineering. CASE tools are computer based tools to assist in the software engineering process. CASE tool is made up of set of tools.

13) What are advantages of CASE Tools? Productivity, Consistency, Methodology Automation, Encourages Good Practice, Documentation, Maintenance. 14) What are different types of CASE tools? Front end or upper case tools, Back end or lower case tool, integrated case tools. 15). Define Quality Control. A systematic method of economically providing products or services that met the User s requirements. 16). What are five factors affecting software quality assurance? Size of the system, Criticality of the system, the cost of correcting errors. type of release. Relationship with user. 17). Write down the five effective methods to ensure the failure of software quality assurance? Too many technical niceties, too much time spent stopping, rather than preventing defects. Efforts wasted. Management has a problem with the mathematical kid. Always complaining about the government but no one does anything. 18). What are the attributes are affect the product quality attributes? Technical solution, Support and service, Marketing, administration, Delivery, Company image. 19). What does software quality control mean? A systematic method of economically providing products or services that met the User s requirements 20). List the non-diagrammatic techniques used in the SSADM? 1) Relational Data Analysis 2) First-cut rules. 3) Physical design control. 4) Project Estimation. 5) QA Reviews 21). What are the functional and non-functional requirements of FURPS model? (Dec 2012) Characteristics in two different categories of requirements: 1. Functional requirements (F): Defined by input and expected output. 2. Non-functional requirements (URPS): Usability, reliability, performance, supportability. 22). Develop a fishbone diagram for problem and causes in software? (Dec 2012) Refer the diagram fig 6.5 page no 112 of the book software quality theory and management by gillies.

UNIT III 1) Define QMS? The organizational structure, responsibilities, procedures, processes and resources for implementing quality management. 2) Write down the SPC techniques? Process flow chart, Tally chart, Histogram, Pareto Analysis., Cause-and Effect diagram. Scatter diagram, Control charts. 3) Define Quality Control. A systematic method of economically providing products or services that met the User s requirements. 4) Define DRE? DRE=Errors found by an inspection * 100% Total Errors in the product before Inspection 5) Name the two metrics for DRE? Total defect containment Effectiveness (TDCE) Phase containment Effectiveness (PCE) TDCE= Number of pre release defects Number of prerelease defects number of post release defects PCE=Number of phase i errors Number of phase I errors Number of phase I defects 6) Write down the characteristics of DRE? There are only two phases of defect removal. The defect removal effectiveness for the two phases is same. 7) Write down the five steps involved in Fagan s Inspection method? 1.Overview 2.Preparation 3.Inspection 4.Rework 5.Follow-up. 8) Why we have to assess the reliability of a software product? It is important for two reasons: As an objective statement of the quality of the product., For resource planning for the software maintenance phase. 9) How the reliability models are classified? Reliability models are classified into two types. 1.Dynamic models 2.Static models A static model uses other attributes of the project or program modules to estimate number of defects in the software. Dynamic models usually based on statistical distributions, uses development defect patterns to estimate end product reliability. 10) What are five factors affecting software quality assurance? 1. Size of the system, 2.Criticality of the system, 3. The cost of correcting errors 4. Type of release 5.Relationship with user. 11) Write down the five effective methods to ensure the failure of software quality assurance? Too many technical niceties. Too much time spent stopping, rather than preventing defects. Efforts wasted. Management has a problem with the mathematical kid. Always complaining about the government, but no one does anything. 12) What is Software Interfaces documentation? Software interfaces documentation describes capabilities and functionality of all interfaces between any two or more components of the system. This includes major components, sub components and external systems.

13) Write down the criteria s involved in reliability models? Predictive validity, Capability, Quality of assumptions, Applicability, Simplicity 14) Write down the procedures involved in modeling software reliability? Examine the data; Select a model or several models to fit the data. Estimate the parameters of the model; obtain the fitted model by substituting the estimates of parameters into the chosen model. Perform a goodness of-fit test and assess the reasonableness of the model. Make reliability predictions based on the fitted model. 15) Define test compression factor? The difference between testing defect density and field defect density is called compression factor. 16) What are the four types of scenarios? Best case scenario, Good scenario, unsure scenario, Worst case scenario. 17) Write down the advantages of using reliability growth model? Comparisons can be made when the first data points become available. If unfavorable signs are detected timely action s can be taken. To determine end date of testing. 18) Write down the general formula to calculate the cyclomatic complexity? M=V(G) =e-n+2p, Where V(G) = cyclomatic number of G E=number of edges. N=number of nodes. P=number of unconnected parts of the graph. 19) Define Structure complexity? Henry and Kafura s structure complexity is defined as Cp=(fan-in *fan-out) 2 20) Define Complexity metrics and models? Complexity metrics and models are by small team metrics. They measure the internal dynamics of design and code of the software and the unit of analysis is usually at the program module level. 21) What is the difference between fault and a defect? (Dec 2011) Error: A discrepancy between a computed, observed, or measured value or condition and the true, specified, or theoretically correct value or condition. See: anomaly, bug, defect, exception, and fault Failure: The inability of a system or component to perform its required functions within specified performance requirements. See: bug, crash, exception, and fault. Bug: A fault in a program which causes the program to perform in an unintended or unanticipated manner. See: anomaly, defect, error, exception, and fault. Fault: An incorrect step, process, or data definition in a computer program which causes the program to perform in an unintended or unanticipated manner. See: bug, defect, error, exception. Defect: Mismatch between the requirements. 22) What is software Quality Assurance? (Dec 2011) Software assurance is defined as the level of confidence that software is free from vulnerabilities, either intentionally designed into the software or accidentally inserted at anytime during its lifecycle and that the software functions in the intended manner. The main objective of software assurance is to ensure that the processes, procedures, and products used to produce and sustain the software conform to all requirements and standards specified to govern those processes, procedures, and products. A secondary objective of Software assurance is to insure that the software-intensive systems we produce are more secure. 23) Define Testability? (Dec 2011) 1. A procedure for critical evaluation; a means of determining the presence, quality, or truth of something; a trial: a test of one's eyesight; subjecting a hypothesis to a test; a test of an athlete's endurance. 2. A series of questions, problems, or physical responses designed to determine knowledge, intelligence, or ability.

3. A basis for evaluation or judgment: 24). What are the Deming s quality management points? (Dec 2012) Deming's 14 points: Constancy of purpose, A new philosophy, Cease dependence on inspections, End lowest tender contracts, Improve every process, Institute training on job, Institute leadership, Drive out fear, Break down barriers, Eliminate exhortations, Eliminate targets, Permit pride of workmanship, Encourage education, Create top management structures 25). What are the weaknesses of ISO 9000 quality factors in quality assurances? (Dec 2012). The disadvantages experienced appear to be too much bureaucracy and lack of flexibility, which are inherent parts of the ISO standards, together with the significant amount of paper work involved. UNIT -IV 1) Write down the principles behind the review process? Establishing what reviews are needed by the project. Contents of various reviews, results o f the review 2) Write down the specification for reviews? Formal reviews occur at meaningful points of the software schedule. Include affected groups within organization and customer or end user representatives as appropriate. Review materials that the responsible software managers have reviewed and approved. Check the commitments, plans and status of the software activities. Document the identification of significant issues, Address the software project risks. Define any refinements in the software development plan 3) Write down the objectives of Management Review Process? Making activities progress according to plan, changing project direction. Identify the need for alternative planning, maintaining the global control of the project. 4) What are the inputs given to the management review process? Statement of objectives, List of issues to be addressed, Current project schedule, Report from other reviews, Reports of resources assigned to project, Data on the software elements completed. 5) What are the procedures involved in the management review? Planning, Overview, Preparation, Examination, rework 6) Write down the objective of Technical review? Evaluation of a specific software element, Identification of any discrepancies from specification and standards, Recommendations after the examination of alternatives. 7) What are inputs given to the technical review processes? Statement of objectives, Software elements being examined, Specifications for the software elements. Plans, standards or guidelines against which the software elements are to be examined. 8) Write down the procedures involved in auditing? Planning, Overview, Preparation, Examination, Reporting 9) Write down the preparations that have to be made by the audit team? Understand the organization, understand the products and processes, understand the objective audit criteria, prepare for the audit report, and Detail the audit plan. 10) Write down the contents included in the Auditing plan? Project processes to be examined, Software required to be examined. Reports shall be identified,

Reports distribution, required follow up activities. 11) What are the requirements required for the document audit and verification? Acquisition of project documentation, Analysis of documents, Dissemination of information. 12) When the auditing is said to be complete? When each element within the scope has been examined and Findings have been presented to the auditing organization. Response to the draft audit has been received. Final findings have been formally presented; The audit report has been prepared and submitted. All follow-up actions by the auditing organization have been performed. 13) Write down the contents of audit reports? Audit Identification, Scope, Conclusions, Synopsis, Follow-up. 14) What is Auditing? An audit provides an objective compliance confirmation of products and processes to certify adherence to standards, guidelines, specifications and procedures. Audits are performed in accordance with documented plans and procedures.the results of the audit are documented and are submitted to the management of the audited organization, to the entity initiating the audit and to any external organizations identified in the audit plan. 15) What is the purpose of performing Review and auditing? The purpose of performing review and audits are to ensure that the products meet all client needs and requirements and to find development anomalies as early and as inexpensively as possible. 16) What are Ishikawa s seven basic tools for quality control? Check sheet, Pareto diagram, Histogram, Scatter diagram, Run chart, Control chart, Cause and effect diagram. 17) What is the purpose of using check sheet? A check sheet is a paper form with printed items to be checked. Its main purpose is to facilitate gathering data and to arrange data while collecting it so the data can be easily used later. 18) What is the use of pareto diagram? A pareto diagram is a frequency chart of bars in descending order. A pareto diagrams can identify the few causes that account for the majority of defects. It indicates which problem can be solved first in eliminating defects and improving the operation. Pareto analysis can be referred to as 80-20% principle. 19) What is the purpose of using Histogram? The histogram is a graphic representation of frequency counts of a sample or a Population. the purpose of histogram is to show the distribution characteristics of a parameter. 20) What is the use of scatter diagram? A scatter diagram vividly portrays the relationship of two interval variables. 21) Define QMS? (Dec 2011) The organizational structure, responsibilities, procedures, processes and resources for implementing quality management. 22). Differentiate software quality and software reliability? ( Dec 2012) Reliability means criteria of quality be employed. Quality means degree of excellence 23). what are the activities involved in statistical process control. ( Dec 2012) Process flow charting - used to show what is done, Tally charts - to show how often something is done Histograms - to show overall variation, Pareto analysis - to highlight the big problems, Cause and effect diagrams - to indicate causes of problems and errors Scatter diagrams - to highlight relationships Control charts - to show which variation to control

UNIT-V 1) Define process capability? Cp= USL-LSL 6σ 2) Define process capability index? Cp = USL-u 3σ 3) Write down the assumptions made in the phases of defect removal activities? Those activities handled directly by the development team for large software projects. The formal machine tests after code integration. 4) How will u calculate the total defects for the life of the software? TD=MP+PTR+Q TD=Total defects for the life of software. MP=Major problems found during review. Q =Number of defects in the released software. 5) What are the two types of inspector phase defined by knight and Myers? Single Inspector Phase and Multi Inspector phase. 6) What is single inspector phase? It s a rigidly formatted process driven by a list of unambiguous checks, for e.g., internal documentation, source code layout, source code readability. 7) What is multi inspector phase? It s designed to check for those properties of the software that cannot be captured in a precise yes or no statement is called the multi inspector phase. 8) What is the use of software reliability models? Software reliability models are used to assess software products reliability or to estimate the number of latent defects when it is available to the customers. 9) What is the need of assessing the software reliability? An estimate is important for two reasons As an objective statement of the quality of the product Resource planning for software maintenance phase. 10) Write down the classification of reliability models? The reliability models can be broadly classified into two categories. They are Static models, Dynamic models 11) What are the assumptions made in the reweigh model curve to model the software development activity? Defect rate observed during development process is positively correlated with the defect rate. Same error injection rate 12) Define component. A component is a group of modules that perform specific functions such as spooling, printing, message handling, file handling, and so on. 13) What is DUD? DUD is a derivative free algorithm for non linear least squares. It competes favorably with even the best derivative based algorithm when evaluated on number of standard test problems. One of the advantage behind this DUD method is its simplicity and its efficiency.

14) Define Predictive validity? Predictive validity refers to the accuracy of model estimates. To achieve the Predictive validity is to make sure that the input data are accurate and reliable. 15) What are the strengths of Rayleigh model? Compared to phase defect removal model, the Rayleigh model is a formal parametric work that can be used for projecting latent software defects when the development work is complete.another strength of Rayleigh model is it provides an excellent framework for quality management. 16) How the Reliability growth models are classified? Reliability growth models are classified into two major classes depending on the Dependent variable of the model. They are time between failure models and Fault count models. 17) Write down the equation for Goal generalized non homogenous Poisson process model? M(t) = a(1-e -btc ) 18) What are different types of Reliability growth models? J-M Model, Little wood Model, Goel-Okumoto Imperfect Debugging Model. Goel-Okumoto Non Homogenous Poisson Process Mode, the Delayed and Inflection S Model. 19) What are assumptions made in J-M model? There are N unknown software faults at the start of testing. Failures occur randomly-times between failures are independent. All faults contribute equally to cause a failure. Fix time is negligible; Fix is perfect for each failure. 20) What is Kaizen? (Dec 2011) Kaizen is small improvements and a change for better. It must be accompanied by change of method. The Kaizen concept stimulates productivity improvement as an ongoing process in any company. It is a practice oriented strategy which leads to creation of culture of improvement it is more a way of life or at least a cultural approach to quality improvement. The implementation of philosophy of Kaizen can be achieved through involvement of employees to effect improvements. 21) What are the assumptions made in fault count model? Testing intervals are independent of each other. Testing during intervals is reasonably homogenous. Number of defects detected during non overlapping intervals are independent of each other. 22) What is Zero Defect Quality? Is it possible to achieve it? Justify. (Dec 2011) "Zero defects" is referred to as a philosophy, a mentality or a movement. It's not a program, nor does it have distinct steps to follow or rules to abide by. This is perhaps why zero defects can be so effective, because it means it's adaptable to any situation, business, profession or industry. The question that often comes up when zero defects is discussed, is whether or not zero defects is ever attainable. Essentially, does adopting a zero defect environment only set users up for failure? Zero defects is NOT about being perfect. Zero defects is about changing your perspective. Zero defects is a standard. It is a measure against which any system; process, action, or outcome can be analyzed. When zero defects is the goal, every aspect of the business is subject to scrutiny in terms of whether it measures up.

PART B (16 MARKS) UNIT I 1.Define Software quality. Explain about Hierarchical model (Dec 2011) & GE model of Software quality To compare quality in different situations, both qualitatively and quantitatively, it is necessary to establish a model of quality. Many model suggested for quality. Most are hierarchical in nature. A quantitative assessment is generally made, along with a more quantified assessment. Two principal models of this type, one by Boehm and one by McCall 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. The issues relating to the criteria of quality are: THE GE MODEL - The three areas addressed by McCall s model (1977) - Product operation - Product revision: - Product transition, McCall s criteria of quality defined, Efficiency - Usability Integrity Correctness Reliability, Maintainability Flexibility Testability Portability Reusability Interoperability 2. Explain the concept of process maturity and its improvement (Dec 2011) 3. Explain the quality models. Explain Mccalls quality model and Boehm model of software quality. Describe the boehm s software quality characteristics tree ( Dec 2012) The high-level characteristics address three main questions that a buyer of software has: As-is utility Maintainability: Portability The intermediate level characteristic represents Boehm s 7 quality factors that together represent the qualities expected from a software system: Portability Reliability Efficiency Usability Testability Understandability. Flexibility The following diagram shows Boehm s quality model and McCall s model attributes and subattributes.

The two models share a number of common characteristics are, 4. What is the need to quality? Illustrate the procedure to measure Software quality for a software product. (Dec 2012) CONCEPTS OF QUALITY: Ability of the product/service to fulfill its function Hard to define Impossible to measure Easy to recognize in its absence Transparent when present

Characteristics of Quality: Quality is not absolute Quality is multidimensional Quality is subject to constraints Quality is about acceptable compromises Quality criteria are not independent, but interact with each other causing conflicts. Software Quality: Views of quality: Popular Views: Professional views: Views of Quality: Quality is a multidimensional construct. It may therefore be considered using a polyhedron metaphor. The software project has the following roles: Project manager, Business analyst, Implementation programmer, Quality auditor End user, Line manager, Project sponsor 5.Explain about software quality and view quality with neat diagram Refer previous question for software quality. Quality is people: Quality is determined by people because It is people and human organizations who have problems to be solved by computer software. It is people who define the problems and specify the solutions. It is still currently people who implement designs and product code. It is people who test code. 6.Explain about software metrics The goals and measurement areas identified by the Motorola Quality Policy for Software Development (QPSD) are listed in the following. Goal 1: Improve project planning. Goal 2: Increase defect containment. Goal 3: Increase software reliability. Goal 4: Decrease software defect density. Goal 5: Improve customer service. Goal 6: Reduce the cost of nonconformance. Goal 7: Increase software productivity. 7. What are the problems with metrics? Functionality, Usability, Reliability, Performance, Supportability, number of other requirements such as testability, adaptability, maintainability, compatibility, configurability, install ability, scalability, localizability. 8. Explain about attributes of Gilb in detail. Workability: Process capacity, Responsiveness, Storage capacity Availability: Reliability, Maintainability, Integrity, Adaptability: Improvability, Expendability, Portability Usability: Entry level, Learning requirement, Handling, Likeability The resource Attribute: Time resource is of two types: calendar time to delivery and the time taken by the system once developed to carry out the task. People resource may be measured in terms of man-years Money resources concern both development and maintenance costs. Measures for the template: Transactions per second, Records per minute, Bytes per line, Bits per node per second. Distinct features: Use of template rather than a rigid model., Explicit recognition of constraints upon quality, Recognition of critical resources., Use of locally defined measures., Close links with the development process.

9. Explain about COQUAMO tools. COQUAMO-1: Prediction The predictive tool makes use of techniques similar to those at the heart of cost estimation models such as COCOMO. Product attributes such as quality requirements, success criticality and difficulty developing the product in question. Process attributes such as process maturity, tool use and method maturity. Personnel attributes such as staff experience and motivation. Project attributes such as the quality norms and leadership style. Organizational attributes such as quality management and physical environment. COQUAMO-2: Monitoring, COQUAMO-3: Testing 10.What are the functions worked on metrics recently and explain it. Recent work on metrics: Metric - quantitative measure of degree to which a system, component or process possesses a given attribute. A handle or guess about a given attribute. Estimate the cost & schedule of future projects, Evaluate the productivity impacts of new tools and techniques, Establish productivity trends over time, Improve software quality, Forecast future staffing needs, Anticipate and reduce future maintenance needs, Example metrics.defect rates: Error rates, Measured by: individual, module, during development Errors should be categorized by origin, type, costproducts, Resources. The size of the metrics are:size of the software produced LOC - Lines Of Code, KLOC - 1000 Lines Of Code, SLOC Statement Lines of Code (ignore whitespace), Typical Measures: Errors/KLOC, Defects/KLOC, Cost/LOC, Documentation Pages/KLOC. UNIT II 1.Consider you have been assigned as a member of QA group that defines and assigns the tasks, work products and processes that will be performed in the software development, for a Banking application. Explain how you implement the Quality Function Deployment. ( Dec 2012) The 3 main goals in implementing QFD are: Prioritize spoken and unspoken customer wants and needs. Translate these needs into technical characteristics and specifications. Build and deliver a quality product or service by focusing everybody toward customer satisfaction. Each of the four phases in a QFD process uses a matrix to translate customer requirements from initial planning stages through production control. Phase 1, Product Planning: Phase 2, Product Design: Phase 3, Process Planning: Phase 4, Process Control: The House of Quality Steps to the House of Quality : Step 1: Customer Requirements - "Voice of the Customer" Step 2: Regulatory Requirements Step 3: Customer Importance Ratings Step 4: Customer Rating of the Competition Step 5: Technical Descriptors - "Voice of the Engineer" Step 6: Direction of Improvement Step 7: Relationship Matrix Step 8: Organizational Difficulty Step 9: Technical

Analysis of Competitor Products Step 10: Target Values for Technical Descriptors Step 11: Correlation Matrix Step 12: Absolute Importance. The Next stage The above process is then repeated in a slightly simplified way for the next three project phases. A simplified matrix involving steps 1, 2, 3, 5, 6, 7, 9 & 11 above is developed. 2. Explain the levels of CMM quality model ( Dec 2012) 3. Write a short note on FURPS and FURPS+ models. (Dec 2011 ) FURPS MODEL (The "+" in FURPS+ includes such requirements as design constraints, implementation requirements, interface requirements and physical requirements.) The FURPS model proposed by Robert Grady and Hewlett-Packard Co. de-composes characteristics in two different categories of requirements: 1. Functional requirements (F): Defined by input and expected output. 2. Non-functional requirements (URPS): Usability, reliability, performance, supportability. FURPS stands for: Functionality, Usability Reliability Performance Supportability FURPS+ MODEL: Functionality, Usability, Reliability, Performance, Supportability, Design constraints, Implementation constraints, Interface constraints, Physical constraints. 4.Write a note on measures and metrics of software quality.

Attempting to collect measures where none had been collected in the past often precipitates resistance. "Why do we need to do this?" asks a harried project manager. "I don't see the point," complains an overworked practitioner. Arguments for Software Metrics As the software design is completed, most developers would be anxious to obtain answers to the questions such as Which user requirements are most likely to change? Which components in this system are most error prone? How much testing should be planned for each component? How many errors (of specific types) can I expect when testing commences? Answers to these questions can be determined if metrics have been collected and used as a technical guide. In later chapters, we examine how this is done. Establishing a Baseline: To be an effective aid in process improvement and/or cost and effort estimation, baseline data must have the following attributes: (1) data must be reasonably accurate " guest imates" about past projects are to be avoided; (2) data should be collected for as many projects as possible; (3) measures must be consistent, for example, a line of code must be interpreted consistently across all projects for which data are collected; (4) applications should be similar to work that is to be estimated it makes little sense to use a baseline for batch information systems work to estimate a real time, embedded application. 5.Explain about gilb s approach (Dec 2011) Refer question no 8 of unit 1 part b answers 6.Explain the stages involved in SSADM? System design methods are a discipline within the software development industry which seek to provide a framework for activity and the capture, storage, transformation and dissemination of information so as to enable the economic development of computer systems that are fit for purpose. SSADM is a waterfall method by which an Information System design can be arrived at; SSADM can be thought to represent a pinnacle of the rigorous document-led approach to system design, and contrasts with more contemporary Rapid Application Development methods such as DSDM.A A baseline for comparison and evaluation of other methodologies and for themes in systems development. Assumptions about information systems: relatively stable routine processing, welldefined interaction, free-standing, developed from "scratch", globally defined data, processes, complete and objectively definable, information is well-structured These stages of SSADM to be explained in detail: 1. feasibility study, 2. Systems analysis 3.systems design 7. Explain GQM model? Purpose, Perspective, Environment: GQM is a framework for developing a metrics program Steps: Generate a set of organizational goals. What do you want to improve? Derive a set of questions relating to the goals, Answers provide visibility into meeting the goals, Develop a set of metrics needed to answer the questions The Goal Question Metric (GQM) approach is based upon the assumption that for an organization to measure in a purposeful way it must first specify the goals for itself and its projects, then it must trace those goals to the data that are intended to define those goals operationally, and finally provide a framework for interpreting the data with respect to the stated goals. The resulting measurement model has three levels 8. Explain about CASE tools? CASE tools: Automated Diagram Support: Checks for syntactic correctness, Data dictionary support Checks for consistency and completeness, Navigation to linked diagrams, Layering, Requirements traceability, Automatic report generation, System simulation, Performance analysis, CASE tools: Software construction and maintenance: Code generators Generate code from the design model Think of the advantages! may also generate database schemata Maintenance tools Reverse

Engineering, Analysis of program code. CASE tools: Advantages: Help standardization of notations and diagrams, Help communication between development team members, Automatically check the quality of the A&D models, Reduction of time and effort, Enhance reuse of models or models components 9.Explain about Rayleigh model frame work? Rayleigh Model Framework: Based on the two assumptions: 1. Defect rate observed during development is positively correlated with defect rate observed in the field 2. Given the same error injection rate, if more defects are found and removed early then fewer will remain in later stages Do it right the first time. It is important to manage quality throughout the entire development process 1. Best scenario is to prevent errors from being injected into the development process (and hence, into the product) 2. When errors are introduced, improve front-end processes (design reviews, code reviews, etc.) to remove as many of them, as early as possible. 3. Unit testing serves as the last chance to catch errors in the front-end process. The Rayleigh model is a good Quality Management model because it promotes defect prevention and early defect detection, As an in-process tool, the data can indicate the quality direction of the current project, 10.What is Quality metrics? Write the various metrics that are used to measure the quality of the product. Measurement is crucial to the progress of all sciences, Scientific progress is made through observations and generalizations based on data and measurements., The confirmation or refutation of theories via hypothesis testing depends on empirical data and measurement. Example Hypothesis To confirm or refute this proposition we need to: Define the key concepts, e.g., the software development process. Distinguish the process steps and activities of the front end from those of the back end. Sample Development Process Front-End and Back-End Steps: Assume everything through debugging and development tests is the front end. The back-end is everything from integration onward. Definition of Rigorous Implementation. How Would We Operationally Define Rigorous Testing? How Would We Operationally Define Back-End Quality? Possible Testable Hypotheses. Levels of Measurement: The four levels of measurement: Nominal Scale, Ordinal Scale, Interval Scale, Ratio Scale, The scales are hierarchical. One should always try to devise metrics that can take advantage of the highest level of measurement allowed by the nature of the concept and its definition. Nominal Scale, Ordinal Scale, Interval Scale, Ratio Scale, Some Basic Measures: Ratio, Proportion, Percentage, Rate, Six Sigma Ratio, Proportion, Percentage, And also explain metrics UNIT III 1.Explain the features of ISO 9000 model. Compare ISO 9000 and CMM models. Specify advantages and disadvantages of these models. ( Dec 2012) Capability Maturity Model versus ISO 9000The Capability Maturity Model (CMM) The Software CMM is organized into five maturity levels, described in Table 1. Maturity Description Level The software process is characterized as ad hoc, and 1 - Initial occasionally even chaotic. Few processes are defined, and success depends on individual effort and heroics. 2- Basic project management processes are established to track

Repeatable 3 - Defined 4 - Managed 5 - Optimized cost, schedule, and functionality. The necessary process discipline is in place to repeat earlier successes on projects with similar applications. The software process for both management and engineering activities is documented, standardized, and integrated into a standard software process for the organization. All projects use an approved, tailored version of the organization's standard software process for developing and maintaining software. Detailed measures of the software process and product quality are collected. Both the software process and products are quantitatively understood and controlled. Continuous process improvement is enabled by quantitative feedback from the process and from piloting innovative ideas and technologies. Table 1 - CMM Maturity Levels - Key Process Area Example 2. What are the components of QMS?. Explain the four principal aspects of a QMS for software. How are stereotype and enthusiant people managed in QMS?. ( Dec 2012) Elements of a QMS:The International Standards Organisation (ISO) defines a quality management system as having the following components: Organisational structure, Responsibilities, Procedures, Processes, resources. The procedures in a QMS Statistical Process Control (SPS) There are seven (7) basic methods used in statistical process control. These are sometimes called Ishikawa's seven basic methods. They are: Process flow charting - used to show what is done Tally charts - to show how often something is done Histograms - to show overall variation, Pareto analysis - to highlight the big problems, Cause and effect diagrams - to indicate causes of problems and errors, Scatter diagrams - to highlight relationships, Control charts - to show which variation to control.the four principal aspects of a QMS for software. Development procedures, Quality control, Quality improvement, Quality assurance 3.Explain about the methods that are used for measuring software quality (Dec 2011) It refers to specified functional & non-functional requirements such as supportability, performance and usability. It refers to the ability to perform well in unforeseeable scenarios with low defect rate. SQA is a control of processes. Reliability is the probability of failure-free software operation. Software Reliability is an important factor in affecting system reliability. Verifiability: Verifiability is the measure of effort to verify (via tests, inspection, demonstration and analysis) software. Safety: The discipline of software safety is a systematic approach to identifying, analyzing, tracking, mitigating and controlling software hazards and hazardous functions (data and commands) to ensure safe operation within a system. Supportability, Which may include testability, extensibility, adaptability, maintainability, compatibility, congurability, serviceability, Installability. 4. Explain the various procedures and elements available in QMS. (Dec 2011) The organizational structure, responsibilities, procedures, processes and resources for implementing quality management. Elements of a QMS: Organizational structure, Responsibilities, Procedures, Processes, Resources, Development procedures, Quality control, Quality improvement, Quality assurance It should have a role in monitoring. Quality of the procedures and processes results in a product that fully meets the users requirements.- Independent group of people whose function is solely to monitor the implementation of the quality plan. 5.List and explain the tools which are used for maintaining software quality. Rational quality health assessment tool, ROI estimator, Web cast.

6.Explain about reliability growth model for QMS. Models from previous products can be used to track the defect rates of the current product To experience significant quality improvement, the current defect arrival rate must fall below the Model curve. Comparing to a model allows for quality actions to be identified and implemented. Models can be good for determining the end date of testing. Other models should be used in conjunction because the Reliability Growth Models do not focus on the front-end of the process 7.Explain the time management process in the quality management system. Motivation, Project Time Management 10 Principles of Agile Project Time Management 1. Use a Definition of "Done". 2. Use Timeboxes to Manage Work. 3. Don't Add Slack to Task Estimates. 4. Defer Decisions. 5. Reduce Cycle Time. 6. Keep the Pipeline Short and Thin. 7. Keep the Discipline. 8. Limit Task Switching. 9. Prevent Sustained Overtime. 10. Separate Urgency from Importance 8. Write a note on quality management standard. The organizational structure, responsibilities, procedures, process and resources for implementing quality management. Senior management responsibility performance standard general approach- structure SPC- basis for improvement Team work costs of quality purchasing vendor rating single sourcing of supply. 9. Explain about quality control assurance and engineering. Quality control assurance definition deming juran and others demonstrates - kaizen 10. Compare different ISO 9000 series standards. The ANSI standards: Q9000, Q9001, Q9002, Q9004 are now closely aligned and consistent with the ISO standards of the same name. ISO 9000 describes the quality elements that must be present for a quality assurance system to be compliant with the standard, but it does not describe how an organization should implement these elements. UNIT IV 1. Explain the approach of Six sigma processes in software quality management.( Dec 2012) Six Sigma' is a highly disciplined approach to decision making that helps people focus on improving processes to make them as near perfect as possible. (Breakthrough Management Group) 'Sigma' is simply a statistical term describing how capable a process is. The more capable the process (ie the less defects, errors or waste), the higher the sigma value. At a level of 'six sigma', the process works right first time in 999,997 cases per million. When 'cost down' or 'volume up' is required through reduction in defects: Where clear financial outcomes must be reliably delivered. Where clear customer requirements need to be understood e.g. trade offs where variation is process output needs controlling within limits. when services or products involve human life or safety. Where designing new services or products (using 'Design for Six Sigma') 2. Assume that a software firm for quality consulting has approached you. What are the factors and measures will you derive to implement the ISO certification for the software firm.( Dec 2012) The most important factors of successful implementation of, customer focus, reviews, quality Policy and Resources (funds, facilities, personnel). The table below shows the relationship between significance and effort for each of these factors. 1. management commitment. 2. Workers commitment. 3. Documentation 4. customer focus 5. quality Policy 6. preventive /. corrective measures. 7. periodic inspections 8. Training 9. reviews 10. Resources 3. Explain CMM and CMMI (Dec 2011)

Maturity Level 1 - Initial 2- Repeatable 3 - Defined 4 - Managed 5 - Optimized Description The software process is characterized as ad hoc, and occasionally even chaotic. Basic project management processes are established to track cost, schedule, and functionality. The software process for both management and engineering activities is documented, standardized, and integrated into a standard software process for the organization.. Detailed measures of the software process and product quality are collected.. Continuous process improvement is enabled by quantitative feedback from the process and from piloting innovative ideas and technologies. 4. Explain about ISO 9001 series (Dec 2011) The International Organization for Standardization is a worldwide federation of national standards bodies. The term ISO stands for the International Organization for Standardization. One would assume that the acronym for the International Organization for Standardization would be IOS, but that is not the case. Apparently, the term ISO was chosen instead, because the term "ISO" in Greek means equal, and the association wanted to convey the idea of equality, that is, the idea that they develop standards to place organizations on an equal footing. The ANSI standards: Q9000, Q9001, Q9002, Q9004 are now closely aligned and consistent with the ISO standards of the same name. ISO 9000 describes the quality elements that must be present for a quality assurance system to be compliant with the standard, but it does not describe how an organization should implement these elements. 5.Explain people, process, product in software development and management spectrum. People: The primary element of any project is the people. People gather requirements, people interview users (people), people design software, and people write software for people. No people -- no software. Process: Process is how we go from the beginning to the end of a project. All projects use a process. Many project managers, however, do not choose a process based on the people and product at hand. They simply use the same process they've always used or misused. Product The product is the result of a project. The desired product satisfies the customers and keeps them coming back for more. Sometimes, however, the actual product is something less. 6. Describe the relevance to software engineering. ISO 9000 Relevance to Software Engineering: The ISO 9000:3 guideline provides an adaptation of the ISO 9001 standard to the field of software engineering. ISO 9000:3 was approved as an American National Standard on August 18 1998. The standard is listed as: ANSI/ISO/ASQ Q9000-3-1997, Guidelines for the Application of ANSI/ISO/ASQC Q9001-1994 to the Development, Supply, Installation and Maintenance of Computer Software. A revision to match ISO 9001:2000 has been assigned to ISO/IEC JTC1/SC7 (i.e. software engineering standards) subcommittee to make it fully compatible with ISO 9001:2000 7. Write a note on statistical quality control. Ishikawa's seven basic methods are: Process flow charting - used to show what is done. Tally charts

- to show how often something is done. Histograms - to show overall variation. Pareto analysis - to highlight the big problems. Cause and effect diagrams - to indicate causes of problems and errors Scatter diagrams - to highlight relationships. Control charts - to show which variation to control Statistica1 quality control (SQC) is the term used to describe the set of statistical tools used by quality professionals. Statistical quality control can be divided into three broad categories: 1. Descriptive statistics, 2. Statistical process control (SPC), 3. Acceptance sampling 8.What are zero defects in software? Explain it. "Zero defects" is referred to as a philosophy, a mentality or a movement. It's not a program, nor does it have distinct steps to follow or rules to abide by. This is perhaps why zero defects can be so effective, because it means it's adaptable to any situation, business, profession or industry. Zero defects is NOT about being perfect. Zero defects is about changing your perspective. It does this by demanding that you: Recognize the high cost of quality issues. Continuously think of the places where flaws may be introduced. Work proactively to address the flaws in your systems and processes, which allow defects to occur. 9. What are the goals of CMM model and its levels? Peer review activities are planned. Defects in the software work products are identified and removed. And so on into each of the five common features. Maturity Level 1 Initial, Maturity Level 2 Managed, Maturity Level 3 Defined, Maturity Level 4 - Quantitatively Managed, Maturity Level 5 Optimizing, Maturity Levels should not be skipped. 10. What are the revisions of ISO 9000: 2000? ISO 9000:2000 Revisions The ISO standard underwent a major revision in the years leading up to the turn of the century, and the result was a set of updated standards now known as ISO 9000/Q9000-2000. The major changes included: The adoption of a process approach to quality management. Recognition of the needs of stakeholders (customer focus). Additional requirements for continual improvement. Compatibility with other management system standards. Connects quality management systems to business processes. Simplified terminology: Subcontractor is now "supplier" Supplier is now "organization" UNIT V 1. Explain the direct and indirect software metrics involved in software project management,(dec 2012). We present in this section a discussion on software metrics as we use in-process testing metrics in our dissertation research. The term software metrics explains many activities, all of which involve some degree of software measurement. Cost and effort estimation, Productivity measures and models, Data collection, Quality models and measure, Reliability models, Performance evaluation and models, Structural and complexity metrics, Capability-maturity assessment, Management by metrics 2. Explain how software processes can be managed automatically in software development life cycle. ( Dec 2012) Requirement analysis- system and software design implementation and coding testing operations and management 3. How are software quality used in software project management and software process management ( Dec 2012). SPC methods allow us to calculate levels of non conformity and also provide a strategy for the reduction of variability. Contract review- design control document control- purchasing customer supplies tracebility process control checking- corrective action protection of quality training quality system audit.

4. What is metrics for small organization? Explain it. (Dec 2011) i) Metrics for Small Organization: The vast majority of software development organizations have fewer than 20 software people. It is unreasonable, and in most cases unrealistic, to expect that such organizations will develop comprehensive software metrics programs. However, it is reasonable to suggest that software organizations of all sizes measure and then use the resultant metrics to help improve their local software process and the quality and timeliness of the products they produce. Kautz describes a typical scenario that occurs when metrics programs are suggested for small software organizations: 5. Explain Ishkawa s seven basic tools (Dec 2011). Ishikawa s seven basic tools for quality control are checklist (or check sheet), Pareto diagram, histogram, scatter diagram, run chart, control chart, and cause-and-effect diagram. 6. Explain about complexity metrics and Models The reliability and quality management models have discussed are either at the project or the product level. Both types of model tend to treat the software more or less as a black box The lines of code (LOC) count are usually for executable statements. It is actually a count of instruction statements. The interchangeable use of the two terms apparently originated from Assembler program in which a line of code and an instruction statement are the same thing 7. Explain the classification of metrics SOFTWARE METRICS: We present in this section a discussion on software metrics as we use inprocess testing metrics in our dissertation research. The term software metrics explains many activities, all of which involve some degree of software measurement. Cost and effort estimation, Productivity measures and models, Data collection, Quality models and measure, Reliability models, Performance evaluation and models, Structural and complexity metrics, Capability-maturity assessment, Management by metrics. Evaluation of methods and tools. Since there is virtually an infinite number of possible software metrics, developers must have some criteria for choosing which metrics to apply for a particular project. 8. Explain about Defect Removal and Prevention Activities Associated with Defect Injection and Removal Development Phase Defect Injection Defect Removal Requirements Requirements-gathering process & Development of programming Requirement analysis and review High-level design Design work High-level design inspections Low-level design Design work Low-level design inspections Code implementation Coding Code inspections Integration/build Integration and build process Build verification testing Unit test Bad fixed Testing itself Component test Bad fixed Testing itself System test Bad fixed Testing itself 9. How will you analyze Customer satisfaction? Customer satisfaction is often measured by customer survey data via the five-point scale: Very satisfied Satisfied, Neutral, and Dissatisfied, Very dissatisfied. 10. What are the factors involved in the measuring and improving the software process? The methodologies may be developed for all or part of the software development process. Information system development methodologies such as IEM are concerned with the whole development process. SSADM is only directly applicable to the design and analysis of the process. *********************