WareHouse Management System

advertisement
Networked Software Systems Laboratory
DEPARTMENT OF ELECTRICAL ENGINNERING, TECHNION
Warehouse Management System
Final Presentation
WINTER 2009 – SUMMER 2009
PRESENTED BY:
George Kour
Hany Danial
SUPERVISOR:
Victor Kulikov
Abstract
Warehouse Management
System is a multi-purpose
solution enables full
control of the warehouse
assets, customers and
users.
Agenda



Requirements
Work Environment & Technologies
Application Design
Layer 0 – Database
 Layer 1 – DAL
 Layer 2 - BLL
 Layer 3 – Web User Interface






Security
Project Management
Documents
Reading Material
Live Demonstration
Project Requirements

System users management



Components management



Report component shortage to the manager
Search for a component
Suppliers management



Add a user to the system
Change user’s password
Find out which supplier supplies a component
Update supplier ‘s address
Dashboard


System admin receives real time updates.
And Monitor system alerts
Project Requirements (Cont.)

Customer management



Lends management



Lend a component to a costumer
Send a loan notification to a customer
Delivery management



Delete a customer
Send a costumer an email
Browse the delivery history
Which user made a specific delivery
Reports Generators & Search Engines


Generate a report from search Results
In each section Users Can perform search with parameters.
Work Environment & Technologies

Source Management



Database


Microsoft SQL Server 2005
.Net Environment





Google Code
Tortoise SVN
Visual Studio 2008
ASP .Net
C#
ADO .Net
AJAX Technologies
Application Design
Layer 3: Web User Interface
Layer 2: C# classes.
Layer 1: ADO.Net Datasets
Layer 0: MSQL Server 2005
Layer 0 - Database
Entity Relationship Diagram
Layer 0 – Database (Cont.)

Guid
 In
each table the primary key is of a type Guid which
generated automatically by the database.

Foreign Keys:
 Relationships
between tables are only via the Guid
fields.

SQL Server
 Concurrency:
optimistic. Managed by DAL.
Data Structure Diagram - update
(Cont.)
Layer 1 - DAL
Layer 2 - BLL

Written in C#

Separates the user Interface from the DAL layer

Enforces Business rules.

Exception handling.
Layer 2 - BLL
Layer 3 – Web User Interface

Asp.Net Pages
 Master

Pages
Asp.Net Components
 Data
Components - Data Grids, details View.
 Standard Components - Button Links, DropDown Lists,
checkBox,…
 Site Map – using XML.
 Navigation Menu.
 Login Control
 Export to excel.
Layer 3 – Web User Interface (Cont.)

AJAX
 Update
Panel
 Update Progress Panel
 Combobox – Auto Complete
 Animation.
 Timers
 Http Editor
Security





Separating Users from Admin module.
Only Admin can perform Application metadata
changes.
Session: The Application Manages the connected
users by state full sessions.
Cookies: Used to remember information about the
user.
Passwords: All passwords are hashed into the
database using one way hashing functions (SHA-1)
Project Management



Working Procedures.
Screen Recording - WebEx.
Google Code
 Defects/Issues
Handling.
 Wiki
Pages
 Downloads Sections

SVN
 Revisions
Management
 working simultaneously
PROJECT MANAGEMENT DEMO
Google Projects
Documents
Project Book
User Manual
Reading Material

www.asp.net

toturials




Vidoes





Data Access
Security
Design Pattern
Master Pages
Events and Postbacks
Web Application State
www.asp.net/ajax
Forums







Bytes
ASP.Net
ADO.Net
Social.msdn
C# Corner
EggHead
Stack Overflow
LIVE DEMONSTRATION
THANK YOU FOR LISTENING
We Need a grade before December 
Download