12th Working IEEE/IFIP Conference on Software Architecture (WICSA)

1. A Unified Approach to
Architecture Conformance
Checking
Andrea Caracciolo, Mircea Filip Lungu, Oscar Nierstrasz
WICSA ’15
http://scg.unibe.ch

2. Architecture Erosion
2
=Design Code/

3. Architecture Erosion
3
Compliance Monitoring

4. Compliance Monitoring
4
non-automated
techniques *60%
* How Do Software Architects Specify and Validate Quality Requirements? (ECSA 2014)

5. 5
A
Б
诶
Compliance Monitoring

6. 6
A
Б
诶
Tools
Compliance Monitoring

7. 7
A
Б
诶
Specification
Formalisms
Compliance Monitoring

8. 8
A
Б
诶
Reports
Compliance Monitoring

9. 9
A
Б
诶
Compliance Monitoring

10. 10
A
诶
Compliance Monitoring

11. 11
Persistence cannot depend on Service
Impl must have annotation "@Service"
System cannot contain cycles
Dictō
A Unified Approach

12. Dictō
12
@ scg.unibe.ch/dicto
Persistence cannot depend on Service
Service must have annotation “@Service”
System cannot contain cycles
Rules

13. Dictō
13
Persistence cannot depend on Service
Service must have annotation “@Service”
System cannot contain cycles
@ scg.unibe.ch/dicto
Persistence = Package with name:"app.*persistence.*"
Service = Package with name:”app.*service.*"
Entities
Rules

14. Dictō
14
@ scg.unibe.ch/dicto
Persistence cannot depend on Service
only Service can have annotation “@Service”
System cannot contain cycles
Rules
Entities
Persistence = Package with name:"app.*persistence.*"
Service = Package with name:”app.*service.*"

15. Dictō
15
Persistence cannot depend on Service
only Service can have annotation “@Service”
System cannot contain cycles
@ scg.unibe.ch/dicto
Persistence = Package with name:"app.*persistence.*"
Service = Package with name:”app.*service.*”,
name!:"*persistence*"
Entities
Rules

16. Dictō
16
@ scg.unibe.ch/dicto
Rules
Method can only be named "String"
only Package can contain dead methods
XMLTag must have attribute “String"
WebResource must have content "String"
Method must catch Class
WebResource must have latency < int ms
WebResource must handle load from int users
Maintainability
Compatibility
Reliability
Performance

17. Analysis
17
depend-on(app.xx.persistence.yy, app.xx.service)
depend-on(app.xx.persistence.yy2, app.xx.service)
depend-on(app.xx.persistence.yy3, app.xx.service)
Persistence cannot depend on Service
.xml.sh

18. Analysis
18
Persistence cannot depend on Service
depend-on(app.xx.persistence.yy, app.xx.service) = True
depend-on(app.xx.persistence.yy2, app.xx.service) = False
depend-on(app.xx.persistence.yy3, app.xx.service) = False
.csv

19. Reporting
19
Persistence cannot depend on Service
Service must have annotation “@Service”
System cannot contain cycles
Dictō
Statistics

20. 20

21. 21

22. Reporting
22
New Issue
Statistics
Dictō
Persistence cannot depend on Service
Service must have annotation “@Service”
System cannot contain cycles

23. 23

24. Evaluation
24
Medium size company
various - Java EE / .NET
100 employees
Open source project
LMS - PHP (1.8M LOC)
12 service providers, 900’000+ users
Large size company
B2B - Java EE (50K LOC)
1’000 employees

25. Evaluation
25
Impact
Process? Culture?
Value
Cost–effectiveness? Quality?
Applicability
Expressivity? Usability?

26. Summary
Dictō
A uniform, readable, executable DSL
for specifying architectural constraints.
26
Persistence cannot depend on Service
Service must have annotation “@Service”
System cannot contain cycles
@ scg.unibe.ch/dictoAndrea Caracciolo

27. Discussion Topics
27
Persistence cannot depend on Service
Service must have annotation “@Service”
System cannot contain cycles
@ scg.unibe.ch/dictoAndrea Caracciolo
- how to streamline/incentivize compliance monitoring?
- which are the common obstacles?