Download Android Mobile App for Criminal Records: System Design and Development and more Translations Compilers in PDF only on Docsity!
A
Minor Project (Stage-1) Report
On
Solution For Inter-state And Inter-country
Criminal Using Identity Inputs
Submitted in Partial Fulfillment of the Requirements for the Third Year of
Bachelor of Engineering
In
Computer Engineering
to
Kavayatri Bahinabai Chaudhari North Maharashtra
University, Jalgaon
Submitted by
Patil Pratiksinh Pravinsinh
Patel Faisal Ashfaque
Halde Virendra Kailas
Sangore Shruti Vijay
Thosar Devidas Manohar
Under the Guidance of
Ms. Dhanashree Tayade
DEPARTMENT OF COMPUTER ENGINEERING
SSBT's COLLEGE OF ENGINEERING AND TECHNOLOGY,
BAMBHORI, JALGAON - 425 001 (MS)
SSBT's COLLEGE OF ENGINEERING AND TECHNOLOGY,
BAMBHORI, JALGAON - 425 001 (MS)
DEPARTMENT OF COMPUTER ENGINEERING
CERTIFICATE
This is to certify that the STAGE-I MINOR PROJECT on Solution for Inter-state and inter- country Criminal using identity inputs , submitted by –
Patil Pratiksinh Pravinsinh Patel Faisal Ashfaque Halde Virendra Kailas Sangore Shruti Vijay Thosar Devidas Manohar
in partial fulfillment of the Third Year of Bachelor of Engineering in Computer Engineering has been satisfactorily carried out under my guidance as per the requirement of North Maharashtra University, Jalgaon.
Date: / / Place: Jalgaon
Ms. Dhanashree Tayade Guide
Prof. Dr. Girish K. Patnaik Prof. Dr. K. S. Wani Head Principal
Contents
- Acknowlegdement………….……………………………………………………………………..……
- Abstract……………..……………………………………………………………………………….….
- 1 Introduction…………………………………………………………………………………….…….
- 1.1 Background …………………………………………………………...………….……….
- 1.2 Motivation ……………………………………………………………...………………….
- 1.3 Problem Defination……………………………………………………………….………..
- 1.4 Scope………………………………………………………………………………....…….
- 1.5 Objective……………………………………………………………………………..…….
- 1.6 Selction of Life Cycle Model for Development……………………………………….….
- 1.7 Organization of Report……………………………………………………………..……...
- 1.8 Summary…………………………………………………………………….…………….
- 2 Project Planning and Management…………………………………………………………..……….
- 2.1 Feasibility Study……………………………………………………………………..…….
- 2.1.1 Technical Feasibility…………………………………………………………….
- 2.1.2 Economical Feasibility……………………………………………..…………...
- 2.1.3 Operational Feasibilty………………………………………………..…...……
- 2.2 Risk Analysis…………………………………………………………………………..…
- 2.3 Project Planning………………………………………………………...………………...
- 2.4 Effort Allocation………………………………………………………………………….
- 2.5 Cost Estimation………………………………………………….……….……………….
- 2.6 Summary…………………………………………………………….…………………...
- 3 Analysis……………………………………………………………………………………...……...
- 3.1 Requirement Collection and Identification……………………………………………...
- 3.2 Software Requirements Specifications…………………………………….………….…
- 3.2.1 Product Features………………………………………………....………….…
- 3.2.2 Operating Environment………………………………………………………
- 3.2.3 Assumptions…………………………………………….…………………….
- 3.2.4 Functional Requirements……………………………………………………..
- 3.2.5 Non Functional Requirements…………….………………………………….
- 3.2.6 Exterrnal Interfaces…………………………………………………………...
- 3.3 Summary……………………………………………….………………………………...
- 4 Design……………………………………..………………………………………………….……
- 4.1 System Architecture………………………………………………………..……………
- 4.2 Data Flow Diagram(DFD) ………………………………………………………..…….
- 4.2.1 Level-0 DFD………………………………………………………………….
- 4.2.2 Level-1 DFD………………………………………………………….………
- 4.2.3 Level-2 DFD………………………………………………….………………
- 4.3 UML Diagrams……………………………………………………………….…………
- 4.3.1 Use Case Diagram…………………………………………….…...…………
- 4.3.2 Sequence Diagram…………………………………………….……….…….
- 4.3.3 Collaboration Diagram………………………………..…………….….……
- 4.3.4 Class Diagram…………………………………………..……………….....…
- 4.3.5 State Transition Diagram………………………….……………………...…..
- 4.3.6 Component Diagram………………………………..……………………......
- 4.3.7 Deployment Diagram……………………………..……..…………………...
- 4.4 Summary…………………………………………………………………………..……
- 5 Conclusion ……………………………………………………….……….……………………….
- Bibliography……………………..………………………………………………………….
Chapter 1
Introduction
This project is about need of criminal record database which will be available through mobile devices. In this chapter introduction of project is mentioned. This chapter answers basic questions like what was need of project, what was the motivation behind it and also it describes the way in which project is going to be implemented and selection of life cycle model is also discussed in chapter. The organization of chapter is as follows. Section 1.1 presents in Background. Motivation is presented in described in Section 1.2. Section 1.3 presents Problem Definition. Scope is presented in Section 1.4. Section 1.5 presents Objectives. Section 1.6 presents Identification of Software Development Process Model, Section 1.7 presents Organization of report. The Last Section 1.8 presents Summary.
1.1 Background
In today’s modern world use of technology is increasing in every sector. So security force are also being updated from recent years. Various states have created databases for their police department. In a traditional situation if police or other central agencies wanted some criminal record. They have request from respective state, and this process takes some time. Also it can not be viewed directly on Mobile device. This affects overall efficiency and speed of security forces.
1.2 Motivation
In section 1.1 as we discussed that there are some problems. Using the current criminal records database. It is difficult to identify the criminals which commit crimes in different countries. To tackle all this problems there is a need of software which uses single database and can be operated from anywhere in world.
1.3 Problem Defination
In this project, there is problem of “ Solution with respect to inter-states and inter-countary criminals ”. As per the problems discussed in section 1.1 solution for inter-states and inter- countary criminals is required. inter-states and inter-countary criminals can have duplicate or redundant records in different databases. This can confuse security force and lower their efficiency. Also lack of desktop machines ( PC ) in remote areas or rural areas is a big problem.
1.4 Scope
The department of police is an independent statutory body which was created to maintain an effective and efficient police service for the public. Their primary task includes securing continuous need of the public in an efficient manner.
1.5 Objective
- To provide Android operating system based applicate to security force.
- To make an application which can be used from any where in world
1.6 Selection of Life cycle Model for Development
Figure 1.1 : Selection of Life cycle Model for Development
1.7 Organization of Report
The report is described in following way:- Chapter 1 titled Introduction, describes Background, Motivation, Problem Denition, Scope and Objective, selection of life cycle model for development, organization of report and summary. Chapter 2 titled Project planning and Management, which presents Proposed system and Feasibility study, Risk analysis, Project scheduling , Effort allocation ,Cost estimation and summary. Chapter 3 titled System Analysis, which presents Software, Hardware, Functional, Non- Functional, requirements and Software requirement specication and summary. Chapter 4 titled System Design presents System Architecture , Data flow diagram and UML diagrams. Chapter 5 titled conclusion and future work.
1.8 Summary
In this chapter introduction is given. In next chapter project planning and Management of project is described.
2.1.3 Operational feasibility
The project satisfies all the operations & functionality described in the project details successfully. It provides the best solutions of the problem. It meets all the requirements of users as described and documented in SRS, we can say that project is operationally feasible.
2.2 Risk Analysis
Risk Analysis can be categorized as:-
- Risk Based on Dependencies:- The app use google cloud “cloud firebase” to perform operations based on data. So its dependent on cloud firebase. Pricing of using firebase is affordable although it may change in future according to googles policies.
- Risk Based on Development teams:-
In todays scenario technology rapidly changes it may be possible that the project team doesn’t have required amount of knowledge regarding the project. This risk can be overcome by giving required training to developers. So above we discussed some points which can become risk for our project. But this risks are available & there is no major risk involved.
2.3 Project Scheduling
A project is made up of many tasks, and each task is given a start and end (or due date), so It can be completed on time. Likewise, people have different schedules, and their availability. And vacation or leave dates need to be documented in order to successfully plan those tasks. members know when their scheduled tasks are due or overdue, and to let the manager know When someone’s availability has changed. For example, most tools have task lists, which enable the manager to schedule multiple Tasks, their due dates, sometimes the planned effort against that task, and then assign that Task to a person. The software might also have resource scheduling, basically the ability To schedule the team’s availability, but also the availability of non-human resources like Machines or buildings or meeting rooms. Because projects have so many moving parts, and are frequently changing, project schedulIng software automatically updates tasks that are dependent on one another, when one Scheduled task is not completed on time. It also generates automated email alerts, so team
Figure 2.1 : project Scheduling
18 - Jun- 20 07 - Aug- 20 26 - Sep- 20 15 - Nov- 20 04 - Jan- 21
Litrerature Survey
Problem Definition
Objective
Feasibility Study
Effort Allocation
Required Collection and…
Data Flow Diagram
Start Date Day to Complete
2.4 Effort Allocation
As part of the effort management process, effective scheduling and recording of the perFormed activities is essential. Depending on the results of the activity, adjustments can Be made to further benefit the project and. These adjustments will generally be made in The areas of quantity, quality and direction. The main goal of effort management within Organizations is to increase viable and beneficial opportunities.
Table 2.1 : Effort Allocation
Software Phases Efforts Problem Defination 10% Requirements 10% Specifications 5% Design 10% Development 10% Testing 15% Quality Assurance 5% Documentation 5% Deployment 10% Training & Support 5% Maintainance 15%
2.5 Cost Estimation
Five Members in Team
Average Android Developer salary per week is approx. 6K
5Member*1Week= 5Weeks
5Weeks*6K=30K= 30000 rs.
30000+ 20000(for testing & other needs) = 50000 rs.+ required plan of firebase
2.6 Summary
In this chapter, project planning is discussed. In the next chapter Analysis of the project is discussed.
- It is assumed that internet connection of mobile device is consistant & connection speed is higher than 100KB/S.
- It is assumed that mobile device has enough space for running application & it doesn’t create any lag.
3.2.4 Functional Requirements
App provides following functionalities:-
Sign Up
Login
Logout
Authentication
Add new records
Show records
Update records
Delete records
3.2.5 Non-Functional Requirements
App wil have following non-functional requirements
App will be available 24 hrs in a day
App is flexible enough to run of different screen sizes of mobiles
Coding sections of this app can be tested easily
App can be operated anywhere
Read/write speed of database will be 20K/Day
3.2.6 External Interfaces
- User Interfaces:- The app will have user friendly & menu based navigation app will have separate slides for input & output data 2)Hardware Interfaces:- App doesn’t need any external hardware component. Internet connectivity is through wireless network. App communicates through internet to cloud firebase.
- Software Interfaces :- Although there is no necessary of any external software, external software’s can be used by users to send data of criminal.
- Communication Interfaces :- Network protocol used by firebase to connect with application is web sockets. Its real time & fast.
3.3 Summary
In this chapter analysis of the software is described. In the next chapter, Design of the Software is described.
Chapter 4
Design
System design provides the understanding and procedural details necessary for implementing the system. In this chapter Section 4.1 presents System Architecture. Section 4.2 presents Data Flow Diagram(DFD). UML Diagrams are presented in Section 4.3 and Finally, Summary is presented in Last Section 4.4.
4.1 System Architecture
A system architecture or systems architecture is the conceptual model that defines the structure, behaviour, and more views of a system. An architecture description is a formal description and representation of a system, organized in a way that supports reasoning about the structures and behaviour s of the system. it can consist of system components and the sub- systems developed, that will work together to implement the overall system. There have been efforts to formalize languages to describe system architecture, collectively these are called architecture description languages (ADLs) Various organizations can define systems architecture in different ways, including: The fundamental organization of a system, embodied in its components, their relationships to each other and to the environment, and the principles governing its design and evolution.
One can think of system architecture as a set of representations of an existing (or future) system. These representations initially describe a general, high-level functional organization, and are progressively refined to more detailed and concrete descriptions.
Figure 4.1 : System Architecture
4.2 Data Flow Digram (DFD) Also known as DFD, Data flow diagrams are used to graphically represent the flow of data in a business information system. DFD describes the processes that are involved in a system to transfer data from the input to the file storage and reports generation. Data flow diagrams can be divided into logical and physical. The logical data flow diagram describes flow of data through a system to perform certain functionality of a business. The physical data flow diagram describes the implementation of the logical data flow. The Data Flow Diagram are of follow types:-
Figure 4.3 : Level-2 DFD
4.3 UML Diagrams Following are the required UML diagrams for the project.
4.3.1 Use Case Diagram Use case diagrams consists of actors , use cases and their relationships. The diagram is used to model the system/subsystem of an application. A single use case diagram captures a particular functionality of a system. Hence to model the entire system, a number of use case diagrams are used.
Figure 4.4 :Use Case Diagram
4.3.2 Sequence Diagram A diagram that shows the existence of Objects over time , and the Messages that pass between those Objects over time to carry out some behaviour. A sequence diagram simply depicts interaction between objects in a sequential order i.e. the order in which these inter- actions take place. We can also use the terms event diagrams or event scenarios to refer to a sequence diagram. Sequence diagrams describe how and in what order the objects in a system function. Sequence diagrams are sometimes called event diagrams or event scenarios. A sequence diagram shows, as parallel vertical lines (lifelines), different processes or objects that live simultaneously, and, as horizontal arrows, the messages exchanged between them, in the order in which they occur.
Figure 4.7 :Sequence Diagram For Add Records
Figure 4.8 :Sequence Diagram For Read Records
Figure 4.9 :Sequence Diagram For Update Records
Figure 4.10 : Sequence Diagram For Delete Records
