Intuitive Technology Consulting

1. Intuitive Technology Consulting Jeremy Anderson Christina Foy Sarah Freeman Paul Jameson Adrienne Johnson Pritam Pun

2. Presentation Overview • Systems Requirements Specifications • E-R Diagram • Logical Database Design • Use Cases • Data Flow Diagrams • Updated Work Plan/ Gantt Chart

3. System Requirements Specification

4. Systems Requirements Specifications • Introduction • Purpose • Detailed description • Intended Audience • Users of the to-be system • Scope • Automating hand written processes for a reduction in costs • Reference • http://business.latech.edu/~CIS450/winter_11/ITC/index.htm

5. Systems Requirements Specifications • Overall Description • Product Perspective • Automate all processes with scheduling and billing • Product Features • Users will be able to schedule appointments and input client data into a client database system. • Users will be able to verify insurance claims electronically. • Users will be able to bill clients automatically after appointments.

6. Systems Requirement Specifications • Overall Description (Continued) • Assumptions • Intuitive Technology Consulting will have ample time to implement the system and train the users to properly operate the system. • ITC has the technological knowledge to develop the entire system in-house with proper funding. • Family Consumer Services will be able to fund ITC if we have to purchase any outside programming assistance. • Family Consumer Services will also purchase any hardware needed for the system. • User Classes

7. Systems Requirements Specifications • System Features • User Requirements • Scheduling System (only a few listed) • System must allow secretary to input client information • System must allow secretary to modify client information • Insurance Claims System • System must allow employee to send claim to Insurance Provider • System must allow employee to verify insurance coverage • Billing System (only a few listed) • System must allow secretary to bill total amount to clients • System must allow secretary to accept payments

8. Systems Requirements Specifications • System Features • Functional Requirements • Scheduling System (Only a few listed) • Must accept manual input of client information • Must accept manual deletion of client information • Must allow search query by client name • Insurance Claims System (Only a few listed) • Must allow employee to send claim to insurance provider • Must allow feedback from insurance provider • Must accept coverage from insurance provider • Billing System (Only a few listed) • Must accept check as form of payment • Must accept credit as form of payment • Must create invoice

9. Systems Requirements Specifications • System Features • Non-functional Requirements • Operational • System should interface with mobile device access • Performance: • System must support a staff of 7 employees • System must update client information when payment is received. • System must perform automatic online backup of client information every month • Security: • Employee must have unique login ID to access the system

10. Database

11. Database • E-R Diagram

12. Database • Logical Diagram

13. Use Cases and DFD’s

14. Use Cases- Add Client

15. Use Cases –Update Client

16. Use Cases- Create Appointment

17. Use Cases- Modify Appointment

18. Use Cases –Cancel Appointment

19. Use Cases- File Insurance Claim

20. Use Cases- Bill Clients

21. Use Cases- Access Files via Technology

22. DFD’s- Context Diagram

23. DFD’s – Process 1 Level 1

24. DFD’s Level 2

25. DFD’s – Process 2 Level 1

26. DFD’s Process 3 level 1

27. DFD’s Process 4 Level 1

28. Updated Work Plan/ Gantt Chart

29. Work Plan

30. Gantt Chart

31. Questions?