SWE 3633 Lecture 9: L9 Software Architecture and Design

30 views2 pages

For unlimited access to Class Notes, a Class+ subscription is required.

Software Architecture and Design
Lecture 9
Improving Candidate Requirements
Identify stakeholder need statements relevant to a candidate requirement.
Use the idea sources and techniques (modeling, brainstorming).
Specification Notations
Natural Language
o Easy to understand
o Prone to ambiguity and vagueness
Semi-formal notations
o More precise than natural language but not defined with mathematical rigor (most
UML diagrams).
o More precise than natural language.
Formal notations
o Mathematical and logical notations
o Very precise
o Hard to understand.
Stating requirements
Follow the rules of good technical writing.
Write complete, simple sentences in the active voice.
Define terms clearly and use them consistently.
Use must or shall
Write verifiable requirements.
There is a definitive procedure to determine whether the requirement is satisfied.
Product Design Principles
Adequacy design that meet stakeholder need, subject to constraints, are better.
Beauty beautiful design is better.
Economy design that can be built for less money, in less time, with less risk, are better.
Feasibility design is acceptable only if it can be realized.
Simplicity simpler designs are better.
Requirements Evaluation Techniques:
With respect to design principles (heuristic evaluation).
By collecting data from stakeholders (empirical evaluation).
find more resources at oneclass.com
find more resources at oneclass.com
Unlock document

This preview shows half of the first page of the document.
Unlock all 2 pages and 3 million more documents.

Already have an account? Log in

Get access

Grade+
$10 USD/m
Billed $120 USD annually
Homework Help
Class Notes
Textbook Notes
40 Verified Answers
Study Guides
1 Booster Class
Class+
$8 USD/m
Billed $96 USD annually
Homework Help
Class Notes
Textbook Notes
30 Verified Answers
Study Guides
1 Booster Class