eBikes Lab Specs

eBikes Lab - Sep 2018

Completion Requirements

Lab Weight: 40% of the Final Grade

Overview

Bikes R Us® Inc. would like to convert their manual Management System into a set of computerized subsystems that will allow employees to manage various aspects of the business via the Internet. Bikes R Us is a business that has a brick-and-mortar presence that needs to be supported by this application. As such, the application will allow the business to perform the following key business tasks:

Purchasing
The application must allow the business to purchase items for their inventory.
Receiving and Returns
The application must allow shippers/receivers to receive incoming products from suppliers.
Sales
The application must support sales for online customers (a new aspect the business wants to support).
Jobing
The application must support the in-store servicing for bikes.

This lab will be your opportunity to demonstrate your ability to:

  1. Analyze the problem and develop a solution according to the requirements outlined in each subsystem
  2. Create a web-based solution using web application and class library components as presented in this course
  3. Code the necessary parts of the solution using tools and techniques presented in this course (e.g.: LINQ, Entity Framework, transactional processing, user controls, UX design considerations, etc.)
  4. Use version control (using GitHub) as directed by your instructor for the entire set of deliverables for this project

Your instructor will give you recommendations on setting up the project and the naming conventions to use.

Your instructor will act as the Bikes R Us business representative to provide clarification details for your project.

Submission Requirements

This lab is worth 40% of the final grade of the course. This lab is broken into two distinct deliverables, all of which must be demonstrated to your instructor in person in-class. Check your course planning calendar for the specific delivery date. If you are repeating this course, you must select a different subsystem from your previous attempt(s) at this course. Failure to do so will result in a mark of zero (0).

  • 15 % Week 12 - Project Setup, Security and Subsystem Design -
    • Purchasing - The application must allow the business to purchase items for their inventory. **Marking Sheet
    • Receiving - The application must allow shippers/receivers to receive incoming products from suppliers.Marking Sheet
    • Sales - The application must support sales for online customers (a new aspect the business wants to support).Marking Sheet
    • Jobing - The application must support the in-store servicing for bikes.Marking Sheet
  • 25 % Week 15 - Final Solution
    • Purchasing - The application must allow the business to purchase items for their inventory. Marking Sheet
    • Receiving - The application must allow shippers/receivers to receive incoming products from suppliers.Marking Sheet
    • Sales - The application must support sales for online customers (a new aspect the business wants to support). Marking Sheet
    • Jobing - The application must support the in-store servicing for bikes.Marking Sheet

Deliverables

Project Setup, Security and Subsystem Design Deliverable

This deliverable consists of 1) all Shared Components are correctly set up and working 2) a working security implementation for the site, along with a Site Administration page to manage users/roles of Employees, and 3) subsystem designs for each student's component. Subsystem designs must include screen designs, notes about the anticipated Asp.Net control types to be used on the page to generate the UI (User Interface) as well as a mapping of the BLL methods that will be called to handle the queries and commands required for the UI. All screens must display the currently logged on employee name (first and lastname) in a read-only text string.

Note: For the working security implementation, you will likely need to adjust the supplied security components generated when you created your web application. Also add any boilerplate code to support security roles, constructing default roles and users, etc. Ensure that the web application has a site administration page to view and manage the site's users and security roles.

Final Solution Deliverable

All the remaining implementation requirements of the lab, as detailed in the rest of this specification documentation.