PHX Session #5 : Architecture Without Big Design Up Front (Garibay)

Editor's Notes

• #3: The ability to right click inside a method, select \"Generate Sequence Diagram...\", resulting in, you guessed it! A sequence diagram! :) 
• #5: Reference: http://blogs.msdn.com/camerons/archive/2008/11/10/testing-draft-to-blog.aspx
• #6: Object Management Group (OMG): *Founded in 1989 *Over 470 member companies*The largest and longest standing not-for-profit, open-membership consortium which develops and maintains computer industry specifications.*OMG maintains active relationships with many other standards bodies and consortia. [ISO,OASIS, IEEE, W3C, THE Open GROUP, AIIM International, STAR, and INCOSE] For more information please see http://www.omg.org/news/about/liaison.htm*OMG’s best known Successes: [http://www.omg.org/gettingstarted/specintro.htm]-Common Object Request Broker Architecture (CORBA®)-Unified Modeling Language (UML)-Common Warehouse Metamodel (CWM)-Meta-Object Facility(MOF)- XML Metadata Interchange- XMI, the XML-UML standardMicrosoft Joins OMG:- September 10, 2008, Microsoft announced its membership in the standards body Object Management Group™ (OMG™). [http://www.microsoft.com/presspass/press/2008/sep08/09-10OMGModelingPR.mspx]
• #7: UML® Resource Page: http://www.uml.org/UML Specification:http://www.omg.org/technology/documents/modeling_spec_catalog.htm#UMLIntroduction to OMG's Unified Modeling Language™ (UML®)http://www.omg.org/gettingstarted/what_is_uml.htm
• #8: A diagram is a view into a model. UMLdefines thirteen types of diagrams, divided into three categories: Six diagram types represent static application structure; three represent general types of behavior; and four represent different aspects of interactions:*Structure Diagrams include the Class Diagram, Object Diagram, Component Diagram, Composite Structure Diagram, Package Diagram, and Deployment Diagram. *Behavior Diagrams include the Use Case Diagram (used by some methodologies during requirements gathering); Activity Diagram, and State Machine Diagram. *Interaction Diagrams, all derived from the more general Behavior Diagram, include the Sequence Diagram, Communication Diagram, Timing Diagram, and Interaction Overview Diagram.
• #9: A diagram is a view into a model. UMLdefines thirteen types of diagrams, divided into three categories: Six diagram types represent static application structure; three represent general types of behavior; and four represent different aspects of interactions:*Structure Diagrams include the Class Diagram, Object Diagram, Component Diagram, Composite Structure Diagram, Package Diagram, and Deployment Diagram. *Behavior Diagrams include the Use Case Diagram (used by some methodologies during requirements gathering); Activity Diagram, and State Machine Diagram. *Interaction Diagrams, all derived from the more general Behavior Diagram, include the Sequence Diagram, Communication Diagram, Timing Diagram, and Interaction Overview Diagram.
• #11: Butterfly Effect is the phenomenon that happens when you make a change in one area of your code and something unforeseen happens somewhere else. Architecture Explorer This overall feature gives you the ability to explorer and visualize your solution / projects inside Visual Studio, allowing you to reason over various questions you may have: \"How is this class dependent on this other?\" \"What assemblies does this assembly reference?\" \"How many lines of code in this method?\" Reference: http://blogs.msdn.com/bharry/archive/2008/06/05/teched-2008-keynote.aspXStandard\" Graphs Common views of your system. In the 2010 CTP, you'll see three menus in the \"Analyze\" menu item, as well as from the Architecture Explorer tool window, seen here: From the \"Analyze\" top level Menu: From the Architecture Explorer toolbar: Selecting any of these menus will result in dependency graphs between Assemblies, Namespaces, or classes. By the time we RTM, we expect to have a few more. Reference:  http://blogs.msdn.com/camerons/Default.aspx?p=2#Understand
• #12: Reference: http://blogs.msdn.com/bharry/archive/2008/06/05/teched-2008-keynote.aspXThe layer diagram allows you to design the logical layering of your application and specify the dependencies you intend to have.  For example, you wouldn't want your client to have a dependency on you data layer in a 3 tier app.  You wouldn't want your server business logic taking a dependency on something in the Windows.Forms assembly, etc.Once you have this logical layering, you can associate the layers with specific assemblies, namespaces or classes in your actual application.  Now, the magic happens.  VSTS can parse/reverse engineer your code to determine the \"actual\" dependencies in your application.  Having done this, it can compare the actual to the \"desired\" as specified in the layer diagram and let you know about any problems you have.  Going even further, you can configure a checkin policy to validate this on every single checkin.  This way you can prevent people from checking in spaghetti architecture in the first place.It's very hard to communicate an architecture to everyone on the team.  It's even harder to prevent them from accidentally violating the architecture.  These tools are a huge leap forward in ensuring that you end up with the architecture you designed.On top of this cool new layer diagram and validation is another feature called the \"Architecture Explorer\".  It is a very handy tool for visualizing the architecture your code implements today.  It allows you to graphically browse through your application and its dependencies and understand them.  As you update your code, you can see the Architecture Explorer diagrams change.