Bus Ticket Reservation System Design CS619 Final Project Semester Fall 2014 Due Date Sun 01 Mar, 2015

<Give Here Your Own Project Title>

Design Document

Version 1.0

Group Id: <Mention your group id>

Supervisor Name :< Mention your supervisor name>

Revision History

Date (dd/mm/yyyy)	Version	Description	Author
Current date	1.0	Introduction of the project	Write student(s) id

Table of Contents

                                                                                                                       

1.      Introduction of Design Document                              

2.      Entity Relationship Diagram (ERD)

3.      Sequence Diagrams

4.      Architecture Design Diagram        

5. Class Diagram                                                
6. Database Design
7. Interface Design
8. Test Cases                                          

   

1. Introduction of Design Document

<Write here in detail about what you have included in this document and also write about the benefits and purpose of this phase in a software development project >

2. Entity Relationship Diagram (ERD) (To be developed using Microsoft Visio or any other drawing software of your choice)

<Provide Entity Relationship Diagram (ERD) of your system>

3. Sequence Diagrams (To be developed using Rational Rose or any other drawing software of your choice)

<Provide Sequence Diagrams for each of the use case to show the task sequence of the system, Provide a sequence diagram for each of the use case provided in use case diagram>

4. Architecture Design Diagram

<Provide a Tiered Architecture of the system>

5.     Class Diagram

<Provide Class Diagram of the system>

6.     Database Design

<Provide Database Design Diagram of the system>

7.     Interface Design

<Provide here the screenshots (GUI) of the system (Provide 3 or 4 main GUIs/interfaces, to show the most important features of the application as you are visualizing your application to be, in actual development phase. You can update these GUIs in Final Report and Final Presentation, in case they are changed after the actual development.> 

8.     Test Cases

<Provide test cases for each use case scenario>