Helium - Web App Architecture

Project Overview

The client for this project runs a business where they fill and ship containers of liquid helium.  The current process of planning and scheduling container fills and shipments is partially done via their existing web application (ASP.NET 3.5), but it also includes manual steps.  The goal for this project is to build a new Production Planning web application that works with the existing web app and removes the manual steps in the process of creating the “Fill and Ship” schedule.

For this challenge, we need you to design the architecture for the new Production Planning web application.  Details and requirements for this application are described in the attached documents (Conceptualization, Wireframes, and Architecture Questionnaire).  

We look forward to seeing your architecture designs!

 

Project Description:

The client for this project runs a business where they fill and ship containers of liquid helium.  The current process of planning and scheduling container fills and shipments includes manual steps, such as adding data to Excel files.  For this project, the client is looking to create a web application that fits into their existing system and can be used to eliminate these manual steps and streamline the process of production planning for their liquid helium business.

The existing logistics planning system uses a combination of manual processes, including data from paper/excel spreadsheets and live data in the client’s existing production logistics system.  This current logistics system collects data from existing, client facing systems and orders entered via an order entry system.  All of this data will need to be consumed by the new web application.

On a weekly basis in the current process (or somewhat real-time when conditions change), logistics personnel will gather data from multiple different sources and make a draft schedule. If everything appears good with that draft schedule, they will create a “fill and ship” schedule to deliver to the client’s plants. This schedule tells the plant employees what container to fill, for which customer, and when to ship it. The plant employees are sent repeated schedules if there are any changes from unforeseen conditions.

The new web application will need to integrate with the existing systems and fill in the gaps where manual steps are currently involved.  The end product produced by the system will be the fill and ship schedule.

Competition Task Overview

Using the provided documentation, competitors will complete the architecture deliverables (https://apps.topcoder.com/wiki/display/tc/Module+Architecture+Tutorial+-+Deliverables).

Detailed Requirements

1. Application Design Specification
2. Entity Relationship Diagram(s)
3. Sequence Diagrams
4. Interface Diagrams
5. Assembly Specifications

NOTE: Game and Integration plans are required

IMPORTANT: For building classes to access the database, the client requires following a very standard way of dealing with the class. We've attached a sample class for the architects to work with. We have also attached a simple tool that can help you get started with a sample class. This tool will read the database table from a connection string and then create a class in the appropriate format. This is an incomplete class as it has no delete method as well as it is probably not feature complete, however, this format is the starting point used to complete the class. 

Technology Overview

Windows 2008 R2 / IIS / ASP.NET / .NET 3.5 - See the attached Architecture Questionnaire for full technical details.

Documentation Provided

1) Architecture_Technical_Questionnaire.doc: Document with technical details about this project.
2) Wireframes: Screens from the existing application.  Your Storyboard Design should be based on this.
3) Conceptualization v2 - Helium Production Planning App - 7-31-14.zip:  Conceptualization Document explaining the project and new application requirements.
4) Existing App Screen Shots.docx:  Screenshots from the existing application.
5) DivingGasCustomers.cs - A sample class that demonstrates the standard way that must be followed to build classes to access the database
6) TableToClassMaker.exe - A simple tool that can help you get started with a sample class. This tool will read the database table from a connection string and then create a class in the appropriate format. This is an incomplete class as it has no delete method as well as it is probably not feature complete, however, this format is the starting point used to complete the class. 

Final Submission Guidelines

Submission Deliverables

1. Application Design Specification
2. Entity Relationship Diagram(s)
3. Sequence Diagrams
4. Interface Diagrams
5. Assembly Specifications

NOTE: Game and Integration plans are required

Submission Guidelines

For each member, the final submission should be uploaded to the Online Review Tool.