F17-Bikers Portal Project Report Table Content and Chapter 1

TABLE OF CONTENTS

 

 

CHAPTER NO. 1

gathering & Analyzing info....................................................... 10

 

1.1 Introduction                                                                            11

 

1.2 purpose                                                                                   11

 

1.3 scope                                                                                        11

 

1.4 definitions, acronyms and abbreviations                                 11

 

1.5 use cases and usage scenarios                                       12     

           

            1.5.1 Use Case Diagrams                                                                                12

           

            1.5.2 Usage Scenarios                                                                                     12

 

1.6 supplementary requirements                                                  18

 

            1.6.1 Usability                                                                                                 18

           

            1.6.2 Reliability                                                                                               18

           

            1.6.3 Supportability                                                                                        18

           

            1.6.4 System Requirements                                                                            18

 

 

CHAPTER NO. 2

planning the project................................................................... 20

2.1 Introduction                                                                           21

 

2.2 Methodology                                                                          21

 

2.3   Available Methodologies                                                        21

 

2.4   Chosen Methodology                                                              28

 

2.5   Reasons for Chosen Methodology                                          29

 

2.6   Work Plan                                                                               29

2.7   Project Structure                                                                  29

 

2.7.1        Team Structure                                                                                       29

 

2.7.2        Project Schedule (Submission Calendar)                                               29

 

 

 

CHAPTER NO. 3

designing the project................................................................. 30

 

3.1 Introduction                                                                            31

 

3.2 purpose                                                                                   31

 

3.3 scope                                                                                       31

 

3.4   definitions, acronyms and abbreviations                                 31

 

3.5   Architectural Representation (Architecture Diagram) 32

 

3.6   Dynamic Model: Sequence Diagrams                             33

 

3.7   Object Model/Logical Model: Class Diagram                       35

 

3.8   Database Model (Database Diagram)                             36

 

3.9   Graphical User Interfaces                                                      36

 

         

 

Chapter no.4

DEvelopment.................................................................................... 38

4.1 Development plan (Architecture Diagram)                    39

                            

 

                   

                            

 

 

 

 

 

 

<<Dear Students, you have to take special care of page numbers, which are written against each Chapter and sub headings. You have to mention your own page numbers and correct one against each document heading. Make proper table of contents. Remember that if there are any new headings or you have included more headings in your documents then you also have to write these in table of contents and modify table of contents according to your documents material>>

 

 

 

 

 

 

 

 

 

<<Dear Students, before starting each chapter the following would be the title page for each chapter on a separate page>>

 

 

 

 

 

 

 

 

 

                   

 

 

 

 

 

 

 

CHAPTER 1

Gathering & Analyzing Info

 

 

 

 

 

 

 

 

 

 

 

 

 

 

             

 

 

 

 

 

 

 

 

 

 

 

 

1.1 Introduction:

Bikers Portal is an online shopping web of Bikes and Bike parts and also with feature of Bike Renting. Where User/Customer can check the specifications bikes and parts and can buy them. User/Customer can also Select a bike on rent. User have created account. After login user can buy bike and parts and can-do online payment. In this document we see Bikers Portal functional requirement and non-functional requirement and his use case and Usage Scenarios how this system work and which adopted methodology we use and why we use this methodology

1.2           Purpose:

The purpose of this document is to present a detailed description of the Bikers Portal.It will explain the purpose

and features of the system, the interfaces of the system, what the system will do, the constraints under which it must operate and how the system will react.

Defining and describing the functions and specifications of the Bikers Portal is the primary goal of this Software Requirements Specification (SRS). This Software Requirements Specification illustrates, in clear terms, the system’s primary uses and required functionality as specified by our supervisor.

1.3           Scope:

This system allows the customers to maintain their cart for add or remove the product over the internet.

Primarily, the scope pertains to the E-Store product features for making Bike, Bike Parts selling and Rent a Bike Feature.

It focuses on the company, and applications, which allow for online sales, distribution and marketing of Bikes, Bike Parts and focus on Rent Bike System.

1.4    Definitions, Acronyms and Abbreviations

 

OASFS = Online Auction System for Furniture Shop

SRS = Software Requirements Specification

 

 

 

 

 

 

 

 

 

 

1.5.1 USE CASES AND USAGE SCENARIOS:

 

 

 

 

 

 

 

 

Use Case Title	Login
Actor	Customer/admin
Use Case ID	01
Description	In this use case system will allow the Customer to login to the system to continue the shopping.
Task Sequence	This use case starts when user wants to buy a product. User should login User name and Password required. This use case end.
Exceptions	None
Pre-Conditions	User must open the application.
Post Conditions	User must have already account
Author	BC140401332
Modification History	1.0

 

Use Case Title	Manage Customer Database
Actor	Admin
Use Case ID	02
Description	In this use case system will allow the admin to manage the database of Customer. To Maintain the record and privacy of customer.
Task Sequence	This use case starts when admin login. Open admin panel Manage Database. This use case end.
Exceptions	None
Pre-Conditions	Admin must open the application.
Post Conditions	Admin must be login
Author	BC140401332
Modification History	1.0

 

Use Case Title	Browse Categories
Actor	Customer
Use Case ID	03
Description	In this use case system will allow the Customer to open the product categories.
Task Sequence	This use case starts when customer login. Customer Open Categories. This use case end.
Exceptions	None
Pre-Conditions	Customer must open the application.
Post Conditions	Customer must login.
Author	BC140401332
Modification History	1.0

 

Use Case Title	Add Remove Update Item Categories
Actor	Admin
Use Case ID	04
Description	In this use case system will allow the admin to add, remove and update the product of categories.
Task Sequence	This use case starts when admin login to admin Add Products of categories from Admin panel Remove Products of categories from Admin panel Update Products of categories from Admin panel This use case end.
Exceptions	None
Pre-Conditions	Admin must open the application.
Post Conditions	Admin must login
Author	BC140401332
Modification History	1.0

 

Use Case Title	Add Remove Update Item from cart
Actor	Customer
Use Case ID	05
Description	In this use case system will allow the Customer to add, remove and update the product from cart
Task Sequence	This use case starts when customer login. Add Products from  categories to cart Remove Products from categories to cart Update Products from categories to cart This use case end.
Exceptions	None
Pre-Conditions	Customer must open the application.
Post Conditions	Customer must login, User must select a product
Author	BC140401332
Modification History	1.0
Use Case Title	Approve  / Reject Shopping Request
Actor	Admin
Use Case ID	06
Description	In this use case system will allow the Admin to approve or reject the shopping request of customer.
Task Sequence	This use case starts when admin login to admin panel  Approve shopping request from admin panel Reject shopping request from admin panel This use case end.
Exceptions	None
Pre-Conditions	Admin must open the application.
Post Conditions	Admin must login ,
Author	BC140401332
Modification History	1.0

 

Use Case Title	Payment and approve order
Actor	Customer
Use Case ID	07
Description	In this use case system will allow the Customer to finally approve his order and select payment method
Task Sequence	This use case starts when customer login. Add Products from  categories to cart And select payment method Finally approve the order. This use case end.
Exceptions	None
Pre-Conditions	Customer must open the application.
Post Conditions	Customer Must login and have bank account
Author	BC140401332
Modification History	1.0

 

Use Case Title	Logout
Actor	Admin/Customer
Use Case ID	08
Description	In this use case system will allow the Customer and admin to logout .
Task Sequence	This use case starts when customer login. After further works The customers and admin can logout. This use case end.
Exceptions	None
Pre-Conditions	User/Admin must open the application.
Post Conditions	User/Admin Should Login
Author	BC140401332
Modification History	1.0

 

Use Case Title	Visit Site
Actor	Visitor
Use Case ID	09
Description	In this use case system will allow the visitor to visit site.
Task Sequence	This use case starts when user visit the site This use case end.
Exceptions	None
Pre-Conditions	User must open the application.
Post Conditions	None
Author	BC140401332
Modification History	1.0

 

Use Case Title	Create Account
Actor	Visitor
Use Case ID	10
Description	In this use case system will allow the visitor to create the account for shopping.
Task Sequence	This use case starts when user visit site. User have to create account for shopping Name of Visitor Father Name of Visitor Email of Visitor Contact No of visitor And register. This use case end.
Exceptions	None
Pre-Conditions	User must open the application.
Post Conditions	Operation done successfully.
Author	BC140401332
Modification History	1.0

 

1.6   Supplementary Requirements:

 

    1.6.1 Usability

                        The system will be user friendly.

 

       1.6.2 Reliability

                      System will be able to complete its ongoing operations in case of error.

 

       1.6.3 Supportability

                      System will be able to complete its ongoing operations in case of error.

 

       1.6.4 System Requirements

                      System will be able to complete its ongoing operations in case of error.