System design presentation

33
System Design Presentation Haley Asher & Dave Katz

description

 

Transcript of System design presentation

Page 1: System design presentation

System Design Presentation

Haley Asher&

Dave Katz

Page 2: System design presentation

The project that we are working on is a system for tracking and planning the work done for the feeding hungry pets program.

Costs for the remaining phases will be the cost of database software and database creation.

The benefits of the new system will be an organized and central database where all the information for the program is based, and any questions about the part of the program can be answered by being looked up in the database.

Management Summery

Page 3: System design presentation

Program Design Output Design Input Design File and Database Design Support Processing Design

System Components

Page 4: System design presentation

All we are storing is data, so a database is the logical choice for simple easy to use system for storing and retrieving data as needed.

Information about the volunteers, the customers, and scheduling will all be stored, for lookup at any time.

Program Design

Page 5: System design presentation

Several different forms of output could be utilized.

The main output form is that of the display screen of the computer hosting the database system.

Other forms of output could include e-mail notification and other forms of accessing the database information such as a wireless device

Output Design

Page 6: System design presentation

Input would be the main computer which is used to interface the database.

There is no need for any other forms of input, except for maybe a wireless device access

Input Design

Page 7: System design presentation

The database will include volunteers and their information, including contact information and history of activities they have done for the program.

Also the customer information will be stored, as well as their history of what they have or are currently receiving from the program for aid.

These will be organized lookup tables, and with the proper assigned relationship bringing everything together.

File and Database Design

Page 8: System design presentation

Support processing for this system would be a computer capable of running office software, and an operator capable of entering and retrieving data, as well as maintaining the database.

Support Processing Design

Page 9: System design presentation

A computer capable of handling office software will be required.

It must have adequate processing power and plenty of storage.

A minimum of 1 terabyte of storage should be in the computer and a backup system will need to be present as well.

Database software will be required, and the computer will need to be secured to protect the customer and volunteer personal information

Environmental Requiremnts

Page 10: System design presentation

Start up processing will include the collection of needed data and initial entry as well as database configuration.

The operator who will be working with the data will need to be trained in operation of the database software.

The required information will be retrieved from the customers and volunteers, and entered into their respective places in the database system.

Implementation Requirements

Page 11: System design presentation

Time and cost include training of users, software and hardware cost, and a database administrator to operate and maintain the data, as well as keep it secure.

$1000-Desktop computer (including required accessories)

$200-Backup storage system

$200-Database software

Time and Cost Estimates

The manager running the program may work as the database administrator, or outsource this job to an employee hired specifically for this task.

Page 12: System design presentation

System Design

Page 13: System design presentation

Types of Outputs

•Email

•Blogs

•Instant Messaging

•Wireless Devices

Page 14: System design presentation

Detail Report with one printed line per employee

Types Of Reports

Page 15: System design presentation

Detail report contains the same data but provides more information. Control breaks are used to separate the data for each store, with

subtotals and grand totals.

Detail Report

Page 16: System design presentation

Exception Reports

•Exception report shows information only for volunteers who worked overtime

Page 17: System design presentation

Summary Report

•Summary report displays totals without showing details.

Page 18: System design presentation

Report Design Principles

Page 19: System design presentation

Improved Version of Report

Page 20: System design presentation

Tasks, commands, and functions should organized in logical groups

Order Tracking System

Page 21: System design presentation

Data DesignEntity-Relationship Diagrams

Page 22: System design presentation

Entity-Relationship Diagram

Page 23: System design presentation

One to One Relationship

Page 24: System design presentation

One to Many Relationship

Page 25: System design presentation

Many to Many Relationship

Page 26: System design presentation

Sales System

Page 27: System design presentation

One and only one CUSTOMER can place anywhere from zero to many of the ORDER entity.

One and only one ORDER can include one ITEM ORDERED or many.

One and only one VOLUNTEER can have one PARTNER or NONE.

One VOLUNTEER, or many volunteers, or none, can be assigned to one PROJECT, or many projects, or none.

Cardinality Notation

Page 28: System design presentation

Normalization

Page 29: System design presentation

Unnormalized

Order(Unnormalized)

Primary key Primary key for repeating group

Repeating groups

Page 30: System design presentation

First Normal Form

Order in 1NFCombination primary key

Repeating groups have been eliminated

Page 31: System design presentation

Second Normal Form

Order in 2NF

Product in 2NF

Order Line in 2NF

Primary Key

Primary Key based on combination of two fields

Primary Key

Page 32: System design presentation

Third Normal Form

Customer in 3NF

Sales-Rep in 3NF

In 3NF, no nonkey field is dependent on another nonkey field

Page 33: System design presentation

Initial Entity-Relationship