TEMPLATE DESIGN © 2008 www.PosterPresentations.com The WareHouse Web Application George Kour and Hanny Danial. Supervisor: Viktor Kulikov Networked Software Laboratory. Technion - Israel Institution of Technology Abstract Application Design Layer 0 - Database Data Structure Diagram Layer 2 - Business Logic Layer Application Security The warehouse application was designed to give a full solution to the warehouse employees and manager. It gives them the ability to manage the warehouse components, Items, users, customers and deliveries. The main objective of this project is to get the experience of programming in a web based environment which includes a database, using the most popular and common design pattern for such software, the 3-tier design. This project was developed using the most advanced programming tools. Web 2.0 components, .Net 3.5 frameworks, ASP.Net, AJAX technology and more. Through the development process we have emphasized the working procedures and the project management. We have set a clear timelines and milestones, defined a defects handling procedures, etc. In addition, we have written many wiki pages to help documenting our work. Like in real life projects, the system security was one of our top concerns. •Source Management •Google Code •Tortoise SVN •Database •Microsoft SQL Server 2005 •.Net Environment •Visual Studio 2008 •ASP .Net •C# •ADO .Net •AJAX Technologies Work Environment & Technologies Layer 3: Web User Interface Layer 2: C# classes. Layer 1: ADO.Net Datasets Layer 0: MSQL Server 2005 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. Entity Relationship Diagram •Written in C# •Separates the user Interface from the DAL layer •Enforces Business rules. •Exception handling. Layer 1 - Data Access Layer BLL Class Diagram •Working Procedures. •Screen Recording - WebEx •Google Code •Defects/Issues Handling •Wiki Pages •Downloads Sections •SVN •Revisions Management •working simultaneously Project Management Project Defects Handling In Google Code Wiki Pages In Google Code •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 Layer 3 – Web User Interface
The WareHouse Web Application George Kour and Hanny Danial. Supervisor: Viktor Kulikov
Feb 14, 2016
The WareHouse Web Application George Kour and Hanny Danial. Supervisor: Viktor Kulikov Networked Software Laboratory. Technion - Israel Institution of Technology. Application Design. Layer 1 - Data Access Layer. Work Environment & Technologies. Source Management Google Code - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
TEMPLATE DESIGN © 2008
www.PosterPresentations.com
The WareHouse Web ApplicationGeorge Kour and Hanny Danial. Supervisor: Viktor KulikovNetworked Software Laboratory. Technion - Israel Institution of Technology
Abstract
Application Design
Layer 0 - Database
Data Structure Diagram
Layer 2 - Business Logic Layer
Application Security
The warehouse application was designed to give a full solution to the warehouse employees and manager. It gives them the ability to manage the warehouse components, Items, users, customers and deliveries.The main objective of this project is to get the experience of programming in a web based environment which includes a database, using the most popular and common design pattern for such software, the 3-tier design.
This project was developed using the most advanced programming tools. Web 2.0 components, .Net 3.5 frameworks, ASP.Net, AJAX technology and more.
Through the development process we have emphasized the working procedures and the project management. We have set a clear timelines and milestones, defined a defects handling procedures, etc. In addition, we have written many wiki pages to help documenting our work.Like in real life projects, the system security was one of our top concerns.
•Source Management•Google Code•Tortoise SVN
•Database•Microsoft SQL Server 2005
• .Net Environment•Visual Studio 2008•ASP .Net•C#•ADO .Net
•AJAX Technologies
Work Environment & Technologies
Layer 3: Web User Interface
Layer 2: C# classes.
Layer 1: ADO.Net Datasets
Layer 0: MSQL Server 2005
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.
Entity Relationship Diagram
•Written in C#•Separates the user Interface from the DAL layer•Enforces Business rules.•Exception handling.
Layer 1 - Data Access Layer
BLL Class Diagram•Working Procedures.•Screen Recording - WebEx•Google Code•Defects/Issues Handling •Wiki Pages•Downloads Sections
•SVN•Revisions Management•working simultaneously
Project Management
Project Defects Handling In Google Code
Wiki Pages In Google Code
•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)
Layer 3 – Web User Interface
Related Documents
