Orthographic Software Modeling A Practical Approach to View Based Development

Transcription

1 Orthographic Software Modeling A Practical Approach to View Based Development Colin Atkinson University of Mannheim Germany MSI th October 2009 Oldenburg

2 Outline Modern software engineering paradigms Review of KobrA Orthographic Software Modeling View-based software engineering Dynamic view generation Dimension Based Navigation Case study Conclusion

3 Modern Software Engineering Paradigms Model-driven Software Development (MDSD) Levels of abstraction Component (service) - based Development (CBD) Composition hierarchy Product-line Engineering (PLE) Product families Other Paradigms Aspect-oriented Using those Paradigms lots of different views different notations

4 Observations New software engineering paradigms dramatically increase number of views traditional source code is also just a view Enterprise Architecture adds more information and more views Executability is only one property of a system. Others include Checkability Predictablity Testability To support these effectively we need Inherently View-oriented Methods Dynamic View Generation Dimension Based Navigation Orthographic Software Service System Modeling

5 Basic Philosophy of the Proposed IDE Support for multi-views Multiple inter-related diagrams and representations Views as Projections Should be as orthogonal as possible Multi-Dimensional Navigation Space Every view exists at a particular set of coordinates Flexible infrastructure that can be extended with new tools and views Single underlying representation of the software system

6 Component Views in KobrA Specification Operational View (operation specifications) Operational View (UML collaboration communic ation diagrams) Business Component Behavioral View (UML statechart diagram) Structural View (UML class/object diagrams) Structural View (UML class/object diagrams) Behavioural View (UML activity diagrams) Realization

7 Modeling Principles Uniformity all behavior rich elements should be viewed as components, including (sub)systems component assembly = component development Parsimony minimal set of concepts (no redundancy) Locality all models should be local to a component Encapsulation component specifications (what) must be separated from component realizations (how)

8 Component Nesting in KobrA UML-based modeling of nested components attempts to reconcile MDD, CBD and PLE key ideas Three fundamental development dimensions three fundamental viewpoints strict separation of black box and white box views key benefits full power of UML available to model components OCL available for formality and precision

9 Separation of Development Dimensions Abstraction (MDA) Genericity (PLE) Composition (CBD) Application Framework instantiation decomposition refinement 9

10 View-Based Modeling Frameworks Current Status CD test XMI cases OpSpec code RegEx software component UML classes Java source Behavior

11 Goal On-Demand View Generation UML classes Java source Behavior

12 A Simple View-Based "Modeling" Metaphor other engineering disciplines have a long and successful tradition of technical drawing orthographic projection so why don't we do this in software engineering?

13 Views as Projections Functional projection system object Structural projection Behavioral projection

14 Separation of Specification and Realizations Functional projection system object Structural projection Behavioral projection

15 Hierarchical (De)Composition

16 Single Underlying Model - Package Structure Component model derived from KobrA (KobrA 2.0) fully integrated into UML formalized definition through OCL constraints views generated on demand via ATL transformations

17 Single Underlying Model Core Metamodel

18 The Navigation Jungle UML classes Java source Behavior

19 Navigation In every dimension, exactly one dimension element can be selected Once an element is selected in every dimension, an appropriate view is generated (i.e. a transformation is launched and an editor is started) Unified navigation Cell (Component-based) Software System

20 Dimension Explorer editor dimensions dimension elements

21 Navigation Dimension configuration example Component (Composition) Abstraction Level Information Hiding / Encapsulation Projection Variant Language Notation

22 Software Modeling Environment Roles Methodologist creates rules for dimensions and its contents Developer predefined elements source of dimension elements (e.g. dynamically generated from the single underlying model) changeability rights by developer uses dimension based navigation manipulates software system through views

23 Case Study: Mobile Tourist Guide

24 Mobile Tourist Guide Name Description Receives - Returns Sends Reads Changes Body - Precondition Postcondition searchtouristattractions Searches for tourist attractions depending on the user s preferences and the current context (e.g. location, time, weather) TouristAttractionList TouristGuideService.getTouristAttraction() ContextSet, Preferences TouristAttractionList Preferences have been set up, Context Sources are available TouristAttractionList contains suitable attractions

25 Mobile Tourist Guide

26 Mobile Tourist Guide Description 1 2 Is the mobile client device capable of playing videos? What visibility should be assignable to the mobile client? (Public context item to the server, private context items not Component MobileTouristGuide MobileTouristGuide Encapsulation Private Private Projection Structural Structural Constraints ResolutionSet Boolean ValueSet {Public, Private, PublicAndP Effects ResolutionValue: True (1) remove stereotype <<variant>> at Class Video (2) remove stereotype <<variant>> on operation MobileTouristGuide.getVideo() ResolutionValue: Public (1) remove <<Komponent>> Private (2) remove association PrivateConte TouristGuide ResolutionValue: False (1) remove Class Video (2) remove operation MobileTourist- Guide.getVideo() ResolutionValue: Private (1) remove stereotype <<variant>> a PrivateContextMatcher ResolutionValue: PublicAndPrivate (1) remove stereotype <<variant>> a PrivateContextMatcher Stakeholder Application Engineer Application Engineer

27 Mobile Tourist Guide

28 Context Manager

29 Context Manager ID 3 Description Is the mobile client device capable of playing videos? Component ContextManager Abstraction Specification Projection Structural Constraints -- ResolutionSet Boolean Effects ResolutionValue == True (1) remove stereotype <<variant>> at Komponent 3rdPartyContextServices Stakeholder ResolutionValue == False (1) remove Komponent 3rdPartyContextServices (2) remove association 3rdPartyContextServices- MobileTouristGuide Application Engineer

30 Conclusion Orthographic modeling offers a simple but powerful paradigm for supporting the multi-view development of software systems Orthographic System Modeling = view generation mechanism + navigation paradigm + View-based method On-demand generation from single underlying model Orthographic (dimension-based) KobrA 2.0 Ongoing work Consolidation of architecture Addition of more views Adaptation to other frameworks

31 Thank you for your attention! Questions?