{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

6310Intro - 6310

Info iconThis preview shows pages 1–6. Sign up to view the full content.

View Full Document Right Arrow Icon
Basic elements Reading Architecture Design Patterns Testing
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Reading Spinellis and Gousios, Beautiful Architecture , O'Reilly Media, 2009, 978-0-596-51798-4: read Foreword (by Stephen J Mellor) Available through Safari (thanks to Prof. Holz for the pointer) http://library.csueastbay.edu/ , then click on “Databases A-Z”, scroll down to find Safari link Search for “Beautiful Architecture” (and “Eclipse”)
Background image of page 2
Architecture How does software architecture compare to architecture for buildings? Why are class/function definitions not architectural issues? Goal: make architecture useful It helps guide assignment of responsibilities It can significantly affect performance, maintenance [what is “maintenance” in software engineering?]
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Basic design principles Loose coupling Avoid unnecessary dependencies between program or design components High cohesion Components should have well-defined responsibilities Components should represent fewer different ideas
Background image of page 4
Basic architectural principles Model-view separation What is this? Why is it desirable?
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Image of page 6
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}