1 / 27

Management of Composites in Software Engineering Environments.

Management of Composites in Software Engineering Environments. Jacky Estublier, German Vega, Thomas Leveque. ADELE. Grenoble University France. Outline. Composites in SE CADSE Composites in CADSE Experiences Conclusion and future works. Composites. Models.

deron
Télécharger la présentation

Management of Composites in Software Engineering Environments.

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. Management of Composites inSoftware Engineering Environments. Jacky Estublier, German Vega, Thomas Leveque ADELE Grenoble University France

  2. Outline • Composites in SE • CADSE • Composites in CADSE • Experiences • Conclusion and future works

  3. Composites Models Objectives • Design and Development Scalability

  4. Composite • A compositerepresents an entity as a whole made up of other entities that are considered its parts.

  5. Wheel 1 Wheel 3 Engine Wheel 2 Wheel 4 Composite Horse power = 120

  6. Composite In SE • Abstraction • High level languages • Models • Composite • Classes

  7. Composite: SE vs Others • Other • Object Physical structure • hierarchical decomposition • Model ≠ Real object • SE • Any kind of decomposition • Structural, functional… • Model = code = application = Real object

  8. Composite: SE vs Others Frame Tool2 Tool2 Structural model Wheel Saddle PDM System Detailed model Tool1 CAD Real object

  9. Composite: SE vs Others Function Sub System System model Concept Package Detailed model SCM System Tool1 Tool1 Source Source Real object Source IDE Sources and executables Executable

  10. Outline • Composites in SE • CADSE • Composites in CADSE • Experiences • Conclusion and future works

  11. CADSE • Computer Aided Domain Specific Environment • Domain specific • Extend generic environments • IDE • SCM • Allow manipulating an application model • Conform to a domain model • A Domain is an area in which a number of stakeholders is repeatedly performing similar activities.

  12. Domain Model Developer CADSE (Computer Aided Domain Specific Environment)

  13. Domain Model • System Model • Abstract, coarse grain view of a system • Come from SCM • Describes logical organization of product • Domain model = System model

  14. Domain Model Example << R >> << R >> << A >> << A >> << R >> << P >> A : AggregationP : PartR : Require

  15. Outline • Composites in SE • CADSE • Composites in CADSE • Experiences • Conclusion and future works

  16. composition link Composite • A composite is an item composed of all items that constitute the destination of a composition link starting from that item. • A composite must be such that, when closed, it can be safely used, for a given purpose, in place of the set of items it contains.

  17. Domain Model Example << R >> << R >> << A, C >> << A, C >> << R >> << P >> A : AggregationP : PartR : RequireC : Composition

  18. Close Comp1 Comp1 contains L1 uses C3 C2 L2 C1 Comp2 contains uses contains C4 C6 C5 uses App Composite Example Comp1 L1 C3 C2 L2 C1 Comp2 C4 C6 C5 App read only opened composite composition link derived link closed composite any link unresolved link

  19. Composite mechanism • Closed a composite => remove its components. • Links are Resolved/Unresolved. • Closed a composite => close the composites it contains. • A close operation must ensure that build of the composite is OK. • Derived link mechanism. • Read Only mechanism.

  20. Outline • Composites in SE • CADSE • Composites in CADSE • Experiences • Conclusion and future works

  21. Experiences • Since 2006, daily used • Many CADSEs • Melusine, APEL, OSGi, iPojo, Think • DOCOSOC, FOCAS and CADSE • Usability • Composite builders are complex to define. • Implementation • Derived link decrease performances • Versioning management part is very complex

  22. Experiences • Abstraction => 10 to 100 smaller • Point of view • Operational object => improved build perf • Model and semantics • Composite management

  23. Outline • Composites in SE • CADSE • Composites in CADSE • Experiences • Conclusion and future works

  24. Conclusion • Model = operational high level software view point • CADSE synchronize model and artifacts • SE composites ≠ Other composites • Operational ≠ descriptive • Open/Close => abstraction, scalability • Composite aspects • Structuring, abstraction, scalability, operational, point of view, concurrent engineering

  25. Future works • Implicit derived links => explicit • Switch from source to binary • Improve build mechanism

  26. References • CADSE web site • http://cadse.imag.fr • ADELE team web site • http://www-adele.imag.fr • APSEC papers • Management of composites in Software Engineering Environments • Domains Specific Engineering Environments

  27. Q & A

More Related