1 Context
2 Definitions
3 The advantage of using SDL+
3.1 Understanding an SDL+ specification
3.2 The application area of SDL+
3.3 Relation to implementation
PART I – THE FRAMEWORK METHODOLOGY
4 Overview of activities and an outline of the methodology
4.1 The Requirements Collection part of requirements capture
4.2 Analysis, Draft Design and Formalization
4.3 Validation and Testing
4.4 Documentation
4.5 Parallelism of activities
5 Analysis activity
5.1 Starting Analysis
5.2 Questions during Analysis
5.3 Modelling approach for Analysis
5.4 Analysis steps
5.5 Conclusion of Analysis
6 Draft Design
6.1 Starting Draft Design
6.2 Draft Design steps
6.3 Conclusion of Draft Design
7 Formalization
7.1 Starting Formalization
7.2 Formalization steps
7.3 Conclusion of Formalization
8 Implementation
9 Validation
9.1 Characteristics of a validation model
9.2 Comparison of the validation model with the formalized model
9.3 Issues in defining the validation of a specification
10 Relationship with other methodologies and models
10.1 Relationship with Recommendations I.130/Q.65 (3-stage method)
1988
10.2 Relationship with OSI layered modelling
10.3 Relationship with ITU-T Q.1200-series (IN) architecture and
SIBs
10.4 Relationship with remote operations (RO and ROSE) in [b‑ITU‑T X.219]
11 Justification of approach
PART II – AN ELABORATION OF THE FRAMEWORK METHODOLOGY
12 Elaboration of the methodology for service specification
12.1 Three-stage methodology: Stage 2 (Recommendation ITU-T Q.65)
13 Analysis steps
13.1 Inspection step
13.2 Classification step for object modelling
13.3 Classification step for use sequence modelling
14 Draft Design steps
14.1 Component relationship modelling
14.2 Data and control flow modelling
14.3 Information structure modelling
14.4 Use sequence modelling
14.5 Process behaviour modelling
14.6 Overview modelling
15 Formalization steps
15.1 Structure steps (S-steps)
15.2 Behaviour steps (B-steps)
15.3 Data steps (D-steps)
15.4 Type steps (T-steps)
15.5 Localization steps (L-steps)
Bibliography