Applying Service Oriented Architecture in the Aerospace Industry

More documents

Recommendations

Info

After successful verification process final development steps and implementation can follow (figure1, step 5).Normally newly implemented systems have to under go extensive testing. Up to know testing wasdone manually and a number of standard and exceptional situations had to be simulated againstwhich the application was tested later on. Simulation of test situations and testing itself requiresadditional time and man power. In our case implemented protocols are exposed to permanentautomatic validation under real environment conditions with the help of Specifications usingXQuery expressions on Traces (SXQT) [15]. SXQT specification technique allows detecting nonconformancesin the occurring message sequences, when compared against protocol specification.The flow of real message exchange is used for the validation purposes to see whether the protocolswork the way that was intended. The permanent validation is not limited to a number of simulatedsituations, the system is validated with each exception appearing, it does not require involvement ofdevelopers, excludes mistakes related to the human factor, informs developers whenever somedeviations appear and in such a way supports developers in creation of conformingimplementations. Validation using SXQT can be implemented for early prototypes, for finalimplementations or in real world working environments.The proposed model with the verification following every stage contributes to creation of properlyworking flexible and extensible systems, while reusing current implementations. This approachenables exclusion of systems errors at the earliest stages possible and allows saving time and costsdue to reduced number of man hours required for test situation simulation and maintenance of thesystem.5. Case StudyFor the purpose of internal and cross enterprise process analysis and to depict the interactionbetween an OEM and SMEs, the business processes between Airbus (OEM) and Innovint AircraftInterior GmbH (SME) have been analyzed.The data was collected by one of the authors that stayed at Innovint AG for one month on full timebasis. The information concerning engineering business process (milestones, development process,Airbus requirements for equipment and system suppliers, product structure) was obtained, the studyof existing documents related to various orders was made and employees involved in execution ofdifferent process steps were interviewed.It was discovered that companies need to comply with certain steps and time spans for variousmilestones while designing and developing products for Airbus. They are precisely described inGRESS provided by the OEM. Telephones and faxes are still used very extensively for exchanging8
data and information in aerospace industry. EDI will be required for cooperation with OEM in thenear future. On the other end, Innovint is using Harmony system [17] for Customer RelationshipManagement (CRM).Complex interaction processes for different products were modelled after the requirementscapturing phase. Production of the Innovint can be divided into two big groups: standard productsand project products. The project products are single units developed and produced on specialrequest. The workflow of the project products extends the standard product ordering process. Latervalidation of the developed models followed. The graphical business process representations werepresented to and discussed with the owners of different process steps. After several revisions andmodel improvement cycles graphical representations were approved by the employees of thecompany.Further on the approved diagrams were used to derive the relevant parameters of communication,data and information flows in a distributed business environment, as well as to identify thebottlenecks and get early alerts for application specific exception handling [8]. The outcomes of theresearch were documented in a form of Software Requirements Specification (SRS). SRS alsodescribes requirements for the integration of the CRM software installed in the company with thestate-of-the-art collaboration platform e.g. [12-14]. This solution will provide an insight to theproject status at the Innovint for their customers and suppliers and will be used for recording ofworking patterns. The customers will be able to check their order status, see whether there are anydelays and prove the availability of standard products of their interest. An insight to the projectorderstatus will allow to better plan and coordinate cooperative design and development projectsamong the companies involved.Prototyping implementing all identified distributed functions using the standard and proven WSprotocolshas been chosen to avoid leaving out any significant information that was not wellcommunicated in the requirements capturing phase. It will also help the users and designers of thefuture system to better understand and comment on the features and will allow us finalizingcooperation parameters. “Prevention of defects begins with better ways to capture, represent, andvalidate the objectives and requirements of systems we are trying to build...”[2]Up to now the project members had to face the problem of making implicit knowledge of processowners explicit by depicting it in a graphical form. This moment is critical, since it allows later onmore efficient integration of the relevant knowledge into the system developed. The difficultiesarose because people in the company did not think about their work in terms of process and dataflows and the engineering sub processes vary significantly depending on the type of the product.9
Page 1: Applying Service Oriented Architect
Page 4 and 5: ForewordInternational students cont
Page 7: this objective the current inflexib
Page 11 and 12: We believe that our proposed soluti

Applying Service Oriented Architecture in the Aerospace Industry

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?