1 Scope
2 References
3 Definitions
3.1 Terms defined elsewhere
3.2 Terms defined in this Recommendation
4 Abbreviations
5 Conventions
6 Requirements for methodology and notational support
7 Methodology
7.1 General considerations
7.2 Application and structure of the methodology
7.3 Detailed methodology
8 Management interface specifications
9 Traceability in MISM process
10 Documentation structure
Annex A – Requirements
A.1 Conventions
A.2 Requirements template
A.3 Simplified requirements template
Annex B – Analysis
B.1 Conventions
B.2 Analysis template
B.3 IOC properties and inheritance
Annex C – MISM UML repertoire
C.1 Introduction
C.2 Basic model elements
C.3 Stereotypes
C.4 Association classes
C.5 Abstract class
C.6 Application of <<InformationObjectClass>> and
<SupportIOC>>
Annex D – Design
Annex E – Information type definitions – type repertoire
E.1 Basic types
E.2 Enumerated type
E.3 Complex types
E.4 Useful types
E.5 Keywords
Annex F – Guidelines on IOC properties, inheritance and entity import
F.1 IOC property
F.2 Inheritance
F.3 Entity (interface, IOC and attribute) import
Appendix I – Requirements example
Appendix II – Analysis example
Appendix III – Comparison with Recommendation ITU-T Z.601
Appendix IV – Issues for further study
IV.1 SOA
IV.2 UML
IV.3 Visibility
IV.4 Type definitions
Appendix V – Additional UML usage samples
V.1 Proxy class
Appendix VI – Guidelines on requirements numbering
Bibliography