Practice Exam 1

Part 1

  1. Name and explain three characteristics of Quality Requirement Statement
  2. Name and describe three characteristics of Quality Requirements Specifications
  3. Non-functional requirements have always been specified in loose, fuzzy terms that are open to wide ranging and subjective interpretation. Name and discuss the characteristics of “SMART” requirements (Mannion and Keepence, 1995)
  4. Name three non-functional requirements that enterprise applications usually get right
  5. Name three non-functional requirements that enterprise applications often do poorly on.
  6. Discuss the usability attributes: learnability, efficiency, memorability, errors & satisfaction

Part 2

  1. What is software quality and how do standards help ensure consistent quality?
  2. why is it that the standards related to computer science are very few? Mention a three Computer science related standards and the specific areas they are applied to.
  3. Draw and discuss ISO/IEC 9126 Quality Mode in terms of internal and external quality assurance as well as Quality in use.
  4. Describe a drawback of a company focusing only to the ISO 9000-3 principles
  5. Discuss the difference between product standards and process standards. Explain why implementing product standards is difficult in software engineering.

Part 3

  1. What is Capability Maturity Model and what are the five levels of process maturity?
  2. What are the five characteristics demonstrated in each maturity level?
  3. What are the common software quality assurance practices among Rational Unified Process (RUP), Microsoft Solution Framework (MSF) and Extreme Programming (XP)?
  4. Discuss the aspects of Software Quality Support in XP.
  5. What are the 3 objectives of SQA activities in software development?

Part 4

  1. Discuss what an interface of a module is. Give an example from the project you developed as part of QA.
  2. What is 'Content Coupling'? Why is not desirable?
  3. Discuss the processes of Validation and Verification. Explain how these two processes became real at the time of presenting your program you developed as part of QA.
  4. Consider the following piece of code. Develop the Control-flow diagram for the piece of code and suggest the nodes, edges or paths where test cases may be designed.
  1. Why is 'Data-Coupling' is an acceptable practice. give an example from the project you developed as part of QA.
  2. For the program you developed as part of QA, it had eight stages in the following order. First you (1) collected the requirements, then you (2) developed the GUI, (3) made some design decisions, (4) designed how data could be handled, (5) did programming, (6) developed test cases, (7) peer-reviewed it before finally (8) presenting your programme. Can you develop a PERT chart using the time taken to do each task as well as the dependencies between the tasks?
  3. Consider the following snippet of code. Identify the kind of coupling present in this piece of code. Rewrite the code to remove the existing coupling and to make it modular.

Part 5

  1. Identify 5 key causes of software failure?
  2. Name and discuss Shneiderman's "Eight Golden Rules". Why are the important for the success of software?
  3. How do we measure the software quality? What are the two measurable attributes of a software product?
  4. How do we turn the ideas about quality (such as reliability, complexity or usability) into measurables?

  1. Solutions 1