Technical Innovations Presentation Two

Overview  Data Models  Entity Relationship Diagram  Logical Database Design  Data Dictionary  Process Models  Data Flow Diagrams  Use Cases  System Requirements Specification  Scope  Functional Requirements  Non-Functional Requirements

Entity Relationship Diagram(ERD)

Logical Database Design

Data Dictionary

Data Flow Diagrams

National Tint and Trim requires an information system that will integrate website functionality with inventory automation, appointment scheduling, online quoting, tracking consumer buyer statistics, and improving customer service. This will allow customers an ease of access to the information while improving the company’s image. This will be accomplished by integrating the business and suppliers through a central database. Scope

Functional Requirements  Online inventory search  Record consumer statistics  Online appointment scheduling  Provide inventory information  Online quoting  Checkout process

Online Inventory Search 1.1) The system will provide the customer with the available inventory. 1.2) The system will narrow the inventory available to customers vehicle specifications. 1.3) The system will allow the customer to compare product specification.

Record Consumer Statistics 2.1) The system will record purchased inventory ordered by consumer. 2.2) The system will track consumer quarterly trends. 2.3) The system will record consumer demographics.

Online Appointment Scheduling 3.1) The system will provide list of available times. 3.2) The system will send a notification to consumer about scheduled appointment.

Provide Inventory Automation 4.1) The system will track inventory levels 4.2) The system will reorder inventory when minimum levels are met.

Online Quoting 5.1) The system will narrow the inventory available to customers vehicle specifications. 5.2) The system will calculate the item’s price, tax, and installation.

Checkout Process 6.1) The system will process the customers payment. 6.2) The system will authorize payment and validation. 6.3) The system will issue a receipt after finish transaction. 6.4) The system will track all sales transactions for future reference.

Non-Functional Requirements  Operational  Performance  Security  Culture/Political

Operational 1.1) The system should run on all smart phones 1.2) The system should work on all operations systems 1.3) The system should be compatible on all popular browsers 1.4) The system should be able to print from multiple in-store printers

Performance 2.1) The system should support a sale staff of at least 10 people. 2.2) The system should update automatically every (7) seven minutes. 2.3) The system should only perform backup maintenance between 3 am - 5am. 2.4) The system should be able to simultaneously support 50 requests. 2.5) The website should be accessible within.703 seconds

Security 3.1) The system will only allow store managers administrator access 3.2) Customers are assigned a username and ID to view history and make purchases 3.3) The system passwords cannot be retrieved only reset 3.4) The system includes all available safeguards against viruses, worms, and Trojan horses 3.5) The system should utilize HTTPS during checkout

Culture/Political 4.1) The system will allow only American currency. 4.2) The system will allow multiple languages for interpretation. 4.3) The system must adhere to all governmental laws: networking, financial, and privacy.

Summary  Data Models  Entity Relationship Diagram  Logical Database Design  Data Dictionary  Process Models  Data Flow Diagrams  Use Cases  System Requirements Specification  Functional Requirements  Non-Functional Requirements

Questions?