375:, one for each viewpoint language and one to express the correspondences between viewpoints, and an approach for structuring them according to the RM-ODP principles. The purpose of "UML4ODP" to allow ODP modelers to use the UML notation for expressing their ODP specifications in a standard graphical way; to allow UML modelers to use the RM-ODP concepts and mechanisms to structure their large UML system specifications according to a mature and standard proposal; and to allow UML tools to be used to process viewpoint specifications, thus facilitating the software design process and the
284:
items in each are identified as related to items in the other viewpoints. Moreover, each viewpoint substantially uses the same foundational concepts (defined in Part 2 of RM-ODP). However, the viewpoints are sufficiently independent to simplify reasoning about the complete specification. The mutual consistency among the viewpoints is ensured by the architecture defined by RM-ODP, and the use of a common object model provides the glue that binds them all together.
250:
questions of a system make-up than would a system implementer. The concept of RM-ODP viewpoints framework, therefore, is to provide separate viewpoints into the specification of a given complex system. These viewpoints each satisfy an audience with interest in a particular set of aspects of the system. Associated with each viewpoint is a viewpoint language that optimizes the vocabulary and presentation for the audience of that viewpoint.
356:" model, or the RM-ODP. These approaches were consciously defined in a notation- and representation-neutral manner to increase their use and flexibility. However, this makes more difficult, among other things, the development of industrial tools for modeling the viewpoint specifications, the formal analysis of the specifications produced, and the possible derivation of implementations from the system specifications.
20:
249:
Most complex system specifications are so extensive that no single individual can fully comprehend all aspects of the specifications. Furthermore, we all have different interests in a given system and different reasons for examining the system's specifications. A business executive will ask different
343:
Although the ODP reference model provides abstract languages for the relevant concepts, it does not prescribe particular notations to be used in the individual viewpoints. The viewpoint languages defined in the reference model are abstract languages in the sense that they define what concepts should
236:
Architecture: Contains the specification of the required characteristics that qualify distributed processing as open. These are the constraints to which ODP standards must conform. This recommendation also defines RM-ODP viewpoints, subdivisions of the specification of a whole system, established to
283:
is a subdivision of the specification of a complete system, established to bring together those particular pieces of information relevant to some particular area of concern during the analysis or design of the system. Although separately specified, the viewpoints are not completely independent; key
232:
Foundations: Contains the definition of the concepts and analytical framework for normalized description of (arbitrary) distributed processing systems. It introduces the principles of conformance to ODP standards and the way in which they are applied. In only 18 pages, this standard sets the basics
228:
Overview: Contains a motivational overview of ODP, giving scoping, justification and explanation of key concepts, and an outline of the ODP architecture. It contains explanatory material on how the RM-ODP is to be interpreted and applied by its users, who may include standard writers and architects
569:
of Parts 2 and 3 of the RM-ODP, together with an index to the
Reference Model, made available in keeping with a resolution of the ISO council. The Table of Contents and Index were prepared by Lovelace Computing and are being made available by Lovelace Computing as a service to the standards
699:
O'Moore, R.R.; De Moor, G.; Boran, G.; Gaffney, P.; Grimson, J.; McNair, P.; Groth, T.; Nykänen, P.; Hasman, A.; Eller, J.; Yearworth, M. (1994). "OpenLabs: the application of advanced informatics and telematics for optimization of clinical laboratory services".
359:
In order to address these issues, ISO/IEC and the ITU-T started a joint project in 2004: "ITU-T Rec. X.906|ISO/IEC 19793: Information technology - Open distributed processing - Use of UML for ODP system specifications". This document (usually referred to as
316:, which focuses on the mechanisms and functions required to support distributed interactions between objects in the system. It describes the distribution of processing performed by the system to manage the information and provide the functionality.
497:
In the same series as the RM-ODP are a number of other standards and recommendations for the specification and development of open and distributed system, for which RM-ODP provides a standardization framework:
309:, which enables distribution through functional decomposition on the system into objects which interact at interfaces. It describes the functionality provided by the system and its functional decomposition.
302:, which focuses on the semantics of the information and the information processing performed. It describes the information managed by the system and the structure and content type of the supporting data.
787:
Kilov, H., Linington, P.F., Romero, J.R., Tanaka, A., Vallecillo, A.: The reference model of open distributed processing: foundations, experience and applications. Comput. Stand. Interfaces 35, 247–256
344:
be used, not how they should be represented. This lack of precise notations for expressing the different models involved in a multi-viewpoint specification of a system is a common feature for most
240:
Architectural
Semantics: Contains a formalization of the ODP modeling concepts by interpreting many concepts in terms of the constructs of the different standardized formal description techniques.
120:. Many RM-ODP concepts, possibly under different names, have been around for a long time and have been rigorously described and explained in exact philosophy (for example, in the works of
340:
for system specification, hampers communication between system developers and makes it difficult to relate or merge system specifications where there is a need to integrate IT systems.
735:
Grimson, William; Brender, Jytte; Grimson, Jane; Groth, Torgny; Hermanson, Bo; Yearworth, Michael; Wade, Vincent (1996). "Specifying an open clinical laboratory information system".
199:(now MD of Microsoft Research in Cambridge), and involved a number of major computing and telecommunication companies. Parts 2 and 3 of the RM-ODP were eventually adopted as
183:
processing systems and provides a well-developed enterprise architecture framework for structuring the specifications for any large-scale systems including software systems.
444:
323:, which focuses on the choice of technology of the system. It describes the technologies chosen to provide the processing, functionality and presentation of information.
256:
has become an effective approach for dealing with the inherent complexity of large distributed systems. Current software architectural practices, as described in
336:
for system modelling. However, there is no widely agreed approach to the structuring of such specifications. This adds to the cost of adopting the use of
368:
2 (UML 2; ISO/IEC 19505), for expressing the specifications of open distributed systems in terms of the viewpoint specifications defined by the RM-ODP.
484:
A complete and updated list of references to publications related to RM-ODP (books, journal articles, conference papers, etc.) is available at the
89:
162:
176:
The RM-ODP family of recommendations and international standards defines a system of interrelated essential concepts necessary to specify
872:
862:
409:
The ENVRI and ENVRIplus projects for common operations of environmental research infrastructures are developing the ENVRI Reference Model
402:
In addition, there are several projects that have used or currently use RM-ODP for effectively structuring their systems specifications:
260:, divide the design activity into several areas of concerns, each one focusing on a specific aspect of the system. Examples include the
93:
587:. They include the UML Profiles of the five ODP viewpoints, the viewpoint metamodels, the GIF files for the ODP-specific icons, etc.
882:
549:
192:
425:
A 239-item reference list covering RM-ODP standards as well as related research, applications and case studies was included in.
629:
618:
607:
596:
295:, which focuses on the purpose, scope and policies for the system. It describes the business requirements and how to meet them.
287:
More specifically, the RM-ODP framework provides five generic and complementary viewpoints on the system and its environment:
439:
643:
846:
112:
based on precise concepts derived from current distributed processing developments and, as far as possible, on the use of
152:
434:
383:
345:
70:
772:
580:
412:
The
Reference Architecture for Space Data Systems (RASDS) From the Consultative Committee for Space Data Systems.
877:
391:
191:
Much of the preparatory work that led into the adoption of RM-ODP as an ISO standard was carried out by the
683:
770:
The
Synapses Project: a three-year project funded under the EU 4th Framework Health Telematics Programme
867:
455:
387:
365:
337:
333:
504:
ITU-T Rec. X.952 | ISO/IEC 13235-3:1998, Provision of
Trading Function using OSI directory service.
237:
bring together those particular pieces of information relevant to some particular area of concern.
376:
177:
117:
47:
887:
382:
In addition, ITU-T Rec. X.906 | ISO/IEC 19793 enables the seamless integration of the RM-ODP
221:
158:
the specification of a system in terms of separate but interrelated viewpoint specifications;
27:, which provides five generic and complementary viewpoints on the system and its environment.
529:
ISO/IEC 19500-2:2003, General Inter-ORB Protocol (GIOP)/Internet Inter-ORB Protocol (IIOP).
62:
8:
834:
180:
169:
54:
50:
217:
840:
510:
ITU-T Rec. X.931 | ISO/IEC 14752:2000, Protocol support for computational interactions.
465:
361:
253:
828:
752:
748:
717:
713:
349:
265:
744:
709:
125:
58:
43:
415:
Interoperability
Technology Association for Information Processing (INTAP), Japan.
776:
687:
647:
523:
450:
280:
141:
129:
109:
39:
640:
196:
113:
669:
856:
372:
74:
200:
756:
721:
681:
Interoperability
Technology Association for Information Processing (INTAP)
485:
581:| ITU-T X.906 | ISO/IEC 19793 "Use of UML for ODP systems specifications"
501:
ITU-T Rec. X.950 | ISO/IEC 13235-1:1998, Trading function: Specification.
133:
121:
831:(Formalisation of ODP Systems Architecture), University of Stirling, UK.
769:
513:
ITU-T Rec. X.930 | ISO/IEC 14753:1999, Interface references and binding.
811:
460:
24:
814:, Swiss Federal Institute of Technology, Lausanne (EPFL), Switzerland.
195:(ANSA) project. This ran from 1984 until 1998 under the leadership of
46:, which provides a co-ordinating framework for the standardization of
552:. All ODP-related ITU-T Recommendations, including X.9xx series, are
540:
Copies of the RM-ODP family of standards can be obtained either from
507:
ITU-T Rec. X.920 | ISO/IEC 14750:1999, Interface
Definition Language.
418:
The
European Advanced Informatics in Medicine (AIM) OpenLabs project.
257:
140:—have recently been provided with a solid mathematical foundation in
137:
553:
19:
801:
66:
843:, Networks and ComputerScience Department of ENST, Paris France.
516:
ITU-T Rec. X.960 | ISO/IEC 14769:2001, Type repository function.
680:
244:
806:
698:
566:
273:
269:
97:
445:
Enterprise
Modelling Methodology/Open Distributed Processing
822:
353:
261:
734:
817:
584:
519:
ITU-T Rec. X.910 | ISO/IEC 14771:1999, Naming framework.
233:
of the whole model in a clear, precise and concise way.
545:
670:
Reference Architecture for Space Data Systems (RASDS)
658:
548:. Parts 1 to 4 of the RM-ODP are available for from
541:
161:
the definition of a system infrastructure providing
332:Currently there is growing interest in the use of
579:Some resources related to the current version of
854:
90:International Organization for Standardization
32:Reference Model of Open Distributed Processing
807:Open Distributed Processing - Reference Model
203:in 1996. Parts 1 and 4 were adopted in 1998.
737:Computer Methods and Programs in Biomedicine
702:Computer Methods and Programs in Biomedicine
245:Viewpoints modeling and the RM-ODP framework
379:specification of large software systems.
94:International Electrotechnical Commission
98:Telecommunication Standardization Sector
18:
522:ITU-T Rec. X.911 | ISO/IEC 15414:2002,
471:
193:Advanced Networked Systems Architecture
855:
390:initiative from the OMG, and with the
147:RM-ODP has four fundamental elements:
847:Distributed Systems Technology Center
524:Reference model - Enterprise language
440:Enterprise Collaboration Architecture
825:, University of Kent, Canterbury UK.
835:Distributed and Cooperative Systems
818:Official Record of the ANSA project
346:enterprise architectural approaches
211:
16:Reference model in computer science
13:
873:Enterprise architecture frameworks
863:Distributed computing architecture
630:ISO/IEC 10746-4 | ITU-T Rec. X.904
619:ISO/IEC 10746-3 | ITU-T Rec. X.903
608:ISO/IEC 10746-2 | ITU-T Rec. X.902
597:ISO/IEC 10746-1 | ITU-T Rec. X.901
132:). Some of these concepts—such as
14:
899:
795:
435:Enterprise Architecture framework
384:enterprise architecture framework
327:
71:enterprise architecture framework
65:and technology independence, and
206:
781:
763:
728:
692:
674:
663:
652:
634:
554:freely available from the ITU-T
397:
388:Model-Driven Architecture (MDA)
222:ISO/IEC International Standards
883:ITU-T X Series Recommendations
623:
612:
601:
590:
573:
559:
534:
491:
478:
421:The Synapses European project.
216:RM-ODP consists of four basic
128:(for example, in the works of
53:processing (ODP). It supports
1:
583:are also available from the
392:service-oriented architecture
114:formal description techniques
749:10.1016/0169-2607(96)01739-R
714:10.1016/0169-2607(94)90034-5
565:There is also a very useful
165:for system applications; and
7:
428:
163:distribution transparencies
103:
88:, is a joint effort by the
10:
904:
812:RM-ODP information at LAMS
186:
168:a framework for assessing
456:Triune Continuum Paradigm
366:Unified Modeling Language
153:object modelling approach
116:for specification of the
276:and, of course, RM-ODP.
155:to system specification;
377:enterprise architecture
307:computational viewpoint
837:, UMPC, Paris, France.
550:free download from ISO
82:ITU-T Rec. X.901-X.904
28:
878:ITU-T recommendations
659:ENVRI Reference Model
364:) defines use of the
314:engineering viewpoint
300:information viewpoint
218:ITU-T Recommendations
22:
823:Computing Laboratory
802:RM-ODP Resource site
585:RM-ODP resource site
486:RM-ODP resource site
472:Notes and references
371:It defines a set of
321:technology viewpoint
293:enterprise viewpoint
567:hyperlinked version
406:The COMBINE project
136:, composition, and
80:RM-ODP, also named
69:, together with an
775:2005-04-06 at the
686:2008-03-11 at the
646:2008-05-15 at the
466:ISO/IEC JTC 1/SC 7
254:Viewpoint modeling
170:system conformance
29:
350:Zachman Framework
266:Zachman Framework
77:of ODP systems.
895:
868:Reference models
789:
785:
779:
767:
761:
760:
732:
726:
725:
708:(1–2): 137–140.
696:
690:
678:
672:
667:
661:
656:
650:
638:
632:
627:
621:
616:
610:
605:
599:
594:
588:
577:
571:
563:
557:
538:
532:
495:
489:
482:
348:, including the
262:"4+1" view model
212:RM-ODP standards
126:systems thinking
108:The RM-ODP is a
44:computer science
903:
902:
898:
897:
896:
894:
893:
892:
853:
852:
798:
793:
792:
786:
782:
777:Wayback Machine
768:
764:
733:
729:
697:
693:
688:Wayback Machine
679:
675:
668:
664:
657:
653:
648:Wayback Machine
639:
635:
628:
624:
617:
613:
606:
602:
595:
591:
578:
574:
564:
560:
539:
535:
496:
492:
483:
479:
474:
451:Reference model
431:
400:
330:
247:
229:of ODP systems.
214:
209:
189:
142:category theory
130:Friedrich Hayek
110:reference model
106:
40:reference model
17:
12:
11:
5:
901:
891:
890:
885:
880:
875:
870:
865:
851:
850:
844:
838:
832:
826:
820:
815:
809:
804:
797:
796:External links
794:
791:
790:
780:
762:
727:
691:
673:
662:
651:
633:
622:
611:
600:
589:
572:
558:
533:
531:
530:
527:
520:
517:
514:
511:
508:
505:
502:
490:
476:
475:
473:
470:
469:
468:
463:
458:
453:
448:
442:
437:
430:
427:
423:
422:
419:
416:
413:
410:
407:
399:
396:
329:
328:RM-ODP and UML
326:
325:
324:
317:
310:
303:
296:
246:
243:
242:
241:
238:
234:
230:
213:
210:
208:
205:
197:Andrew Herbert
188:
185:
174:
173:
166:
159:
156:
105:
102:
96:(IEC) and the
15:
9:
6:
4:
3:
2:
900:
889:
888:ISO standards
886:
884:
881:
879:
876:
874:
871:
869:
866:
864:
861:
860:
858:
848:
845:
842:
839:
836:
833:
830:
827:
824:
821:
819:
816:
813:
810:
808:
805:
803:
800:
799:
784:
778:
774:
771:
766:
758:
754:
750:
746:
743:(2): 95–109.
742:
738:
731:
723:
719:
715:
711:
707:
703:
695:
689:
685:
682:
677:
671:
666:
660:
655:
649:
645:
642:
637:
631:
626:
620:
615:
609:
604:
598:
593:
586:
582:
576:
568:
562:
555:
551:
547:
543:
537:
528:
525:
521:
518:
515:
512:
509:
506:
503:
500:
499:
494:
487:
481:
477:
467:
464:
462:
459:
457:
454:
452:
449:
446:
443:
441:
438:
436:
433:
432:
426:
420:
417:
414:
411:
408:
405:
404:
403:
395:
393:
389:
385:
380:
378:
374:
369:
367:
363:
357:
355:
351:
347:
341:
339:
335:
322:
318:
315:
311:
308:
304:
301:
297:
294:
290:
289:
288:
285:
282:
277:
275:
271:
267:
263:
259:
255:
251:
239:
235:
231:
227:
226:
225:
223:
219:
207:RM-ODP topics
204:
202:
201:ISO standards
198:
194:
184:
182:
179:
171:
167:
164:
160:
157:
154:
150:
149:
148:
145:
143:
139:
135:
131:
127:
123:
119:
115:
111:
101:
99:
95:
91:
87:
86:ISO/IEC 10746
83:
78:
76:
75:specification
72:
68:
64:
60:
56:
52:
49:
45:
41:
37:
33:
26:
21:
849:, Australia.
783:
765:
740:
736:
730:
705:
701:
694:
676:
665:
654:
636:
625:
614:
603:
592:
575:
561:
536:
493:
480:
424:
401:
398:Applications
381:
373:UML Profiles
370:
358:
342:
331:
320:
313:
306:
299:
292:
286:
278:
252:
248:
215:
190:
175:
146:
118:architecture
107:
85:
81:
79:
59:interworking
55:distribution
35:
31:
30:
181:distributed
134:abstraction
122:Mario Bunge
92:(ISO), the
67:portability
51:distributed
23:The RM-ODP
857:Categories
570:community.
461:View model
25:view model
447:(EMM/ODP)
386:with the
281:viewpoint
258:IEEE 1471
138:emergence
124:) and in
100:(ITU-T).
773:Archived
684:Archived
644:Archived
544:or from
429:See also
104:Overview
73:for the
63:platform
829:FORMOSA
757:8875017
722:7889746
641:COMBINE
394:(SOA).
362:UML4ODP
352:, the "
187:History
38:) is a
788:(2013)
755:
720:
264:, the
36:RM-ODP
546:ITU-T
274:DoDAF
270:TOGAF
753:PMID
718:PMID
319:The
312:The
305:The
298:The
291:The
220:and
178:open
84:and
48:open
841:ILR
745:doi
710:doi
542:ISO
354:4+1
338:UML
334:UML
151:an
42:in
859::
751:.
741:50
739:.
716:.
706:45
704:.
279:A
272:,
268:,
224::
144:.
61:,
57:,
759:.
747::
724:.
712::
556:.
526:.
488:.
172:.
34:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
