yada yada

1. Architecture Arnon Rotem-Gal-Oz Product Line Architect [email_address] http://www.rgoarchitects.com

4. Architecting a dog house Can be built by one person Requires Minimal modeling Simple process Simple tools Kruchten

5. Architecting a house Built most efficiently and timely by a team Requires Modeling Well-defined process Power tools Kruchten

6. Architecting a high rise Kruchten

17. Architecture vs. Design non-functional requirements (“ilities”) functional requirements (domains) Important : this is a general guideline – sometimes the borders are blurred Architecture: where non-functional decisions are cast, and functional requirements are partitioned Design: where functional requirements are accomplished architecture design

28. Documentation Conceptual Model IEEE 1471-2000

29. Stakeholders & their concerns Ease of Integration Ease of Use Functionality Price Dev Costs On Time Delivery Performance Stability & Maintainability Ease of Debugging Modifiability Testability & Traceability Structure & dependency between component Ease of Installation End User Sales Dev Manager Developer Sys Admin Maintainer Customer

30. Documentation Conceptual Model IEEE 1471-2000

33. RUP – 4+1

34. RM-ODP Viewpoints (2001) Enterprise Information Engineering Technology Computational Manager Database Modeler Operating Sys. Engineer Designers Developer Business model Logical, data modeling Logical view of services Servers, Comm, Physical view of data and services (IDL, WSDL)

35. DODAF (3 Main Views)

36. DoDAF Products 1/2

37. DoDAF Products 2/2

38. Zachman Framework Scope (Ballpark) view Owners View (Enterprise Model) Designers View (System Model) Builder’s View (Technology Model) Out of Context View (Detailed Model) Operational View (Functioning) Data (What) Function (How) Network (Where) People (Who) Time (When) Motivation (Why)

40. Old Model MSF 3.0 + Views Aimed at business executives Aimed at business process owners Aimed at architects and designers Aimed at designers and developers Contextual Conceptual Logical Physical

42. New Model set of views and artifacts - Business Capabilities Manual Procedures Technology Architecture Constraints Reconciliation Services, Messages, Applications, Endpoints XML, Projects, DBs, Classes, Code Logical Data Center Physical servers & segments Deployment Units Abstraction/ Refinement Constraints packaged into deployed on Business Processes and Entities Reconciliation Abstraction/ Refinement

43. Can be mapped… Contextual Conceptual Logical Physical Business Applications Information Technology Business Capabilities Manual Procedures Technology Architecture Constraints Reconciliation Services, Messages, Applications, Endpoints XML, Projects, DBs, Classes, Code Logical Data Center Physical servers & segments Deployment Units Abstraction/ Refinement Constraints packaged into deployed on Business Processes and Entities Reconciliation Abstraction/ Refinement

44. Documentation Conceptual Model IEEE 1471-2000

46. “ Non Standard” - Block Diagrams EAI Human Workflow ECM DW OLTP E-Publish DAL Service Agents Business Rules Activity Workflow Authorization Monitoring Service Interface Controls Log & Trace Exception Management Configuration Authentication Signing Rich UI Web UI

51. UML

52. DSL Services, Messages, Applications, Endpoints XML, Projects, DBs, Classes, Code Logical Data Center Physical servers & segments Deployment Units Abstraction/ Refinement Constraints packaged into deployed on Business Processes and Entities Reconciliation Abstraction/ Refinement Business Capabilities Manual Procedures Technology Architecture Constraints Reconciliation

55. Documentation Conceptual Model IEEE 1471-2000