60 likes | 169 Vues
This document explores the similarities between architecture styles and patterns in software design. It highlights the importance of separating data from presentation and control from presentation, thereby allowing for multiple views and controllers. The Model-View-Controller (MVC) framework is discussed, with links to resources that cover its use and potential pitfalls. Essential architecture patterns, their attributes, and next steps for further exploration are also outlined. Learn to create architecture tables based on established reports to enhance your design workflow.
E N D
CPSC 875 John D. McGregor Class 6 – Design Concept
Styles and patterns • An architecture style and a pattern are very similar • A pattern may have more information, particularly more information about trade-offs among attributes.
Model-View-Controller • http://www.enode.com/x/markup/tutorial/mvc.html • http://msdn.microsoft.com/en-us/library/ff649643.aspx • As anti-pattern • http://broadcast.oreilly.com/2008/10/mvc-as-anti-pattern.html
What are the essentials? • Separation of data from presentation • Have multiple views • Separation of control from presentation • Have multiple controllers • Attributes • Extensible
Pipeline • http://msdn.microsoft.com/en-us/library/ff963548.aspx
Next steps • Search for architecture patterns (some are already in the EPF) • Create the table as shown on page 30 of the tech report CMU/SEI-2006-TR-023. • Submit via email prior to 6am next Thursday. • Watch the video at • https://webcast.stsci.edu/webcast/detail.xhtml?talkid=2246&parent=1