Mae A System Model and Environment for Managing Architectural Evolution

Transcription

1 Mae Mae A System Model and Environment for Managing Architectural Evolution Roshanak Roshandel roshande@usc.edu USC-CSE Annual Research Review March

2 Motivation Architecture-based software development Software evolves Changes in the implementation Configuration Management (CM) techniques Changes in the architectures Mae No technique beyond storing different versions of artifacts System model Extensible environment 2

3 Background Software Architecture Components, connectors, configurations, styles, architecture description languages (ADLs), subtyping Configuration Management Versions, variants, branches, locks, version tree, system models, configurations 3

4 Architectural System Model Integrated system model based on architectural and CM concepts Concept Components, connectors, interfaces Compatibility rules Hierarchical composition Linear evolution Diverging paths of evolution Alternatives (variation points) Non-mandatory architectural elements Type evolution constraints Realization Types and instances Behaviors and constraints Subarchitectures Revisions Inter-file branches Guarded variants Guarded options Subtyping 4

5 Element Notional Arch. Model Mae System Model Connector type Connector instance Variant component type Variant connector type Element name interface* Interface type component* connector* {interfacemapping}* behavior* constraint* Interface name instance direction name interfacetype Component {sourceinterface name [, mydestinstance]}* type {[mysourceinterface,] interface* destinterface}* connectortype component* - connector* {interfacemapping}* behavior* constraint* - Component Instance Notional Arch. Model name representation name componenttype name, Mae revision System Model {interface [, guard]}* {component name [, guard]}* {connector revision [, guard]}* {interfacemapping}* representation behavior* ascendant* constraint* descendant* subtype name*, ascendant*, descendant* direction name interfacetype {sourceinterface name [, mydestinterface]}* {[mysourceinterface, revision ] destinterface}* connectortype {interface [, guard]}* variantconnectortype name, {component Revision [, guard]}* {connector [, guard]}* {interface [, guard]}* {interfacemapping}* {componenttype, behavior* guard}* subtype* constraint* ascendant*, subtype* descendant* ascendant* Name, revision descendant* {interface [, guard]}* {connectortype, guard}* subtype* name ascendant*, componenttype descendant* variantcomponenttype 5

6 Realization of the System Model Generic system model Variety of implementation methods UCI sxadl 2.0 Style independent ADL Extensible tool support Core Schemas (types, instances) CM concepts (variants, versions) Architectural behaviors (subtyping, constraints, services) 6

7 Schema <xsd:complextype name= StaticComponentType"> <xsd:complexcontent> <xsd:extension base="archversions:variantcomponenttypeimplvers"> <xsd:sequence> <xsd:element name="subtype" type="subtypedecl" minoccurs="0"/> <xsd:element name="statedecl" type="statedecl" minoccurs="0 maxoccurs="unbounded"/> <xsd:element name="invariantdecl" type="xsd:string"/> <xsd:element name="interfacedecl" type="interfaceelementdecl minoccurs="0" maxoccurs="unbounded"/> <xsd:element name="operationdecl" type="operationdecl minoccurs="0 maxoccurs="unbounded"/> <xsd:element name="mapdecl" type="mapdecl" minoccurs="0 maxoccurs="unbounded"/> <xsd:element name="isvirtual" type="archbool:bool minoccurs="0"/> <xsd:element name="isextern" type="archbool:bool minoccurs="0"/> </xsd:sequence> </xsd:extension> </xsd:complexcontent> </xsd:complextype> 7

8 Example 8

9 9 Headquarters conna Clock conn2 conn2 conn3 conn4 Weather Repository Map Weather Analyzer Resource Manager Strategy AnalysisKB Simulation Agent Resource Monitor SAKBUI Rendering Agent conn1 Soldier conn7 Soldier Manager Rendering Agent connd Deployment Advisor Commander connb Resource Monitor Strategy AnalyzerAgent Deployment Advisor SAKBUI Clock conn6 Simulation Agent Commander Manager connc Rendering Agent conn5 Legend: Optional Component Variant Component Optional Variant Component Intra-process Connector Inter-process Connector Strategy AnalyzerAgent

10 Implementation CM Subsystem Selector Subsystem Analysis Subsystem xadl 2.0 Data Binding Library XML Schemas XML Architectural Specification 10

11 CM & Selector Subsystem 11

12 Analysis Subsystem 12

13 Demonstration Version aware design assistance Compliance Checker Component-level patches Architectural differencing Architectural merging Multi-Versioning Connectors Wrap multiple version of the components Reliable component upgrade 13

14 Current Status Under evaluation by JPL and Boeing MDS extension Enhancements underway R. Roshandel, A. van der Hoek, M. Mikic-Rakic, N. Medvidovic, Mae - A System Model and Environment for Managing Architectural Evolution, Submitted to ACM Transactions on Software Engineering and Methodology (In review), October A. van de Hoek, M. Rakic, R. Roshandel, N. Medvidovic, Taming Architecture Evolution, in Proceedings of the Sixth European Software Engineering Conference (ESEC) and the Ninth ACM SIGSOFT Symposium on the Foundations of Software Engineering (FSE-9), Vienna, Austria, September Nenad Medvidovic, Marija Mikic-Rakic, Roshanak Roshandel (USC) Andre van der Hoek (UCI) 14