Software Architecture Training at SEI - My recollection and ...

976 views

Published on

Published in: Education, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
976
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
52
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Software Architecture Training at SEI - My recollection and ...

  1. 1. Software Architecture Training at SEI – my recollection and comments Ning Chen, Ph.D. Professor Department of Computer Science California State University, Fullerton
  2. 2. SEI (Software Engineering Institute) at Carnegie Mellon University source: www.sei.cmu.edu
  3. 3. Cathedral of Learning at University of Pittsburgh (source: www.umc.pitt.edu)
  4. 4. SEI Training Materials <ul><li>The materials used in training are copyrighted by SEI and distribution is limited to attendees only. </li></ul><ul><li>Book from which the training is based– Available to everyone if you buy one. </li></ul>
  5. 5. What is Software Architecture? <ul><li>My understanding of the SEI’s approach: Before one defines Software Architecture, one needs to define two additional terms - Enterprise Architecture and System Architecture. </li></ul><ul><li>My comments: I like this idea that Software Architecture is a subset of System Architecture and System Architecture is a subset of Enterprise Architecture. </li></ul>
  6. 6. What is Software Architecture? (continued) <ul><li>One of the SEI’s definitions: “The software architecture of a program or computing system is the structure or structures of the system, which comprise the software elements, the externally visible properties of those elements, and the relationships among them.” (source: Software Architecture in Practice second edition) </li></ul>
  7. 7. Why is Software Architecture Important? <ul><li>SEI: “1. It provides a vehicle for communication among stakeholders. 2. It is the manifestation of the earliest designs about a system. 3. It is transferable, reusable abstraction of a system.” </li></ul><ul><li>My comments: There are disputes on how one defines the term “Software Architecture.” Not many people dispute the usage of a software architecture. </li></ul>
  8. 8. Vehicle for Communication <ul><li>SEI: “1. Negotiating with users. 2. Keeping the customer informed of progress. 3. Implementing management decisions and allocations. 4. Architects and implementers use the architecture to guide development.” </li></ul><ul><li>My comments: The word “Software Architect” is gaining popularity. It is important to realize that a software architect involves more than just software. </li></ul>
  9. 9. Early Design Decisions <ul><li>SEI: “Architecture allows predicting system qualities without waiting until the system is developed or deployed.” </li></ul><ul><li>My comments: SEI actually comes up with a lot of good arguments for early design decisions. </li></ul>
  10. 10. Transferable, Reusable Abstraction <ul><li>SEI: “1. Architecture supports building systems using large, independently developed components. 2. Architecture enables template-based development.” </li></ul><ul><li>My comments: This is easier said than done. Nevertheless, everyone agrees that this is the thing to come. By the way, in my opinion, J2EE is a good starting point. </li></ul>
  11. 11. Architecture Structure <ul><li>SEI: “Architecture structure can be divided into three types: 1. module structures, 2.component-connector structures, 3. allocation structures.” </li></ul><ul><li>My comments: This probably is one of the most important concepts you want to know. </li></ul>
  12. 12. Architecture Structure <ul><li>Modules: uses, decomposition, layers, class/generalization, etc. </li></ul><ul><li>Component-and-Connector: client-server, concurrency, process, share-data, etc. </li></ul><ul><li>Allocation: work assignment, deployment, implementation, etc. </li></ul>
  13. 13. Architecture Business Cycle (ABC) source: Software Architecture in Practice second edition <ul><li>SEI: </li></ul>
  14. 14. I think I have learned enough. Can I design a software architecture now? <ul><li>Q. My stakeholders handed me the requirements already and I have a pretty good understanding of the system. Can I start designing my software architecture now? </li></ul><ul><li>A. SEI’s answer: Not yet. You need to know two more things before you can start: Quality Attributes and Patterns/tactics. </li></ul>
  15. 15. Quality Attribute (this is one of the SEI’s babies. You may want to pay great attention to it) <ul><li>Some general quality attributes: availability, modifiability, performance, security, testability, usability, etc. </li></ul><ul><li>SEI: ”Architecture is critical to the realization of quality attributes.” </li></ul><ul><li>My interpretation: if, for example, the availability is the must-have quality attribute of your system, then you had better to come up with an architecture that “shoots” for that quality. In other words, the architectural design is driven by the desired quality attributes. </li></ul>
  16. 16. Quality Attribute (this is one of the SEI’s babies. You may want to pay great attention to it) <ul><li>SEI: “In a traditional system development quality attributes are rarely captured in requirements specifications. They are often vaguely understood and weakly articulated.” </li></ul><ul><li>What should we do? </li></ul><ul><li>SEI’s answer: QAW (SEI Quality Attribute Workshop) </li></ul>
  17. 17. SEI QAW steps <ul><li>1. QAW presentation and introductions </li></ul><ul><li>2. Business/Mission presentation </li></ul><ul><li>3. Architectural plan presentation </li></ul><ul><li>4. Identification of architectural drivers </li></ul><ul><li>5. Scenario* brainstorming </li></ul><ul><li>6. Scenario consolidation </li></ul><ul><li>7. Scenario prioritization </li></ul><ul><li>8. Scenario refinement </li></ul><ul><li>(Iterate above as necessary with broader stakeholder community) </li></ul><ul><li>*SEI came up with a quality scenario consisting six parts: 1. Source, 2. Stimulus, 3 Artifact, 4. Environment, 5. Response, 6. Response Measure. </li></ul>
  18. 18. My comments on SEI QAW <ul><li>Don’t ever underestimate this one-page QAW description. Based on what I heard, QAW is a big money-making machine for SEI. If you ask SEI to do a QAW for you, it will cost you a-leg-and-an-arm. </li></ul><ul><li>My analogy: high-cost marriage counseling: almost everyone knows what is the source of difficulty in marriage and you just can’t fix them by yourself. </li></ul>
  19. 19. Patterns <ul><li>SEI: “An architectural pattern 1. is found repeatedly in practice, 2. is package of design decisions, 3. has known properties that permit reuse, 4. describes a class of architectures.” </li></ul><ul><li>My comments: don’t mix the concept of patterns and the usage of patterns. Sometimes dealing with one thing at a time will make things much easier. </li></ul><ul><li>Example: pipe-and-filter </li></ul>
  20. 20. Tactics <ul><li>SEI: “Tactics are the building blocks of design from which architectural patterns are created.” </li></ul><ul><li>Pattern tactics relationship: Any pattern implements several different tactics, often to promote various quality attributes. Each implementation of a given pattern involves unique choices of tactics. </li></ul>
  21. 21. Tactics (continued) <ul><li>SEI: “Tactics example for availability: ping/echo” </li></ul><ul><li>My explanation: If the system you are designing requires high availability, then you may want to use the ping/echo tactic/pattern as one of the building blocks of your software architecture. </li></ul>
  22. 22. Tactics (continued) source: Software Architecture in Practice second edition <ul><li>SEI came up with a mapping between the well-known tactics and the quality attributes. </li></ul>
  23. 23. I guess, finally I can start designing an architecture for my system. Right? <ul><li>SEI: Not quite yet. You need to learn one more buzzword – SEI’s ADD </li></ul><ul><li>What is ADD? </li></ul><ul><li>ADD stands for Attribute-Driven Design </li></ul>
  24. 24. SEI’s Attribute-Driven Design <ul><li>SEI: “The Attribute-Driven Design (ADD) method, developed by the SEI, is an approach to define a software architecture that bases the decomposition process on the quality attributes the software must fill. ADD follows a recursive decomposition process where, at each stage in the decomposition, tactics and architectural patterns are chosen to satisfy a set of quality attribute scenarios.” </li></ul>
  25. 25. SEI’s Attribute-Driven Design (continued) <ul><li>My interpretation: The idea is quite interesting. The attribute-driven architecture goes the following way. First break (decompose) the system to small workable parts. Get quality attributes from your boss. Find some suitable patterns/tactics from your pattern catalog (just consider this is a pattern yellow book). Repeat the process if necessary. </li></ul><ul><li>My thoughts: Unfortunately My SEI instructor for some reason “flew through” this portion without working out a detailed example. It is highly possible that applying ADD to a non-trivial real-world problem is not that straightforward. </li></ul>
  26. 26. Conclusion: Want to become a Software Architect? <ul><li>My informal survey: about 30 people from industry attended this workshop. Half of them said they belonged to the Software Architecture Department in their organizations. About 20% of them actually have the job title of Software Architect. </li></ul>
  27. 27. Conclusion: Want to become a Software Architect? <ul><li>Will the job title of “Software Architect” become abundant? </li></ul><ul><li>My thoughts: No one has a crystal ball and it is still hard to say whether industry will seek lots of Software Architects in the near future. Nonetheless, I have seen the transition from “programmer” to “Software Engineer.” It is not that unusually now to find a Software Architecture Department in a mid-size organization. </li></ul>
  28. 28. Conclusion: Want to become a Software Architect? <ul><li>What should I do to prepare myself? </li></ul><ul><li>You may want to play “follow the leader” game. SEI apparently is one of the major mover-and-shakers. You many want to “ride the SEI train.” </li></ul><ul><li>You may want to improve your people/communication skills – Software Architecture involves lots people-related activities. Your technology skill alone is not enough. You had better be good at the people skill too. </li></ul>

×