Project Status Review I Sales Management System Team 26 David Jeng (0653) Sophia Yang (3163) James Chan (4777) On-Campus CSCI 588 Fall 05 Introduction – Description – Requirements – Navigation – User Analysis – Design – Main Screen – Prototypes – Conclusion

Topic Description Windows-based sales management system that allows users to track orders in the system in real-time. Interactive map allows users to manipulate icons on the screen to display order and vehicle information in greater details. Provides basic sales management functionalities (all-in-one) such as managing orders/RMAs, customer database, inventory, and tracking capabilities. Enhanced feature to current technology Real-time tracking system compared to static text-based tracking system (www.ups.com). System integrates with GPS and vehicle tracking systems. Introduction – Description – Requirements – Navigation – User Analysis – Design – Main Screen – Prototypes – Conclusion

System Requirements Performance System shall take no longer than 2 seconds to authenticate and log in a user. System shall automatically log off idle users after 10 minutes. Functional System shall allow users to manage customer orders, RMAs, customer database, and inventory. System shall allow real-time tracking of orders/RMAs in the system. System shall allow the user to interact and manipulate the icons and map itself. Interfaces System shall display a graphical map for real-time tracking and geographic location of customers. System shall interface with GPS and vehicle tracking system to retrieve real-time information. System shall be designed as a Windows application using the .NET framework. Introduction – Description – Requirements – Navigation – User Analysis – Design – Main Screen – Prototypes – Conclusion

Navigation Map Login Page Main Menu Order Management Tracking Return Material Authorization (RMA) Customer Information Management Inventory Add new order Order status Add new RMA Add new customer Inventory information/status Current order RMA status Current RMA Check customer Information/Order history Cancel order Cancel RMA Modify customer information Delete existing customer Introduction – Description – Requirements – Navigation – User Analysis – Design – Main Screen – Prototypes – Conclusion

User Analysis Discussion User Profile Cognitive: Spatial/intuitive Attitude: Neutral Motivation: Moderate Reading Level: Above twelfth grade Typing skill: Low System experience: Moderate/Novice Education: High school degree Task experience: Application experience: Some Native language: English Use of other system: Little/none Computer Literacy: Frequency of use: Primary training: Mandatory formal System use: Mandatory Job categories: Manager/Sales Turnover rate: Other tools: Telephone/E-mail Task importance: High Task structure: High/Moderate Introduction – Description – Requirements – Navigation – User Analysis – Design – Main Screen – Prototypes – Conclusion

User Analysis Discussion (continued) User Characteristics - Sales people at Wintec - Managers who are responsible for the sales department - Familiarity with interfaces of Windows applications - Familiarity with the sales ordering processes - Familiarity with reading maps Introduction – Description – Requirements – Navigation – User Analysis – Design – Main Screen – Prototypes – Conclusion

User Analysis Discussion (continued) User workload - Regular usage by sales people at Wintec - Generally adding new information into the system and checking the status of them User Environment Office and warehouse Working alone and sometimes with others Desktop computer systems, handheld computers and laptops connected to the company network Introduction – Description – Requirements – Navigation – User Analysis – Design – Main Screen – Prototypes – Conclusion

User Analysis Discussion (continued) Dialog Style Selected Menus Task selections Ease of use Intuitive Fill-in Forms Order/Customer information input Direct manipulation Map Introduction – Description – Requirements – Navigation – User Analysis – Design – Main Screen – Prototypes – Conclusion

Order info & confirmation Task Analysis Order & Inventory Management Add/Check/Remove Order Order Management Orders Send request Order info & confirmation Order info & confirmation/failure Sales Personnel In/Out of Stock Item number Inventory Section Item info & status Inventory Management Item number Inventory Item info & status Introduction – Description – Requirements – Navigation – User Analysis – Design – Main Screen – Prototypes – Conclusion

Task Analysis (continued) Tracking & RMA Management Tracking Management Order number Orders Order information Send request Order/RMA information Sales Personnel RMA information RMA number Send request RMA Management Add/Check/Remove RMA RMA info & confirmation RMA RMA info & confirmation Introduction – Description – Requirements – Navigation – User Analysis – Design – Main Screen – Prototypes – Conclusion

Task Analysis (continued) Customer Management Customer Management Customer selection Customer number Sales Personnel Customers Customer information Customer information Introduction – Description – Requirements – Navigation – User Analysis – Design – Main Screen – Prototypes – Conclusion

User Analysis Discussion (continued) I/O Devices Input Keyboard Mouse Output LCD/CRT Monitor

Visual Design General Style Guide All interface designs will be viewable on a minimum screen resolution of 640x480. Standard Windows controls will be used. Upper left corner of each screen will have the Wintec logo. Upper right corner of each screen will have a “Back” button with the exception of the main menu. Center top displays name of the system. Each sub-menu will have a bar across the top that is color-coded with the navigation button’s color. A sub-title of the current task will be displayed Navigation buttons will contain an icon of approximately 48x48 pixels to denote the task/action. Tooltips will be used on all navigation elements. Introduction – Description – Requirements – Navigation – User Analysis – Design – Main Screen – Prototypes – Conclusion

Style Guide (continued) Colors All interfaces should maintain the Wintec theme and colors (e.g. blue, gray, white) at the least. Fonts Consistent fonts are used throughout all screens (e.g. Sans-Serif). Avoid hard-to-read or non-standard fonts such as Calligraph, Papyrus, Script MT Bold, etc… All titles and headings should use a font of size 16 while all other contents should use font size 10. Introduction – Description – Requirements – Navigation – User Analysis – Design – Main Screen – Prototypes – Conclusion

Icons/Symbols Usage Task icons Vehicle identification/markers Orders, RMA, Inventory, etc… Vehicle identification/markers UPS, FedEx, and DHL Destination marker Denote delivery location Map navigation Zoom in and out Introduction – Description – Requirements – Navigation – User Analysis – Design – Main Screen – Prototypes – Conclusion

Main Screen Design Screen divided into three parts: Upper: logo, name of system, log out button, and welcome message for user. Left: message box that provides notifications of important messages. Right: navigation elements. Simple use of colors White background makes reading easier for user. Black text on light color background. Navigation buttons are color-coded. Big buttons for easy selection. Avoids accidental clicks. Introduction – Description – Requirements – Navigation – User Analysis – Design – Main Screen – Prototypes – Conclusion

Login Screen Initial screen displayed by system. User enters login information. Introduction – Description – Requirements – Navigation – User Analysis – Design – Main Screen – Prototypes – Conclusion

Main Menu Provides access to all functions of the system. User clicks on tracking management. Introduction – Description – Requirements – Navigation – User Analysis – Design – Main Screen – Prototypes – Conclusion

Tracking Management All processed orders in the system are displayed. Status bar shows total number of orders, orders in delivery, and orders that have been delivered. User can go back to main menu by clicking on the “Back” button on top right. Switch between orders and RMAs using buttons on left side. To use real-time tracking, user clicks on “View Map” button. Introduction – Description – Requirements – Navigation – User Analysis – Design – Main Screen – Prototypes – Conclusion

Real-Time Tracking Selected item is displayed on map Main icon represented by actual vehicle appearance Green and gold dot represent other deliveries in progress Use simple icon to reduce clutter on map Delivery destination is represented by blue icon with outline of a house. Vehicle status is updated via GPS and vehicle tracking system. Introduction – Description – Requirements – Navigation – User Analysis – Design – Main Screen – Prototypes – Conclusion

Options Menu Right click on icon to display drop-down menu Cancel delivery Send message to delivery driver’s handheld device Hide destination icon on map Introduction – Description – Requirements – Navigation – User Analysis – Design – Main Screen – Prototypes – Conclusion

Zooming User can view map at different zoom level using icons. Automatically recalculates vehicle positions with respect to map view. Introduction – Description – Requirements – Navigation – User Analysis – Design – Main Screen – Prototypes – Conclusion

Customer Relations Management Retrieves list of customers from database system. Retrieves GPS location of customers and displays them on the map denoted by red dots. Introduction – Description – Requirements – Navigation – User Analysis – Design – Main Screen – Prototypes – Conclusion

Tooltips Usage Mouse over red dot (customer) to display customer information in greater details. Introduction – Description – Requirements – Navigation – User Analysis – Design – Main Screen – Prototypes – Conclusion

Edit Customer Information Fill-in forms used to edit customer information Drop-down menus for easy selection Large buttons to avoid accidental clicks Introduction – Description – Requirements – Navigation – User Analysis – Design – Main Screen – Prototypes – Conclusion

Closing Remarks Tools Lessons learned Remaining plans Programming languages: C#, .NET Development environment: Visual Studio .NET 2003, Adobe Photoshop Lessons learned Not as easy as it seems when designing interfaces Design from user’s perspective Remaining plans Improve upon and complete tracking and customer management functionalities Add 3D map feature possibly Implement rest of functionalities Ordering/RMA and inventory Add more icons and visual elements. Slides available online at: http://www-scf.usc.edu/~jameswch/csci588review1.ppt Introduction – Description – Requirements – Navigation – User Analysis – Design – Main Screen – Prototypes – Conclusion