F17-Bikers Portal Project Report Chapter 3

 

 

 

 

 

 

 

 

 

 

 

                   

 

 

 

 

 

 

 

CHAPTER 3

Designing the Project

 

 

 

 

 

 

 

 

 

 

 

 

 

3.1       Introduction

 

The purpose of this document is to present a System Design of F17-Bikers Portal.This document is presented both graphically in screenshots and in text. This document produces the detailed design with the help of several design drawings including ERD, Sequence, Architecture Design and Class diagrams, Database and Interface designs. Finally, it lists down the suggested Test cases for the Unit and Integrated testing of the system.

 

The Class diagram, Data base Design, Interface Design and Test Cases are the main ideas of this document. All the processes of the project are defined by help of diagrams. Class diagram is static structure diagram that shows the structure of the system using classes. Database diagram represents the picture of database.

User interface diagram typically one or two purposes.

1^st they are used to model interaction between software and user

 

2^nd to gain high level overview of user interface of your system.

 Deployment diagram are used to how components are physically related to each other’s. Test cases determine whether the system is working properly or not.

 

3.2       Purpose

 

The purpose of this document is to present a System Design of F17-Bikers Portal. This document is presented both graphically in screenshots and in text. This document produce the detailed design with the help of several design drawings including ERD, Sequence, Architecture Design and Class diagrams, Database and Interface designs. Finally it lists down the suggested Test cases for the Unit and Integrated testing of the system.

 

3.3 Scope

 

This document presents the current design & implementation of the F17-Bikers Portal. The Class diagram, Data base Design, Interface Design and Test Cases are the main ideas of this document.. All the processes of the project are defined by help of diagrams. Class diagram is static structure diagram that shows the structure of the system using classes. Database diagram represents the picture of database. User interface diagram typically one or two purposes. 1^st they are used to model interaction between software and user and secondly to gain high level overview of user interface of your system. Deployment diagram are used to how components are physically related to each other’s. Test cases determine whether the system is working properly or not.

 

3.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS

 

SRS: Software Requirement Specification

User: Person who uses the system.

            Admin/user: Person who has authority has to monitor the system

            Username: Unique username

            Password: Secret code to access the system

 

 

 

3.5         Architectural Representation (Architecture Diagram)

 

 

 

3.5      Entity Relationship Diagram (ERD)

 

 

 

3.5        Dynamic Model: Sequence Diagrams

 

Sequence Diagrams of Full System:

 

 

Registration:

 

 

 

 

login:

add to cart:

rent a bike:

 

 

 

 

3.9  Database Model (Database Diagram)

 

 

3.8   Object Model/Logical Model: Class Diagram

 

 

 

3.10 Graphical User Interfaces

 

5.     Interface Design

 

Registration:

 

Login:

 

Bike Details: