G&W Chapter 15: Attributes Software Specification Lecture 22

Slides:



Advertisements
Similar presentations
EDEXCEL LEVEL 2 BTEC FIRST DIPLOMA FOR ICT PRACTITIONERS
Advertisements

Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 1. Interviews 2. Workshops 3. Brainstorming.
Chapter 4 Capturing the Requirements 4th Edition Shari L. Pfleeger
College of Engineering and Computer Science Computer Science Department CSC 131 Computer Software Engineering Fall 2006 Lecture # 1 (Ch. 1, 2, & 3)
Eng. Mohammed Timraz Electronics & Communication Engineer University of Palestine Faculty of Engineering and Urban planning Software Engineering Department.
 Explain the role of a system analyst.  Identify the important parts of SRS document.  Identify the important problems that an organization would face.
1 CS 426 Senior Projects Chapter 3: The Requirements Workflow [Arlow & Neustadt, 2005] January 31, 2012.
Chapter 12 Evaluating Products, Processes, and Resources.
Requirements and Specifications Prepared by Stephen M. Thebaut, Ph.D. University of Florida Software Testing and Verification Lecture 3.
Pleasing in appearance.
Safety: Emergency Procedures Diggy & Steven. Procedures -Emergency procedures: The actions to be performed at the time of accident or illness. - immediate.
SWE 513: Software Engineering
Requirements and Specifications Prepared by Stephen M. Thebaut, Ph.D. University of Florida Software Testing and Verification Lecture 3.
Workflows Eighth Edition, WCB/McGraw-Hill, 2011 Stephen R. Schach.
Chapter 2 The Design and Problem-Solving Process.
Algorithms and Problem Solving
G&W Chapter 5: Starting Points Software Specification Lecture 12
Chapter 5 – Requirements Engineering
User-centred system design process
Nursing Process Applied to Community Health Nursing
G&W Chapter 22: Test Cases Software Specification Lecture 29
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
SEVERITY & PRIORITY RELATIONSHIP
Project Points Software Specification Lecture 8
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
SYSTEM ANALYSIS AND DESIGN
Introduction to New Product Development (Specifications)
Lesson Design Study Leading Lesson Study.
Taking Sides By Gary Soto.
Recall The Team Skills Analyzing the Problem (with 5 steps)
Requirements and Specifications
G&W Chapter 12: The Project’s Name Software Specification Lecture 19
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
CS 790M Project preparation (I)
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
PERFORMANCE AND POTENTIAL APPRAISAL
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
Obtain appropriate informed consent
G&W Chapter 24: Making Agreements Software Specification Lecture 31
G&W Chapter 17: Preferences Software Specification Lecture 24
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
Thursday’s Lecture Chemistry Building Musspratt Lecture Theatre,
Thebaut’s Guaranteed Method Software Specification Lecture 5
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
G&W Chapter 19: Ambiguity Metrics Software Specification Lecture 26
Reducing Managed Facility Configuration Information
G&W Chapter 25: Ending Software Specification Lecture 32
G&W Chapter 16: Constraints Software Specification Lecture 23
Designing an Intervention
G&W Chapter 20: Technical Reviews Software Specification Lecture 27
Getting Along with Others
Algorithms and Problem Solving
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
Robertson & Robertson: Chapter 2 Software Specification Lecture 10
Black-Box Testing Techniques II
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
G&W Chapter 11: Software Specification Lecture 18
12 Safe Maintenance Rules
Algebraic Specification Software Specification Lecture 34
G&W Preface Software Specification Lecture 4
G&W Chapter 14: Functions Software Specification Lecture 21
Designing an Intervention
Engineering Approach to Problem Solving
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
Brainstorming Subtopics
Black-Box Testing Techniques II
CS 426 CS 791z Topics on Software Engineering
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
CS 426 CS 791z Topics on Software Engineering
Presentation transcript:

G&W Chapter 15: Attributes Software Specification Lecture 22 Prepared by Stephen M. Thebaut, Ph.D. University of Florida

Software Specification: G&W Chapter 15 What are Attributes? They describe characteristics or qualities desired by the client. Think of them as adjectives or adverbs modifying one or more functions. Two products could have the same functions, but different attributes can make them completely different products. Software Specification: G&W Chapter 15

Attribute Identification Heuristic Have the client brainstorm a list of potential attributes. Sort attributes from attribute details. Fill in the list with attributes for all the details, and with the details suggested by all the attributes. Attribute = (list of attribute details) Associate each attribute with the appropriate function or functions. Attribute A of function F = (list of attribute details) Software Specification: G&W Chapter 15

Attribute Identification Heuristic (cont’d) Classify each attribute as must (M), want (W), or ignore (I). You must struggle to reduce the number of M and W attributes... If you don’t, the cost of design will rise astronomically, which is why designers instinctively and implicitly eliminate hundreds of attributes from consideration. Document the M and W attributes for further processing. Software Specification: G&W Chapter 15

Attributes vs. Attribute Details Attributes are dimensions in which we are interested. Attribute details are points, or sets of points, along that dimension. colorful color brown legal inexpensive low-maintenance Software Specification: G&W Chapter 15

Software Specification: G&W Chapter 15 Other Ideas It’s essential to generate large numbers of attributes “out of the world of fantasy” and without regard to achievability. Only then is explicit elimination safe. Remind participants of the elimination step, which gives them the safety to mention “ridiculous” attributes. Software Specification: G&W Chapter 15

Software Specification: G&W Chapter 15 Other Ideas (cont’d) You must deliberately carry the attribute-generation process to the point where attributes seem to conflict. That’s the way the real design issues emerge. Software Specification: G&W Chapter 15

Software Specification: G&W Chapter 15 Example A client has brainstormed the following “attributes” for “a device to tell time”. Identify actual attributes / attribute details for the appropriate functions. Easy to tell time Weather resistant High-Tech Classic Extremely accurate Fun to use Portable Reliable Software Specification: G&W Chapter 15

G&W Chapter 15: Attributes Software Specification Lecture 22 Prepared by Stephen M. Thebaut, Ph.D. University of Florida