Presentation of the paper A Catalogue of Software Requirement Patterns for the Domain of CMSs in SAC 2013. Authors: Cristina Palomares, Carme Quer, Xavier Franch, Samuel Renault, Cindy Guerlain. http://sac2013.ecomp.poli.br/index.htm

1. A Catalogue of Software
Requirement Patterns for
the Domain of CMSs
Cristina Palomares (GESSI - UPC)
Carme Quer (GESSI - UPC)
Xavier Franch (GESSI - UPC)
Samuel Renault (SSI - TUDOR)
Software Engineering for Information Systems Group (SSI - TUDOR)
Cindy Guerlain
GESSI

2. A Catalogue of Functional SRP for the CMS Domain
Context
SSI department Centre de Recherche Publique Henri Tudor (TUDOR)
• Helping SME with no experience in Requirements Engineering.
• Designing requirement books to conduct Call-For-Tender processes for
selecting Off-The-Shelf solutions.
1. The system must be available 22 hours
per day and 7 days per week.
2. Should be possible to use the system in English
or French.
3. The system should not stop more than 1
hour per working day. The solution’s
availability rate should be 98% minimum.
4. The solution should permit to trace all the user
actions. The data to trace are: user name, date,
accessed or modified data.
• More than 40 projects done.
• Applied reuse: starting a new project by editing the most similar one.
• Better capitalization of requirements in a high-level manner.
• Avoiding ambiguous, incomplete or incoherent requirements.
Strategy
• Software Requirements Patterns (SRP).
• Withall, 2007 ‘‘a requirement pattern is a guide to writing a particular type
of requirement’’.
2

3. Which domain or type
of system do you want
to acquire?
NEXT STEP:
Functional SRP
SRP & Catalogue
Metamodel
Requirement
Analyst
PABRE
System
PABRE
Catalogue
PABRE
Method
A Content
Management
System.
Customer
A Catalogue of Functional SRP for the CMS Domain
PABRE Framework
Requirement
Specifications
29 Non-Functional SRP
37 Non-Technical SRP
3

4. A Catalogue of Functional SRP for the CMS Domain
Catalogue Construction Process
SRP
Catalogue
SRPs
SRP
Cantidates
Functional
Aspects
Functional
Requirements
SRP
Formulation
Requirements
Analysis
Catalogue
Construction
Requirements
Alignment
SRSs
Requirements
Filtering
Terms and
Metrics
Glossary
4

5. • 45 F-SRP obtained
• Classified in a CMS Classification Schema
Classification
in ISO
CMS Specific
Subcharacteristics
F- SRP
ISO/IEC 9126-1 based
A Catalogue of Functional SRP for the CMS Domain
Functional SRP Catalogue for CMS
5

6. A Catalogue of Functional SRP for the CMS Domain
SRP Example (I): Content Version Management
• General aspects:
• Problem: Allowing the customer having a content version management.
• Solutions: SRP following the PABRE metamodel.
• Forces: It is necessary to distinguish among the version management
needed for different content types or not.
• Related Patterns: Content Management, History Features.
• Others: Name, Authors, Known Uses, RE Activity, Organizational
Environment Factors, Application, Classification, etc.
6

7. A Catalogue of Functional SRP for the CMS Domain
SRP Example (II): Content Version Management
7

8. A Catalogue of Functional SRP for the CMS Domain
Analysis
1.
SRS coverage: How many of the F-reqs that appear in the 6 SRS
used to construct the catalogue can be obtained as application of
the F-SRP?
 87% F-reqs can be produced (average of 183 F-reqs per SRS)
2.
Classification schema coverage: How many of the classifiers in the
classification schema have F-SRP bound?
 3 of 10 subcharacteristics (Users, Roles, Groups) not present F-SRP.
•
Requirements related to them were classified as NF-SRP
 5 extra subcharacteristics added because:
•
•
3.
CMS Functionality not represented in the base classification schema
(e.g. Agenda Management)
CMS Functionality operationalizess some NF aspect (e.g. Text Input)
Generality: How many of the F-SRP can be applied to other
software domains?
 15% for any software domain (e.g. Automatic storage, Spell checker)
8

9. A Catalogue of Functional SRP for the CMS Domain
Conclusions
• 45 F-SRP for CMS domain incorporated in the PABRE
framework.
• SRP organized according to a previous existent
functionality classification for CMS domain.
• Catalogue analysis:




F-SRP catalogue covering most functionalities for CMS
Better SRS documents
Organized SRS documents
F-reqs are specific to a domain
• SRP benefits:
 More effective requirements elicitation
 Improved quality and consistency of requirements documents
 Improved requirements management
9

10. A Catalogue of Functional SRP for the CMS Domain
Future Work
• Validate the constructed F-SRP with different SRS.
• Validate SRP benefits.
• Facilitate the patterns usability and understandability from a requirement analyst point of
view.
• Construct F-SRP for different domains.
• Integrate F-,NF- and NT-SRP catalogues into a
single one and validate it in real elicitation
processes.
10

11. A Catalogue of Software
Requirement Patterns for
the Domain of CMSs
Cristina Palomares (GESSI - UPC)
Carme Quer (GESSI - UPC)
Xavier Franch (GESSI - UPC)
Samuel Renault (SSI - TUDOR)
Software Engineering for Information Systems Group (SSI - TUDOR)
Cindy Guerlain
GESSI