use case model of crime management system
DESCRIPTION
Muzaffar SalikTRANSCRIPT
1.1. ABSTRACT LEVEL USE CASE MODELING:The abstract use case model of system is shown here that gives an abstract overview of system functionalities.
Abstract level Use case of System
1.2. ABSTRACT LEVEL DESCRIPTION OF USE CASES
1.2.1 Use Case Name:
Manage criminal record.
`
UC # 01 Ref: Req. # 01
UC Name Manage criminal record
Level Abstract.
Description This use case manages the criminal record
Actor (s) DO
Stakeholders DO, City Police Office, Courts/ Area Magistrate, General Public
Preconditions DO is signed in to use this use case.
Success Guarantee All Data is managed successfully.
Main Success Scenario Action System Response
1. DO view criminal record 2. System shows the report.
3. DO insert criminal record. 4. System save the information in managed way.
Extensions 2a. Invalid data entry. System asks to re-enter wrong entry.
Special requirements No
Frequency of Occurrence As per requirement
Miscellaneous No
1.2.2 Use Case Name:
Manage database
UC # 02 Ref: Req. # 02
UC Name Manage database
Level Abstract.
Description This use case manages the database system.
Actor (s) DO
Stakeholders DO, City Police Office, Courts/ Area Magistrate, General Public
Preconditions DO must have Criminal detail.
Success Guarantee Whole database is controlled by this use case.
Main Success Scenario Action System Response
1. DO update record in system. 2. System update record.
3. DO search record form database 4. System shows the required record.
Extensions 1a. Invalid data entry. System asks to re-enter wrong entry.
Special requirements No
Frequency of Occurrence As per requirement
Miscellaneous No
1.2.3 Use Case Name:
View record
UC # 03 Ref: Req. # 03
UC Name View record
Level Abstract.
Description This use case shows the criminal record.
Actor (s) Accountant.
Stakeholders SP,City Police Office, Courts/ Area Magistrate, General Public.
Preconditions SP must have Criminal detail.
Success Guarantee All criminal related issues managed by this use case.
Main Success Scenario Action System Response
1. SP view the record. 2. System Shows the record.
Extensions 1a. Invalid password. System asks to re-enter wrong password.
Special requirements No
Frequency of Occurrence As per requirement
Miscellaneous No
1.2.6 Use Case Name:
View reports
UC # 06 Ref: Req. # 06
UC Name View reports
Level Abstract.
Description This use case shows the report
Actor (s) CPO
Stakeholders City Police Office, Courts / Area Magistrate, General Public.
Preconditions CPO must have Criminal detail.
Success Guarantee All criminal related issues managed by this use case.
Main Success Scenario Action System Response
1. CPO views the report 2. System generates the report.
Extensions 1a. Invalid password. System asks to re-enter wrong password.
Special requirements No
Frequency of Occurrence As per requirement
Miscellaneous No
1.2.1 MANAGE CRIMINAL RECORD
1.2.1.a Use Case Name:
View criminal record
UC # 01.1 Ref: Req. # 01
UC Name View criminal record.
Level Detailed
Description This use case provides the criminal record view.
Actor (s) DO
Stakeholders DO, City Police Office, Courts/ Area Magistrate, General Public
Preconditions Criminal record must already add in system.
Success Guarantee Criminal record is viewed by DO.
Main Success Scenario Action System Response
1. DO sign in to the system. 2. System verifies access and provides main Interface.
3. DO select view record control object. 4. System shows record to user.
Extensions 1a. Invalid sign in data entry. System asks to re-enter user name and password.
Special requirements No
Frequency of Occurrence As per requirement
Miscellaneous No
1.2.1.b Use Case Name:
Add criminal record
UC # 01.2 Ref: Req. # 01
UC Name Add criminal information
Level Detailed
Description This use case adds criminal detail to system.
Actor (s) DO
Stakeholders DO, City Police Office, Courts/ Area Magistrate, General Public
Preconditions DO must be signed in.
Success Guarantee The criminal record added successfully.
Main Success Scenario Action System Response
1. DO sign in to system. 2. System shows the main interface after verification of success.
3. DO trigger the add order information control object.
4. System shows the form to input information.
Extensions 1a. Invalid data entry. System asks to re-enter sign in username and password.
4a. Invalid data entry. System asks to re-enter order correct detail.
Special requirements No
Frequency of Occurrence As per requirement.
Miscellaneous No
1.2.1.c Use Case Name:
Generate report
UC # 01.3 Ref: Req. # 01
UC Name Generate report
Level Detailed
Description This use case generates report
Actor (s) DO
Stakeholders DO, City Police Office, Courts/ Area Magistrate, General Public
Preconditions Criminal record must already add in system.
Success Guarantee Report is generated.
Main Success Scenario Action System Response
1. DO sign in to system. 2. System shows the main interface after verification.
3. DO trigger the generate report control. 4. System shows the report.
Extensions 1a. Invalid data entry. System asks to re-enter user name and password.
Special requirements No
Frequency of Occurrence As per requirement
Miscellaneous No
1.2.2. MANAGE DATABASE
1.2.2.a Use Case Name:
Update Record.
UC # 02.1 Ref: Req. # 02
UC Name Update Record.
Level Detailed
Description This use case update the existing record in system.
Actor (s) DO
Stakeholders DO, City Police Office, Courts/ Area Magistrate, General Public
Preconditions DO must be sign in and database must have some record.
Success Guarantee Accurate updating is done.
Main Success Scenario Action System Response
1. DO sign in to system. 2. System shows the main interface after verification.
3. DO invoke the update record control. 4. System shows the criminal detail.
5. DO update record. 6. System saves the updated record.
Extensions 1a. Invalid data entry. System asks to re-enter user name and password.
Special requirements No
Frequency of Occurrence As per requirement
Miscellaneous No
1.2.2.b Use Case Name:
Search the record.
UC # 02.2 Ref: Req. # 02
UC Name Search the record.
Level Detailed
Description This use case searches the record.
Actor (s) DO.
Stakeholders DO, City Police Office, Courts/ Area Magistrate, General Public
Preconditions DO must be sign in.
Success Guarantee Record is search by the DO.
Main Success Scenario Action System Response
1. DO sign in to system. 2. System shows the main interface after verification.
3. DO invokes the search record report control.
4. System shows the record
Extensions 1a. Invalid data entry. System asks to re-enter user name and password.
Special requirements No
Frequency of Occurrence As per requirement.
Miscellaneous No
1.2.2.d Use Case Name:
View Report.
View Report.
DO
DO, City Police Office, Courts/ Area Magistrate, General Public
DO must be sign in.
Report is viewed by DO
Action System Response
1. DO sign in to system. 2. System shows the main interface after verification.
3. DO invoke the view record report control. 4. System shows the report.
1a. Invalid data entry. System asks to re-enter user name and password.
No
As per requirement.
No
1.3.1.b Add criminal record.
DO
SYSTEM
DO Sign In to the System
System verifies access and provides main Interface.
DO select view record control object.
System shows record to user.
1.3.1.c Generate Report.
DO
SYSTEM
DO sign in to system.
System shows the main interface after verification of success.
DO trigger the add order information control object.
System shows the form to input information.
1.3.2 MANAGE CRIMINAL DATA BASE.
1.3.2.a Update record
DO
SYSTEM
DO sign in to system.
System shows the main interface after verification.success.
DO trigger the generate report control.
System shows the report.
1.3.2.b Search the record.
DO
SYSTEM
DO sign in to system.
System shows the main interface after verification.success.
DO invoke the update record control.
System shows the criminal detail.
DO update record.
System saves the updated record.
1.3.2.c View the record.
DO
SYSTEM
DO Sign In to the System
System verifies access and provides main Interface.
DO invoke the search record report control.
System shows the record
1.3.2.d View report.
DO
SYSTEM
DO Sign In to the System
System verifies access and provides main Interface.
DO invoke the view record report control.
System shows the record
DO
SYSTEM
DO Sign In to the System
System verifies access and provides main Interface.
DO invoke the view record report control.
. System shows the report.
DOMAIN MODEL :