METHOD ENGINEERING
Process Deliverable
Diagram
Requirements reuse for improving information
systems security : A practitioner’s approach
Kourosh VIVAN (F122028) –Group 3
08/03/2013
PDD
Activity table
Activity
Require
ments
selection
Sub-activity
Definition
Choose a
Domain
Choose
profiles
Elicitation of
specific
requirements
Select all the requirements belonging to the current application field.
(Toval, 2002)
Select all the requirements from various homogeneous set of
requirements that are relevant to the current project. (Toval, 2002)
Create requirements specific to this project and related test protocol.
(Toval, 2002)
Set
requirement
parameters
Some requirements from reuse repository need to be instantiate.
(Toval, 2002)
Merge
requirements
Merge requirements from the three sources (domain requirement,
profile requirement, informal requirement), correct redundancy and
incompatibly between requirements. (Toval, 2002)
Classify requirement according to IEEE 1233 standard.(IEEE 1233, 1996)
Analysis
and
negotiati
on
Documen
tation
Classify
requirements
Validatio
n
Write
validation
review
Review
requirement
validation
Reposito
ry
improve
ment
Stakeholders and analyst write a validation review. (Toval, 2002)
Review requirement validation, the result of this step is validated
requirements documents ready for analysis, design and implementation
of project. (Toval, 2002)
Improve reused repository with new requirements. (Toval, 2002)
Concept table
Concept
REQUIREMENT
REUSED
REPOSITORY
DOMAIN
REUSED
REQUIREMENT
PROFILE REUSED
REQUIREMENT
REUSED TESTING
CRITERIA
INFORMAL
REQUIREMENT
TESTING
CRITERIA
REQUIREMENT
PARAMETER
REQUIREMENT
SPECIFICATION
TEST
SPECIFICATION
REQUIREMENTS
DOCUMENTS
REQUIREMENT
VALIDATION
REVIEW
NEW
REQUIREMENT
Description
A general type of requirement with identification, priority, criticality, viability,
risk, and source(IEEE 1233, 1996)
The repository contains requirements from specific domains and profiles and
related testing criteria. Requirements can be parameterized or nonparameterized. (Toval, 2002)
All requirements in reused repository from one specific domain. (Toval, 2002)
All requirements in reused repository from one specific profile. (Toval, 2002)
Testing criteria from reused repository. (Toval, 2002)
Requirement specific to this project (not in the reused repository) (Toval, 2002)
Testing criteria for a requirement. (Toval, 2002)
Requirement parameter for parameterized requirement, their values is specific
to a project. (Toval, 2002)
Contains all requirement specification for parameterized requirement, divided
by software, system and interface requirement. (Toval, 2002)
Contains all testing specification, divided in system test specification (SyTS) and
software test specification (STS). (Toval, 2002)
All documents for specification and testing. (Toval, 2002)
Validation review for requirement documents; (Toval, 2002)
New requirement extracted from current specification, it will be used to
improve reused repository. (Toval, 2002)
References
Toval A., Nicolas J., Moros B., Garcia F. (2002). Requirements Reuse for Improving Information
Systems Security: A Practitioner’s Approach
Institute of Electrical and Electronics Engineers (1998). IEEE Standard 1233-1998. Guide for
developing system requirements specifications. IEEE Software Engineering Standards Collection.