Car Rentel Final Adition

Software Requirement Specification for
Car Rantel System
BSCS Session (2017_ 2021)

Version 1.0
Department of Computer Science & Information Technology

University of Sargodha
1
PREAMBLE
In the name of Allah, The compassionate The Merciful.
“Read in the name of your Lord,

Who creates, man from a clot of blood.
Read, your Lord is most gracious who teaches by means of
the pen,
teaches man what does not know”.
(AL-Quran)
2
Title of the Project:
Car Rentel System
Project Supervisor:
Prof. Kainat
Project Team:
Name of Student Roll Number Signature
Arshia Noor 18BSCS29041
Rahat Arshad 18BSCS29063
Principal Signature:
Project Supervisor’s Signature:
Date:
3
Acknowledgment
The satisfaction that accompanies that the successful completion of any task would be
incomplete without the mention of people whose continued cooperation made it possible,
whose constant guidance and encouragement crown all efforts with success. At first, we thank
Almighty Allah for giving us a greater chance to make this happen.
We dedicate our project to our friends and family who have supported us throughout the
process. We shall always appreciate all they have done, especially our supervisor, to help us
develop our skills, for the many hours of proofreading and coordinate management sciences
for helping us master the leader of dots. We dedicated this work and gave special thanks to our
loving Head of Department Mr. Aftab Razzaq and all our teachers who teach and help us a lot
to learn.
We wish to say thanks to our classmates who helped us sharing their opinion with a great mind
and to all staff members who were directly or indirectly instrumental in enabling us to stay
committed.
4
Contents
 Abstract ............................................................................................................. 1
 Introduction ...................................................................................................... 2
1. Problem Statement ........................................................................................................ 3
2. Aim and Objectives ....................................................................................................... 3
3. Scope and Features ........................................................................................................ 4
4. Tools and Languages ..................................................................................................... 4
5. Methodology................................................................................................................... 5
 System Requirement Analysis........................................................................ 7

1. Information Gathering.................................................................................................. 7
1. Determination of system requirements ................................................................... 7
2. Technology Specifications ............................................................................................. 8
3. System Feasibility .......................................................................................................... 8
1. Technical Feasibility .............................................................................................. 8
2. Behavioral Feasibility ............................................................................................ 9
3. Temporal Feasibility .............................................................................................. 9
4. Functional Requirements.............................................................................................. 9
5. Non-Functional Requirements ................................................................................... 13
 System Design ................................................................................................. 15

1. Architectural Design ................................................................................................... 15
2. Flow Charts .................................................................................................................. 16
3. ER Diagram ................................................................................................................. 21
4.1.Use Case Diagram: Member....................................................................................... 22
Use Case Diagram: Artist ........................................................................................... 23
Use Case Diagram: Admin ......................................................................................... 23
Main Use Case Diagram ............................................................................................. 24
5 Activity Diagrams ........................................................................................................... 25
1. Activity Diagram: Customer ................................................................................ 25
2. Activity Diagram: Artist ....................................................................................... 26
6 Sequence Diagrams ........................................................................................................ 27
3.6.1. Sequence Diagram: Member ............................................................................. 27
3.6.2 Sequence Diagram: Artist .................................................................................... 28
7. Data Flow Diagrams .................................................................................................... 29
8. Context Diagram ......................................................................................................... 31
5
9. Object Diagram ........................................................................................................... 32
10. State Chart Diagram ................................................................................................... 32
i. State Chart Diagram: Online Registration .......................................................... 32
ii. State Chart Diagram: Online Transaction ........................................................... 33
11. Class Diagram .............................................................................................................. 33
12. Database Diagram ....................................................................................................... 35
13.Collaboration Diagram ................................................................................................ 36
 User Interface Design .................................................................................................. 37
Home Page ........................................................................................................... 37
Login Page ........................................................................................................... 38
Register Page ....................................................................................................... 39
Shopping Cart....................................................................................................... 40
Profile Setting ....................................................................................................... 41
My arts .................................................................................................................. 42
My sales ................................................................................................................ 43
Gantt Chart ........................................................................................................................ 46
 Testing ............................................................................................................ 48
6.1.1 Objectives: ............................................................................................................ 48
 Personal Reflection........................................................................................ 56
 Future Scope ................................................................................................... 58
Extensibility ................................................................................................................. 58
Reusability .................................................................................................................... 58
Understandability ........................................................................................................ 58
Cost-effectiveness......................................................................................................... 58
 Summary ......................................................................................................... 60
 References ....................................................................................................... 62
6
Abstract
Car rental management system is a project which aims in developing a computerized system to maintain all
the daily work of Car Rental .This project has many features which are generally Not available at regular car
rental stores , like facility of customer login and a facility of admin login .It also has a facility of admin login
through which the admin can monitor the wholes system .It also has facility of an online notice board where
Admin can put up information about the cars available in the exhibition and their prices and updating all data
that go through the rental process. It has also a facility where user after logging in their accounts can see list
of cars and its price and Availability of the car and also the customer can request the admin to add new type
of cars by filling the cars request form. The admin after logging into his account is admin account can
generate various reports such as cars report, users/ customer report. Overall, this project of ours is designed to
help anyone make it easier during the process of buying or renting a car in the best possible way, as well as
reducing human efforts and obtaining the best offers.
\
Car Rental System Introduction
rRRRRequi
rement
Chapter 1
Introduction
2
\
rRRRRequi
rement
 Introduction
Now days, almost human life becomes more and more easier. It is possible only because of the
technology. Various online systems make the life of human very comfortable. By some clicks
only, we can get whatever you want at home. We already know about the online shopping, e-
banking, etc. Similarly, The Car Rental System is the online facility to book cars online within
few clicks only. Some people cannot affort of having a car, for those people this system becomes
very helpful. This system includes various cars, as per the customer order and comfort, it place
the order and deliver the car as per the location within the area. For travelling a long distance,
booking can be done via internet service only.
Document Purpose:
The main purpose of this document is to provide information about the entire system. Online connectivity
with database provides information about various cars and costing. The organization uses a manual system
for reserving, renting, register and to keep record of all the rental activities and customer information. Online
Car Rental system gives car rental service forlocal customers. This organization carries out its daily work by
providing; their service to the customers using manually system. That will be make easy reservation for
customers.
1. Drawbacks of the present systems

The drawbacks or disadvantages are the critical points for the development of the proposed
system. Some of the flaws are as follows:
1. Higher Prices
2. Strict Term
3. Extra Charges
4. Limitations License
5. Payment issues
6. Ambiguous Website Policies
7. Delivery problems
8. Safety issues
9. Delay in the delivery
10. Hidden costs and shipping charge
2. Document Purpose
The main purpose of this document is to provide information about the entire system. Online connectivity
with database provides information about various cars and costing. The organization uses a manual system
for reserving, renting, register and to keep record of all the rental activities and customer information. Online
Car Rental system gives car rental service for local customers. This organization carries out its daily work by
3
\
rRRRRequi
rement
providing; their service to the customers using manually system. That will be make easy reservation for
customers.
4
\
rRRRRequi
rement
3. Scope and Features
The idea of renting a car is on the boom because of the flexibility and independence that
comes along with it.
The scope of this project is as follows:

1. The Car rental system to keep detail records of both the cars and the customers. The duration they
rent car as well as the type of car they rent.
2. The system will be mainly design for small a company that renders it car rental services to customers.
3. The system will have the ability to generate and print in voice for each successful transaction.
4. Level of assess
5. The system will have two level of access
6. The administrator
7. The customer
Features:
1. Easy Bookings
2. Flexible plans
3. Communication and updates
4. Localization
5. Social media integration
6. Communication and updates
7. The FAQ section
8. User role management
9. Grouping and tracking
10. Member profiles
11. Websites analytics
12. Social media integration
13. Flexible quotation system
14. Quick and secure payments
This Project traverses a lot of areas ranging from business concept to computing field and required to
perform several researches to be able to achieve the project objectives.
The area covers include:
 Vehicle Rental industry:

This includes study on how the vehicle business is being done, process involved and
opportunity that exist for improvement.
 .NET technology is used as front end for development of application.
 MYSQL is used as backend for development of application.
 General customer as well as company staff will be able to use them effectively.
 Web platform means that the system will be available for 24/7 except when there is a
temporary server issue which is expected to be minimal.
Intended Audience And Document Overview:
An existence system has a number of problems in the working procedure for the organization and
customers. These problems are: -
5
\
rRRRRequi
rement
1. During reservation a customer reserve a car on phone or expected to go to the organization for
reserving. This has its own problem in the business sector.
 The organization phone may be busy or may not work when customer is calling to make
reservation.
 It may be difficult to customers to get the phone number or the location of the organization.
 The customers may be resulted to unnecessary extra expense and waste their time.
 Their may accrue duplicated reservation of the same car.
 The organization may not be able to serve many customers.
 The customers may not get service of the organization 24/7 (twenty four hours a day and
seven days a week) and limiting their service to local domain only.
2. During renting a car, the customer information and contract made between them are filled in a
form.
 The contract form made between the customer and organization may be difficult to find in
case of misplacing or disappearing due to massive collection of data.
3. During generating monthly report.

 When generating report, it takes time and it may not be easy to manage and analysis the
monthly work due to massive collection of data and the generated report may not be accurate.
4. Tools and Languages
Web development languages will be used such as
 HTML, CSS, Bootstrap Framework for front end.

 PHP and MySQL for backend.
Tools will be used such as
 Microsoft Visual Studio

 XAMPP
All of the above tools and languages are free to use and does not require a purchased license.
6
\
rRRRRequi
rement
2. Methodology
To provide solution to the objectives, we'll design responsive front end for end-users and store
staff. We will develop using PHP scripting language and MySQL for backend or server side,
and use CSS, Bootstrap, JavaScript for making front end as responsive as possible. Designing
simple, friendly and less complex are going to be the primary priority. Implementation and unit
testing are going to be meted out within the development cycle of the application. Proper
documentation will be carried out. The approach that was employed in the look of the system
is that the Incremental Model of System Development Life Cycle where the product being
designed is implemented and tested incrementally. It is relatively cheap and is employed for
small projects. This system is best suited for the project because of the project’s future
requirements which might require changes within the system.
Definitions, Acronyms and Abbreviations
SRS - Software Requirement Specification

Admin - Administrator
HTTP- Hyper Text Transfer Protocol
PHP- Hypertext Preprocessor
1.5 Document Conventions

Font size (title): 16
Font size(Subtitle):14
Font size (content):12
Font style (title, content): Times New Roman
1.6 References and Acknowledgments

Academia.org
7
\
rRRRRequi
rement
Chapter 2
System Requirement Analysis
8
Online Art Gallery System Requirement Analysis
 System Requirement Analysis
2.1.1 Existing system function:

Car Rental System gives car rental service for local customers. This organization carries out its daily work
by providing; their service to the customers using manually system. The organization uses a manual system
for reserving, renting, register and to keep record of all the rental activities and customer information. the
detailed existing system functions are listed as follows: -
 During car reservation the customers reserve a vehicle by making a phone call to the
organization; otherwise he/she is expected to go to the organization to make reservation.
 During renting a car the customer personal information, payments status and rent agreements
are filled in the car rent agreement form in order to hold legal contract between the customer
and organization for renting the vehicle.
 The organization gives services for 24/7 hours.
 The organization makes a general report about the rented cars once at the end of the month
and generates a report.
2.1.2 Product functionality:

Car Rental System provides the features for booking a car online.It includes several functionalities describes
as below:
 Car Rental Management:
It provides car reservation facility online. Customer can visit the website and check for various cars.If they
are feasible with requirement, then booking can be done.
 Checking For Availability:
Employee can check for the availability of the car. He/she maintains the database of car.If no any car is
available it is the responsibility of the employee to provide alternative options.
 Payment system:
Administrator/owner of the applicationis responsible for payment to the
employee.Ordercancellation,orderfinalize,these all activities are done by the administrator of the
application.
 Maintenance Manager:
9
If any car requires maintainace like repair or replacement of any parts,thenmaintainance manager maintain
the data about that.Payment of maintainance are done by the administrator of the application.
Users and Characteristics:

 Admin:
Admin can login to the system.
Verify the car information database.
Generate price strategy.
Handle the payment system.
Finalize the order.
Cancel the order.
Manage location
 Customer:
Customer can login to the system.
Visit the website.
Select/search a car
Place the order.
Payment
Cancel the order.
 Maintanance Manager:
It checks for the maintainance.
Give information to the admin.
Update the database.
2.1 Operating Environment :
Server Side:
 Processor : Intel PIII or Higher
 HDD : Minimum 20GB Disk Space
 RAM : Minimum 1GB
 OS :Windows XP, Linux
 Database : SQLServer 2005
10
 Software : SQLServer 2005,Microsoft Visual Studio 2008

Client Side:
 Processor : Intel PIII or Higher
 HDD : Minimum 20GB Disk Space
 RAM : Minimum 1GB
 OS : Windows XP, Linux
2.2 Design and Implementation Constraints
 We have used Asp.Net, Ajax and JQuery as our language for this web application.
 Minimum Intel Pentium 4 and 256MB Ram is required.
 HTTP and FTP protocols are used as communication protocols. FTP is used to upload the web
application in live domain and the client can access it via HTTP protocol.
 Several types of validations make this web application a secured one and SQL Injections can also be
prevented.
 Since Car Rental system is a web-based application, internet connection must be established.
 The Car Rental System will be used on PCs and will function via internet or intranet in any web
browser.
User documentation:
There will be no user manuals, online helps or tutorials as it is made as simple as web beginners can also use
it easily with best web GUI functionality.
2.3 Assumptions and Dependencies :
 Regularity Policies:
Each center user has account created and authenticated by admin. This Website can be accessible within
company’s intranet and other user can see the all details about the franchisee. Each user has to first login
itself to present him/her after entry in franchisee. This will be done automatically.no user can share their
username and password to each other.
11
 Hardware Limitations:
There is no limitation in the operating system in which Car Rental Systemwill work. However, the Car
Rental System and the database will work on a server that needs to be always online. Users can access the
system with any internet browser.
Functional Requirements:
Functional requirements are a set of specifications that describe the functions, features, and capabilities that a system
or product must have in order to meet the needs and expectations of its users. These requirements are typically
expressed as specific, measurable, and testable criteria that the system must fulfill.
The functional requirements and basic flow for this android application are;
1. Registration:
 Users will be able to create an account by signing up a form.
 Profile Screen will show the user his/her details (His/her name, Address, Postal
Code, note regarding address.
 Registration Confirmation by the System.
 User can see the history of his rental.
2. Car registration:
 The car owner will be able to enter details about their cars i.e. model, seats
available, brand, etc.
 Registration Confirmation by the System.
3. Explore car by category:
 Display list of available cars to user in the mobile app view.
 User can select rent a car with and without Driver option.
 User will select the desired car for rent and click book now button.
4. Payment Method:
 Allows users to rent an online car, and performs the transaction using online
payment methods.
5. Feedback:
 The screen will show a wide text area and the submit button so that users can send
feedback.
6. Generate Report:
 Daily, monthly, and yearly report should be generated.
Non- functional requirements:
The non-functional requirements and basic flow for this android application are
Performance Requirements:
The database shall be able to accommodate a minimum of 1,000 records of renters. The database
shall be able to accommodate a minimum of 1,000 records of rentee. The website shall support the
use of multiple users at a time.
There are no other specific performance requirements that will affect development.
12
Availability:
The website is available 24/7 anywhere, but the dealing can be done when both parties are
available.
Reliability:
The website would perform desired tasks as expected.
Ease of Use
The proposed system be user-friendly and would provide a Graphical User Interface (GUI).
13
14
15
16
Chapter 3
System Design
17
Online Art Gallery System Design
 System Design
1. Architectural Design
Internet
Server
Two-Tier Architecture
Users
The two-tier architecture is where a client talks directly to a server, with no intervening server.
It is simple to build. In our project, this architecture is implemented because the client that is
the user sends a request to the server that the server fulfils by merely referring to the database
and retrieving the information asked for.
Architectural Context Diagram
Users Online Art Database

Gallery
Management
System
18
2. Flow Charts
A flowchart is a picture of the separate steps of a process in sequential order. It is a generic tool
that can be adapted for a wide variety of purposes, and can be used to describe various
processes, such as a manufacturing process, an administrative or service process, or a project
plan.
a) Signup:
Start
Enter username and

password and re-
enter password
Verify from database
Print username
Does No already exists.
exist? Choose another
username
Yes
Move to
registration page
Stop
19
b) Login:
Login is the system that authenticates users to use the system to prevent unauthenticated
users from using the system. To login into the system, the user will provide login
credentials like username and password. The system verifies the user from the database
and authenticates if the credentials are valid. The system will redirect the user to a page
containing dynamic content, only regarding that specific user.
Start
Enter username and

password
Verify from database
Print Invalid
No username or
Is Correct?
password
Yes
Login to home
page
Stop
20
c) Registration:
Start
Enter username,
password
Verify to check
weather all constraints
are satisfied
Print Your
No details cannot
Is Correct? be added. You
may try again
Yes
Print Your details have
been a successfully
added to database
Stop
21
d) Add Painting:
e) View Painting:
22
f) Update Painting:
g) Buy Painting:
23
3. ER Diagram
Price
Art id
Art Type
Art Uploads Name

User
Art Name Address
IS-A Artist Password

Customer
Name
Artist id
View Not-registered IS-A Admin

Password
Email
Email
Name
Manages
Registered
Address
Shipping
Password Email
Places Order
Customer-id
Payment
Order-id
24
4. Use Case Diagram
 There are the following use case diagrams for an Online Art Gallery:
Use Case Diagram: Member
<<include>> Name
Registration <<include>>
Password
<<include>>
Email
Get-profile
<<include>>
View Gallery
Place order
<<include>>
Search-By-Artist <<include>>
<<extend >> Payment

<<extend >>
Shipping Details
Customer Artist Name Artist Id
Shipping Details
Online Art Gallery
Payment
Login/ Logout
25
Use Case Diagram: Artist
Registration
Login
Select Car
Artist
Online Art Gallery

Search
C
Login/ Logout
Use Case Diagram: Admin
Login
Manage Customer
Manage Car rent

provider
Admin
Manage Payments
Location
Online Art Gallery
26
Main Use Case Diagram:
There are the following main use case diagram for an Online Art Gallery:
<<include>> Name
Registration <<include>>
<<include>>
Password
Email Manage Arts
View-gallery Manage Artists

<<include>>
Registered Place order

<<include>>
<<include>>
Customer
Shipping Details
Payment
Non -Registered
Search-By-Artist
<<extend >>
<<extend >>
Manage Customers
Artist Name
Artist Id Admin
Sell Arts
Manage Orders
Artist
Online Art Gallery
Get-profile
Login/Logout
27
5 Activity Diagrams
Activity diagram is another important behavioral diagram in UML diagram to describe
dynamic aspects of the system. Activity diagram is essentially an advanced version of flow
chart that modeling the flow from one activity to another activity. There are the following
activity diagrams for the system:
1. Activity Diagram: Customer
Start
Registration
No
If Registered
Yes
login
No
Valid
Yes
Get profile
View Gallery
Place Order
Password
Payment
Logout
End
28
2. Activity Diagram: Artist
Start
Registration
Input details
Store details
login
Valid
No
Yes
Get profile
View Gallery
Update Gallery
Logout
End
29
6 Sequence Diagrams
A sequence diagram represents the interaction between different objects in the system. The
important aspect of a sequence diagram is that it is time-ordered. This means that the exact
sequence of the interactions between the objects is represented step by step. Different objects
in the sequence diagram interact with each other by passing "messages".
3. Sequence Diagram: Member
:member login get profile view gallery billing order payment

:Member :Admin
1: register()
2: login()
registered
Logged-in
3: update()
updated 4: get arts ()
5: submit()
Submitted
successfully 6: order ()
ordered
7: payment ()
8: transactions ()
9: confirmation ()
30
3.6.2 Sequence Diagram: Artist
artist login get profile upload view gallery

:Artist :Admin
1: register()
registered 2: login()
Logged-in
3: update()
Logged-in
4: upload()
Uploaded
5: get arts()
successful
6: check arts()
7: confirmation ()
31
7. Data Flow Diagrams
Data flow diagram is used to decrease analysis the movement of data through a system store of data
in the system. Data flow diagrams are the central tool basing on which components are developed.
The transformation of data from input to output, through process may be describe logically and
independently of physically components associated with the system. They are called logical data flow
diagrams. In contrast physical data flow diagrams show the actual implementation and movement of
data between people, Department, and work station.
The data flow diagram shows functional composition of the system. The first level of conceptual level
in context diagram is flowed by the description of input and output for each of entities the next level
of DFD is level 0, which shows the main functions in the system. Level 0 is followed by the description
of the main functions. The main function further broken into functions and sub functions.
Square: which represents source or

destination.
Arrow: which represents dataflow.

ie; data stream.
Circle: which represents a process

that transforms data streams.
Represents database.
32
DFD level 0:
Member Artist
Art Gallery
Admin
DFD Level 1 Artist:
Artist Registration
Change
Password
Login
Database
Get View Search by Upload

Profile Gallery Artist Art
33
DFD Level 1 Admin:
Artist
Member Art Gallery Database
Admin
Context Diagram:
login login
register register
Member Art Gallery Artist
get details get details
Activate &
transactions
deactivation
Admin
34
a. Object Diagram:
The object diagram is a special kind of class diagram. An object is an instance of a class. This
essentially means that an object represents the state of a class at a given point of time while the
system is running. The object diagram captures the state of different classes in the system and
their relationships or associations at a given point of time.
1.1 1.1
A: Admin
1.1 1.1 1.1
1:*
1:*
1:*
1:*
M: Member L: Login R: Register T: Transactions G: Gallery
b. State Chart Diagram:
A state diagram, as the name suggests, represents the different states that objects in the system
undergo during their life cycle. Objects in the system change states in response to events. In
addition to this, a state diagram also captures the transition of the object's state from an initial
state to a final state in response to events affecting the system.
i. State Chart Diagram: Online Registration
Member Registration Admin Database
Registration Validation Store
Confirmation
35
ii. State Chart Diagram: Online Transaction
Member Login Admin Transaction Database
Login Valid
Purchase Store
Confirmation
c. Class Diagram:
The class diagram represents the static, structural, “data” aspects of a system. Typical
information in a class diagram includes classes, associations, and inheritance. The class
represents entities with common characteristics or features such as attributes, associations, and
operations. Classes represent an abstraction of entities with common characteristics.
Associations represent the relationships between classes. The class diagram shows how the
different entities (people, things, and data) relate to each other; in other words, it shows the
static structures of the system. A class diagram can be used to display logical classes, which
are typically the kinds of things the business people in an organization talk about --Admin,
customers, System; Category, Products, Details. Class diagrams can also be used to show
implementation classes, which are the things that programmers typically deal with. An
implementation class diagram will probably show some of the same classes as the logical
class’s diagram. The implementation class diagram won't be drawn with the same attributes.
Illustrate classes with rectangles divided into compartments. Place the name of the class in the
first partition (centered, bolded, and capitalized), list the attributes in the second partition, and
write operations into the third.
36
37
d. Database Diagram
38
e. Collaboration Diagram:
A collaboration diagram groups together the interactions between different objects. The
interactions are listed as numbered interactions that help to trace the sequence of the
interactions. The collaboration diagram helps to identify all the possible interactions that each
object has with other objects.
For member:
Member
: member
1: register ()
2: login () 9: confirmations ()
6: order ()
: login : order Admin

: get profile
3: update ()
7: payment ()
5: submit () 8: transactions ()
4: get arts ()
: view gallery : payment
: billing
For artist:
Artist
: artist
1: register ()
2: login () 7: confirmation ()
3: update ()
: get profile
: login Admin
5: get arts () 4: upload ()
6: check arts ()
: view gallery : upload
39
 User Interface Design
Home Page
40
Login Page
41
Register Page
42
Shopping Cart
43
Profile Setting
44
My arts
45
My sales
46
Categories
Drawing
Painting
47
1.1.8.2 Photography
1.1.8.2 Sculpture
48
Gantt Chart:
The Gantt chart enumerates the activities to be performed on the vertical axis and their
corresponding duration on the horizontal axis. It is possible to schedule activities by either
early start or late start logic. In the early start approach, each activity is initiated as early as
possible without violating the precedence relations. In the late start approach, each activity is
delayed as much as possible as long as the earliest finish time of the project is not compromised.
Based on the Work Breakdown Structure (WBS), a timeline or Gantt chart showing the
allocation of time to the project phases or iterations should be developed. This Gantt chart
would identify major milestones with their achievement criteria. It must contain duration
estimation of all the necessary activities to be carried out during the project development along
with the human resources responsible for the respective tasks. Activity dependencies are also
required to be mentioned in it.
49
Online Art Gallery Testing
Chapter 4
Testing
50
 Testing
Testing is the process of detecting errors. Testing performs a very critical role for quality
assurance and for ensuring the reliability of software. The results of testing are used later on
during maintenance also.
6.1.1 Objectives:
 To identify Testing Requirements (Scope):

 to identify the software to be tested
 to identify the testing objectives
 to identify the test phases (testing coverage) within the testing life cycle that is
required
 To identify Testing Approach:

 to identify the methods and testing tools required
 to identify any client assumptions/dependencies/limitations
 To identify Testing Tasks and Deliverables:

 to identify the activities to perform within each testing phase.
 to identify the external (client) deliverable document.
 to identify the table of contents for each deliverable
 to identify the internal deliverable documents
 to identify document deliverable reviewer
 To compile Testing Estimates:

 to identify the budgetary estimate for each identified phase of software testing.
 To determine Testing Schedules:

 to identify the start and end date for each phase of software testing
 to identify all testing phase overlaps in the schedule
 to identify delivery dates for all document deliverables
 To determine Test Environments:

 to identify the software/hardware requirements for each test phase
 to identify the number of test environments
 To identify Test Team Roles and Responsibilities:

 to identify the overall testing management responsibility and for each test phase
 to identify client roles and responsibilities
51
Levels of Testing
In order to uncover the errors, present in different phases we have the concept of levels of
testing. The basic levels of testing are as shown below:
Acceptance Testing
Client Needs
System Testing
Requirements
Integration Testing
Design
Unit Testing
Code
Fig: 6.2.1 Levels of Testing
Code Testing:
This strategy examines the logic of the program. To follow this method, we developed some
test data that resulted in executing every instruction in the program and module i.e. every path
is tested. Systems are not designed as entire nor are they tested as single systems. To ensure
that the coding is perfect two types of testing is performed or for that matter is performed or
that matter is performed or for that matter is performed on all systems.
Unit Testing:
The goal of unit testing is to assure that all functions and features of a single compliable unit
of code perform as specified in the Design Specification.
A unit test covers the testing of a software unit, or a group of closely related units, as a single
entity. Unit testing is performed in isolation, using test drivers to simulate higher level units,
and/or stubs to simulate lower-level units.
Unit Testing Procedures consist of:
 Creating a Unit Test Plan
52
 Creating test data

 Conducting tests according to the Unit Test Plan
 Reporting and reviewing the results of the test
These procedures are performed by the team member responsible for programming and testing
of the unit.
A Unit Test Plan is a set of test cases arranged in the sequence of chronological execution. The
Unit Test Plan is created before the programming of the unit is started, and the test cases should
cover the functional, input, output, and function interaction of the unit.
Integration Testing:
The goal of integration testing is to ensure that all interacting subsystems in a system interface
correctly with one another to produce the desired results. Furthermore, in trying to attain this
goal, integration tests will ensure that the introduction of one or more subsystems into the
system does not have an adverse effect on existing functionality.
An integration test covers the testing of interface points between subsystems. Integration
testing is performed once unit testing has been completed for all units contained in the
subsystems being tested.
Integration Testing Procedures consist of:
 Creating and integration test plan

 Conducting tests according to the integration test plan
During this phase, the interaction between subsystems is tested. This includes interfaces
through Inter Process Communications (IPC) and files. This phase is performed by an
independent test team. This team prepares and executes integration tests, generates problem
reports and is responsible for passing the integrated system on to the System Test Team for
system testing. The Integration Test team then enters a support mode in which it will test
problem reports generated by the System Test team before forwarding code fixes to the System
Testing environment.
This phase is sometimes combined with the system test phase as per the client's request.
System Testing:
The goal of System Testing is to ensure that the system performs as per the functional
requirements specified by client.
A system test covers the testing of functions within the system. System testing is performed
once integration testing has been completed. System Testing procedures consist of:
53
 Creating Test Plans

 Conducting tests according to the System Test Plan
Features to be tested during System Testing are:

 Functional Requirements
 Depending on the project, any regression tests deemed necessary
Acceptance Testing:
Acceptance Test is performed with realistic data of the client to demonstrate that the software
is working satisfactorily. Testing here is focused on external behavior of the system; the
internal logic of program is not emphasized. In this project we have collected some data and
tested whether project is working correctly or not.
Test cases should be selected so that the largest number of attributes of an equivalence class is
exercised at once. The testing phase is an important part of software development. It is the
process of finding errors and missing operations and also a complete verification to determine
whether the objectives are met and the user requirements are satisfied.
54
Chapter 5
Implementation and Maintenance
55
5. Implementation and Maintenance
 Implementation:
To implement a project means to carry out activities proposed in the application form with the
aim to achieve project objectives and deliver results and outputs. Its success depends on many
internal and external factors. Some of the most important ones are a very well-organized project
team and effective monitoring of the project progress and related expenditures. Overall
management has to be taken over by the lead partner and project manager, who is often
employed or engaged by the lead partner. The project management has to have an efficient
management system and always has to be flexible to current needs and changes situations, as
the project is rarely implemented exactly according to the initial plan. Nevertheless, the
partnership should aim to deliver quality results and outputs. Quality means expectations
described in the application and those agreed upon within the partnership.
 Maintenance:
The system analyst has to keep on carrying out changes and modifications into the system, a
stage called normally system maintenance.
 Corrective maintenance: This pertains to changes in the software to correct defects.
 Adaptive maintenance: Over time, the original environment for which the web
application was developed is likely to change, this maintenance results in a modification
to the software to accommodate changes to its external environment.
For the implementation and maintenance of this system, the administrator must have the
following tools and environment:
 A webserver to host this application
 The webserver must allow MySQL database and PHP
 A domain name for the system website
 System Training
 Internet connection
 A web browser to access the system through the internet
To, implement Online Art Gallery following procedure needs to be followed:
 The package contains a zip file. Extract the zip file and there should be folder named
oag and database backup file oag.sql,
 Create a database named oag in the server. Then select the database and click on the
import button.
 Choose the backup file oag.sql, extracted from the zip file, and click go button to
restore the database backup which will also create database tables.
 Now, copy the oag folder to the server, in htdocs folder or public_html.
 Open the config.php file in includes folder, from oag folder.
 You’ll find the following part of code:
56
$servername = "localhost";
$username = "root";
$password = "";
$dbname = " oag";
 Change the credentials according to your server credentials if necessary.
57
Chapter 6
Personal Reflection
58
Online Art Gallery Personal Reflection
6. Personal Reflection
In this project development process, we have learnt a lot of new knowledge and programming
code from this project. Besides that, there are also some problems that appears as biggest
challenge during the development process. During system design stages, the problem appears
on how to construct the Entity Relationship diagram and Data Flow Diagram. Assignments and
studies materials in Diploma level studies materials are referred back. Some sample diagram
and researches are done via Internet for more reference.
On the other hand, the biggest harvest gained through this project development process is the
importance of communication between teammates. The communication is very important
because there must be integration between 2 teammate’s systems. We must communicate at
early stage so that there is no crash when integration. A good communication is needed to avoid
unnecessary problems appear and delay the completion time.
59
Online Art Gallery Personal Reflection
Chapter 7
Future Scope
60
Online Art Gallery Future Scope
1. Future Scope
For future enhancement, there are few suggestions to improve the system abilities. There is a
future scope of this facility that many more features such as artworks can be added by artists
as well as admin, a feature of chat where they can discuss various issues of engineering can be
added to this project thus making it more interactive more user friendly and project which
fulfils each user need in the best way possible.
This application can be easily implemented in various situations. We can add new features as
and when we require. Reusability is possible as and when require in this application. All the
modules are flexible.
Extensibility
This software is extendable in ways that its original developers may not expect. The following
principles enhance extensibility like hiding data structure, avoid traversing multiple links or
methods, avoid case statements on object type and distinguish public and private operations.
Reusability
Reusability is possible as and when required in this application. We can update it next version.
Reusable software reduces design, coding and testing cost by amortizing effort over several
designs. Reducing the amount of code also simplifies understanding, which increases the
likelihood that the code is correct. We follow up both types of reusability: Sharing newly
written code within a project and reusing previously written code on new projects.
Understandability
A method is understandable if someone other than the creator of the method can understand
the code (and the creator after a time-lapse). We use the method, which small and coherent,
helps to accomplish this.
Cost-effectiveness
Its cost is under the budget and make it within the given period. It is desirable to aim for a
system with a minimum cost subject to the condition that it must satisfy the entire requirement.
61
Online Art Gallery Summary
Chapter 8
Summary
62
Summary
The art gallery management system has to be computerized to save time. The aim of the site is
reliability, availability, security and portability. The proposed art gallery management system
in this proposal will be a computerized management system developed to keep up all the daily
work of Gallery. Art gallery management systems are designed to store all the knowledge about
Arts and Artists.
The application entitled Online Art Gallery developed is designed in such a way that any further
enhancement can be done with ease. The system has the capability for easy integration with
other systems. New modules can be added to the existing system with less effort. we put as
much as our effort to develop this system-based application titled Online Art Gallery that is
easily accessible, informative and helpful. It has been designed in such a way that it is easy to
modify, can be updated efficiently and accurately. The forms are designed user friendly by
providing messages and captions whenever necessary, so that user has no problem to overcome
difficulties in data entry, validation, searching etc. On realizing the importance of systematic
documentation all the processes are implemented using a software engineering approach.
Working in a live environment enables one to appreciate the intricacies involved in the system
development life cycle (SDLC). we have gained a lot of practical knowledge from this project,
which we think, shall make us stand in a good state in the future.
Once again, we would like to thank everyone who was somehow or other related with the
successful completion of this project.
63
Chapter 9
References
64
Online Art Gallery References
References
 Software Engineering: A Practioner's Approach by Roger S. Pressman
 Wikipedia.org
 W3Schools Online Web Tutorials (w3schools.com)
 Bootstrap (getbootstrap.com)
 Visual Paradigm Online (visual-paradigm.com)
 Google web search
65

Car Rentel Final Adition

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Car Rentel Final Adition

Uploaded by

Copyright:

Available Formats

Software Requirement Specification for

Car Rantel System

BSCS Session (2017_ 2021)

Department of Computer Science & Information Technology

In the name of Allah, The compassionate The Merciful.

“Read in the name of your Lord,

Name of Student Roll Number Signature

Arshia Noor 18BSCS29041

Rahat Arshad 18BSCS29063

Project Supervisor’s Signature:

 System Requirement Analysis........................................................................ 7

 System Design ................................................................................................. 15

1. Drawbacks of the present systems

The scope of this project is as follows:

 Vehicle Rental industry:

Intended Audience And Document Overview:

3. During generating monthly report.

4. Tools and Languages

Web development languages will be used such as

 HTML, CSS, Bootstrap Framework for front end.

 Microsoft Visual Studio

Definitions, Acronyms and Abbreviations

SRS - Software Requirement Specification

1.5 Document Conventions

1.6 References and Acknowledgments

 System Requirement Analysis

2.1.1 Existing system function:

2.1.2 Product functionality:

Users and Characteristics:

 Software : SQLServer 2005,Microsoft Visual Studio 2008

2.2 Design and Implementation Constraints

2.3 Assumptions and Dependencies :

Non- functional requirements:

The website would perform desired tasks as expected.

Architectural Context Diagram

Users Online Art Database

Enter username and

Verify from database

Enter username and

Verify from database

Art Uploads Name

IS-A Artist Password

View Not-registered IS-A Admin

4. Use Case Diagram

Use Case Diagram: Member

<<extend >> Payment

Use Case Diagram: Artist

Online Art Gallery

Use Case Diagram: Admin

Manage Car rent

Main Use Case Diagram:

Email Manage Arts

View-gallery Manage Artists

Registered Place order

1. Activity Diagram: Customer

2. Activity Diagram: Artist

3. Sequence Diagram: Member

:member login get profile view gallery billing order payment

updated 4: get arts ()

3.6.2 Sequence Diagram: Artist

artist login get profile upload view gallery

7. Data Flow Diagrams

Square: which represents source or