Sultan Qaboos University
College of Science
Software Engineering
Driving School Management System
User Requirements
Done By:
Ali Yousuf Ali Al Amri
Faisal Mohammed Alhajri I
- Registering new customer.
- Manager schedule tasting for the customer.
- Adding / Firing employee by the manager.
- Trainers view their profile and added some information.
- The manager distributed the salary.
- More functional for manager.
- We have done
- Develop the system that organized the data of driving school
- We have learned
- How to motivate group members
- How to divide the work between group members
- Get experience for final year project
- We have faced
- Different companies request different requirements
- Limit time to do the project
- MS Project is not free
- Suggestions for improve and complete the system
- Increase the functionality for the manager and trainer
- Upgrade the system to interact with other type of employees
Suggested Solution
Problem definition
Develop an efficient database system ( Driving School System) to make the process of add and change the information of customers and employee in more organized and secured way ,also the system should be easy to use and avoid the conflict of appointments tests.
Writing the employees and customer's information's in the some book notes, containing their profiles and data was done manually in driving school. They usually need to update continually and retrieve it, also maybe some conflict happen with test scheduling.
All these processes need more human resource, more money and more time. Moreover it's hard and difficult to save and remember all data .
Class Diagram
Use Case Diagram
Introduction
Result of Testing
The driving school has many people to deal with
them. Some of them are trainees and the others are
its worker.
This system will facilitate the functioning of organizing
school data so the data of school will be stored in
protected database like customer’s name, phone
number, registration date etc. Therefore would
greatly decrease the time and save the company
resources.
Sequence Diagram
Content
Non-Functional Requirements
- Introduction
- Problem definition and solution
- User Requirements
- Functional Requirements
- Non-Functional Requirements
- System design
- Static Aspect
- Dynamic Aspect
- Result of testing
- Conclusion and future work
- Demo
- The manager give the customer a background about the contract types (e.g.: 6 months contract, open contract, one year contract) and the price of each contract.
- The customers chose the suitable contract.
- The manager creates new user account filled with full customer’s information and print the contract to sign it by the manager.
- The system generate an ID that used by the customer to view and edit his\here details.
- Reliability: the system should produce and give the correct database for all users such as customer as well as employee and give the full reports.
- Availability: this system should be easy for use and available when would like be use it, also have simple design and understandable by the customers, manager and trainer
- Security: the system must be secure for report purpose and user accounts, only the manager, customer and employee can use this system, also the trainer cannot access the profile of customer who is not training him or her.
design by Dóri Sirály for Prezi