3.

SYSTEM DESIGN
3.1 Introduction
The system design will include the overall view of the system from the functional viewpoint. It is
the process of defining the components, modules, interfaces, and data for a system to satisfy
specified requirements. System development is the process of creating or altering systems, along
with the processes, practices, models, and methodologies used to develop the system. The system
is a web application that is primarily concerned with the crime information management aspect
along with a crime archive.

3.2 Design goal

The design goals of a system are derived mainly from the non-functional requirement. It helps us
in identifying the qualities that the system is optimized to satisfy. The following four major
quality perspectives are used to identify the design goals of the system.

3.2.1. Performance
This includes the speed and space requirement imposed on the system. Accordingly, the
following two performance criteria are identified.

 Response time: As the system is a web based application acknowledgment of remote user
requests should be optimized.
 Throughput: As the system need to be accessed by different users, so it is required to
accomplish several users request.

3.2.2 Dependability
Determines the effort that will be expended in minimizing system crushes and their consequence.
The following are identified as the main dependability criteria.

 Reliability: The system must be reliable by using Operating System provided backup
systems.
 Availability: The system must be available whenever the user of the system needs so
despite some of internal or external problems of the system.
 Robustness: The system should have the ability to withstand invalid user input by
validating all the inputs of the user.
  Fault tolerance: The system should be fault tolerant by displaying warning messages to
the user even when erroneous data are inputted.
 Security: The system should have a secure authentication mechanism so as to prevent
unauthorized users from accessing non-allowed resources.

3.2.3 Maintainability
 Extensibility: Since the system uses object oriented design approach, new functionalities
and classes can easily be added.
 Modifiability: It should be easily modifiable after deployment without affecting the
current working system.

3.2.4 End User Criteria

 Usability: The system should be a user-friendly system so that users can easily learn and
use it.

3.3 Current Software Architecture

Currently the Police station doesn’t have a well-organized architecture on criminal information
exchange between the police station and staff members. As it has been assessed during the
requirement analysis document currently the police station uses the manually dominated system
supported by software like MS-Word and MS-Excel that running on standalone computer to
manage and facilitate the day to day routine. The information about the criminals are stored in
MS-Excel of the standalone computer and paper based files.

3.3 proposed software architecture

3.3.1 Overview
As the application is a web based application, it is required to have a tightened security feature
and high performance capability. And to ensure these quality requirements, the system design
proposed to implement Three-Tier client/server architecture, with a database and web servers. In
the client/server architecture, a subsystem, the server, provides services to instances of other
subsystems called the clients, which are responsible for interacting with the user.

Web based applications are accessed by web browser over a network of client/server
architecture. Users will use their web browser software to communicate with the system. Users
will interact with the database system through the graphical user interface. All data entries that
are performed on the client PC are transferred to the web server via an appropriate network
connection. The following figures show the generic software architecture the layout out of the
proposed system.

Subsystem Decomposition
System decomposition is constitutes the bulk of system design. In order to reduce the complexity
of the system of the application domain, smaller parts called classes are identified and organized
into packages. Similarly, to reduce the complexity of the solution domain, system decomposed
into smaller part called subsystem, which are made up of a number of solution domain classes.
Normally each subsystem is realized independently.

During system decomposition different system-wide issues need to be addressed. These include
issues like hardware/software mapping, data management and etc. Details of each of these issues
will be presented in the topics dedicated to each.

The crime information management system is proposed to be divided into the following
subsystem.

 User interface subsystem

 User Account management subsystem
 Case Registration management subsystem
 Post management subsystem
 Data management subsystem
 User interface subsystem

The user interface subsystem is primarily responsible for interaction with the other subsystem
and also the interaction of end user with system.

The interface subsystem include the following interfaces:

 User Account management subsystem interface: this interface enables the authorized
user to interact with the user management subsystem.
 Case management registration subsystem interface: this interface enables the authorized
user to register all information needed about the criminals.
 Post management subsystem interface: this interface enables the authorized user to post
some information for the public.
 Data management subsystem interface; this interface allow interfacing with the data
management subsystem.
 User Account management subsystem

This subsystem is responsible for user login and maintenance of user information. It include
registering investigator, inspector, prosecutor and complaint. These actors data are only
differentiate by their status.

User Account management subsystem include the following classes:

 Investigator management: this class is responsible with registration, amendment and

deletion of investigation profile.
 Inspector management: this class is responsible with registration, amendment and
deletion of investigation profile.
 Prosecutor management: this class is responsible with registration, amendment and
deletion of investigation profile.
 Complaint management: this class is responsible with registration, update and deletion of
complaint profile.
 Post management subsystem

This subsystem is responsible with post management and it is made up of the following classes:

 Absconder: this class is responsible for posting absconder person for the public in order
to find the person.
 Most wanted person: this class is responsible for online announcing most wanted person.
 Generate report: this class is responsible for generating information about criminals’ data
monthly.
 Appointment: this class is responsible for announcing the appointment to the plaintiff and
defendant.
 Feedback: this class is used by the public user to post their feedback.
 Data management subsystem

This subsystem is responsible with the data management tasks like storage, update and retrieval
requests triggered by the subsystem.

 Data storage: this class is responsible to handle persistent data storage activities.
 Data access: this class is responsible to retrieve any information from data base.
 Message: this class is responsible to display error or success message related to data entry
and data retrieval.
 Hardware/Software Mapping

Since the system is a web based application and has client/server software architecture, all the
subsystems except the storage subsystem will reside on the web server inside the web hosts
device and no application except a web browser is required in the client machine. Whenever a
user requests a service from a personal machine the system on the Web server will authenticate if
the service needs authentication and grant the associated access privilege to the user.
Accordingly, the following are devices that constitute the hardware components;
 Web server: This server holds the entire subsystems except the data management
subsystem.
 Database Server: This server holds the data management subsystem.
 Client Machines: Client machine is a terminal from which the user will access the
system.
The following diagrams shows UML deployment of the system.
3.4.4 Persistent Data Management
Persistent data management basically describes data that is needed to be stored persistently,
where it should be stored and how it should be accessed. We use PHPMYADMIN database
server and SQL commands to communicate and store inside the database. The decision of
storage management is dictated by non-functional requirements such as data retrieval request
quickness and if a need for complex query requests. Among the different storage management
systems, the Relational Database management system is chosen for the following reason of

 Need for efficient and complex queries

 Need for concurrency control
 Simple to structure and easy to implement
  Easy to add tables and requirements emerging in the future.

3.4.6 Subsystem Services

A subsystem is characterized by the services it provides to other subsystems. A service is a set of
related operations that share a common purpose.

This section describes the services provided by each subsystems of Crime Information
Management System in terms of their operations.

Subsystem Classes Operations Description

User Account
management
Interface subsystem