1. R.A.P.S Dan Hudlow Kyle Lee Mike Fisher Brad Justice Team no. 3

2. Content Overview Business Objectives System Objectives Project Objectives Assumptions and Constraints

3. Content Project Schedule Project Context UML Diagram Sample Components ◦ Logging in ◦ Browsing product inventory ◦ Searching Next Steps Questions

4. Overview Task: design, implement, and test a complete store management and online ordering system to satisfy the expansion requirements of an auto parts retailer. Users: customers, retail employees, and managers. Development Model: Evolutionary

5. Business Objectives Online ordering Shopping cart functionality Customer history Employee management Three employee access levels Transaction processing Search functionality

6. System Objectives Web-based: PHP Database: MySQL DBMS Connectivity: Dreamhost.net

7. Project Objectives Implement RAPS with open source technologies for lower software costs and higher transparency Design site for cross-browser compatibility

8. Assumptions and Constraints Assumptions ◦ Network issues not our responsibility ◦ Ignore legal concerns ◦ Ignore personnel specific activities ◦ Ignore post project maintenance Constraints ◦ Lack of web development expertise ◦ Time management issues  All team members full-time university students

9. Project Schedule Phase I: Sept. 17, 2008 ◦ Scope and Initiation Phase II: Oct. 8, 2008 ◦ All non-code artifacts Phase III: Dec. 3, 2008 ◦ Final product ◦ Demo

10. Project Context

11. Mockup

12. UML Class Diagram

13. Sample Components: Accessing the System

14. System Access Compatibility: ◦ Internet Explorer ◦ Mozilla Firefox ◦ Safari Requirements For employee-level access: ◦ Login required ◦ For customers browsing: ◦ No login required ◦ Customers making a purchase: ◦ Login/registration required Security ◦ Passwords stored as MD5 hashes

15. User Account Types Customer ◦ Make purchases ◦ View history Trainee ◦ Generate reports ◦ View inventory Employee ◦ Manage customer data ◦ Manipulate store inventory Master ◦ Manage employee user accounts ◦ Store account creation

16. Use Cases Use Case DescriptionR = requirement; A = assumption; C = constraint How does a customer log in to the system?R1: The customer will bring up the system and view the entry screen. R2: The customer will click the “Customer login” link. A1: The customer is not required to log in prior to checking out, but the option is available. R3: The customer will enter their username and password. C1: If an incorrect username or password is entered 4 times, the user will be locked out of the system. R4: After successfully logging in, the customer is returned to the main page. How does an employee log in to the system?R1: The employee will bring up the system and view the entry screen. R2: The employee will click the “Employee login” link. R3: The employee will enter their username/password. R4: After successfully logging in, the employee is sent to the Operations page.

17. Login State Diagram

18. Sample Component: Performing Product Searches

19. Searching Bad input (i.e., with invalid characters) will be rejected The user may search within a single category or all categories Searching is available at all user access levels Search by product type or product ID

20. Search: Use Case Use Case DescriptionR = requirement; A = assumption; C = constraint How does a user perform a search? R1: The search field is displayed on the index page as well as all pages not involved in checkout A1: Invalid strings (i.e., those containing characters not allowed in names) are rejected. R2: The user may search within a category or the entire database. R3: The search returns a formatted page with matching products and descriptions. C1: Without using search algorithm, results may not be exact

21. Search State Diagram

22. Sample Component: Browsing the Inventory

23. Browsing the Inventory Browsing is available to all access levels Browse by category Browse all products

24. Browse: Use Case Use Case DescriptionR = requirement; A = assumption; C = constraint How does a user browse the inventory? R1: Customer goes to site index for top- level selection A1: Customer does not need to log in to browse. R2: Customer may browse by product category. A2: Customer may also browse all products by selection “all products” category. A3: A search field will be provided for more specific browsing. C1: No product images will be supported.

25. Browsing: State Diagram

26. Next Steps Familiarize team with MySQL/PHP Design site layout Start coding

27. Questions?