《ISO-15849-2001.pdf》由会员分享，可在线阅读，更多相关《ISO-15849-2001.pdf（40页珍藏版）》请在三一文库上搜索。
1、INTERNATIONAL STANDARD IS0 15849 First edition 2001 -1 1-01 AMENDMENT 1 2003-09-01 Ships and marine technology - Guidelines for implementation of a fleet management system network AMENDMENT 1 : Annex A Navires et technologie maritime - Lignes directrices pour la mise en ?uvre dun systme de managemen
2、t dune flotte par rseau AMENDEMENT 1: Annexe A Reference number IS0 15849:2001/Amd.l:2003(E) 0 IS0 2003 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/11/2007 20:55:43 MDTNo reproductio
3、n or networking permitted without license from IHS -,-,- IS0 1 5849: 2001/Amd. 1 : 2003( E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are
4、licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The IS0 Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details
5、of the sofiware products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by IS0 member bodies. In the unlikely event that a problem relat
6、ing to it is found, please inform the Central Secretariat at the address given below. O IS02003 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, with
7、out permission in writing from either IS0 at the address below or ISOs member body in the country of the requester. IS0 copyright office Case postale 56 CH-I211 Geneva 20 Tel. + 41 22 749 O 1 11 Fax +41 227490947 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii O IS0 2003 -All rig
8、hts reserved Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/11/2007 20:55:43 MDTNo reproduction or networking permitted without license from IHS -,-,- IS0 1 5849: 2001/Amd. 1 : 2003( E)
9、 Foreword IS0 (the International Organization for Standardization) is a worldwide federation of national standards bodies (IS0 member bodies). The work of preparing International Standards is normally carried out through IS0 technical committees. Each member body interested in a subject for which a
10、technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. IS0 collaborates closely with the International Electrotechnical Commission (i EC) on all matte
11、rs of electrotechnical standardization. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of technical committees is to prepare International Standards. Draft International Standards adopted by the technical committees are circula
12、ted to the member bodies for voting. Publication as an International Standard requires approval by at least 75 % of the member bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. IS0 shall not be held responsibl
13、e for identifying any or all such patent rights. Amendment 1 to IS0 15849:2001 was prepared by Technical Committee ISOTC 8, Ships and marine technology, Subcommittee SC 1 O, Computer applications. O IS0 2003 -All rights reserved iii Copyright International Organization for Standardization Provided b
14、y IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/11/2007 20:55:43 MDTNo reproduction or networking permitted without license from IHS -,-,- IS0 1 5849: 2001/Amd. 1 : 2003( E) Introduction Annex A indicates an example of the specifications for the design
15、of the software of the Application Program Interface (API) when it is applied to the SITP and the LITP, as required by the main text of IS0 15849 (Guidelines for the Fleet Management System Network, FMSN) to secure the effective execution of the mutual connectivity with transparency. iv O IS0 2003 -
16、All rights reserved Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/11/2007 20:55:43 MDTNo reproduction or networking permitted without license from IHS -,-,- IS0 1 5849: 2001/Amd. 1 : 2
17、003( E) Ships and marine technology - Guidelines for implementation of a fleet management system network AMENDMENT 1 : Annex A O IS0 2003 -All rights reserved 1 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545
18、001 Not for Resale, 04/11/2007 20:55:43 MDTNo reproduction or networking permitted without license from IHS -,-,- IS0 1 5849: 2001/Amd. 1 : 2003( E) Annex A (inform ative) Example of specifications for the design of the software of the Application Program Interface (API) when it is applied to the SI
19、TP and LITP A.l Scope The scope of this Annex is the software design guide for the purpose of applying the API for the functions of the SITP and the LITP that are specified in the main text of IS0 15849. In this Annex, the concept is based on the use of CORBA (A.2.3) as the specification of a distri
20、buted object for a model. A.2 Terms and definitions For the purposes of this Annex, the following terms and definitions apply. A.2.1 acquire data list operation of acquiring the data list from the database, on the specified server A.2.2 acquire ship information polling operation from the specified s
21、erver A.2.3 CORBA Common Object Request Broker Architecture standard of distributed object model as defined by the Object Management Group A.2.4 database server station which became independent of the LITP-installed system and the SITP-installed system, when a database is arranged on this station A.
22、2.5 IDL Interface Definition Language language to define interface in each operation NOTE CORBAs primary tool to insulate language. A.2.6 IDL skeleton when CORBA is used and the client and server communicate, a program (as a part of API) on the server side to provide an application program to start
23、the operation directly 2 O IS0 2003 -All rights reserved Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/11/2007 20:55:43 MDTNo reproduction or networking permitted without license from
24、IHS -,-,- IS0 1 5849: 2001/Amd. 1 : 2003( E) A.2.7 IDL stub when CORBA is used and the client and server communicate, the client program that accesses the operation on the server side provided with the corresponding pseudo-object (as a part of API) on the client side A.2.8 naming service common refe
25、rence service provided by CORBA NOTE the network. The naming service responds to the inquiry from the object, relating the name of the object to its location in A.2.9 naming service interface program, which executes the API request from the user application, in the series of processes when a naming
26、service is used A.2.10 OMG Object Management Group international standardization group which prescribes technology for the infrastructure which is necessary for the development of the application in the environment of the dispersion of object oriented architecture and independent of the hardware A.2
27、.11 ORB Object Request Broker software which provides the tasks of communication between stub and skeleton A.2.12 read data operation of reading one particular datum from the database, on the specified server A.2.13 user application program, which is established by the user of the FMSN in accordance
28、 with the requirement by the LITP-installed system to realize the functionality on the FMSN NOTE The functionality on the FMSN serves to acquire the operational management information andlor the ship management information. A.2.14 user-application interface interface in the API opened between the AP
29、I and user application NOTE information) as described in the A.4.1.2 to A.4.3.2. This also defines four kinds of operation (Read data, Write data, Acquire data list and Acquire ship A.2.15 write data operation of writing one particular datum to the database, on the specified server A.3 Objectives Se
30、e 7.2 “Overview of APIS” in the main text. For design of the software of the API, the following objectives should be considered: a) make the system platform transparent to the programming language and development environment of the application; O IS0 2003 -All rights reserved 3 Copyright Internation
31、al Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/11/2007 20:55:43 MDTNo reproduction or networking permitted without license from IHS -,-,- IS0 1 5849: 2001/Amd. 1 : 2003( E) I I b) provide links to external
32、operating system; c) provide links to external networks; d) provide transparency to distributed objects; e) provide an easy interface between the user application and the API; f) provide a data structure of the information that is used for the communication between an application and the API, using
33、a common method of data exchange. i API (client program) User application interface m I Acquit!eship information I I Naming service I/F I . I A.4 Software configuration A.4.1 LITP I I A.4.1.1 Illustration The LITP software configuration is schematically shown in Figure A.1, surrounded by a dotted li
34、ne. IDLstub Naming service I/F m IAcquire ship information I I User application i LITP ORB -.-.-.-.-.-.-.-.-.-.-.-.-.-.- I.-.-.-.-.-.-.-.-.-.-.-.-.-.- Figure A.l - Example of construction of software of the LITP-installed system A.4.1.2 API software block - User application interface A requirement f
35、rom the user application invokes the operation. - Readdata Invokes a program for accesses for the read data operation in the IDL stub block. - Write data Invokes a program for accesses for the write data operation in the IDL stub block. 4 O IS0 2003 -All rights reserved Copyright International Organ
36、ization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/11/2007 20:55:43 MDTNo reproduction or networking permitted without license from IHS -,-,- IS0 1 5849: 2001/Amd. 1 : 2003( E) - Acquire data list Invokes a program for
37、 accesses for the acquire data list operation in the IDL stub block. - Acquire ship information Invokes a program for accesses for the acquire ship information operation in the IDL stub block. - Naming service interface Naming service provided by ORB is invoked and Object reference of the server is
38、assigned. A.4.1.3 IDL stub block - Readdata It requests the invocation of an operation program for the read data on the server (SITP-installed system) to the ORB. - Write data It requests the invocation of an operation program for the write data on the server (SITP-installed system) to the ORB. - Ac
39、quire data list It requests the invocation of an operation program for the acquire data list on the server (SITP-installed system) to the ORB. - Acquire ship information It requests the invocation of an operation program for the acquire ship information on the server (SITP-installed system) to the O
40、RB. A.4.1.4 Naming service It acquires the Object reference for the server (SITP-installed system or on the network of ones station). A.4.2 SITP A.4.2.1 Illustration The SITP software configuration is schematically shown in Figure A.2. O IS0 2003 -All rights reserved 5 Copyright International Organi
41、zation for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/11/2007 20:55:43 MDTNo reproduction or networking permitted without license from IHS -,-,- IS0 1 5849: 2001/Amd. 1 : 2003( E) SITP API (server program) (client program)
42、 l .-.-.-.-.-.-.-.-.-.-.-.-.-. I I I I I I Acquire ship information I I Write data I I Acquire ship information I I Naming service I/F I i l I I! I I I I I IDL skeleton I IDLstub I I Acquire ship information I I I I l. ORB l i os Figure A.2 - Example of construction of software of the SITP-installed
43、 system A.4.2.2 API server program block Read data The read data operation requests, which are received from the client of the LITP-installed system, are then transmitted to a client program. Write data The write data operation requests, which are received from the client of the LITP-installed syste
44、m, are then transmitted to a client program. Acquire data list The acquire data list operation requests, which are received from the client of the LITP-installed system, are then transmitted to a client program. Acquire ship information The acquire ship information operation requests, which are rece
45、ived from the client of the LITP-installed system, are then transmitted to a client program. A.4.2.3 API client program block - User application interface A requirement from the user application is transmitted to the server, and invokes the operation. - Readdata Invokes a program for accesses for th
46、e read data operation in the IDL stub block. 6 O IS0 2003 -All rights reserved Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/11/2007 20:55:43 MDTNo reproduction or networking permitted
47、 without license from IHS -,-,- IS0 1 5849: 2001/Amd. 1 : 2003( E) Write data Invokes a program for accesses for the write data operation in the IDL stub block. Acquire data list Invokes a program for accesses for the acquire data list operation in the IDL stub block. Acquire ship information Invoke
48、s a program for accesses for the acquire ship information operation in the IDL stub block. Naming service interface Invokes a Naming service operation, provided by ORB, and acquires the Object reference for the server. IDL skeleton Requirements of each operation, which are issued from the client program of the LITP-installed system, are transmitted to the API server program. A.4.2.4 IDL stub block - Readdata It requests the invocation