| |
Step |
Input |
Techniques |
Participants |
Output |
| 1 |
Agree on definitions |
Candidate definitions from IEEE and other standards |
Structured interviews, focus group |
Stakeholders, requirements team |
Agreed-to definitions |
| 2 |
Identify assets and security goals |
Definitions, candidate goals, business drivers, policies and procedures, examples |
Facilitated work session, surveys, interviews |
Stakeholders, requirements engineer |
Assets and goals |
| 3 |
Develop artifacts to supprt security requirements definition |
Potential artifacts (e.g., scenarios, misuse cases, templates, forms) |
Work session |
Requirements engineer |
Needed artifacts: scenarios, misuse cases, models, templates, forms |
| 4 |
Perform risk assessment |
Misuse cases, scenarios, security goals |
Risk assessment method, analysis of anticipated risk against organizational risk tolerance, including threat analysis |
Requirements engineer, risk expert, stakeholders |
Risk assessment results |
| 5 |
Select elicitation techniques |
Goals, definitions, candidate techniques, expertise of stakeholders, organizational style, culture, level of security needed, cost benefit analysis, etc. |
Work session |
Requirements engineer |
Selected elicicitation techniques |
| 6 |
Elicit security requirements |
Artifacts, risk assessment results, selected techniques |
Joint Application Development (JAD), interviews, surveys, model-based analysis, checklists, lists of reusable requirements types, document reviews |
Stakeholders facilitated by requirements engineer |
Initial cut at security requirements |
| 7 |
Categorize requirements as to level (system, software, etc.) and whether they are requirements or other kinds of constraints |
Initial requirements, architecture |
Work session using a standard set of categories |
Requirements engineer, other specialists as needed |
Categorized requirements |
| 8 |
Prioritize requirements |
Categorized requirements and risk assessment results |
Prioritization methods such as Triage, Win-Win |
Stakeholders facilitated by requirements engineer |
Prioritized requirements |
| 9 |
Inspect requirements |
Prioritized requirements, candidate formal inspection technique |
Inspection methods such as Fagan, peer reviews |
Inspection team |
Initial selected requirements, documentation of decision-making process and rationale |