1 / 29

e-Restaurant

e-Restaurant. Supervisor: Nguyễn hồng kỳ. 1. Introduction add Title. 2. Project management plan lick to add Title. 7. 3. Requirement Specifications. Demo & Q&A. 4. Design Description to add Title. 5. 6. Testing. Implementation Title. Contents. Background add Title.

rafal
Download Presentation

e-Restaurant

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. e-Restaurant Supervisor: Nguyễnhồngkỳ

  2. 1 Introductionadd Title 2 Project management plan lick to add Title 7 3 Requirement Specifications Demo & Q&A 4 Design Description to add Title 5 6 Testing Implementation Title Contents 3TC Company

  3. Background add Title Literature Review Our Proposal 1. Introduction Company Logo

  4. Project Planning • Project organization Process Model • Development Environment 2. Project management plan Company Logo

  5. Development Environment 2. Project management plan • Hardware • Operating system: Windows 7 • Software • Visual Studio 2010 • SQL Server 2008 • Web Server: IIS 7 • Office 2010 Company Logo

  6. Process Model 2. Project management plan V-Model Company Logo

  7. Project organization 2. Project management plan Company Logo

  8. Project Planning 2. Project management plan • Schedule Management • Resource Management • Communications management • Risk management Company Logo

  9. Non-functional requirements • User Requirements • System Requirements 3. Requirement Specifications Company Logo

  10. 3.1 User Requirements • Website : • Customers : • View information on the website. Example : News, Event, Menu, Albums… • Make the reservation on the website • Make a contact on website. • Applications: • Customer : • Make the reservation on the website or phone • Administrators : • Add edit delete information user Company Logo

  11. 3.1 User Requirements • Applications: • User: • Manage Reservation (Add, edit, delete) • Manage table’s information • Manage menu’s information, menu details(Add, edit, delete) • Manage customer’s information(Add, edit, delete) • Statistics menu lists dishes in a restaurant • Statistics monthly bills • Statistics client list has reservation • Send SMS, Email to customers • Manage Website’s information Company Logo

  12. Usability Availability Reliability Security Performance Security Maintainability 3.2 Non-functional requirements Non-functional Requirement Company Logo

  13. 3.3 System Requirements • Document requirements as use-cases • Each use case include: • Use case diagram • Actor • Summary • Goals • Triggers • Exceptions • Relationship • Description • Screen • Data field Company Logo

  14. Database design • Architectural design • Detailed design 4. Software Design Description Company Logo

  15. Architecture Design Company Logo

  16. Component Design • Business Process Layer • Reservation • Menu • Report • Table • Business Component Layer • Customer • Account • Room Company Logo

  17. Detail Component Design Company Logo

  18. Database Design Entity Relationship • Business tables • Every table has a primary key named Id which is of type: int not null identity(1, 1) • Max length and null ability strictly follow field definitions • Every business table will have the trigger to save all the table changing Company Logo

  19. Coding convention • Technologies Tools 5. Implementation Company Logo

  20. Technologies 5. Implementation • DotNetBarfor Windows forms (Devcomponent) • GSM Communication Library (GSMComm) Company Logo

  21. Tools 5. Implementation • Visual Studio 2010 • ReSharper • TortoiseSVN Company Logo

  22. Coding convention 5. Implementation • Follow general .NET coding conventions (e.g. Pascal Casing, Camel Casing…) • Create specific conventions for our project Company Logo

  23. Test Model • Test plan • Test Phases • Test report • Bug control 6. Testing Company Logo

  24. 6.1. Testing Model Process Testing 3TC Company

  25. 6.2. Test Plan 3TC Company

  26. Unit Testingwill be done by developers (ThuongTH, CuongTM, TienND), is integrated and approved by ThuDA, ThuongTH Acceptent Testwill be done by people who use product with supported of team member Unit Testing Acceptant Test Integration Testwill be done by ThuDA Integration Test System Testwill be done by ThuDA and ThuongTH System Test 6.3Testing Phases 3TC Company

  27. 6.5. Test Report 3TC Company

  28. Demo & Q&A 3TC Company

  29. Thank You ! e-Restaurant

More Related