Nr: 1 FGAN Research Institute for Communication, Information Processing, and Ergonomics KIE Reengineering an Ada95-programmed Command and Control Information.

Slides:



Advertisements
Similar presentations
ARCH-05 Application Prophecy UML 101 Peter Varhol Principal Product Manager.
Advertisements

Visualization Kenny Inthirath.  Reviewing a Suitable Technique to Use  Scope and Purpose  What types of models can be represented?  Architectural.
Chapter 7 – Object-Oriented Design
Job No/ 1 © British Crown Copyright 2008/MOD Developing a High Integrity Code Generator Using iUML/iCCG Sam Moody AWE plc, Aldermaston, Berkshire, United.
Unified Modeling Language
An Integrated Approach to Enterprise Architecture LIACS, Martijn Wiering 23 juni ‘04.
Introduction To System Analysis and Design
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
Revision Session 1.UML Overview 2.Detailed software design : operation specification, designing for re-use.
1 UML – an overview What is UML? UML stands for Unified Modelling Language. ”The Unified Modelling Language is a visual language for specifying, constructing.
Satzinger, Jackson, and Burd Object-Orieneted Analysis & Design
UML and the Software Lifecycle
CS 290C: Formal Models for Web Software Lecture 6: Model Driven Development for Web Software with WebML Instructor: Tevfik Bultan.
Automatic Data Ramon Lawrence University of Manitoba
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Chapter 1 The Systems Development Environment
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
1.Database plan 2.Information systems plan 3.Technology plan 4.Business strategy plan 5.Enterprise analysis Which of the following serves as a road map.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 18 Slide 1 Software Reuse.
Software Engineering Muhammad Fahad Khan
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 14Slide 1 Design with Reuse l Building software from reusable components.
FALL 2005CSI 4118 – UNIVERSITY OF OTTAWA1 Part 4 Web technologies: HTTP, CGI, PHP,Java applets)
Technical Overview.
Liang, Introduction to Java Programming, Sixth Edition, (c) 2007 Pearson Education, Inc. All rights reserved Chapter 12 Object-Oriented.
1 The Architectural Design of FRUIT: A Family of Retargetable User Interface Tools Yi Liu, H. Conrad Cunningham and Hui Xiong Computer & Information Science.
CS 160: Software Engineering October 8 Class Meeting
Assessing the Suitability of UML for Modeling Software Architectures Nenad Medvidovic Computer Science Department University of Southern California Los.
Lecture 3: Visual Modeling & UML 1. 2 Copyright © 1997 by Rational Software Corporation Computer System Business Process Order Item Ship via “ Modeling.
Requirements Engineering Requirements Elicitation Process Lecture-8.
Introduction To System Analysis and Design
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
Object Management Group (OMG) Specifies open standards for every aspect of distributed computing Multiplatform Model Driven Architecture (MDA)
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 4, Requirements Elicitation.
WSMX Execution Semantics Executable Software Specification Eyal Oren DERI
University of Southern California Center for Systems and Software Engineering Model-Based Software Engineering Supannika Koolmanojwong Spring 2013.
FGAN Research Institute for Communication, Information Processing and Ergonomics KIE Dep. Ergonomics and Informations Systems 1 Visualisation of Heterogeneous.
Model Driven Development An introduction. Overview Using Models Using Models in Software Feasibility of MDA MDA Technologies The Unified Modeling Language.
Systems Analysis and Design in a Changing World, 3rd Edition
Programming Logic and Design Fourth Edition, Comprehensive Chapter 15 System Modeling with the UML.
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
Copyright © 2013 Curt Hill UML Unified Modeling Language.
FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.
SWT - Diagrammatics Lecture 4/4 - Diagramming in OO Software Development - partB 4-May-2000.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 18 Slide 1 Software Reuse.
Design and Implementation of a Rationale-Based Analysis Tool (RAT) Diploma thesis from Timo Wolf Design and Realization of a Tool for Linking Source Code.
CIM LAB MEETING Presentation on UML Rakesh Mopidevi Kwangyeol Ryu.
Source Mastering UML with Rational Rose 2002 Information System Engineering Introduction to UML.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
Week 04 Object Oriented Analysis and Designing. What is a model? A model is quicker and easier to build A model can be used in simulations, to learn more.
SOEN 343 Software Design Section H Fall 2006 Dr Greg Butler
August 2003 At A Glance The IRC is a platform independent, extensible, and adaptive framework that provides robust, interactive, and distributed control.
March 19th 2007 TANGO collaboration 1 POGO-7 Pascal Verdier ESRF- Hamburg - 25 th of October 2010 A Short History of Pogo A Short History of Pogo New Technology.
Chapter 5 System Modeling. What is System modeling? System modeling is the process of developing abstract models of a system, with each model presenting.
® IBM Software Group © 2009 IBM Corporation Essentials of Modeling with the IBM Rational Software Architect, V7.5 Module 15: Traceability and Static Analysis.
UML (Unified Modeling Language)
Source Mastering UML with Rational Rose 2002 Information System Engineering Introduction to UML.
UML Course Instructor: Rizwana Noor. Overview  Modeling  What is UML?  Why UML?  UML Diagrams  Use Case  Components  Relationships  Notations.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Technical Overview. What Is MagicDraw?  Business Analysts  Software Analysts  Programmers  QA Engineers  Documentation Writers MagicDraw is a powerful.
1 SYS366 Week 2 - Lecture 2 Visual Modeling & UML.
Aspect-oriented Code Generation Approaches Abid Mehmood & Dayang N. A. Jawawi Department of Software Engineering Faculty of Computer Science and Information.
1 College Automation Software Arifa Tehseen Ara(509) Farzana Begum(512) Syeda Fatima(513) Firdous Sameena(514) Tahmina Jabeen(556)
Chapter 5 – System Modeling Lecture 1 1Chapter 5 System modeling.
1 Design Object Oriented Solutions Object Oriented Analysis & Design Lecturer: Mr. Mohammed Elhajj
Software Reuse. Objectives l To explain the benefits of software reuse and some reuse problems l To discuss several different ways to implement software.
Towards Effective Adaptive User Interfaces Design
Software Design Lecture : 14.
Presentation transcript:

Nr: 1 FGAN Research Institute for Communication, Information Processing, and Ergonomics KIE 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 Address:

Nr: 2 FGAN Research Institute for Communication, Information Processing, and Ergonomics KIE 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

Nr: 3 FGAN Research Institute for Communication, Information Processing, and Ergonomics KIE 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

Nr: 4 FGAN Research Institute for Communication, Information Processing, and Ergonomics KIE INFIS’ Global Architecture consists of finitely many domains

Nr: 5 FGAN Research Institute for Communication, Information Processing, and Ergonomics KIE Kernel selfdefined annotation difficult to understand no automatic codegeneration

Nr: 6 FGAN Research Institute for Communication, Information Processing, and Ergonomics KIE 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

Nr: 7 FGAN Research Institute for Communication, Information Processing, and Ergonomics KIE INFIS’ Reengineering Process INFIS without UML-model Automatically reengineering INFIS‘ low-level structures with StP/UML Separate UML-models of INFIS‘ high-/low-level structures Manually combining INFIS‘ high-/ low-level structures Static UML-model of INFIS Manually modelling INFIS‘ dynamic behaviour Static and Dynamic UML-model of INFIS UML-models of INFIS‘ high-level structures Manually modelling INFIS‘ high-level structures

Nr: 8 FGAN Research Institute for Communication, Information Processing, and Ergonomics KIE INFIS’ Reengineering Process (2) Extract and model requirements Requirements Model Redesign of System Redesigned Model Code generation + reimplementation Reengineered System New requirements

Nr: 9 FGAN Research Institute for Communication, Information Processing, and Ergonomics KIE UML-Model of INFIS’ Global Architecture (High-Level) INFIS Domain Data Base Handler Subsystem Kernel DBSDBSD DBAP GUI 1..* 0..*

Nr: 10 FGAN Research Institute for Communication, Information Processing, and Ergonomics KIE UML-Model for a Kernel (High-Level)

Nr: 11 FGAN Research Institute for Communication, Information Processing, and Ergonomics KIE Inheritance Tree (Low-Level) automatically produced by reengineering component of CASE-Tool Software through Pictures / UML

Nr: 12 FGAN Research Institute for Communication, Information Processing, and Ergonomics KIE Detailed UML-Model (Low-Level) automatically produced by reengineering component of CASE Tool Software through Pictures / UML

Nr: 13 FGAN Research Institute for Communication, Information Processing, and Ergonomics KIE Combination of UML-Models of High-/Low-Level Structures

Nr: 14 FGAN Research Institute for Communication, Information Processing, and Ergonomics KIE Dynamic Model (Sequence Diagram) Application Control Application Session Control Data Base Control GUI User writing permission name of template get information about template send information about template display template template displayed writing permission template displayed notification input input data start application name of template start application input data application specific behaviour writing permission

Nr: 15 FGAN Research Institute for Communication, Information Processing, and Ergonomics KIE Requirements Model Extract requirements from the models Model requirements in use case diagrams

Nr: 16 FGAN Research Institute for Communication, Information Processing, and Ergonomics KIE 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

Nr: 17 FGAN Research Institute for Communication, Information Processing, and Ergonomics KIE INFIS’ Reengineering Process (2) Extract and model requirements Requirements Model Redesign of System Redesigned Model Code generation + reimplementation Reimplemented System New requirements

Nr: 18 FGAN Research Institute for Communication, Information Processing, and Ergonomics KIE Conclusion UML-model of INFIS documentation of the system, readable by new developers extraction of requirements decision for new implementation