1. Acknowledgement: some slides from Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy. Software Architecture EECE417 Lecture 2

2. Software Architecture Definition (source: Taylor et al., “Software Architecture: Foundations, Theory, and Practice) “[Software architecture is] the set of principal design decisions governing a system”

3. Software Architecture Definition (source: Software Engineering Institute @ CMU) “The software architecture of a computing system is the structure(s) of the system, which comprise software elements, the externally visible properties of those elements, and the relationships among them.” Provided services, Interfaces, Performance characteristics, Fault handling, Shared resource usage Omit information not related to structure  abstraction More than one structure! Implications: (1) any system has a structure; (2) does not say what’s a good or a bad architecture.

4. Essential Difficulties Only partial solutions exist, if any Cannot be abstracted away u Complexity u Conformity u Changeability u Intangibility 4

5. More about the Architect A distinctive role in a project Broad training, leverages extensive experience A keen sense of aesthetics Deep understanding of the domain u Properties of structures, materials, and environments u Needs of customers 5 Even first-rate programming skills are insufficient for the creation of complex software applications u But are they even necessary?

6. What is the role of the architect?

8. f

9. Why is software architecture important? Communication with stakeholders Manifests early design decisions Transferable abstraction of a system

10. Why is software architecture important? Communication with stakeholders u Offers a common language! Manifests early design decisions Transferable abstraction of a system

11. Why is the architecture important? Communication with stakeholders Manifests early design decisions u The architecture defines constraints on implementation u The architecture dictates organizational structure u The architecture inhibits/enables system's quality attributes High-performance, modifiability, security, scalability, reusable- components System qualities can be predicted by studying the architecture u The architecture makes it easier to reason about and manage change Transferable abstraction of a system

12. Why is software architecture important? Communication with stakeholders Manifests early design decisions Transferable abstraction of a system u Reuse at architectural system level Less is more: It pays to restrict the vocabulary of design alternatives u Systems can be built using large, externally developed elements u Enables families of products

13. So far What is a software architecture? What is the role of the software architect? Why is software architecture important? Next Examples of architectures An architecture-centric design process

14. Is this an architecture? An attempt to describe the architecture of an underwater acoustic simulation Missing: What is the nature of the elements? What are the responsibilities of the elements? What is the significance of the connections? What is the significance of the layout?

15. Architecture in Action: WWW What is the architecture of the WWW? 15 Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission.

16. Architecture in Action: WWW This is the Web 16 Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission.

17. Architecture in Action: WWW So is this 17 Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission.

18. Architecture in Action: WWW And this 18 Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission.

19. WWW in a (Big) Nutshell The Web is a collection of resources, each of which has a unique name known as a “uniform resource locator” (URL) Each resource denotes, informally, some information. URL’s can be used to determine the identity of a machine on the Internet, known as an origin server, where the value of the resource may be ascertained. Communication is initiated by clients, known as user agents, who make requests to servers. u Web browsers are common instances of user agents. 19

20. WWW in a (Big) Nutshell (cont’d) Resources can be manipulated through their representations. u HTML is a very common representation language used on the Web. All communication between user agents and origin servers must be performed by a simple, generic protocol (HTTP), which offers the command methods GET, POST, etc. Communication between user agents and origin servers is fully self-contained. u (So-called “stateless interactions”) 20

21. WWW’s Architecture Architecture (of the Web) is wholly separate from the code There is no one piece of code that implements the architecture. There are multiple pieces of code that implement each of the various components of the architecture. u E.g., different Web browsers Stylistic constraints of the Web’s architectural style are not apparent in the code u The effects of the constraints are evident in the Web One of the world’s most successful applications is only understood adequately from an architectural vantage point. 21

22. Architecture in Action (2): @ small scale Unix command line ls invoices | grep -e august | sort 22

23. Unix command line ls invoices | grep -e august | sort Application architecture can be understood based on very few rules Applications can be composed by non-programmers u Akin to Lego blocks A simple architectural concept that can be comprehended and applied by a broad audience 23 Architecture in Action (2): @ small scale

24. Architecture in Action (3): Product Line Motivating example u A consumer is interested in a 35-inch HDTV with a built-in DVD player for the North American market. Such a device might contain upwards of a million lines of embedded software. This particular television/DVD player will be very similar to a 35- inch HDTV without the DVD player, and also to a 35-inch HDTV with a built-in DVD player for the European market, where the TV must be able to handle PAL or SECAM encoded broadcasts, rather than North America’s NTSC format. These closely related televisions will similarly each have a million or more lines of code embedded within them. 24

25. Growing Sophistication of Consumer Devices 25

26. Families of Related Products 26

27. The Necessity and Benefit of PLs Building each of these TVs from scratch would likely put Philips out of business Reusing structure, behaviors, and component implementations is increasingly important to successful business practice u It simplifies the software development task u It reduces the development time and cost u it improves the overall system reliability Recognizing and exploiting commonality and variability across products 27

28. Reuse as the Big Win Architecture: reuse of u Ideas u Knowledge u Patterns u Engineering guidance u Well-worn experience Product families: reuse of u Structure u Behaviors u Implementations u Test suites… 28

29. The Centerpiece – Architecture 29

30. So far What is a software architecture? What is the role of the software architect? Why is software architecture important? Examples of architectures Next An architecture-centric design process