JUAN PABLO ALBALADEJO MÁRQUEZ JAVIER PONCELA GONZÁLEZ

1. Adaptation of SOMT to the development of systems based upon a standard JUAN PABLO ALBALADEJO MÁRQUEZ JAVIER PONCELA GONZÁLEZ

2. Adaptation of SOMT to the development of systems based upon a standard Introduction DECT network layer SOMT methodology Requirements analysis System analysis System design Object design Conclusions Introduction

3. Introduction • Need for fast and reliable development processes • Maintenance of quality levels • More capable methods • Formal languages • Object orientation SDL’92 Introduction

4. Objective Adaptation of SOMT to the development of systems based upon a standard Method Election of an object-oriented methodology Use of the tool Tau 3.2 by Telelogic Modelling of the network level of a DECT system (Digital Enhanced Cordless Telecommunication) Introduction

5. Adaptation of SOMT to the development of systems based upon a standard Introduction DECT network layer SOMT methodology Requirements analysis System analysis System design Object design Conclusions

6. DECT network level DLC: Data Link Control MAC: Medium Access Control LLME: Lower Layer Management Entity CC: Call Control MM: Mobility Management LCE: Link Control Entity Introduction

7. Adaptation of SOMT to the development of systems based upon a standard Introduction DECT network layer SOMT methodology Requirements analysis System analysis System design Object design Conclusions

8. SOMT methodology Requirements Capability to be used with formal languages Adaptation to the object-oriented focus Progressive evolution towards the final result Traceability among the elaborated models Integration with the chosen tool SOMT methodology

9. SOMT (SDL-oriented Object Modeling Technique) SOMT methodology

10. Adaptation of SOMT to the development of systems based upon a standard Introduction DECT network layer SOMT methodology Requirements analysis System analysis System design Object design Conclusions

11. Requirements analysis Modified SOMT activities SOMT activities Textual requirements model Requirements use case model Requirements object model System operation model Data dictionary Incorporation of the standard Data dictionary Requirements analysis

12. DECT standard Study of the architecture Particularization for GAP (Generic Access Profile) Data dictionary • Nouns section Mobility Management (MM) - Entity in charge of managing the identities, authentication, localization, access rights, key assignment and ciphering. • Actions section Identification of PT - Procedure used by FT to ask PT for its identification using specific parameters such as IPUI o IPEI. (MM Procedure) • Relations section: implicitly elaborated Requirements analysis

13. Adaptation of SOMT to the development of systems based upon a standard Introduction DECT network layer SOMT methodology Requirements analysis System analysis System design Object design Conclusions

14. System analysis Modified SOMT activities SOMT activities Analysis use case model Analysis use case model Analysis object model Textual documentation Analysis object model Textual documentation System analysis

15. Analysis use case model (1) • Dynamic viewpoint of the standard • Messages exchange • Timer handling • State changing • Different levels of hierarchy • HMSCs • Use cases • Behaviour patterns System analysis

16. Analysis use case model (2) Increased formality compared to the standard Connection through implinks of each diagram with its definition in the data dictionary System analysis

17. Textual documentation • Original purpose: to complete the description of the system • Modified purpose: explain the informalities in the use case model • Treated aspects: • Handling of timers in subdiagrams • Actions associated to the expiry of timers • Reuse of diagrams System analysis

18. Object model (1) • Static viewpoint of the standard • Elaboration • Cooperating objects: association and composition relations • Similar objects: inheritance relations System analysis

19. Object model (2) • Elaboration: • Contained information: attributes • Performed actions: operations • Connection through implinks of each class with its definition in the data dictionary System analysis

20. Adaptation of SOMT to the development of systems based upon a standard Introduction DECT network layer SOMT methodology Requirements analysis System analysis System design Object design Conclusions

21. System design Modified SOMT activities SOMT activities Design uses case model Design module structure Architecture definition Textual requirements Object model Design uses case model Architecture definition System design

22. Object model (1) Advance in the study of the standard Introduction of Card class Modification of existing relations Connection through implinks with the analysis object model classes System design

23. Object model (2) Incorporation of attributes Adition of operatios related to the new classes System design

24. Design module structure Detailed study of the standard Considerations concerning the implementation Connection through implinks with the design object model classes System design

25. Architecture definition Translation of the former model contents to SDL’92 Taking into account of the object model Structural and functional modules System design

26. F_NWK system Blocks modelling the composition relations Incompatibility of blocks and processes Adyacent levels modelled as the environment System design

27. Nwk block Analogue structure to the one defined in the standard Adyacent levels modelled as the environment System design

28. Adaptation of SOMT to the development of systems based upon a standard Introduction DECT network layer SOMT methodology Requirements analysis System analysis System design Object design Conclusions

29. Object design Modified SOMT activities SOMT activities Object design model (SDL) • Object design model (SDL) • Interfaces • Behaviour Object design

30. Interfaces definition • Signal lists SIGNALLIST SAP0_NWK = DL_DATA_IND, DL_ESTABLISH_CFM, DL_ESTABLISH_ IND, DL_RELEASE_CFM, DL_RELEASE_IND; • Messages and primitives /* ETS 300 175-5 [5], subsclause 16.3.6.1 */ /* */ newtype ASP_MM_IDENTITY_REQ struct mm_endpoint_identifier ENDPOINT_IDENTIFIER /* */;/* */ identity_type IDENTITY_TYPE /* */ ; /* */ iwu_to_iwu IWU_TO_IWU /* */ ; /* */ endnewtype ASP_MM_IDENTITY_REQ; • Information elements /* ETSI 300 175-5 [5], subclause 7.7.19 */ /* */ newtype IDENTITY_TYPE struct iei OCT_1 /* */ ; /* */ length OCT_1 /* */ ; /* */ id_group BIT_4 /* */ ; /* */ space BIT_3 /* */ ; /* '000' */ f3 BIT_1 /* */ ; /* '1' */ type_mio BIT_7 /* */ ; /* */ f4 BIT_1 /* */ ; /* '1' */ endnewtype IDENTITY_TYPE; Object design

31. Behaviour definition First step Second step Connection through implinks of the behaviours withs their definitions in the data dictionary Object design

32. Adaptation of SOMT to the development of systems based upon a standard Introduction DECT network layer SOMT methodology Requirements analysis System analysis System design Object design Conclusions

33. Conclusions • Common advantages to SOMT and M-SOMT • Object-orientation and use of formal languages • Progressive evolution towards the final result • Connection of the elaborated models • Improvements of M-SOMT • Improved use of the previous models in the elaboration of the next ones Conclusions

34. M- SOMT methodology SOMT methodology Conclusions

35. Adaptation of SOMT to the development of systems based upon a standard JUAN PABLO ALBALADEJO MÁRQUEZ JAVIER PONCELA GONZÁLEZ