1 / 7

CPSC 372

CPSC 372. John D. McGregor Module 3 Session 4 Quality Attributes. Quality attributes.

hogan
Download Presentation

CPSC 372

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CPSC 372 John D. McGregor Module 3 Session 4 Quality Attributes

  2. Quality attributes • IEEE Std. 1061 subfactors:Efficiency                                    Portability• Time economy                           • Hardware independence• Resource economy                    • Software independenceFunctionality                               • Installability• Completeness                            • Reusability• Correctness                              Reliability• Security                                    • Non-deficiency• Compatibility                             • Error tolerance• Interoperability                          • AvailabilityMaintainability                           Usability• Correctability                             • Understandability• Expandability                             • Ease of learning• Testability                                  • Operability                                                  • Comunicativeness http://en.wikipedia.org/wiki/ISO/IEC_9126

  3. Qualities • Trade-offs (a trade off is when one quality degrades another quality as the first quality increases • Testability & modifiability • Performance and modularity • Develop a catalog of trade-offs

  4. Perspectives on quality • The executive • The customer • The developer • The tester

  5. Structure of a scenario • Source of stimulus (e.g., human, computer system, etc.) • Stimulus – a condition that needs to be considered • Environment - what are the conditions when the stimulus occurs? • Artifact – what elements of the system are stimulated. • Response – the activity undertaken after arrival of the stimulus • Response measure – when the response occurs it should be measurable so that the requirement can be tested.

  6. Performance scenario • Source of stimulus – typically an actor – Any user • Stimulus – clicks on save button • Environment – data has been entered into a matrix editor • Artifact – data matrix • Response – the data is written to the current file • Response measure – takes less than 2 seconds to write

  7. Quality without a name Naming something denotes certain properties more than others. By not putting into words what we see or feel about this scene we allow each viewer to emphasize what is important to them.

More Related