1 / 15

Pattel SDD

Pattel SDD. Andrew Miles Brian Bogovich Chris Fleenor Dan Harrington. Pattern – A pattern is an empirically tested solution to a recurring problem.

mari-cross
Download Presentation

Pattel SDD

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Pattel SDD Andrew Miles Brian Bogovich Chris Fleenor Dan Harrington

  2. Pattern – A pattern is an empirically tested solution to a recurring problem. Pattern Language - A pattern language is a hierarchical structure of linked patterns that can be navigated to select the subset of patterns appropriate to a particular situation. Our System Introduction

  3. Example Pattern: Building a House - Neighborhood N • Entryway (E) • House (H) • Entryway (E) • Rooms (R) • Entryway (E) • Bedroom (BR) • Closet (C) • Entryway • Bathroom (BA) • Toilet (T) • Kitchen (K) • Stove (S) H R BR BA K E C T S

  4. C BR E BR E C E E E BA T S K E Building a House (cont.) • Use the new pattern language as a basis for designing the finished product

  5. Design Goals • Security: The administrator’s privileges must not be accessible to other users. Administrators have potentially damaging privileges. • Availability: The system will be available to anyone with access to the internet. • Development Cost – The client does not expect to pay any money for the delivery of the system. • Readability – The code of the system will be a deliverable, and the client to have other people maintain the project. The readability of the code is important.

  6. Subsystems • User Interface • Used to interact with the other subsystems • User Manipulation • Responsible for all transactions with the user information • Pattern Manipulation • Responsible for all transactions with the pattern information

  7. Subsystems (cont.) • Search • Responsible for the users search ability • Navigation • Responsible for navigation between linked patterns • Communication • Responsible for all communication with the DB

  8. Subsystems (cont.) • Database • Responsible for keeping all pattern and user information.

  9. Persistent Data Management • Persistent data: patterns and illustrations, and registered user information • Access database used to store patterns and registered user data • Local HD used to store images, animations, and movies • Interfaces and web server stored on a separate HD from the DBMS

  10. Entity Relationship Diagram

  11. Access Control and Security • 2 Types of Users • Administrators • Users

  12. Global Software Control • Event-driven System • User interacts with web-based frontend • System facilitates users request through backend database server • Programming Languages • MS Access database • C# & .ASP components

More Related