REQUIREMENTS ENGINEERING AND MANAGEMENT

REVIEW-3

PROJECT TOOL
ENTERPRISE ARCHITECT-SPARX SYSTEM

PROJECT TITLE
VEHICLE MANAGEMENT SYSTEM

FACULTY
DEEPA.M

PROJECT HOLDERS
N. PUNITH [17MIS0093]
M.SHYAM PRASAD REDDY [17MIS0371]
C. VENKATESH [17MIS0388]
J. JAGADEESHVARAN [17MIS0400]
INDEX: -

S.NO TOPIC

1 ABSTRACT

2 INTRODUCTION ON PROJECT TOOL AND TITLE

3 PROBLEM ANALYSIS

4 FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS

5 STAKEHOLDER AND USE CASES

6 USE CASE DIAGRAM

7 DESCRIPTION OF MODULES

8 OUTPUT

9 CONCLUSION

10 REFERENCE
ABSTRACT: -
Enterprise Architect is an intuitive, flexible and powerful UML analysis and design tool for building robust
and maintainable software. From requirements gathering, through analysis, modelling, implementation
and testing to deployment and maintenance, Enterprise Architect is a fast, feature-rich, multi-user UML
modelling tool, driving the long-term success of your software project.
Will be able to create new user and passwords. We will be able add or update the employee information in
the company. One can add and view the information of transport categories and also available routes and
we can know the details of the modules and we can be able access each module and compare the
information in the modules. Depending on the users’ demands new routes and also new pick up points can
be added to the database. the whole vehicle system management system depends on the user and user
can modify the information. The transport people can view all the information related to who are the
employees utilizing the transporting. they can take a decision to approve or disapprove the request placed
for transportation.
User and guest users are employee who want to use the transport facility. The users can place their request
for a bus to reach the company or for a cab when they want to go to a different place. these requests are
approved or declined by the transport people or project manager

KEY WORDS IN TOOL: -

SPARX: - Single particle analysis for resolution for extension
i)Design and Build Diverse Systems Using UML:
ii)Model and Manage Complexity
iii)Structured Use Case Scenarios
INTRODUCTION ON PROJECT TOOL: -
Sparx Systems Enterprise Architect is a full life-cycle UML based tool for:
✓ Designing and constructing a wide range of software systems

✓ Business analysis, business process modelling, managing requirements

✓ Systems modelling, systems architecture modelling, component design, simulation

✓ Generalized domain specific modelling

✓ Building domain specific modelling languages based on UML

✓ Visualizing a wide range of systems, processes, data, activities and structures

✓ Simulating behavioral processes, state machines and interactions

✓ Collaborating and sharing information and models

✓ Testing, quality control and end-to-end verification/traceability of complex systems

✓ Managing developmental tasks, work and scheduling

Enterprise architect: sparx system helps us to draw the UML diagram like
use case diagram
sequence diagram
class diagram
activity diagram
state diagram
deployment diagram and
component diagrams
INTRODUCTION ON TITLE: -
VEHICLE MANAGEMENT SYSTEM:
Vehicle Management System is software which is helpful for bus operators, who wants to operate many bus
trips in a day. which focused in the area of adding, editing and deleting the passengers, staff and the bus
routes. In this software a person can be register as a user and he can manage the bus routes and the staff,
passengers and details He can add a bus and its details including bus route details. User can also add the
details of the staff and their duty time in the system. It is very useful for the operators and passengers they
can decrease the working strain and can keep essential documents associated to the bus and the passengers.
The advantage of the proposed system is the decrease in the cost of the office equipments , the business is
done speedily and any operator can analyze easily if any seats for a particular route in a particular day are
available or not.
Modules:
i) Bus Management

ii)Employee Management
iii)Route Management
iv)Passenger Management
BUS MANAGEMENT SYSTEM: -
In Bus module a client can add another transport subtle elements to the database. He can set the subtle
elements of the course and the planning moreover. Transport points of interest like the sort, motor number,
seating limit and the course in which the transport will be worked are included.
EMPLOYEE MANAGEMENT SYSTEM: -
This system makes the process of scheduling much easier and computerized. By this system the manager or
top level designated employee can fix the schedule of any employee working under him, he even can check
whether the employee is free in the particular time or in other times. Thus the top level management can
easily fix the process of scheduling, and even can change the appointment which is reflected immediately to
the related employee avoiding direct contact of the employee resulting in saving lot of time and work
overhead.
ROUTE MANAGEMENT: -
Route Management module deals with the route management of the bus. A user can add the route and if he
wants he can change it or delete that route. The main advantage is that this module is helpful for the agents
to get details of the route and the details of the bus which have trip to that route. He can also get the
information of the number of seats available in a particular day.
PASSENGER MANAGEMENT: -
The proposed system is very useful for the operators and passengers. This avoids the overheads for the
operators. They can minimize the working stress and can keep essential documents related to the bus and the
passengers as a softcopy. The advantage of the proposed system is the reduction in the cost of the office
equipments and the transaction is done quickly. Any operator can answer if any seats for a particular route in
a particular day are available or not. if they have any complaint against staff he can approach the operator
and easily identify the employee. Details of every passenger are stored in the system. A user can add a
passenger only one time and if he came again operator can identify that person. Operator can add, edit and
delete the details of the passenger.
PROBLEM ANALYSIS: -

PROBLEM DOMAIN: -

➢ Requirements can cause substantial in large software projects

➢ The problem of missing requirements or incorrect descoping of project are virtually the most
prominent ones

➢ Domain requirements reflect the environment in which the system operates so, when we talk about
an application domain we mean environments such as train operation, medical records, e-commerce
etc.

➢ Domain requirements may be expressed using specialised domain terminology or reference to

domain concepts.

➢ The loss of data in the database

➢ It does not inform the customer if bus reaches late to the destination

➢ It constrains both the design of the device and the development process. Other requirements have to
be checked against this standard.

SOLUTION DOMAIN: -

➢ Reducing the requirements and designing the software high usability

➢ Mistakes can be done by human and if human enter the correct information then computer will never
make mistakes

➢ Domain requirements may be expressed using specialised domain terminology or reference to

domain concepts. Because these requirements are specialised, software engineers often find it
difficult to understand how they are related to other system requirements.

➢ We should save the information before it get lost and if windows closes suddenly the infor mation
should be saved

➢ The information should be given to the user and manager through the notifications

➢ The design should be less complex and it helps user to use the software easily
FUNCTIONAL REQUIREMENTS: -

The functional requirements of the bus management system are those requirements which are necessary to
the eye of user and the client. Here we try to make the module possible to accomplish the need of the desired
function. Four main functionalities: -
1. Administrative User Functions:

2.Approvers Functions:
3.Transport Functions:
➢ In this functionality the administrator will do his own responsibilities

➢ If any reason administrator needs to add a new user he can directly add

➢ the Approver can enter into his functionality using his own User ID and Password. After entering
into his functionality, whenever he needs to change his password then he can directly change it.

➢ The approver’s and transport’s user can view the details of all the routes and their destination,
location, route id, route code all these details will displayed in this list.

➢ The transport user can view the details of all the bus requests which are posted from the employees
of the company.

NON-FUNCTIONAL REQUIREMENTS: -

➢ Usability: User interface will be user friendly, So user can familiar to the system and easy to use.

➢ Reliability: The system will be able to meet specified objectives as well as the expectations of the
customers.

➢ Performance: The system should provide the services in considerable time interval.

➢ Security: The information provider by the user should be authentic which protect the system from
external attack and spamming

➢ Straightforward and harmonic means that are making you i is extraordinarily intuitive and needs to
followed

➢ The typography is taken care strictly as the wish of the system.

➢ Colour band of skim and dark is sweet means that stress and done well throughout this method

➢ Feedback sort may well be excellent implies that taking feedback of forms and rising the system.

➢ The structure is made simple to fill with a clean program.

STAKEHOLDER AND USE CASES: -

USERS STAKEHOLDERS

Passengers Manager

Super visor Employee

Billing clerk Authority

Customer service Others

Others use cases: -

Problem details
Booking time
Budget
Timing
Assign employees
Assign tasks
Check task progress
Check route
Check passenger details.
Check employee details
Managing vehicles
USE CASE DIAGRAM: -

In the above use case diagram user can access all four system and he can use the functionalities and sub-
functionalities
Each and every system has their own functionalities and sub functionalities
To operate the a system we need to login first and start operating the software
Every system are interlinked or indirectly linked but they are not linked directly
System as nearly 6 to 8 use cases and their linked with other system use cases
Every time we change the information or update the information data base will be updated.
MODULES DESCRIPTION: -
USE CASE DIAGRAM FOR BUS MANAGEMENT: -

DESCRIPTION FOR USE CASE DIAGRAM: -

In the bus management system the customer need to login first and if need to change the password or
anything he can change in his profile and he can search for his train if he finds the seats empty he
books the ticket and the reservation will be complete if customer need to cancel the reservation
customer should see in the booking details their he can cancel tickets.
USE CASE DIAGRAM FOR EMPLOYEE MANAGEMENT: -

DESCRIPTION FOR USE CASE DIAGRAM: -

In the employee management the employee can access the details of the other three modules. A
employee has his or her own login were can change his or her details. Employee can apply for the
leave and he can find his salary for that particular month. He can add the user to the software
database and see their files.
USE CASE DIAGRAM FOR ROUTE MANAGEMENT: -

DESCRIPTION FOR USE CASE DIAGRAM: -

In the route management system the user need to login using his login details then he can search the
route by giving the current location and destination. he can change the route to travel once the route
is fixed then the database should be updated and distance should be mentioned in the ticket and in the
database of the software
USE CASE DIAGRAM FOR PASSENGER MANAGEMENT: -

DESCRIPTION FOR USE CASE DIAGRAM: -

In the Passenger module first we need to enter the authentication details and check the availability of
the tickets and seats in the vehicle and book the ticket by selecting the seat place in the bus and make
payment if you cancel the ticket the refund will be add to the customer details and while paying the
tickets we can different option to pay the money for ticket.
OUTPUT: -
The outputs of the vehicle management system are Unified Modelling Language diagram like use case
diagrams, etc. in the project we used Use case diagrams in which it displays the actors and use cases and
their need in the vehicle management system . Unified Modelling Language is a visual modelling language
based on object-oriented methods. It combines with vehicle management information system of logistics
company for system analysis, date analysis and database design, system design. Business process diagram,
use case diagram, class diagram and sequence diagram can be drawed by UML at the analysis stage
TOOL FEATUES AND FORNT PAGE: -

USE CASE DIAGRAM: -

KEY FEATURES: -

CONCLUSION: -
The information in vehicle management system was not secure before after using enterprise architect sparx
system to develop the securing process. Integrating database technologies in vehicle management systems is
considered controversial by many. The general conception of database systems is that they are highly
resource demanding both with respect to memory consumption and computational overhead. Furthermore,
database systems are considered too non-deterministic to be used in vehicle management systems. This is
true for many general purpose database management systems. However, commercially embedded solutions
exist today, with database engines as small as a few kilobytes. Furthermore, many years of research in real-
time database management systems shows that these systems can be made deterministic.

REFERENCE: -
➢ https://sparxsystems.com/products/ea/
➢ http://www.intoweb.com/hr/module_vehicle.php
➢ http://www.mhnetwork.com/news/the-5-reasons-you-need-a-vehicle-management-system-for-
your-industrial-trucks/
➢ https://creately.com/diagram/example/hg56dnv82/Vehicle+Management+System
➢ https://www.projecttopics.info/Computer/Vehicle_Management.php