1 / 14

SoftLab Project Winter 2008 Supervisor : Victor Kulikov Students : Dmitry Kanevsky Nir Lev-Ari

SoftLab Project Winter 2008 Supervisor : Victor Kulikov Students : Dmitry Kanevsky Nir Lev-Ari. Project goals. Design and implement a modern end-to-end Web Project. Learn C# and the .NET framework. Get acquainted with the Microsoft Web Development environment: Visual Studio

wind
Download Presentation

SoftLab Project Winter 2008 Supervisor : Victor Kulikov Students : Dmitry Kanevsky Nir Lev-Ari

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. SoftLab Project Winter 2008 Supervisor: Victor Kulikov Students: Dmitry Kanevsky Nir Lev-Ari

  2. Project goals • Design and implement a modern end-to-end Web Project. • Learn C# and the .NET framework. • Get acquainted with the Microsoft Web Development environment: • Visual Studio • ASP.NET • ADO.NET • Ajax • SQL server

  3. Project description • “Collections” website which allows users to create and organize their own privet and public collections. • Registered users can manage and present their collections in galleries. • All users can view public galleries and items of others.

  4. Website functionality • User management - Registering, password changing, “deleting”*, updating, adding/removing friends and permissions*. • Group management - Creating*, deleting*, updating*, adding/removing users (for group messages). • Galleries management - Creating, deleting, updating adding/removing items. • Items management - Creating, deleting, searching, updating rating and adding/removing files. *Administrator

  5. Relationship diagram

  6. 3-Layer Design • Reasons for choosing 3-Layer design: • Divide design into layers that have different purposes. • Each layer can be independently maintained and improved, while the connecting interfaces remain unchanged.

  7. 3-Layer Design • DataBase: • Consists of the DBMS (SQL Server), the table data and structure. • Responsible for data type validation, relationship validation, etc. • SQL Server

  8. 3-Layer Design • Relationship diagram: • SQL Server

  9. 3-Layer Design • StoredProcedure: • Interface to the database. • Precompiled  better performance. • Transactions  prevent data corruption. • Return parameters  reduce number of database accesses. • Easy DB access. • SQL Server

  10. 3-Layer Design • Data Access Layer: • Abstraction layer between BLL and DB. • Support for multiple DBMSs. • Automated data auditing. • Connection management. • Hiding of connection strings. • ADO.NET

  11. 3-Layer Design • Business Logic Layer : • Intermediate layer between DAL and PL. • ASP.NET

  12. 3-Layer Design • Presentation Layer: • Ajax Master pages – homogenous look & refresh-less update. • Ajax extensions – dialogs and popup. • User controls – reuse, page replacement. • ASP.NET

  13. Improvements • New media types – we handle only picture types. • Security – add password encryption. • Ajax – file upload, download, popup login… • Item trade – drag & drops Ajax functionality. • Improved Image handling –thumbnail creation. • Email notifications – adding an email authentication. • Cookies – supporting user recognition (preferences). • ASP.NET

  14. Thanks Thanks to softlab staff, Viktor Kulikov and Ilana David - The End -

More Related