Making Metrics Practical - INCOSE

One simple example is the way we specify requirements

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: rs to specify the relationship of anything (requirement, design, plan) to any other part of a total specification, and outside environment. One simple example, is the way we specify requirements with ‘[Qualifiers]’ – which are a list of conditions that must all be true for the specification to be effective or ‘true’: Goal [Deadline = Release 9.0, Market = {China, HR Departments}, Condition = Merger with China Hotline OK, User = HR Employee, Tasks = Critical Tasks] 60% Another Planguage tactic for specifying relationships are specification parameters such as: • Authority • Source • Owner • Author • Implementer • Impacts • Supports • Supported By • Version • Derived From • Sub-component of • Sub-components {list} • Dependencies • Contract • Test Case • Scenario • Model • And more! • And ‘Qualifiers, like • Goal [UK, Teens, 2009] 35% Figure 4: Specification options in Planguage to help us understand relationships. 6. If you fail to quantify a critical variable, it will fail to be what you need. Developers will naturally prioritize quantified target requirements that they believe they will be judged on delivering And they will prioritize delivering to quantified constraints (deadline, budget) So we need to have a notion of being ‘complete’ for the quantified critical requirements: We cannot have some quantified and others equally important in un-quantified formats like “Very User-Friendly”, “Highly Secure...
View Full Document

Ask a homework question - tutors are online