2014:requirements_engineering
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| 2014:requirements_engineering [2013/11/14 19:26] – created jonjagger | 2014:requirements_engineering [2016/06/11 14:05] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 6: | Line 6: | ||
| **Duration**: | **Duration**: | ||
| **Description**: | **Description**: | ||
| - | We will teach the following practical tools:\\ | + | • Requirements Engineering: The use of a quantified |
| - | 1. The discipline | + | Planning Language to articulate all quality, and other |
| - | idea’ on any quantified | + | performance variable, requirements - as a basis for |
| - | by a Scale of measure, and a Goal or Tolerable level of | + | Architecture Engineering and Quantified Agile Project |
| - | requirement)\\ | + | Management (Evo)\\ |
| \\ | \\ | ||
| - | 2. The corresponding discipline | + | 1. Overview of a semi formal Planning language (Planguage) |
| - | in several dimensions | + | for articulation of variable requirements and system |
| - | time, and human resources\\ | + | objectives. In particular performance and quality objectives.\\ |
| + | 2. Components | ||
| + | a. Core: Tag, Scale, Past, Tolerable, Goal\\ | ||
| + | i.Advanced supplements to the core\\ | ||
| + | b. Background: non core info about the requirement, | ||
| + | as: Sponsor, Owner, Dependencies, | ||
| + | Issues, Risks, Proposed Designs, and many more\\ | ||
| + | 3. Examples of constructing a specification\\ | ||
| + | 4. How to articulate and tailor a Scale of Measure (for any | ||
| + | quality or critical variable requirement)\\ | ||
| + | 5. Basic Quantified quality control of requirements: | ||
| + | Spec QC method. The use of Rules to measure against. The | ||
| + | use of Entry Exit level standards.\\ | ||
| \\ | \\ | ||
| - | 3. The use of the Impact Estimation Table discipline, for | ||
| - | articulating the quality of estimates: ± uncertainty, | ||
| - | or Budget, Source, Evidence, Credibilty, Safety Factor\\ | ||
| \\ | \\ | ||
| - | 4. Process and Specification standards: Procedures, Rules, | + | Location: Oslo, Norway |
| - | Templates, Principles, for Architecture Engineering. Derived | + | |
| - | from the Competitive Engineering book (digital copy supplied | + | JJ: Tom says this Tutorial can be condensed (with loss of detail and time to discuss and absorb, but with gain of seeing the connection between requirements and design, into a half day tutorial, immediately followed by his other preconference submission, Architecture Engineering, also as a half-day.\\ |
| - | free).\\ | + | |
| \\ | \\ | ||
| - | 5. Case studies of use of the Architecture Engineering method\\ | ||
| - | \\ | ||
| - | 6. Application of Dynamic Design Prioritization\\ | ||
| - | \\ | ||
| - | 7. Project Management consequences of this basis for articulating the Architecture.\\ | ||
| - | \\ | ||
| - | \\ | ||
| - | \\ | ||
| - | |||
2014/requirements_engineering.1384457188.txt.gz · Last modified: 2016/06/11 14:05 (external edit)