Introducing Lattix

591 views
447 views

Published on

Lattix: software architecture recovery and visualization tool

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
591
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
14
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Introducing Lattix

  1. 1. Introducing By Innocent Akhidenor & Ahmed Ibrahim ECE 750 - Fall 2013
  2. 2. Architecture Recovery The Microsoft IIS Structure Source: VisualComplexity.com Lattix LDM, founded to visualize and manage the architecture of complex software systems
  3. 3. Dependency Model • A Dependency Model is the representation of the architecture of a system. It consists of: • An ordered hierarchical decomposition of the System into its Subsystems • Display of current dependencies between Subsystems • Design Rules for allowable dependencies between Subsystems
  4. 4. Dependency Structure Matrix (DSM) • • • • Class Reference - A reference to a class or object, but not to any of the objects members. Invokes - A method call Inherits - A reference to a superclass, or to Interface implemented Data Member Reference A reference to a variable of a class / object
  5. 5. Design Rules • Each cell in a DSM represents a “design intent” • Dependency Model = DSM + Design Rules DSM with Rules View Green Triangle – Dependency Acceptable Yellow Triangle – Dependency Unacceptable Red Triangle – Rule Violation Discovered
  6. 6. Why Lattix ? • Create a system blueprint by mapping dependencies across the various domains of the system • Analyze, optimize, and specify the system architecture through the DSM, diagrams, and dependency rules • Identify dependencies which violate the architecture • Identify and explore opportunities to improve the modularity of the system • Measure quality with key metrics and track changes to the system architecture over time • Assess the impact and risk of proposed changes to the system
  7. 7. Using Lattix 1. Create a initial DSM of your Application 2. Organize the DSM to reflect the Intended Architecture 3. Design Rules: Specify External Library Usage 4. Design Rules: Specify Application Interdependencies 5. Print out the DSM and the Conceptual Architecture
  8. 8. Case Study
  9. 9. Example /1 Case study:
  10. 10. Example /2 Subsystem with internal dependencies The (N x N) matrix shows how each subsystem is related to every other subsystem
  11. 11. Architecture Patterns using DSM 1/3 Layered System
  12. 12. Architecture Patterns using DSM 2/3 Strictly Layered System
  13. 13. Architecture Patterns using DSM 3/3
  14. 14. Example /3
  15. 15. Demo...Please Okay
  16. 16. Example /1 Case study:
  17. 17. Recommended Reading Design Structure Matrix Methods and Applications by Steven Eppinger, 2012
  18. 18. Questions?
  19. 19. References 1. N. Sangal, E. Jordan, V. Sinha, and D. Jackson, “Using Dependency Models to Manage Complex Software Architecture,” Proc. 20th Conf. Object Oriented Programming, Systems, Languages, and Applications, 2005

×