Upload
spencer-watson
View
217
Download
3
Tags:
Embed Size (px)
Citation preview
ContentContentOverviewBusiness ObjectivesSystem ObjectivesProject ObjectivesAssumptions and Constraints
ContentContentProject ScheduleProject ContextUML DiagramSample Components
◦Logging in◦Browsing product inventory◦Searching
Next StepsQuestions
OverviewOverviewTask: 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
Business ObjectivesBusiness Objectives
• Online ordering• Shopping cart functionality• Customer history• Employee management• Three employee access levels• Transaction processing• Search functionality
Project ObjectivesProject ObjectivesImplement RAPS with open
source technologies for lower software costs and higher transparency
Design site for cross-browser compatibility
Assumptions and Assumptions and ConstraintsConstraintsAssumptions
◦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
Project ScheduleProject SchedulePhase I: Sept. 17, 2008
◦Scope and InitiationPhase II: Oct. 8, 2008
◦All non-code artifactsPhase III: Dec. 3, 2008
◦Final product◦Demo
System AccessSystem AccessCompatibility:
◦ Internet Explorer◦ Mozilla Firefox◦ Safari
RequirementsFor employee-level access:
◦ Login required
◦For customers browsing:◦ No login required
◦ Customers making a purchase:◦ Login/registration required
Security◦ Passwords stored as MD5 hashes
User Account TypesUser Account TypesCustomer
◦ Make purchases◦ View history
Trainee◦ Generate reports◦ View inventory
Employee◦ Manage customer data◦ Manipulate store inventory
Master◦ Manage employee user accounts◦ Store account creation
Use CasesUse CasesUse Case Description R = 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.
SearchingSearching
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
Search: Use CaseSearch: Use Case
Use Case Description R = 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
Browsing the InventoryBrowsing the InventoryBrowsing is available to all
access levelsBrowse by categoryBrowse all products
Browse: Use CaseBrowse: Use Case
Use Case Description R = 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.