TABLE OF CONTENT

No. Content Page

1.0 Introduction 2

2.0 Problem Statement 2

3.0 Project Objective 3

4.0 Consequences 3

5.0 User Scope 3

6.0 Context Diagram 4

7.0 Data Flow Diagram 5

8.0 Conclusion 8
1.0 Introduction

The common problem students who brings transport such as car and motorcycle to

university would be to legally parking inside the University. The parking provided are

limited so University staff would have to restrict their parking space in the university. Thus

the Vehicle Sticker System is developed to keep track of cars that parked in the university.

The user of the system would be students, university staff, police, guard and Admin. The

student and university staff would need to apply for a sticker from the Admin. The Admin

then will process a unique serial number for each transport plate. The police and guard are

assigned to check for counterfeit and illegal parking.

2.0 Problem Statement

There are three problem statement as follows:

i) Data record on paper-based system

- Administrator would need to record all user data into paper-based system which could

cause waste of paper.

ii) A lot of counterfeit and duplicate series number

- False and duplicated serial number of stickers was created by others illegally

iii) Space needed to store user record N

- Keeping the data would require a huge place to keep, by keeping in a paper based

would take a lot of space.

3.0 Mission Objective

I. To develop a system entitled “Vehicle Sticker System” that can stored data easily

in one system

II. To design a system which ensure all number are genuine and not duplicate

III. To store a huge amount of user record in a system easily and neat.

4.0 Mission Statement

I. Admin

Database Developer: What kinds of data do you work with?

Admin: I need to see everything, well at least a summary of the data used or

generated by Vehicle Sticker System. That includes data about application at all

staff, all student and all vehicle. I also like to keep an eye on the extent to which

branches advertise properties in newspapers.

Database Developer: What types of things do you need to keep track of?

Admin: As I said before, I need to have an overview of everything. I need to see

the whole picture.

Database Developer:

II. Police

III. Staff

IV. Student
5.0 System Boundary

Vehicle

Admin Student

Police Staff

System Boundary

Figure 1: System Boundary

6.0 Main User Views

 Data Access Type Admin Police Guard Student

Edit X X
User
Delete X
Information
View X X X X

Edit X
Vehicle
Delete X
Information
View X X X X

7.0 System Requirement Specification

The system specification should list all the important features for the Vehicle Sticker

System database system. The type of features that should be described in the systems

specification include:

 Initial database size

 Database rate of growth

 The types and average number of record searches

 Networking and shared access requirements

 Performance

 Security

 Backup and recovery

 Legal issues
System Requirements for Vehicle Sticker System Database System

Initial database size

1) There are approximately 1000 members of staff working at over 8 faculties. There is an

average of 80 and a maximum of 100 members of staff at each faculty.

2) There are approximately 8000 students at over 8 faculties. There is an average of 1000 and

maximum of 1500 students at each faculty.

3) There are approximately 20 members of security guard at over 10 security post. There is

an average of 3 to maximum of 5 members of security guard at each security post.

4) There are approximately 200 members of police at 2 police station and 1 police office.

There is an average of 8 and a maximum of 12 in every police station and there is an average

of 50 and a maximum of 150 in police office.

5) There are approximately 1000 vehicle in UTEM.

Database rate of growth

1) Approximately 100 new vehicle and 2000 new vehicle will be added to the database for

each 6 months.

2) Once a student is no longer study in UTEM, the corresponding record will be deleted from

the database. Approximately 2000 records of students will be deleted each 6 months.

The type and average number of record searches

1) Searching for the details of a vehicle approximately 20 per day.

2) Searching for the details of a students approximately 20 per day.

Networking and shared access requirements

All application, vehicle and student should be securely networked to a centralized database

located at computer center in UTEM. The system should allow for at least two to eight people

concurrently accessing the system from each police station. Consideration needs to be given to

the licensing requirements for this number of concurrent accesses.

Performance

1) During opening hours for applying sticker, but not during peak periods, expect less than a

1-second response for all single record searches During peak periods, expect less than 5-

second response for each search.

2) During opening hours for applying sticker, but not during periods, expect less than a 5-

second response for each multiple record search. During peak periods, expect less than a

10-second response for each multiple record search.

3) During opening hours for applying sticker, but not during periods, expect less than 1-second

response for each update/save. During peak periods, expect less tan a 5-second response

for each update/save.

4) During opening hours of roadblock, but not during peak periods, expect less tan a 1-second

response for all single record searches. During peak periods, expect less tan 5-second

response for each search.

5) During opening hours of roadblock, but not during peak periods, expect less than 5-second

response for each multiple record search. During peak periods, expect less than a 10-second

response for each multiple record search.

Security

1) The database should be password-protected.

2) Each member of admin should be assigned database access privileges appropriate to a

particular user view, namely Students, Security and Police.

3) A member of staff should see only the data necessary to do his or her job in a form that

suits what he or she is doing.

4) A student should see only vehicle data and their own personal details using Vehicle Sticker

System Web site.

Backup and Recovery

1) The data should be backup monthly at the end of the month at 12 midnight.

Legal Issues

Each county has laws that govern the way that the computerized storage of personal data is

handled. As the Vehicle Sticker System database holds data on staff, students and vehicle, any

legal that must be complied with should be investigated and implemented.

8.0 User Requirement Specification

9.0 Conceptual Model

10.0 Logical Model

11.0 Physical Design

12.0 Conclusion
13.0 Reference