130 likes | 474 Views
UCM -> SUT model. 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.
E N D
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
Goals • Easily readable requirements representation bridges the gap in understanding of project details • Verification of requirements’ consistency
Proposed Approach (general scheme) Specifications Developer Project manager Use case map Checking requirements’ consistency Model based on specifications Customer
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
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 specification 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
UCM Primitives (1) StartPoint {s} tr {s’} {s} R {s’} Responsibility Sequential composition {s} R1;R2 {s’’}
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’}
Concept • Specifications are easily readable; decreasing chance of misunderstanding • Generation of a system’s model (based on UCM representation) • Possible to check specifications’ consistency • Test cases can be easily derived from UCM
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