UCM -> SUT model

1
UCM -gt SUT model
2
Team

• Alexey Veselov
• St.Petersburg State Polytechnic University
• Alexander Ivanov
• St.Petersburg State Polytechnic University
• Igor Nikiforov
• St.Petersburg State Polytechnic University
• Alexey Zakharov
• St.Petersburg State Polytechnic University
• Mentor Sir Tony Hoare

3
Introduction Motivation
4
Goals

• Easily readable requirements representation
  bridges the gap in understanding of project
  details
• Verification of requirements consistency

5
Proposed Approach (general scheme)
Specifications
Project manager
Developer
Use case map
Checking requirements consistency
Model based on specifications
Customer
6
Use Case Maps (UCM)

• Standardized notation for use cases
• ITU-T, Recommendation Z.151 (11/08) User
  Requirements Notation (URN) - Language Definition
  (Draft version)
• ITU-T, Recommendation Z.150 (02/03) User
  Requirements Notation (URN) - Language
  Requirements and Framework

7
Related Work

• Early Availability Requirements Modeling Using
  UseCase Maps. Hassine, Jameleddine. Information
  Technology New Generations (ITNG), 2011 Eighth
  International Conference on Digital Object
  Identifier
• Use Case Maps as a property speci?cation
  language. Jameleddine Hassine Juergen Rilling.
  Rachida Dssouli. Softw Syst Model (2009)
• Generation of test purposes from Use Case Maps.
  Daniel Amyot, Luigi Logrippo, Michael Weiss.
  Computer Networks 49 (2005)
• UCMExporter Supporting Scenario Transformations
  from Use Case Maps. Daniel Amyot, Ali Echihabi,
  Yong He. Nouvelles TEchnnologies de la
  R'Epartition (NOTERE'04), Sa"idia, Morocco
• Enhanced use case map traversal semantics. Jason
  Kealey, Daniel Amyot. SDL'07 Proceedings of the
  13th international SDL Forum conference on Design
  for dependable systems

8
UCM Primitives (1)
StartPoint
s tr s
s R s
Responsibility
Sequential composition
s R1R2 s
9
UCM Primitives (2)
OrFork
s /\ cond1 tr1 s1 \/ \/ s /\ condN trN
sN
OrFork is alternative (i.e. only one path is
selected at a time)
s stub s
Stub
stub - encapsulated behavior
EndPoint
s tr s
10
Concept

• Specifications are easily readable decreasing
  chance of misunderstanding
• Generation of a systems model (based on UCM
  representation)
• Possible to check specifications consistency
• Test cases can be easily derived from UCM

11
Current State and Future Plans

• Currently there is a concept only
• Next steps
• integration of existent model checking tool
• generation of test cases
• testing against realistic examples
• introduction of concurrency

12
Thank youQA?