FH Augsburg - FB Informatik 1 CADUI'96 - 5-7 June 1996 - FUNDP Namur Software Life Cycle Automation for Interactive Applications: The AME Design Environment.

Slides:



Advertisements
Similar presentations
K. Ingram1November 2000 Object Orientated Analysis and Design - Contents When to use OO? What is OO? Unified Modelling Language OO Methodologies: –Object.
Advertisements

UML an overview.
From Model-based to Model-driven Design of User Interfaces.
University of Rostock 1 CADUI' June FUNDP Namur Automatic user interface generation from declarative models Egbert Schlungbaum & Thomas.
Ch 3: Unified Process CSCI 4320: Software Engineering.
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
Software Project Management
Overview Traditional systems development life cycle (SDLC)
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Chapter 4 - Object-Oriented Analysis and Design in a Nutshell1 Chapter 4 Object-Oriented Analysis and Design in a Nutshell.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 9 Slide 1 Appendix 3 Object-Oriented Analysis and Design.
Background information Formal verification methods based on theorem proving techniques and model­checking –to prove the absence of errors (in the formal.
The Problem Domain Component (PDC) [Coad/Yourdon]
Chapter 1 Object-Oriented System Development
Introduction To System Analysis and Design
Component-Level Design
1 SWE Introduction to Software Engineering Lecture 23 – Architectural Design (Chapter 13)
The OOD Process - II The Human Interaction Component (HIC) [Coad/Yourdon]
7. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Detailed Object-Oriented Requirements Definitions  System Processes—A Use.
The OOD Process Design as a Logical Continuation of Analysis.
End-to-End Design of Embedded Real-Time Systems Kang G. Shin Real-Time Computing Laboratory EECS Department The University of Michigan Ann Arbor, MI
Architecture, Implementation, and Testing Architecture and Implementation Prescriptive architecture vs. descriptive architecture Prescriptive architecture:
Chapter 2: Approaches to System Development
MITSUBISHI 1 CADUI' June FUNDP Namur A Case-Based Design Suppor Method Incorporated With Designer’s Intention Recognition Takayuki Yamaoka.
Faculty of Informatics and Information Technologies Slovak University of Technology Peter Kajsa and Ľubomír Majtás Design.
Satzinger Chp. 2 Part Part 4 of 4 2 Object-Oriented Analysis and Design with the Unified Process Testing Testing is critical discipline Testing activities.
Prepared by: Sanaz Helmi Hoda Akbari Zahra Ahmadi Sharif University of Tech. Summer 2006 An Introduction to.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
Database Management System Prepared by Dr. Ahmed El-Ragal Reviewed & Presented By Mr. Mahmoud Rafeek Alfarra College Of Science & Technology Khan younis.
Introduction To System Analysis and Design
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
Content The system development life cycle
Copyright 2003 Scott/Jones Publishing Standard Version of Starting Out with C++, 4th Edition Chapter 13 Introduction to Classes.
Université Toulouse I 1 CADUI' June FUNDP Namur Automatic Ergonomic Evaluation : What are the Limits ? Christelle FARENC *, Véronique LIBERATI.
1 Introduction to Software Engineering Lecture 1.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 05. Review Software design methods Design Paradigms Typical Design Trade-offs.
Architectural Patterns Support Lecture. Software Architecture l Architecture is OVERLOADED System architecture Application architecture l Architecture.
1 COMP 350: Object Oriented Analysis and Design Lecture 1Introduction References: Craig Larman Chapter 1.
User interface design and human computer interaction Xiangming Mu.
Chapter 12: User Interface Design
Chapter 8 Object Design Reuse and Patterns. Object Design Object design is the process of adding details to the requirements analysis and making implementation.
CS 4850: Senior Project Fall 2014 Object-Oriented Design.
7 Systems Analysis and Design in a Changing World, Fifth Edition.
Univ. Autónoma de Madrid 1 CADUI' June FUNDP Namur A Framework for the Automatic Generation of Software Tutoring Javier Contreras Francisco.
CS 8532: Advanced Software Engineering Dr. Hisham Haddad Overview of Object-Oriented Design Highlights of OOD Concepts, Components, and Process.
Software Design: Principles, Process, and Concepts Getting Started with Design.
PROC-1 1. Software Development Process. PROC-2 A Process Software Development Process User’s Requirements Software System Unified Process: Component Based.
Introduction to OOAD and the UML
Software Maintenance Speaker: Jerry Gao Ph.D. San Jose State University URL: Sept., 2001.
S. Wilson and P. Johnson 1 CADUI' June FUNDP Namur Bridging the Generation Gap: From Task Models to User Interface Designs Stephanie Wilson.
Stanford University 1 CADUI' June FUNDP Namur The Mecano Project Angel R. Puerta Knowledge Systems Laboratory Stanford University Stanford.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
Formal Verification. Background Information Formal verification methods based on theorem proving techniques and model­checking –To prove the absence of.
Class Diagrams. Terms and Concepts A class diagram is a diagram that shows a set of classes, interfaces, and collaborations and their relationships.
CSIS 4850: CS Senior Project – Spring 2009 CSIS 4850: Senior Project Spring 2009 Object-Oriented Design.
Oracle eBusiness Financials R12 Oracle Receivables Functional Overview TCS Oracle Practice.
Université Toulouse I 1 CADUI' June FUNDP Namur Implementation Techniques for Petri Net Based Specifications of Human-Computer Dialogues.
A Hierarchical Model for Object-Oriented Design Quality Assessment
INF230 Basics in C# Programming
Systems Analysis and Design With UML 2
Introduction to Design Patterns
Object-Oriented Design
Introduction to Software Testing
Chapter 20 Object-Oriented Analysis and Design
Object-Oriented Systems Development Life Cycle (CH-3)
Introduction To software engineering
OBJECT ORIENTED ANALYSIS AND DESIGN
Basic OOP Concepts and Terms
Introduction to OOAD and the UML
Presentation transcript:

FH Augsburg - FB Informatik 1 CADUI' June FUNDP Namur Software Life Cycle Automation for Interactive Applications: The AME Design Environment Christian Märtin Fachbereich Informatik Fachhochschule Augsburg D Augsburg (Germany)

FH Augsburg - FB Informatik 2 CADUI' June FUNDP Namur Introduction Concurrent support for automating the design of the UI and the domain parts of interactive systems Unifying specification and generation approaches AME: architecture and scope AME´s life cycle for automated model refinement Future work

FH Augsburg - FB Informatik 3 CADUI' June FUNDP Namur Integration of the life cycles OO technology as the common denominator

FH Augsburg - FB Informatik 4 CADUI' June FUNDP Namur Unifying specification and generation Balancing the ratio of flexibility vs. automation –The designer´s choice at each life cycle activity accept the intermediate model as proposed by the system partly modify or extend the intermediate model interactively integrate reusable components into the intermediate model –Model refinement knowledge standard knowledge for standard design problems optional domain or user specific knowledge for adaptation experience of the designer technical knowledge for automated system integration

FH Augsburg - FB Informatik 5 CADUI' June FUNDP Namur AME Architecture AME Architecture Three levels: –modeling –construction –implementation OO representation scheme Target applications: –Business domain

FH Augsburg - FB Informatik 6 CADUI' June FUNDP Namur AME life cycle model

FH Augsburg - FB Informatik 7 CADUI' June FUNDP Namur OOA Modeling Example OOA model specification –attributes –operations –gen/spec relations –aggregations –associations –message channels

FH Augsburg - FB Informatik 8 CADUI' June FUNDP Namur Generating the window hierarchy Mapping of complex OOA classes to windows, if possible –expanding gen/spec relations –exploiting attributes, attribute types, grouped attributes –exploiting aggregations (to simple OOA classes) –adopt simple OOA classes as OOD classes Creating the menu- and command hierarchy –exploit target environmental constraints and synonym lists –assignment of OOA operations to menu entries or buttons

FH Augsburg - FB Informatik 9 CADUI' June FUNDP Namur Assigning interaction objects Exploiting qualified attribute types, if available: –map the attribute type to a specific OOD object pattern –assign AIOs to the OOD objects If not: activate a number of rule groups –exploit content oriented meta data –exploit synonym lists to find the correct qualified data type –exploit the cardinality of attributes and/or operations –refinement of already assigned AIOs Apply user or environment-specific rule groups

FH Augsburg - FB Informatik 10 CADUI' June FUNDP Namur UI behavior spec AME exploits –OOA/D-messages, relational OOA/D patterns, embedded code fragments to automatically specify –menu/command activation, inter-object communication, method code integration Designer adds domain specific dynamics

FH Augsburg - FB Informatik 11 CADUI' June FUNDP Namur Layout generation Layout simulation –choosing dialogbox and window types automatically –standard set of layout alternatives –user/env. profiles –additional forward chained rule sets –interactive layout modification

FH Augsburg - FB Informatik 12 CADUI' June FUNDP Namur Target application generation Scanning/Parsing the detailed specification Generating C++-code, callbacks, defaults Integration of existing domain method code Integration of standard dialog boxes and behavior Integration of reusable major application parts Activating the Borland C++-compiler As an alternative a UIMS interface exists

FH Augsburg - FB Informatik 13 CADUI' June FUNDP Namur Conclusions and future work Benefits –complete prototypical life cycle support for interactive system development –automating many standard UI design tasks: the time gained can be used for domain modeling and refinements Drawbacks –AME needs a relatively long incremental learning process –modeling system level dialog dynamics is time consuming Future –Borland Delphi, multimedia, new domains, OO synergies

FH Augsburg - FB Informatik 14 CADUI' June FUNDP Namur Thank you for your attention!