1 / 18

Reengineering an Ada95-programmed Command and Control Information System by Using UML

Reengineering an Ada95-programmed Command and Control Information System by Using UML. Heinz Faßbender Research Establishment for Applied Sciences Research Institute for Communication, Information Processing, and Ergonomics E-Mail Address: fass@fgan.de. Contents.

dunne
Download Presentation

Reengineering an Ada95-programmed Command and Control Information System by Using UML

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Reengineering an Ada95-programmed Command and Control Information System by Using UML Heinz Faßbender Research Establishment for Applied Sciences Research Institute for Communication, Information Processing, and Ergonomics E-Mail Address: fass@fgan.de

  2. Contents • Structure of the existing system • Why UML? • INFIS’ Reengineering Process • High-Level Architecture • Low-Level Architecture • Combination of High-/Low-Level Models • Dynamic Model • Requirements Model • Conclusion

  3. INFIS • experimental integration platform for C2 information systems • test bed for the German part in the context of the ATCCIS (Army Tactical Command and Control Information System) study and MIP (Multilateral Interoperability Programme) • platform independent access

  4. INFIS’ Global Architecture • consists of finitely many domains

  5. Kernel • selfdefined annotation • difficult to understand • no automatic codegeneration

  6. Why UML? • UML = Unified Modeling Language • understood by most of other interesting people • nearly formal meaning • standardized by Object Management Group • automatic Code Generation by CASE-Tools UML

  7. INFIS’ Reengineering Process INFISwithout UML-model UML-models of INFIS‘high-level structures Manually modelling INFIS‘high-level structures Separate UML-models of INFIS‘ high-/low-level structures Automatically reengineering INFIS‘low-level structures with StP/UML Manually combining INFIS‘ high-/ low-level structures Static UML-model of INFIS Manually modelling INFIS‘dynamic behaviour Static and Dynamic UML-model of INFIS

  8. INFIS’ Reengineering Process (2) Extract and model requirements Requirements Model Redesign of System Redesigned Model New requirements Code generation + reimplementation Reengineered System

  9. UML-Model of INFIS’ Global Architecture (High-Level) INFIS 1..* Domain 1..* Data Base Subsystem Handler 0..* 0..* DBS DBSD DBAP Kernel GUI

  10. UML-Model for a Kernel (High-Level)

  11. Inheritance Tree (Low-Level) automatically produced by reengineering component of CASE-Tool Software through Pictures / UML

  12. Detailed UML-Model (Low-Level) automatically produced by reengineering component of CASE Tool Software through Pictures / UML

  13. Combination of UML-Models of High-/Low-Level Structures

  14. Dynamic Model (Sequence Diagram) Data Base Application Session Control User Control GUI Control start application Application start application start application start application name of template name of template get information about template send information about template send information about template send information about template display template display template display template template displayed template displayed template displayed writing permission writing permission writing permission notification input input data input data input data application specific behaviour

  15. Requirements Model • Extract requirements from the models • Model requirements in use case diagrams

  16. How to continue? • Redesign the complete system, such that only the application level has to be extended in further extensions Build your own application server • Use new techniques and buy an application server Java 2 Enterprise Edition

  17. INFIS’ Reengineering Process (2) Extract and model requirements Requirements Model Redesign of System Redesigned Model New requirements Code generation + reimplementation Reimplemented System

  18. Conclusion UML-model of INFIS • documentation of the system, readable by new developers • extraction of requirements • decision for new implementation

More Related