vehicles online SRS

PROJECT NAME: VEHICLES ONLINE VERSION

Software requirement specification

Team name: ABC DELTA

1

Vehicles Online Software Requirement Specification Team Name: ABC DELTA State: West Bengal Version 1.0

Guided By : Molay Dutta Team Members Atin Chakraborty Sukanta Das Sachchidananda Soren Pinaki Karmakar.




2

INDEX

Chapter 1. Overview & Scope 1.1 Overview 1.2 Identification Of Need 1.3 Preliminary Investigation 1.4 Feasibility Study

Chapter 2. Assumptions and Dependencies

Chapter 3. Planning & Scheduling 3.1 Planning 3.2 Scheduling

Chapter 4. Definitions, Acronyms and Abbreviations Chapter 5. Technologies to be used Chapter 6. Specific Requirements

6.1 Information Description

6.1.1 Description of the Project 6.1.2 Scope

6.2 Functional Description

6.2.2 Functional Partition 6.2.3 Functional Description 6.2.4 Data Flow Diagram [DFD] 6.2.5 Control Flow Diagram

6.3 Preliminary Object Oriented Domain Analysis

6.3.1 Inheritance Relationship 6.3.2 Class Description

6.3.2.1 Abstract Concrete 6.3.2.2 List of Subclass

6.3.2.3 Purpose 6.3.2.4 Collaboration 6.3.2.5 Attributes

6.3.2.6 Constants




3

6.3.3 Class Diagram 6.3.4 CRC Models 6.3.5 Use Case Diagram

6.4 Data description

6.4.1 Table Structure 6.4.2 E R Diagram 6.4.3 Data Dictionary

6.5 Behavioral Description

6.5.1 System Performance 6.5.2 State Transition Diagram 6.5.3 Activity Diagram

6.6 Supporting Information 6.6.1 Architecture diagram

6.6.2 User Interface

6.6.3 Security 6.6.4 Implementation 6.6.5 Resource Utilization 6.6.6 Test Case 6.6.7 TESTING STRATEGY 6.6.8 Cost estimation of the project

6.7 Supplementary Requirements 6.8 References




4

Chapter 1. Overview & Scope 1.1 Overview

This is a website regarding all kinds of vehicle trading and their respective

services. Customer can gather information regarding new and old vehicles

through this web site. They can also collect information regarding car finance

and insurance. Customer or visitors can see the updated information regarding

companys policies, their upcoming launches and their current market status

including sensex details.

1.2 Identification Of Need

With the help of this web site users can do the following things like,

a. users can see the various type of vehicles

b. users can book any vehicles of their own choice

c. they can gather information regarding finance, insurance, service etc

1.3 Preliminary Investigation

Understanding the requirement of the problems is among the most difficult task.

For a preliminary investigation there are certain points which are important: Like

Q1. What is the need of this web site? Ans. To present the full information of all types of vehicles in one platform. Q2. What is the current market scenario? Ans. Represent the current and upcoming vehicles and their information. Q3. How to compare model of vehicles? Ans. In this site user can compare between different models of vehicles.




5

Q4. How can you buy new and old vehicles? Ans. User can buy new and old vehicle from this site. Q5. How can you get service feasibilities of different vehicle of different company in one platform? Ans. User can book and cancellation of services of any vehicle of any company. Q6. How can user get duplicate key of your vehicle?

Ans. User can order duplicate key of vehicle. Q7. How can user search new and old vehicles of different companies in one platform? And. User can search new and old vehicles of different companies 1.4 Feasibility Study

Feasible study means practical, possible or plausible. Feasibility is the determination

of whether or not a project is worth doing. The process followed in making this

determination is called a Feasibility study. This type of study determines if a project

can and should be taken. Once it has been determined that a project is feasible, the

analyst ca go ahead and prepare the project specification which finalizes projects

requirements.

The aim of the Feasibility Study is to identify the best solution under the

circumstances by identifying the effects of this solution on the organization.

The system analyst undertakes the feasibility study. Based on the analysis of

the problem the analyst uses his/her understanding of software design and

development to describe and evaluate a feasible solution to the problem. These are

presented to management as alternatives or options in the Feasibility Report to

allow management to select the best solution.




6

The constraints of the Feasibility Study are as follows:-

1. Technical Feasibility.

2. Economic Feasibility.

3. Operational Feasibility.

1. Technical Feasibility.

Technical Feasibility is concerned with

specifying equipment and software that

will satisfy the user requirement. The

Technical Feasibility include:

1. The facility to produce outputs

in a given time.

2. Response time under certain

conditions.

3. Ability to process a certain

volume of transaction at a

particular speed.

4. Facility to communicate data to

distant location.

It is the role of the analyst to provide

realistic solutions to the users problem. To

determine Technical Feasibility a System

Analyst must be update with the latest

developments in Hardware and Software.

Points: 1) Developed the system in windows Platform which is user friendly

system.




7

2) Tools used for the system are web spare, java script, DB2 which are

widely used for the development.

On basic this points we can say that the system is a technically feasible

system.

2. Economic Feasibility.

Economic analysis is the most frequently

used technique for evaluating the

effectiveness of a proposed system. It is

commonly known as Cost-Benefit analysis;

the procedure to determine the benefits

and saving that are expected from a

proposed system and compare them with

costs. A system that can be developed

technically and that will be used if

installed must be profitable for the

organization. Financial benefits must equal

or exceeds the cost. If benefits outweigh

costs, a decision must be taken to design

and implement the system. Otherwise

further justification in the proposed

system will have to be made if it is to have

chance of being approved.

Points: 1) The system is a common system and the price of the software will be

fixed as per market demand.

On basic this points we can say that the system is a Economically

feasible system.




8

3. Operational Feasibility.

It is mainly related to human

organizational and political aspects. In this

feasibility, we evaluate the effects of each

alternative on the routine operation of the

organization.

Proposed projects are beneficial

only if they can be turned into information

systems that will meet the operating

requirements of the organization. This test

of feasibility asks if the system will work if

developed and installed. This is carried

out by a small group of people who are

familiar with information system

techniques, who understand the parts of

the business that are relevant to the project

and are relevant to the project and are

skilled in system analysis and design

process.

Points: 1) The system has been designed in a GUI Interface where the user can

use the software more easily.

2) A Training program will be taken so that the user can easily operate

the overall system. On basic this points we can say that the system is a

operationally feasible system.




9

Chapter 2. Assumptions and Dependencies

a) The administrator of the system will be add up manually by the system b) Development environment must have windows & JVM c) Their should be internet connection d) Project is based on vehicles like two wheelers, four wheelers and heavy

vehicles.

Chapter 3. Planning & Scheduling

3.1 Planning

Project planning has four basic objectives: -

1. Organizing the resources available for the Project.

2. Scheduling the events of the Project.

3. Evaluating the Progress.

4. Establishing standards for the Project.

An effective manager is essential for successful project planning. The techniques

of project planning are not a substitute for good management, but merely a tool

to be used by managers to achieve better results. Only effective management can

complete the project on time, within budget, and with satisfactory results.

A systems project requires extensive interaction between developers and users.

Users are preoccupied with day-to-day operations, and it cannot be assumed that

they will be enthusiastic about participation in a system study.

To organize a project, the project leader must determine who all are required for

the project, when they are available, and for the project, when they are available,

and for how long their services can be expected. The key people required in a

system projects are often the key people in day-to-day operations of an

organization, and they probably will have to continue their normal routines as

they participate in the systems project. In organizing their efforts, the project

leader must avoid scheduling important project activities when the users are

very busy with normal duties.




10

The project leader is solely responsible for the completion of a project, but

obviously cannot do it alone. Responsibilities must be defined precisely, and

overlapping responsibilities avoided.

Besides organizing people, the project leader must budget money and order

equipment. Acquainting people with their responsibilities and enabling them to

discharge these responsibilities is the essence of leadership.

The objective of software project planning is to provide a framework that enables

the manager to make reasonable, cost and schedule. These estimates are made

within a limited time frame at the beginning of a software project and should be

updated regularly as the project progresses. In addition, estimates should

attempt to define best case and worst case scenarios so that project outcomes can

be bounded.

The planning objective is achieved through a process of information

discovery that leads to reasonable estimates.

Human Resources

The planner begins by evaluating scope and selecting the skills required to

complete development. Both organizational position (e.g., manager, senior

software engineer) and specialty (e.g., telecommunications, database,

client/server) are specified. For relatively small projects (one person-year or

less), a single individual may perform all software engineering task, consulting

with specialist as required.

The number of people required for a software projects can be determined

only after an estimate of development effort (e.g., person-month) is made.

Human Resources 4




11

Reusable Software Resources

Component-based software engineering emphasizes reusability that is, the

creation and reuse of software building blocks. Such building blocks, often called

components must be cataloged for easy reference, standardizes for easy

application and validated for easy integration.

Bennatan suggest four software resource categories that should be considered as

planning proceeds:

Off-the-shelf components. Existing software that can be acquired from a

third party or that has been developed internally for a past projects. COTS

(Commercial off-the-shelf) components are purchased from a third party, are

ready for use on the current project, and have been fully validated.

Full-experience components. Existing specifications, designs, code, or test

data developed for pasty projects that are similar to the software to be built for

current project. Members of the current software team have had full experience

in the application area represented by these components. Therefore,

modifications required for full-experience components will be relatively low

risk.

Partial-experience components. Existing specifications, designs, code, or

test data developed for past projects that are related to the software to be built

for the current project but will require substantial modification. Members of the

current software team have only limited experience in the application area

represented by these components. Therefore, modifications required for partial-

experience components have a fair degree of risk.




12

New Components. Software components that must be built by the software team

specifically for the needs of the current projects.

Off-the-shelf components No third Party software is used for the

development of the system

Full-experience components. Existing Analysis/Design/Code was

not taken for the development

Partial-experience components. References taken from the existing

software

New Components No new components are designed, But

new analysis based on the project have

been designed.

Environmental Resources

The environment that supports the software project, often called Software

Engineering Environment (SEE), incorporates hardware and software. Hardware

provides a platform that supports the tools (software) required to produce the

work products that are outcome of good software engineering practice. Because

most software organizations have multiple constituencies that require access to

the SEE, a project planner must prescribe the time window required for software

and hardware and verify that these resources will be available.

When a computer based system (incorporating specialized hardware and

software) is to be engineered, the software team may require access to hardware

elements being developed by other engineering teams.

Hardware

1] Processor 1.8 GHz

2] RAM 2 Gb

3] Hard Disk Drive 250 GB

4] Monitor 15 inches




13

5] DVD Rom 16x

6] Floppy Drive 1.44 Mb

7] Keyboard/ Mouse

Software

OS (windows 2000, XP etc)

Planning for the Distribution of task Proposed

3.2 Scheduling

Project planner use charting techniques for scheduling like GANNT chart (for

simple projects) or PERT chart (for typical projects).Projects are organized into

modules, or segments, of related data.

A schedule must be flexible because unexpected events may occur that

may affect the schedule of development of the system. Seldom do system

projects meet the original schedule at each milestone. This doesnt imply that

schedules are made to be broken, but a schedule cannot be so rigid that when the

unexpected occurs, subsequent events cannot be rescheduled.

Requirement Analysis 02/08/2009 17/08/2009

Identification of Need 04/08/2009 19/08/2009

Preliminary Investigation 04/08/2009 24/09/2009

Feasibility Study 28/08/2009 12/10/2009

Analysis 18/09/2009 30/09/2009

Design 20/09/2009 10/10/2009

Coding & Initial Testing 25/09/2009 5/12/2009

Documentation 30/10/2009 25/11/2009

Testing and Implementation 28/11/2009 23/12/2009




14

A schedule has two primary functions, it is both a plan and a device for

measuring progress. The key steps in a schedule are called milestones, or

checkpoints. As the project progresses, the date on which each milestone is

completed is compared with the date for which it was projected. In any project,

frequent progress reviews take place in which the status of events is reported

and evaluated.

The status of the project is often reported in terms of Percentage of

completion. The problem with reporting of percentage of completion is that

events on the critical path are not emphasized. A project may have 90% of its

events complete, but if one of the incomplete events is on the critical path and is

two years late, then the project may be in serious trouble.

Accurate scheduling requires extensive experience. The novice scheduler

almost always doesnt allow enough time for activities. Even when requirements

are carefully gathered, as in PERT network, some areas of delay are not apparent.

When a project is behind schedule, corrective steps must be taken. Establishing

milestones is meaningless unless the project manager can enforce adherence to

schedule. If a project leader cannot enforce schedule, someone else should be

leading the project. If one area is consistently behind schedule, or over budget,

the project leader must discuss the problem with the individuals responsible and

take corrective action. The following are variety of options that are open to the

project leader:

Increase the budget.

Increase manpower in the form of overtime or additional people.

Add equipment.

Change priorities.

Replace the individual responsible.




15

The project leader must remember that this is not the only project under

way and delays will occur routinely simple because another, more important

projects may have to be handled first. Schedules are highly dependent upon

priorities and should be planned accordingly.

Task Network Chart

TimeLine Chart

When creating a software project schedule, the planner begins with a set of tasks.

If automated tools are used, the work breakdown is input as a task network or

task outline. Effort, duration, and start date are then input for each task. In

addition, tasks may be assigned to specific individuals.

As a consequence of this input, a Time Line Chart, also called a Gantt Chart, is

generated. A Time Line Chart is developed for the entire project.

Requiremen

t Analysis

Identification of Need

Preliminary

Investigatio

n

Analysis

Design

Coding

Testing




16

GANTT CHART

TASKS

Requirement

Analysis

Identification

of Need

Preliminary

Investigation

Feasibility

Study

Analysis

Design

Coding and

Initial Testing

Documentation

Testing and

Implementation

Aug Sep Oct Nov Dec




17

Resource Table

Work Task Plan Plan Assigned Effort

Started Complete Person Allocated

Requirement

Analysis

WK1, D1 WK2, D5 A, P 2 PD

WK1,

D1

WK3, D7

So, Su 2 PD

WK1,

D1

WK3,

D5

So, P 2 PD

WK1,

D1

WK5,

D7 A, P 2 PD

WK1,

D1

WK5,

D7

A, P, So 3 PD

WK1,

D1

WK3,

D3

A, So 2 PD

WK1, D1

WK12, D4 A,P,So,Suu

4 PD

WK1,

D1 WK4, D5 A,P,So,S

u

4 PD

WK1,

D1

WK4, D6 A,P,So 3 PD

Identification

of Need

Preliminary

Investigation

Feasibility

Study

Analysis

Design

Coding and

Initial Testing

Documentation

Testing

Implementation




18

Chapter 4. Definitions, Acronyms and Abbreviations

Users End users, those who only visit this site.

HTML Hypertext Markup Language is to create static

websites.

J2EE Java 2 Enterprise Edition is a programming platform

and it is the part of the java platform for developing and

running distributed java applications.

WASCE Web sphere application server community edition

is an application server that runs and supports the J2EE and web

service applications.

WSAD Web sphere studio application developer is a

designer toolkit which is designed for develop more

complex projects by providing fully dynamic web service.

DB2 Database 2 is the database management system that

provides a flexible and efficient database platform to erect

strong on demand business applications.

HTTP Hypertext transfer protocol is a transaction oriented

client/server protocol between web browser and a web server.

HTTPS Secure hypertext transfer protocol is a hypertext

transfer protocol over secure socket layer.

TCP/IP Transmission control protocol/internet protocol is

the communication protocol used to connect hosts on the

internet.




19

Chapter 5. Technologies to be used

J2EE Application architecture

JAVA Application architecture

WSAD Development tool

WASCE - Web Server

DB2 Database

Rational Design tool

Chapter 6. Specific Requirements

6.1 Information Description 6.1.1 Description of the Project

This is a website regarding all kinds of vehicle trading and their respective

services. Customer can gather information regarding new and old vehicles

through this web site. They can also collect information regarding car finance

and insurance. Customer or visitors can see the updated information regarding

companys policies, their upcoming launches and their current market status

including sensex details. Users can search any type of vehicle like two wheelers,

four wheelers, heavy vehicles etc. They can compare between two vehicles of

their own choice and see the different parameters of the vehicles. They can book

test drive of any four wheelers. Customer can gather information regarding

vehicles spare parts and their respective services. They can book or cancel their

booking regarding new vehicle or vehicle service. Users can book their respective

vehicles key incase of key missing.




20

6.1.3 User Description

User Type Level Properties

Administrator 1 Update Vehicle Manage Deliveries Manage Key Modules Manage User

Support Manager 2 Maintain Service care Vehicle compare

Customer 3 Vehicle Booking Service Booking Searching Used vehicle Booking

6.2 Functional Description 6.2.2 Functional Partition

VEHICLE ONLINE

BOOKING

DELIVERY

SERVICE / KEY

SEARCH

COMPARE

TEST DRIVE

FINANCE / INSURANCE




21

6.2.3 Functional Description

Administrator module: Administrator updates all the information regarding this webpage in the server. Registration module: User can enter his/her name and e-mail id for further communication Vehicle booking module: Customer can book their car/bike/heavy vehicle.

Delivery Report module: User can generate the delivery report.

Vehicle Cancellation module: Customer can cancel their booking.

Service booking module: Customer can book their service.

Service cancellation module: Customer can cancel their service.

Used vehicle book: User can book second hand vehicle.

Vehicle search: User can search any new vehicle of their own choice

Vehicle Compare: User can compare between any two vehicles of their own

choice.

Used vehicle search: User can search any type of second hand vehicle

Insurance: A customer can gather information about vehicle insurance.

Finance: A customer can gather information about vehicle finance.

Key module: Customer can ask for new keys for their respective vehicles.

Test drive: User can ask for test drive of any four wheeler vehicle




22

6.2.4 Data Flow Diagram [DFD]

details

details

details

details

details

details

details




23

details

details

details

details

details

details

details

details

details

details

details




24

details details

details

details




25

6.3.2 Class Description




26




27




28




29




30




31




32




33

6.3.3 Class Diagram




34

6.3.5 Use Case Diagram




35

6.4 Data description 6.4.1 Table Structure

NAME DATA TYPE PROPERTIES

Name VARCHAR(20)(20) User name

E-MAIL ID VARCHAR(20) User e-mail id


Booking cancellation number

VARCHAR(20) Auto generated no.

Booking number VARCHAR(20) Previous booking no.

CUSTOMER NAME VARCHAR(20) name

ADDRESS VARCHAR(20) address

PH _NO BIGINT Phone no.

E-MAIL ID VARCHAR(20) e-mail id

CAR_NAME VARCHAR(20) Vehicle name

MODEL_NO VARCHAR(20) Respective model no.

COLOUR VARCHAR(20) color

SEATER BIGINT capacity

Booking DATE DATE Previous booking date

Booking Cancellation Date

DATE Current date

Country VARCHAR(20) country

State VARCHAR(20) Respective state

Dealer VARCHAR(20) dealer

TABLE 1: registration

TABLE 2: vehicle cancellation




36


Booking number VARCHAR(20) Auto generated no.

CUSTOMER_NAME VARCHAR(20) Name

PH_NO BIGINT Phone no.

E-mail id VARCHAR(20) e-mail id

BOOKING DATE DATE Current date


MODEL_NO VARCHAR(20) Respective model no.

COLOUR VARCHAR(20) Color

SEATER BIGINT Capacity

COUNTRY VARCHAR(20) Country

STATE VARCHAR(20) State

NEAREST_DEALER VARCHAR(20) dealer


CUSTOMER_NAME VARCHAR(20) name

Booking number VARCHAR(20) Previous booking no.

ADDRESS VARCHAR(20) Address

BOOKING_DATE VARCHAR(20) Previous booking date

Delivery date VARCHAR(20) Current date

MODEL_NO VARCHAR(20) Vehicle no.

Engine number VARCHAR(20) Respective vehicles engine no

Chassis number VARCHAR(20) Respective vehicles chassis no.


SEATER BIGINT capacity

DELIVRY_FAILURE_REASON VARCHAR(20) Particular reason

TABLE 4: Delivery report

TABLE 3: vehicle booking




37


Service Booking Number VARCHAR(20) Auto generated no.

CUSTMOR_NAME VARCHAR(20) Name

ADDRESS VARCHAR(20) address


CAR NAME VARCHAR(20) Vehicle name

MODEL_NO VARCHAR(20) Model no.

WARRENTY_BOOKLET_NO VARCHAR(20) Respective vehicles w b no.

Engine number VARCHAR(20) Engine no.

Chassis number VARCHAR(20) Chassis no.

Date DATE Current date



NEAREST_DEALER/SERVICE_STATION VARCHAR(20) Service station





E-MAIL ID VARCHAR(20) e-mail id

DATE DATE Current date

Engine number VARCHAR(20) Vehicles engine no.

Chassis number VARCHAR(20) Chassis no

DSA_NAME VARCHAR(20) Agent name


TABLE 5: service booking

TABLE 6: used car book




38






REGISTRATION_NO VARCHAR(20) Motor vehicles registered no

ENGINE_NO VARCHAR(20) Engine no.

CHASSIS_NO VARCHAR(20) Chassis no.

PRICE BIGINT Selling price

KILOMETER VARCHAR(20) Distance covered


CAR _NAME VARCHAR(20) Vehicle name




PRICE BIGINT Selling price

DEALER_NAME VARCHAR(20) Dealer name


INSURANCE_CO_NAME VARCHAR(20) Company name

HYPERLINK_COLOUR VARCHAR(20) Companys web site

TABLE 7: used car search

TABLE 8: new car search

TABLE 9: insurance




39


FINANCE_CO_NAME VARCHAR(20) Company name

FINANCE_HYPERLINK VARCHAR(20) Companys web site





E-MAIL_ID VARCHAR(20) e-mail no.


MODEL_NO VARCHAR(20) Model no

BOOKING_DATE VARCHAR(20) Previous booking date



DEALER_NAME VARCHAR(20) Dealer name

ENGINE_NO VARCHAR(20) Engine no.






EMAIL_ID VARCHAR(20) e-mail id

Date DATE Current date



NEAREST_DEALER VARCHAR(20) dealer

TABLE 10: finance

TABLE 11: key

TABLE 12: test drive




40


Service Booking Number VARCHAR(20) Previous no.

Service cancellation number VARCHAR(20) Current no.

CUSTMOR_NAME VARCHAR(20) Name



CAR NAME VARCHAR(20) Vehicle name


WARRENTY_BOOKLET_NO VARCHAR(20) Vehicles w b no.

ENGINE_NO VARCHAR(20) Engine




Service booking date VARCHAR(20) Previous date

Service cancellation date DATE Current date

NEAREST_DEALER/SERVICE_STATION VARCHAR(20) dealer


GRADE_NAME VARCHAR(20) Type

ENGINE VARCHAR(20) Type of engine

TRANSMISSION VARCHAR(20) Type

LENGTH VARCHAR(20) dimension

HEIGHT VARCHAR(20) Dimension

FUAL_TANK_CAPACITY VARCHAR(20) Capacity

WEIGHT_CURB_KG VARCHAR(20) Weight

DISPLACEMENT_IN_CC VARCHAR(20) Engines displacement

MAX_OUTPUT(KG_PS@RPM) VARCHAR(20) Output

SUSPENTION(FRONT @ REAR)

VARCHAR(20) Type

BRERAK(FRONT @ REAR) VARCHAR(20) Type

WHEEL VARCHAR(20) Type


Starting VARCHAR(20) Type of starter

Fuel reserve VARCHAR(20) Reserve capacity

TABLE 14

TWO WHEELER

TABLE 13: service cancellation




41

Fuel type VARCHAR(20) Type

Compression ratio VARCHAR(20) Output

Ignition VARCHAR(20) Ignition

Bore VARCHAR(20) bore

Stroke VARCHAR(20) type

Clutch VARCHAR(20) Type

Gear box VARCHAR(20) Type



ENGINE VARCHAR(20) Type


DISPLACEMENT_IN_CC VARCHAR(20) Output

MAX_OUTPUT(KW-PS@RPM) VARCHAR(20) Output

MAX_TARQUE(NM-KG-M@RPM) VARCHAR(20) Output

FUAL_CAPACITY VARCHAR(20) Total capacity

LENGTH VARCHAR(20) dimension

WIDTH VARCHAR(20) Dimension

HEIGHT VARCHAR(20) Dimension

OVER HANG(FRONT & REAR) VARCHAR(20) Type

WHEEL_BASE VARCHAR(20) length

THREAD_FRONT VARCHAR(20) Type

THREAD_REAR VARCHAR(20) Type

PERSON_CAPACITY VARCHAR(20) No. of person

MIN_GROUND_CLEARENCE VARCHAR(20) Length

MIN_TURNING_RADIOUS VARCHAR(20) Length

WEIGHT_CAR_KG VARCHAR(20) Weight

SUSPENSION_FRONT VARCHAR(20) type

SUSPENSION_REAR VARCHAR(20) Type

BREAK_FRONT VARCHAR(20) Type

BREAK_REAR VARCHAR(20) Type

TYRE VARCHAR(20) Type

WHEELS VARCHAR(20) Type

FRONT_BUMPER VARCHAR(20) Style

FOG_LAMP VARCHAR(20) Parameter

OUTSIDE_REAR_VIEW_MEASURE VARCHAR(20) Parameter

WIPER_FRONT VARCHAR(20) Parameter

WIPER_REAR VARCHAR(20) Parameter

TABLE 15

FOUR WHEELER




42

METER_PANEL_TACHO&ODO/TRIP VARCHAR(20) Type

AUDIO VARCHAR(20) Style

AC VARCHAR(20) Type

STEARING VARCHAR(20) Style

THIFT_DETERRENT_SYSTEM VARCHAR(20) Parameter

POWER_OUTLET_DC_OUTPUT VARCHAR(20) Output

STORAGE(GLOVE BOX) VARCHAR(20) Parameter

STORAGE(SUNGLASS HOLDER) VARCHAR(20) Parameter

ABS_ANTILOCK_BREAKING VARCHAR(20) Parameter

AIR_BAG VARCHAR(20) Parameter

GOA_BODY VARCHAR(20) Parameter

GPS VARCHAR(20) Parameter




ENGINE VARCHAR(20) Type


OVERALL_DIMENSION VARCHAR(20) Length

WHLL_BASE VARCHAR(20) length

PERSON_CAPACITY INT Total person no.

TURNING_CAPACITY VARCHAR(20) Length

DISPLACEMENT VARCHAR(20) Output

MAX_OUTPUT(KW_PS@RPM) VARCHAR(20) output

MAX_TORQUE(NM_KG_M@RPM) VARCHAR(20) Output

SUSPENSION_FRONT VARCHAR(20) Type

SUSPENSION_REAR VARCHAR(20) Type

FUEL_CAPACITY VARCHAR(20) Total capacity

BREAK_FRONT VARCHAR(20) Type

BREAK_REAR VARCHAR(20) Type


YEAR OF MANUFACTURE VARCHAR(20) Year

NO_OF_SYLENDER VARCHAR(20) Type

TYRE_SIZE_FRONT_AXALE VARCHAR(20) Parameter

TYRE_SIZE_REAR_AXALE VARCHAR(20) Parameter

AXALE WEIGHT_FRONT VARCHAR(20) Weight

AXALE_WEIGHT_REAR VARCHAR(20) Weight

TABLE 16

HEAVY VHEICLE




43

UNLADEN_WEIGHT VARCHAR(20) Weight

NO_OF_TYRE VARCHAR(20) Total no. of tyre present in the vehicle

6.4.2 E R Diagram

# for the shortage of space the attributes are not added with entities...




44

6.5 Behavioral Description 6.5.1 State Transition Diagram

State Transition Diagram




45




46




47




48




49




50




51




52




53

6.5.2 Activity Diagram 1) ADMINISTRATOR

Invalid valid

Update tables

Login by admin

View update

details




54

2) REGISTRATION

Invalid data valid data

Enter the e-mail

Verification of data

Registration




55

3) VEHICLE BOOKING MODULE

Invalid data

Valid data

Enter vehicle for

searching

Verification of details

Booking of the details

car

Vehicle

booking




56

4) DELIVERY REPORT

Delivery details retrieval

Generation of report




57

5) VEHICLE CANCELLATION MODULE

Valid entry

Invalid entry

Enter vehicle and

customer details

Cancellation process




58

6) SERVICE BOOKING MODULE

Invalid entry valid entry

Enter service and

customer

Data processed

Service




59

7) SERVICE CANCELLATION MODULE

Invalid data valid data

Enter service details

Data cancelled

Service

cancellation




60

8) USED VEHICLE BOOK

Valid search

Invalid searching

Enter used

vehicle for

Searching

Verification of

Details

Used

case

book




61

9) KEY MODULE

Valid

Invalid

Enter customer &

car details

Enter details of

key

Key




62

10) TEST DRIVE

Invalid Valid

Enter customer

details

Enter test book

Test

Drive




63

6.6 Supporting Information 6.6.1 Architecture diagram




64

6.6.2 User Interface




65




66




67




68




69




70




71

1. BOOKING NEW BIKE




72

2. BOOKING NEW CAR




73

3. BOOKING NEW HEAVY VEHICLE




74

4. BOOKING OLD CAR




75

5. BOOKING OLD BIKE




76

6. BOOKING OLD HEAVY VEHICLE




77

7. KEY ORDER




78

8. NEW CAR SEARCH

9. NEW BIKE SEARCH




79

10. NEW HEAVY VEHICLE SEARCH

11. SEARCH OLD CAR




80

12. SEARCH OLD HEAVY VEHICLE

13. SEARCH OLD BIKE




81

14. FINANCE




82

15.INSURENCE




83

16.SERVICE BOOKING:




84

17. SERVICE CANCELLATION:




85

6.6.3 Security

DB2 security mechanisms: There are three main mechanisms within DB2 that

allow a DBA to implement a database security plan: authentication, authorization,

and privileges.

Authentication is the first security feature you'll encounter when you attempt to

access a DB2 instance or database. DB2 authentication works closely with the

security features of the underlying operating system to verify user IDs and

passwords. DB2 can also work with security protocols like Kerberos to

authenticate users.

Authorization involves determining the operations that users and/or groups can

perform, and the data objects that they may access. A user's ability to perform

high-level database and instance management operations is determined by the

authorities that they have been assigned. The five different authority levels

within DB2 are SYSADM, SYSCTRL, SYSMAINT, DBADM, and LOAD.

Privileges are a bit more granular than authorities, and can be assigned to users

and/or groups. Privileges help define the objects that a user can create or drop. .




86




87

They also define the commands that a user can use to access objects like tables,

views, indexes, and packages.

To prepare for the next section of the tutorial, you will need to create a database

within the db2inst1 instance. Make sure that the db2instance variable is still set

to db2inst1, and then create the sample database using the command db2sampl

drive, using the name of the drive where you want to create the sample. For the

examples in this tutorial, we'll create the sample database on our C drive, as

follows:

C:\PROGRA~1\SQLLIB\BIN>db2sampl c:

Clients, servers, gateways, and hosts: It is particularly important that you

understand the terms client, server, gateway, and host when considering the

security of the entire database environment. A database environment often

consists of several different machines; you must safeguard the database at any

potential data access point. The concepts of clients, servers, gateways, and hosts

are particularly important when dealing with DB2 authentication.

The diagram below illustrates a basic client-server-host configuration.

The database server is the machine (or machines in a partitioned database system)

on which the database physically resides. The DB2 database clients are machines

that are configured to run queries against the database on the server. These

clients can be local (that is, they can reside on the same physical machine as the

database server) or they can be remote (that is, they can reside on separate

machines).

If the database resides on a mainframe machine running an operating system like

AS/400 (iSeries) or OS/390 (zSeries), it's called a host or host server. A gateway is a

machine running the DB2 Connect product. Through the gateway, DB2 client

machines can connect to a DB2 database that resides on a host machine. The

gateway is also referred to as the DB2 Connect Server.

DB2 authentication:

When DB2 authenticates: DB2 authentication controls the following aspects of a database security plan:

Who is allowed access to the instance and/or database

Where and how a user's password will be verified

It does this with the help of the underlying operating system security features

whenever an attach or connect command is issued. An attach command is used to

connect to the DB2 instance, whereas a connect command is used to connect to a




88

database within a DB2 instance. The examples below walk you through the

different ways that DB2 will authenticate a user issuing these commands. In

these examples, we've used the default authentication type of SERVER in the

database manager configuration file.

Log on to the machine where DB2 is installed, with the user ID you used to

create the db2inst1 instance. Issue the following commands:

1. db2 attach to db2inst1

Here, authentication is done implicitly. The user ID used to log onto the machine

is

used and is assumed to be already verified by the operating system.

2. db2 connect to sample user tst1 using mypass

Database Connection Information

Database server = DB2/NT 8.1.0

SQL authorization ID = TST1

Local database alias = SAMPLE

Here, authentication is done explicitly. The user tst1 with the password mypass is

verified by the operating system. User tst1 is successfully connected to the

sample

database.

3. db2 connect to sample user tst1 using mypass new chgpass

confirm chgpass

The user ID tst1 with password mypass is verified by the operating system as in

example 2. The password for tst1 is then changed by the operating system from

mypass to chgpass. As a result, the command in example 2 will fail if you reissue

it.

DB2 authentication types: Authentication types are used by DB2 to determine

where authentication is to take place. For example, in a client-server

environment, will the client or the server machine verify the user's ID and

password? In a client-gateway-host environment, will the client or host machine

verify the ID and password?




89

The following table summarizes the available DB2 authentication types. In a

client-gateway-host environment, these authentication options are set on the

client and gateway, not on the host machine.

Type Description

SERVER Authentication takes place on the

server.

SERVER_ENCRYPT Authentication takes place on the

server. Passwords are encrypted at the

client machine before being sent to the

server.

CLIENT Authentication takes place on the

client machine.

*KERBEROS Authentication is performed by the

Kerberos security software.

*KRB_SERVER_ENCRYPT Authentication is performed by

Kerberos security software if the client

setting KERBEROS. Otherwise,

SERVER_ENCRYPT is used.

*These settings are valid only for Windows 2000 operating systems. 6.6.4 Test Case

Deliverable Responsibility Completion

Date

Develop Test cases Testers 1/12/09

Test Case Review Test Lead, Dev. Lead,

Testers

4/12/09

Develop Automated test suites Testers 6/12/09

Requirements Validation Matrix Test Lead 6/12/09

Obtain User ids and Passwords the

system/database

Test Lead 7/12/09

Execute manual and automated

tests

Testers & Test Lead 8/12/09




90

Complete Defect Reports Everyone testing the

product

10/12/09

Document and communicate test

status/coverage

Test Lead 11/12/09

Execute Beta tests Test Lead 12/12/09

Document and communicate Beta

test status/coverage

Test Lead 13/12/09

Execute User Acceptance tests Test Lead 14/12/09

Document and communicate

Acceptance test status/coverage

Test Lead 15/12/09

Final Test Summary Report Test Lead 15/12/09 Testing Strategy The test strategy consists of a series of different tests that will fully exercise the vehicles online system. The primary purpose of these tests is to uncover the systems limitations and measure its full capabilities. A list of the various planned tests and a brief explanation follows below.

System Test The System tests will focus on the behavior of the vehicles online system. User scenarios will be executed against the system as well as screen mapping and error message testing. Overall, the system tests will test the integrated system and verify that it meets the requirements defined in the requirements document.

Performance Test Performance test will be conducted to ensure that the vehicles online systems response times meet the user expectations and does not exceed the specified performance criteria. During these tests, response times will be measured under heavy stress and/or volume.

Security Test Security tests will determine how secure the new vehicles online system is. The tests will verify that unauthorized user access to confidential data is prevented.

Automated Test A suite of automated tests will be developed to test the basic functionality of the vehicles online system and perform regression testing on areas of the systems that previously had critical/major defects. The tool will also assist us by executing user scenarios thereby emulating several users.




91

Stress and Volume Test We will subject the vehicles online system to high input conditions and a high volume of data during the peak times. The System will be stress tested using twice (20 users) the number of expected users.

Recovery Test Recovery tests will force the system to fail in a various ways and verify the recovery is properly performed. It is vitally important that all payroll data is recovered after a system failure & no corruption of the data occurred.

Documentation Test Tests will be conducted to check the accuracy of the user documentation. These tests will ensure that no features are missing, and the contents can be easily understood.

Beta Test The Payroll department will beta tests the new vehicles online system and will report any defects they find. This will subject the system to tests that could not be performed in our test environment.

User Acceptance Test Once the vehicles online system is ready for implementation, the Payroll department will perform User Acceptance Testing. The purpose of these tests is to confirm that the system is developed according to the specified user requirements and is ready for operational use.

6.6.8 COST ESTIMATION OF THE PROJECT

For a given set of requirements it is desirable to know how much it will cost to develop

the system to satisfy the given requirements, and how much time development will take.

These estimates are needed before development is initiated. The primary for cost and

schedule estimation is to enable the client or developer to perform a cost-benefit analysis and

for project monitoring and control. Software cost estimation has two uses in software project

management. Firstly, during the planning stage, one needs to decide how many engineers

are needed for the project and develop a schedule. Secondly, in monitoring the projects

progress, one needs to assess whether the project is progressing according to schedule and

take corrective actions if necessary.

One can perform cost estimation at any point in the project life cycle. During the feasibility

study we have only some idea of the classes of data the system will get and produce. There

is a great deal of uncertainty about the actual specifications of the system. Specifications with

uncertainties represent a range of possible final products, not one precisely definite product.




92

Hence cost estimation based on this type of information cannot be correct. As we specify the

system more fully and accurately, the uncertainties are reduced and more accurate cost

estimates can be made. Thus once the requirements are completely specified, more accurate

cost estimates can be made compared to feasibility study. Once the design is complete, the

estimates can be made still more accurately.

In developing cost estimate for a system we need to use several cost elements. Among them are hardware, personnel, facility, operating and supply costs.

Hardware Costs: it relate to the actual purchase or base of the computer and

peripherals.

Personnel Costs: it includes EDP staff salary and benefits.

Facility Costs: it includes all the costs associated with lighting, false flowing, air

conditioning etc.

Operation Costs: it includes all the costs associated with Day to Day running of the

system.

Supply Costs: supply is variable cost that increases with the increase of paper.

PROJECT COST ESTIMATION (approx)

Hardware Cost: Rs. 30, 000

Software Cost:

JAVA Rs. 7, 500

DB2 Rs. 3.000

-MS Windows xp Rs. 9, 500

Testing Cost: Rs. 5, 000

Paper Cost: Rs. 1, 000

Reference Books Cost Rs. 1, 500

Implementation Cost: Rs. 1, 500




93

Maintenance Cost: Rs. 1, 000

Printing Cost: Rs. 1, 500

Miscellaneous Cost: Rs. 500

TOTAL Rs. 59,000

However the project pricing will be best suited if it is beween Rs.25,000 to Rs.30,000.

6.7 Supplementary Requirements

Software Interface

Client on Internet: Internet Explorer 6.0 & more, Operating System (any). Client on Intranet: Client Software, Internet Explorer 6.0 & more, Operating System. Web Server: WAS, Operating System (any). Database Server: DB2, Operating System (any). Development End: WSAD (J2EE, Java, Java Bean, Servlets, HTML), DB2, OS (Windows), Web Server.

Hardware Interface

User Characteristics

Every user should be comfortable of working with computer and net. Browsing and should have basic knowledge of English language.

Constraints

GUI is only in English. Login and password is used for identification of customer and there is no facility for guest.

6.8 References

STUDY MATERIALS PROVIDED BY TGMC.

Date post:	07-Mar-2016
Category:	Documents
Upload:	uttariyo-bandhu
View:	33 times
Download:	1 times

vehicles online SRS

Documents