Your SlideShare is downloading. ×
CARD - Controlling Architectural Degradation in Real life Applications
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

CARD - Controlling Architectural Degradation in Real life Applications

240
views

Published on

This presentation gives a very brief overview of my MSc dissertation at the University of St Andrews.

This presentation gives a very brief overview of my MSc dissertation at the University of St Andrews.

Published in: Technology, Business

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

  • Be the first to like this

No Downloads
Views
Total Views
240
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. CArD: Controlling ArchitecturalDegradation in Real life Applications
  • 2. Overview Software Architecture defines the structure of the system in terms of its components, connectors and interactions. It is a key tool widely used in the industry because:  Improves communication with stakeholders;  Facilitates early design decisions;  Promotes transferable abstractions of a system;  Considered as the basis for implementation
  • 3. Overview(2) Original design that is created prior the system’s implementation is known as the prescriptive architecture The architecture reflecting the current implementation is called the descriptive architecture. The inconsistency between both architectures results in architectural degradation.
  • 4. System Evolution
  • 5. Proposed System Mapping of an entity in the model to its corresponding entity in the implementation, and vice-versa. Compare and conform involves the detection of any architectural property violation between the two descriptions. Master and Slave. The master can alternate between model and implementation. The respective slave has to conform to the master.
  • 6. What is conformance? Ensures that the model conforms to the implementation or vice-versa. A set of rules have been designed and implemented, such as Inheritance Relationship Rule:Definition: DA conforms to PAif and only if every entity thatinherits from another entity in PAis required to inherit an identicalentity type in its corresponding DA.
  • 7. More Structural Rules…Definition: Communication Integrity – Absent Link Rule.DA conforms to PA if and only if every entity that communicateswith another entityin PA is required tohave the sameassociation relationshipin its corresponding DA.+ 19 more rules.
  • 8. Extension - Interaction RulesDefinition: Temporal Rule. PA conforms to DA if and only ifthe same sequence of method calls is maintained between PA andDA.
  • 9. FlaggingWhen a violation is detected, a flagging notification isdisplayed to the user, as follows:
  • 10. ConclusionCArD is:- An Eclipse plug-in;- Checks Conformance;- Between Model in UML 2.0 Class Diagrams/Sequence Diagrams and Implementation;