1. SA Capstone Requirements and Design Week 6 SYST36367 - Winter 2017
Some slides adapted from:
Systems Analysis and Design in a Changing World, 6th Edition, Satzinger, Jackson, Burd, CENGAGE Learning, 2012

2. Systems Analysis and Design in a Changing World, 6th Edition
Two Levels of Design
Architectural Design
High Level Design
Design Patterns
Goal is to build well structured and MAINTAINABLE code
Get away from spaghetti code
Systems Analysis and Design in a Changing World, 6th Edition

3. Software Components and Frameworks
Time to Market is paramount in today’s competitive marketplace
Selecting powerful and tested frameworks and components can save lots of development time
Systems Analysts often need to participate in “Buy versus Build” decisions regarding components and frameworks
Capstone is designed to reflect industry best practices. So your team should look for components and frameworks that can speed your development and improve your product!
Past groups have used several components and frameworks including:
CakePHP, Yii, jQuery, Bootstrap, HTML5, PhoneGap, Google Web Toolkit (GWT), Microsoft Entity Framework, ASP.NET MVC, ASP.NET AJAX Control Toolkit, Crystal Reports, etc.

4. Software Design Patterns
Design patterns became widely accepted after the publication of Elements of Reusable Object-Oriented Software,(1996) by Gamma et al (the “Gang of Four”)
A common architectural design pattern:
Three layer or model-view-controller architecture
Systems Analysis and Design in a Changing World, 6th Edition

5. Three Layer Architecture
Three Layer Client-Server Architecture
a client/server architecture that divides an application into view layer, business logic layer, and data layer
View layer
the part of the three-layer architecture that contains the user interface
Business logic layer or domain layer
the part of a three-layer architecture that contains the programs that implement the business rules and processes
Data layer
the part of a three-layer architecture that interacts with the data store
Systems Analysis and Design in a Changing World, 6th Edition

6. Systems Analysis and Design in a Changing World, 6th Edition

7. Systems Analysis and Design in a Changing World, 6th Edition
Michael Angelos Software Architecture
Systems Analysis and Design in a Changing World, 6th Edition

8. Systems Analysis and Design in a Changing World, 6th Edition
PCIM System Architecture
Systems Analysis and Design in a Changing World, 6th Edition

9. Programming Design Patterns
The first example of a programming design pattern shown is the Controller Pattern.
Problem is deciding how to handle all of the messages from the view layer to classes in the problem domain layer to reduce coupling
Solution is to assign one class between the view layer and the problem domain layer that receives all messages and acts as a switchboard directing messages to the problem domain
Systems Analysis and Design in a Changing World, 6th Edition

10. Systems Analysis and Design in a Changing World, 6th Edition
Controller Pattern First step toward multilayer architecture More design patterns are at the end of the chapter
Reduce coupling between view layer and problem domain/business layer classes
Acts as a intermediary between outside world and internal system
Acts as a switchboard
Systems Analysis and Design in a Changing World, 6th Edition

11. Sheridan Design OptionsVM
Windows Server 2012R2 Standard
Ubuntu Linux LTS
LAMP + GIT
Systems Analysis and Design in a Changing World, 6th Edition

12. Hosting Alternatives for Internet Deployment
Sheridan Hosting:
Limited options
Support, Familiar Environment
Cloud Hosting
Azure, AWS
Cost, learning curve
Control flexibility
Consider making sure your hosting is done on Canadian servers to ensure your data is subject to Canadian laws
Systems Analysis and Design in a Changing World, 6th Edition