CelsiusTech Case Study

1
CelsiusTech Case Study

• SE540 Software Architecture
• Mark Ardis, Rochester Institute of Technology
• Fall 2007

2
Acknowledgements

• Some of the material in these slides is taken
  from Software Architecture in Practice, 2nd
  edition by Bass, Clements and Kazman.

3
Outline

• CelsiusTech Background
• Product-Line Results
• Motivation for Change
• Quality Attributes and Tactics

4
CelsiusTech Background

• Swedish naval defense contractor
• 2000 staff, 3M annual sales
• Command, Control and Communication (C3) systems
• Swedish corvettes (380 tons)
• Australian/New Zealand frigates (3225 tons)
• Danish patrol vessels (2700 tons)
• Swedish submarines (1330 tons)
• ...

5
Product-Line Projects
6
Code Re-Use
7
Motivation for Change

• 1975 - 80
• 30-100K SLOC assembly and RTL/2
• Analog to 16-bit digital
• 1980 - 85
• 700 SLOC RTL/2
• Minicomputers, multi-processors
• 1986 - future
• Ada
• Microcomputers, fault-tolerant
• Prototyping, iterative process

8
Organizational Structures

• Prior to 1986
• functional areas
• 1986 to 1991
• product-line development
• 1992 - 1998
• application engineering

9
Project Organization Prior to 1986
10
Project Organization 1986 - 1991
11
Project Organization 1992 - 1998
12
Video of the Day

• http//www.youtube.com/watch?vdxZOfXGwdtg

13
Quality Attributes

• Performance
• Modifiability
• Safety, reliability, and availability
• Testability

14
Tactics - Performance

• Introduce concurrency
• Reduce demand
• Multiple copies
• Increase resources

15
Tactics - Modifiability

• Semantic coherence
• Anticipate expected changes
• Generalize modules
• Abstract common services
• Interface stability

• Intermediary
• Configuration files
• Component replacement
• Standard protocols

16
Tactics - Safety, Reliability, Availability

• Exceptions
• Active redundancy
• State resynchronization
• Transactions

17
Tactics - Testability

• Separate interface from implementation