Model-Based Systems Engineering with GENESYS

Attributes of a “Good” Requirement

We want requirements that at least meet some basic criteria to be acceptable.

There are many paradigms for requirement statements. Perhaps the easiest of these is having a “SMART” Requirement:

S – Specific – specify a singular, unique aspect of the intended system M – Measurable – quantify one “thing” in the requirement statement A – Assignable – we can assign an organization to meet the requirement R – Realistic – state requirements that can be realistically be met or achieved T – Time-Related – we can achieve the requirement within the time frame of the project

There are many lists of characteristics for good requirements. One good source for further study is the INCOSE Systems Engineering Handbook, 4 th

Edition, Section 4.3.2.2 which elaborates an extensive list of “Characteristics and Attributes of Good Requirements.”

119

Break-up Composite Requirements Composite Requirements need to be broken down into “single” requirement statements Goal is to: ▪ Break up Originating Requirements without changing the meaning ▪ Maintain Traceability to Originating Requirement and Originating Document Steps to create new child requirements from composite parent requirements: 1. Create New Requirement 2. Copy Parent Requirement Description attribute

3. Paste and then Edit Description in New Child Requirement 4. Relate Parent to Child using “ refined by / refines” relation 5. Provide traceability by setting Origin type

120