Upload
others
View
3
Download
0
Embed Size (px)
Citation preview
Traffic Violations Fine Assignment SystemBy: Ahmed Alomrani, Surayhan Alharbi and Sultan Almasoud
Supervisor: Dr.Muhammad Badruddin Khan
Kingdom of Saudi ArabiaMinistry of Higher EducationImam Muhammad Bin Saud Islamic UniversityCollege of Computer and Information SciencesDepartment of Information System
2013-2014
Acknowledgement
The assistance and guidance of Dr.Muhammad Badruddin Khan of Imam bin
Saud Islamic University in the composition of this paper is gratefully acknowledged,
especially pertaining to his advice regarding organizing the project and completing
subsequent drafts.
Lastly, we wish to convey our thanks to the writers of the texts we have
employed in the composition of this project.
Table of Contents
Acknowledgement........................................................................................................IIITable of Contents ........................................................................................................ V1. Executive Summary...................................................................................................1
1.1 Background.................................................................................................21.2 System Request...........................................................................................31.3 Proposed Solutions.....................................................................................3
1.3.1 Scope Of Work............................................................................32. Literature Review.......................................................................................................43. Business Requirements..............................................................................................7
3.1 Business Context........................................................................................83.2 Required Functionality...............................................................................9
3.2.1 Functionality................................................................................93.2.2 Expected Reports.........................................................................93.2.3 Records Mistakes.........................................................................9
3.3 Analyze Feasibility.....................................................................................93.3.1 Technical Feasibility: Can we Build it?.......................................93.3.2 Economic Feasibility: Should we Build it?...............................103.3.3 Organizational Feasibility..........................................................103.3.4 User culture Feasibility..............................................................10
3.4 Business Benefits Justification.................................................................103.4.1 Tangible.....................................................................................103.4.2 Intangible...................................................................................10
3.5 Project Constraints and Limitations..........................................................114. Implementation Plan................................................................................................12
4.1 Information Gathering Technique............................................................134.1.1 Our Project (TVFAS)................................................................134.1.2 Interview technique is applicable..............................................134.1.3 Joint Application Design (JAD)................................................134.1.4 Conclusion.................................................................................13
4.2 Develop Work-Plan..................................................................................134.2.1 WBS activities...........................................................................13
4.2.2 WBS Structure...........................................................................154.2.3 Staff the Project.........................................................................16
4.3 Non-Functional Requirements..................................................................174.3.1 Operational requirement............................................................174.3.2 Performance requirement...........................................................174.3.3 Security requirement..................................................................17
5. Enterprise Model......................................................................................................185.1 Architecture Approach..............................................................................195.2 Architecture Diagram...............................................................................195.3 Software Architecture...............................................................................20
5.3.1 Human Components..................................................................215.3.2 Interface Components................................................................215.3.3 Software Functions Components...............................................225.3.4 Backend Components................................................................22
5.4 Integration with Existing ES.....................................................................226. Prototype..................................................................................................................24
6.1 Data Design and Management..................................................................256.1.1 Class Diagram............................................................................256.1.2 Use Case Diagram.....................................................................266.1.3 Sequence Diagram.....................................................................276.1.4 State Chart (State Machine).......................................................296.1.5 Diagrams Relationship...............................................................30
6.2 Design Strategy.........................................................................................316.2.1 Based on.....................................................................................316.2.2 Select a Strategy........................................................................316.2.3 Conclusion.................................................................................31
6.3 Moving to Design.....................................................................................316.4 Database Design.......................................................................................346.5 User Interface............................................................................................36
1
Executive SummaryTraffic Violations Fine Assignment System (TVFAS)
Executive Summary
1.1 Background
In our work, we have ERP Systems that integrated all systems in one system
to manage and stored information. Currently, we've system to manage the car
information. The car system stored employee data who use the car. After the "Saher"
System, we have problem in our ministry with the violations that occur by our
employees. This point is big issue because who paid the amount of violation. Cars
might be in the department parking then the employees uses the car without know
who use it.!
Presently, the department would be paid the value of violation without
deducting from employee salary. So, the our manager decide to automated system that
records the employee data who borrow the car in specific time and date, then it brings
the violation's data (Printed papers) from (TM) then someone insert those data to
determine who committed it. The system called Traffic Violations Fine Assignment
System (TVFAS).
Later, we need our ministry connected with Interior of ministry about those
violations and inserted directly in Traffic Violations Fine Assignment System
(TVFAS), after that TVS deduct the amount of violation from employee salary who
uses the car from Financial System.
Traffic Violations Fine Assignment System (TVFAS) proposed for GIP which
integrated cars and Financial Systems in GIP with Violations System (TM) at
Ministry of Interior. That will be recording the employee who borrow the car in
specific time and date, then it brings the violation's data from (TM) automatically and
Traffic Violations Fine Assignment System 2
Executive Summary
treat those data to determine who committed it. Then links the violation's Amount
with the Financial System (FIN) and deduct it from employee's salary.
1.2 System Request
1. Project Name: Traffic Violations Fine Assignment System (TVFAS).
2. Project Sponsor: Financial and IT Department at GIP.
3. Business Need: This Project has been determined who committed the violation
and deduct it from his salary.
1.3 Proposed Solutions
The purpose of the project is to analyze the requirements, design, implement,
and maintain the software to develop Traffic Violations Fine Assignment System
(TVFAS) at GIP, according to the requirements specified by the User. All activities
directly related to the purpose are considered to be in scope. All activities not directly
related to the purposes are considered to be out of scope.
1.3.1 Scope Of Work
Our ministry has two types of entrust a car: by department and by personal.
The scope of work is uses the car by department and the car does not registered by
someone. Out Of the Scope is employee has car permanently and the car is registered
by his name.
Traffic Violations Fine Assignment System 3
2
Literature Review About company vehicle policy
Traffic Violations Fine Assignment System (TVFAS)
Literature Review
According to Wiki, a moving violation is any violation of the law committed
by the driver of a vehicle while it is in motion. The term "motion" distinguishes it
from other motor vehicle violations, such as paperwork violations (which include
violations involving automobile insurance, registration, inspection, etc.), parking
violations, or equipment violations. [1]
For the literature review, fleet vehicles were considered to encompass light
vehicles, such as cars and vans less than 4.5 tones and ‘best practice’ was considered
to refer to management practices that have been identified as superior and/or have
been shown through research and/or experience to be associated with a reduction in
vehicle crashes, occupant injuries or near-miss crashes. [2]
“Both carriers and drivers will have to be more on their toes at roadside,”
Woodford said. “That’s simply because every violation will now count. In the past it
was simply out-of-service violations and certain moving violations [that counted].”
He said the industry attempts to “game” the SafeStat system that is being replaced. [3]
According to Middleton & Company Insurance which specialized in company
vehicle insurance, declared that company vehicles are provided to support business
activities and are to be used only by qualified and authorized employees.
They are not to be considered a part of an employee’s compensation and must
not be used as an inducement for employment. In all cases, these vehicles are to be
operated in strict compliance with motor vehicle laws of the jurisdiction in which they
are driven and with the utmost regard for their care and cost efficient use.[4]
Moreover, Middleton & Company Insurance says, "Fines for parking or moving
violations, towing storage or impoundment are the personal responsibility of the
Traffic Violations Fine Assignment System 5
Literature Review
assigned operator". The company will not condone nor excuse ignorance of any motor
vehicle violations that result in court summons being directed to itself as owner of the
vehicle. [4]
In literature review we found that statement is used many times in statement of
company vehicle policy: "Please be aware that motor vehicle violations incurred
during non-business (personal use) hours will also affect your driving status as well
and are subject to review". [3]
According to Daniel P. Bearth, each driver is responsible for the actual
possession, care and use of the company vehicle in their possession. [3] The increased
collision involvement of company car drivers was also found by Cartwright et al.
(1996) and Dimmer and Parker (1999) who stated that 27% of company car drivers
reported involvement in at least one crash in the previous three years compared to
18% reported by non-company car drivers. In part, the high representation of
company drivers in collision involvement can be explained by increased exposure to
risk (Davey et al., 2007), but there is anecdotal as well as the research evidence
provided by Dimmer and Parker (1999) of a ‘work driver effect’, which means that
responsible companies must endeavor to reduce the risks to society and their
employees. [5]
Traffic Violations Fine Assignment System 6
Literature Review
3.1 Business Context
Traffic Violations Fine Assignment System 7
CARs
Employee
E nt ru st
to
Entrust to Departmen
t1. Employee in his department uses the
car without record data.2. Through use the car, he committed
violations.3. After days, arrive report from ministry
of Interior about the violations.4. The department does not knows who
committed It.!5. Finally, the department paid the amount
of violation without deduct it from employee salary who uses the car.
3
Business RequirementsTraffic Violations Fine Assignment System (TVFAS)
Literature Review
3.2 Required Functionality
3.2.1 Functionality
TVFAS application is record the data of employee who borrow the car and date of return it.
TVFAS shall connect with external DB (ministry of Interior). TVFAS application brings data from TM system has violations information. Treatment TVFAS data with TM system data. TVFAS shall determine who committed the violation and send information to
Financial system (FIN). Deduct the violation's amount from the salary in financial system (FIN). TVFAS shall send SMS alert to employee and he should see report about
violation. Create reports and statistics.
Traffic Violations Fine Assignment System 8
Out Of Scope
As - Is
1. Record the data of employee who borrow the car and date of return it.
2. Brings data from TM system has violations information.
3. Treatment data with TM system data.4. Deduct the violation's amount from the
salary in financial system (FIN) in our Ministry.
5. Create reports and statisticsTo - Be
Literature Review
3.2.2 Expected Reports
Report about traffic violations. Report about who committed traffic violations. Report about total amounts of traffic violations. Report about who the most committed the violations.
3.2.3 Records Mistakes
If we found some mistakes of any records, we should be doing:
In case the amount was deducted:o We refund the amount of traffic violation to employee.o Deduct the amount of traffic violations from the correct record.
In case the amount wasn't deducted:o Correct the record, and then deduct the amount.
3.3 Analyze Feasibility
3.3.1 Technical Feasibility: Can we Build it?
Familiarity with communication between GIP database and External database (Ministry of Interior).
Familiarity with delay updating. Network availability. Project size is not big or very large, we can deal with it.
3.3.2 Economic Feasibility: Should we Build it?
Development team cost within budget. Deal with the accumulated debts. Hardware cost (microwave). User Training is easy.
We get benefits:o Reduce accumulated debts.o Improving productivity.o Higher quality product and increase performance.
3.3.3 Organizational Feasibility
We can deal with: The affected employee shall not work. Delay the work. Delay updating caused refrain paid double violation.
Traffic Violations Fine Assignment System 9
Literature Review
3.3.4 User culture Feasibility
Sometimes, we may face: User does not record data about who borrow the car. Lack cooperation from Financial Department.
Passiveness
3.4 Business Benefits Justification
3.4.1 Tangible
Reducing the financial losses. (Estimated financial losses during the past years 1,915,650 million S.R.)
Reducing error rates through automated editing or validation. Collecting receivables (violation's amount) more rapidly. Reducing paperwork costs by implementing electronic data interchange and
other automation.
3.4.2 Intangible
Increased discipline staff on driving a car. Increasing efficiency. Achieving quicker processing. Increased user satisfaction. Increased levels of service. Reduced employee morale.
3.5 Project Constraints and Limitations
Implement the project within 6 months. Complete the project within budget. Complete the project by the project due date.
Approval to connect with TM system at Ministry of Interior.
Traffic Violations Fine Assignment System 10
Literature Review
Traffic Violations Fine Assignment System 11
4
Implementation PlanTraffic Violations Fine Assignment System (TVFAS)
Literature Review
4.1 Information Gathering Technique
4.1.1 Our Project (TVFAS)
We have short time to complete project. There are some techniques: Interview, JAD and questionnaire. There are criteria such as depth and breadth of information, integration of
information, User involvement and cost of technique. The depth of information in our project is the most important, so the
questionnaires technique is not applicable with our project. Interview and JAD are applicable with our project because it has high depth
and integration of information, also it has high user involvement and low-medium cost.
4.1.2 Interview technique is applicable
We meet with stakeholders: User (who uses the system). Financial department (connect with employees salaries system). We meet with Ministry of Interior for connecting with Violations System
(automated link).
4.1.3 Joint Application Design (JAD)
The Staff of Project make some meetings for brainstorm. Discuses requirements got it from stakeholders and ministry of Interior. Putting solutions for the system.
4.1.4 Conclusion
We use two technique for get or gathering information: Interview and JAD, because we don't have more time and need to depth of information as soon as.
4.2 Develop Work-Plan
4.2.1 WBS activities
We develop work-plan activities (WBS) as shown below in (Figure 1).
Traffic Violations Fine Assignment System 12
Figure 2 WBS Structure
Literature Review
Traffic Violations Fine Assignment System 13
TVFAS1
Gather requirements
1.1
Project Schedule
1.2
Feasibility Study
1.3
Analysis 1.4
Design1.5
Meet with stakeholders 1.1.1
Determine Scope 1.1.2
Write problem 1.1.3
Identify benefits 1.1.4
users 1.1.1.1
Ministry of Interior1.1.1.2
Financial Department
1.1.1.3
Build WBS 1.2.1
Estimate resource 1.2.2
Produce Gantt chart 1.2.3
Expected Value 1.3.1
Study technical feasibility
1.3.2
Study economic feasibility
1.3.3
Study Organizational
feasibility 1.3.4
Tangible benefit 1.3.1.1
Intangible benefit 1.3.1.2
Network availability 1.3.2.1Connect
with external DB 1.3.2.2
Determine requirement
s 1.4.1
Structure modeling
1.4.3
Functional modeling
1.4.2
use case diagram 1.4.2.2
class diagram 1.4.3.1
sequence diagram 1.4.4.1
Behavioral modeling
1.4.4
Collaboration
1.4.4.2
Design Strategy1.5.1
Moving to Design1.5.2
Database Design 1.5.3
User Interface
1.5.4
Relationships
1.4.5
state chart
1.4.4.3
TVFAS
Gather requirements Meet with stakeholders
usersMinistry of InteriorFinancial Department
Determine ScopeWrite problem descriptionIdentify application benefits
Project ScheduleBuild WBSEstimate resourceProduce Gantt chart
Feasibility Study Expected Value
Estimate Tangible benefitEstimate Intangible benefit
Study technical feasibilityNetwork availabilityConnect with external DB
Study economic feasibilityStudy Organizational feasibility
Analysis
Figure 3 Gantt Chart (activities responsibility)
Figure 1 WBS Activities
Literature Review
4.2.3 Staff the Project
4.2.3.1 Project Manager (1)
Dr.Abdullah Bin Mohammed AlshehriGeneral manager of IT at GIP
4.2.3.2 Vice Project Manager (1)
Dr.Khalid Bin Furayeej Alotaibimanager of Information Department at GIP
4.2.3.4 System Analyst (2)
Ahmed Bin Abdul-Aziz Alomrani Sultan Bin Nasser Almasoud
4.2.3.5 Technical Programmer (3)
Rayef Mohammed Karim Abdullah Sultan Alrashidi
4.2.3.6 DBA (1)
Surayhan Bin Gazi Alharbi
Traffic Violations Fine Assignment System 14
Literature Review
4.3 Non-Functional Requirements
4.3.1 Operational requirement
The TVFAS should be integrating with work environment. The TVFAS should be able to work on web application. The TVFAS reports should be compatible with reports system.
4.3.2 Performance requirement
The TVFAS should not exceed 3-5 seconds when user interacts with system. The TVFAS should be receiving updated violations information from
Ministry of Interior every one hour. The TVFAS should be available for use 10 hours per work day.
4.3.3 Security requirement
Managers and direct user can see violations report. The data DB should be encrypted. The TVFAS should be having audit (who changing data).
Traffic Violations Fine Assignment System 15
5
Enterprise ModelTraffic Violations Fine Assignment System (TVFAS)
Table 1 Architecture Approach
Enterprise Model
5.1 Architecture Approach
Function requirement ,Solution must be able to provide the following
functionality: Approach
1-the solution shall record detailed information about the borrowing car including name of employee, date and time the borrow and return it.
The proposed solution will be able to record the data of employee who borrow the car and date of return it by the specialize employee.
2- The solution shall connect with external DB (ministry of Interior).
The proposed solution will be connect to database of ministry of interior by web service (TM system) to get violation.
3-Deduct the violation's amount from the salary in financial system (FIN).
The proposed solution after bring data and treatment with (TM system) will deduct the amount of violation from salary in (FIN system)
4- Create reports and statistics. The proposed solution will be provide report and statistic for all violation by department and person.
Security
5-The solution should be having audit (who changing data).
The proposed system will be add the all information that happen in (TV System ) in audit system that applied on my organization.
Performance6- The solution should not exceed 3-5 seconds when user interacts with system and print report.
The proposed solution will be leveraging database in-memory features to provide real-time search and almost real-time reporting.
5.2 Architecture Diagram
1. Client application : all user can access to any system have privilege on it by the portal.
2. Server application : the server application is oracle application server version 10 g.
3. Database server : is oracle database 11g .
4. External database : is database that have (TM system) through web service, we can make queries and retrieve our data.
Traffic Violations Fine Assignment System 19
Figure 4 Architecture Diagram
Enterprise Model
the solution depend on create new system that records the employee data
(from PRS system) who borrow the car in specific time and date, then it brings the
violation's data from (TM) and treatment data to determine who committed it. After
that, it links the violation's Amount with the Financial System (FIN) and deduct it
from employee's salary.
5.3 Software Architecture
The software architecture of TVFAS demonstrates the structures of the
system, which include software components, the Human Components of those
elements, Backend Components, Interface Components and the relationships between
them. Architecture is responsible to the public side of interfaces; with brief
description of private details of components. In the architecture below its describing
the set of significant components about the audience of a software including the
different of the structural elements and their interfaces by which the system is
Traffic Violations Fine Assignment System 20
Client Application Server
ApplicationDatabase
server
External database
(TM System)
The systems in application server (TVS , FIN ..etc) that connect together.
Human Component
Interface Components
Software Function
Component
Backend Components
Deducting salary Assigner
Borrow Car EntryCar Info Admin
Car Registration InterfaceBorrowing Car
Interface Reporting & Statics Interface
Integrate violation Info with deducting Info
Integrate borrower info with car info
Record Car Info
Record employee who borrow car
Deduct violation's amount from salary
CarDB
EmployeeDB
ViolationDB
Figure 5 Software Architecture
Enterprise Model
designed; behavior as specified in collaboration between those components;
composition of these structural and interaction structural into lower and upper
components that guides this organization.
TVFAS records the employee data who borrow the car in specific time and
date, then it brings the violation's data from (TM) and treatment data to determine
who committed it. After that, it links the violation's Amount with the Financial
System (FIN) and deduct it from employee's salary
5.3.1 Human Components
Car Info Admin Deduction Salary Assigner. Borrow Car Entry
5.3.2 Interface Components
Interface page for record the data borrowing the car.
Traffic Violations Fine Assignment System 21
Figure 6Integration with Existing Enterprise Systems
Enterprise Model
Interface page for deducting the violation's from the salary. Interface page for creating reports and statistics.
5.3.3 Software Functions Components
Record the data of employee who borrow the car Brings data from TM system has violations information. Treatment data with TM system data. Deduct the violation's amount from the salary.
5.3.4 Backend Components
Car Info Database Borrowing Database. Violation Database.
5.4 Integration with Existing ES
TVFAS association with other systems (internally, externally). TVFAS linked
internally with three existing systems: HR, SCM and FIN.
Traffic Violations Fine Assignment System 22
Ministry of Interior
TVFASsend
dat
a
HR SCM
FIN
Enterprise Model
First, verified employee data using HR system to get full information of employee
data. Second, get car data through CAR system which associated with SCM. After
that, the data is recorded entry and exit of any car on the employee. Third: If adjust
any violation recorded on a certain car is verified those who committed the violations.
thus deducted these violations through using the financial system (FIN(.
TVFAS also linked with the Ministry of Interior in order to obtain the fully
information (time - date) of traffic violations that occurred on custom cars for GIP.
Traffic Violations Fine Assignment System 23
6
PrototypeTraffic Violations Fine Assignment System (TVFAS)
Enterprise Model
6.1 Data Design and Management
6.1.1 Class Diagram
Traffic Violations Fine Assignment System 24
Enterprise Model
6.1.2 Use Case Diagram
Traffic Violations Fine Assignment System 25
Figure 9Use Case of manage borrow activity
Enterprise Model
Traffic Violations Fine Assignment System 26
TVFAS Boundary
Figure 1.10
Sequence Diagram for TVFAS (activity between Employee and Borrow Admin)
Figure 11
Sequence Diagram for TVFAS (Borrow Admin activity)
Enterprise Model
6.1.3 Sequence Diagram
Traffic Violations Fine Assignment System 27
Figure 12
Sequence Diagram for TVFAS (activity between Employee and Financial Admin)
Enterprise Model
6.1.4 State Chart (State Machine)
Traffic Violations Fine Assignment System 28
Figure 13 General State chart or State Machine
Enterprise Model
6.1.5 Diagrams Relationship
Traffic Violations Fine Assignment System 29
Use Case Diagram
Class Diagram
Enterprise Model
6.2 Design Strategy
6.2.1 Based on
Short time to complete project. So, selection vendor in the government ministries is not quickly process.
Administrative procedures for buying program it's take long time also. Good Programmers in our ministry. Business need or system requirements are very clear. There are a good management and technical staffs. Our ministry has some privacy. Ability to development in the future.
Traffic Violations Fine Assignment System 30
Car Package
Create Car Table in DB.take cars data from SCM system (immigration data).
DB
Design Car screen that have car information.
User Interface
Enterprise Model
6.2.2 We Select a Strategy
In-house building, because it's meet the above criteria, also: Allow flexibility and creativity in solving problems. Easier to change components. Ability to overcome the potential risk. Builds personnel skills. Increase the experience.
6.2.3 Conclusion
We use In-house development strategy because it's the best choice for our project and our ministry.
6.3 Moving to Design
We have 4 basic components: Cars, borrow car, violations and deducting from salary.
Traffic Violations Fine Assignment System 31
Violations Package
Create violation Table in DB.Connected link between External system(ministry of Interior) and TVS.
DB
Design Violations screen that have traffic violations about car.
User Interface
Enterprise Model
Traffic Violations Fine Assignment System 32
Deducting salary Package
Take violations information from violation table.Connected link between violation and employee table (with financial system.
DB
Integration between violation package and deducting package.After that, integrated with car package.Then, integrated with borrow car package. Finally, Integration between all packages.
Integration
EMPLOYEE
Employee_id (PK)Employee_nameDepartment_id (FK)
DEPARTMENT
Borrow_CAR
Borrow_id (PK)Employee_id (PK) (FK)Car_id (FK)Borrow_date Return_datePlate_no (FK)
Violation_Information
Enterprise Model
6.4 Database Design
Traffic Violations Fine Assignment System 33
Enterprise Model
Traffic Violations Fine Assignment System 34
TVFAS.EMPLOYE
TVFAS.CAR
TVFAS.DEPARTMEN
Figure 17 Tables Relationship by Using Toad
tool
Enterprise Model
6.5 User Interface
Traffic Violations Fine Assignment System 35
TVFAS.BORROW_CAR
TVFAS.VIOLATION_INFORMATION
TVFAS.SAL
TVFAS.TRAFFIC_VIOLATION
Figure 19 Record Car screen for TVFAS
Figure 18 Log in Screen for TVFAS
Enterprise Model
Traffic Violations Fine Assignment System 36
Figure 20 Screen of who borrow car
Figure 21 Inquire about employee violations
Screen
Enterprise Model
Traffic Violations Fine Assignment System 37
Figure 22 Deducting Screen
Enterprise Model
Traffic Violations Fine Assignment System 38
7
Evaluation of Proposed SystemTraffic Violations Fine Assignment System (TVFAS)
Evaluation of Proposed System
7.1 The Impact of System
The Impact Study assessed the performance of the projects focusing on the following
evaluation issues:
7.1.1 Effectiveness (have the goals been attained)
Reducing error rates through automated editing or validation. Collecting receivables (violation's amount) more rapidly. Reducing paperwork costs by implementing electronic data interchange
and other automation.
7.1.2 Efficiency (what is the return of investment)
Reducing the financial losses. (Estimated financial losses during the past years 1,915,650 million S.R.)
Achieving quicker processing.
7.1.3 Impacts (what has happened as a consequence of the project outputs)
Expected impacts after applying the proposed system:
Staff will be follow the instructions of traffic. Reduce expenses to the organization.
7.1.4 Additionality (what has happened which wouldn’t have happened otherwise)
Decrease employee morale. Decrease employee loyalty. Lack of employee satisfaction. Lack of productivity.
7.2 Issues
7.2.1 Security issues Security breaches by the staff responsible for system :
solution :1- Effective administrative control to manage the system.2- Strong authentication measures to prevent security breaches.
Traffic Violations Fine Assignment System 25
Evaluation of Proposed System
7.2.2 Code of Ethics issues Change or delete the correct information by the staff :
solution :1- Adding the TVFAS tables on Audit system.
Ignoring of registration the borrowed cars:
solution :1- Recording the traffic violations on the responsible employee.
7.2.3 Intellectual Property
TVFAS have been looking for ways to correlate what user information should be protected inside of the TVFAS system with what information could be shared with other departments:
The software components and information that generated by TVFAS is belonged and owned to our agency. The reuse of the software components by other ministries or agencies is conducted only by formal permissions.
With a goal of reducing the losing of money of the recorded violation on TVFAS. The employee's data will transferee only between TVFAS and Finance system. The statics and knowledge generated by this software is belonging to our agency.
7.2.4 TVFAS Reliability
TVFAS is now part of lager system which is connected to sensitive finance and employee data, and ultimately it is the reliability of the entire system that is important. We believed that in TVFAS has been followed systematic method to analyze and design the system:
A well-engineered system (good system analysis and design) can tolerate the malfunction of any single component without failing.
The data entry for TVFAS will find a clear screen with good description for text box and button to avoid data-entry mistakes
The redundancy of data is avoided by designing relational DB with primary key and foreign key to avoid assigning or duplicating violations amount for one employee.
Traffic Violations Fine Assignment System 26
Evaluation of Proposed System
Since the violation ticket is connected directly to employee Id, so this step
According to reliability of saved data on TVFAS system, the infrastructure and security department taking daily full backup to prevent the loss of data.
7.2.5 TVFAS Privacy
The TVFAS contains information about an event or action that recorded and made by employees who borrowed the cars. This information is so sensitive for employees and attributed as personnel information. TVFAS has some specifications which save employees' rights of personnel information such as:
The obtained and recorded data by TVFAS will be saved and shared only by authorized employees in our agency. This step will save employee rights who conduct the violation.
As we mentioned in security part the accesses for TVFAS is restricted only for authorized employees. This step is suggested as major step to protect the information generated by system.
As mentioned in analysis part the administrator of borrowing has only the authority of managing the certain components of software. This step save will prevent chaotic access to personnel information for each other.
Traffic Violations Fine Assignment System 27