GESSISoftware Engineering for Information Systems Group

A Catalogue of Software Requirement Patterns for

the Domain of CMSs

RE TRACK @ SAC’13 – 22/03/2013Requirements Engineering Track at

28th Symposium on Applied Computing

Cristina Palomares (GESSI - UPC)Carme Quer (GESSI - UPC)Xavier Franch (GESSI - UPC)Samuel Renault (SSI - TUDOR)Cindy Guerlain (SSI - TUDOR)

ContextA Catalogue of Functional

SRP

for the CMS

Domain

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.

•Software Requirements Patterns (SRP).•Withall, 2007 ‘‘a requirement pattern is a guide to writing a particular type of requirement’’.

2

Strategy

PABRE FrameworkA Catalogue of Functional

SRP

for the CMS

Domain

33

Which domain or type of system do you want to acquire?

A Content Management System.

Req

uire

men

tA

naly

st

Custom

er

PABRE Catalogue

29 Non-Functional SRP

37 Non-Technical SRP

PABRE System

PABRE Method

RequirementSpecifications

NEXT STEP: Functional SRP

SR

P &

Cat

alo

gu

e M

etam

od

el

Catalogue Construction ProcessA Catalogue of Functional

SRP

for the CMS

Domain

Requirements Filtering

Requirements Alignment

Requirements Analysis

SRP Formulation

Catalogue Construction

SRSs

FunctionalRequirements

SRP Cantidates

SRPs

SRP Catalogue

4

Functional Aspects

Terms and Metrics

Glossary

Functional SRP Catalogue for CMSA Catalogue of Functional

SRP

for the CMS

Domain

• 45 F-SRP obtained• Classified in a CMS Classification Schema

ISO

/IEC

91

26-1

ba

se

d

CMS Specific Subcharacteristics

F- SRPClassification in ISO

5

SRP Example (I): Content Version Management

A Catalogue of Functional

SRP

for the CMS

Domain

• 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

A Catalogue of Functional

SRP

for the CMS

Domain

SRP Example (II): Content Version Management

7

AnalysisA Catalogue of Functional

SRP

for the CMS

Domain

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:

• CMS Functionality not represented in the base classification schema (e.g. Agenda Management)

• CMS Functionality operationalizess some NF aspect (e.g. Text Input)

3. 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

ConclusionsA Catalogue of Functional

SRP

for the CMS

Domain

• 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

Future WorkA Catalogue of Functional

SRP

for the CMS

Domain

• Validate the constructed F-SRP with different SRS.

• Validate SRP benefits.

• Facilitate the patterns usability and understan- dability 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

GESSISoftware Engineering for Information Systems Group

A Catalogue of Software Requirement Patterns for

the Domain of CMSs

RE TRACK @ SAC’13 – 22/03/2013Requirements Engineering Track at

28th Symposium on Applied Computing

Cristina Palomares (GESSI - UPC)Carme Quer (GESSI - UPC)Xavier Franch (GESSI - UPC)Samuel Renault (SSI - TUDOR)Cindy Guerlain (SSI - TUDOR)