70 likes | 82 Views
Learn about Open Distributed Processing (ODP), a framework for systems with open service interfaces on objects, distribution of objects, data, and management. Explore the concept of ODP and its assessment against the RM-ODP, as well as the importance of language support for transparency in ODP. Discover ITU-T languages for ODP and their suitability and usage in different environments. Benefit from the methodology of using RM-ODP as a general framework for tool-supported design methodology.
E N D
ITU languages for ODP- a personal view - I may be wrong! Rick Reed TSE Limited
ITU-T languages 2003 • URN (GRL,UCM) - draft • MSC • ASN.1 (XML) • SDL • TTCN • eODL
What is Open Distributed Processing? A name for systems that have • Open service interfaces on objects • Distribution of objects, data and management X.90x.. is a Framework Reference Model • An ODP system can (but need not be) assessed against RM-ODP • Conformance to RM-ODP does not ensure openness
Viewpoints • Enterprise, Information, Computation, Engineering, Technology • RM-ODP set not unique or definitive • Viewpoint needs a language • Overlaps require consistency • Traceable concepts & semantics • Development through viewpoints • Are viewpoints part of ODP? • If yes, must they be the RM-ODP ones?
Transparency • Hiding distribution from the “user” • Access - differences in interface • Failure - difference in mode • (re)Location/Migration • Replication - number of server objects • Transaction - co-ordination of activities • Should conform to RM-ODP if used • Language support for Transparency?
ITU-T languages for ODP • Are they suitable? • Are they used? • If not, why not? What is? • Do they match RM-ODP viewpoints? • Attributes: • Remote, Concurrent, Diverse Environments, Mobile, Multiple Copies, Asynchronous, Indirect, Separate, Relative, Partial Failure, Late Dynamic Binding ...
Methodology RM-ODP has been used as a general framework for tool supported design methodology. It provides object-oriented concepts and principles for structuring the system design. The design process is not a pure top-down approach, but is an iterative usage of each of the stages from an abstract level down to the detailed specification and implementation. Repetition of steps is needed if errors are detected either by validation on the design plane or by testing the implementation.