You are on page 1of 15

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.

C IM M N G M N S S E R E A A E E T YT M
m anage crim inal record

D O

m anage data base

view record

S P

view record

D P S

view record

D IG

View The Reports

C O P

Abstract level Use case of System

1.2. ABSTRACT LEVEL DESCRIPTION OF USE CASES

1.2.1 Use Case Name:

Manage criminal record. ` UC # UC Name Level Description Actor (s) Stakeholders Preconditions Success Guarantee Main Success Scenario 01 Manage criminal record Abstract. This use case manages the criminal record DO DO, City Police Office, Courts/ Area Magistrate, General Public DO is signed in to use this use case. All Data is managed successfully. Action 1. DO view criminal record 3. DO insert criminal record. System Response 2. System shows the report. 4. System save the information in managed way. System asks to re-enter wrong entry. Ref: Req. # 01

Extensions Special requirements Frequency of Occurrence Miscellaneous

2a. Invalid data entry. No As per requirement No

1.2.2 Use Case Name: Manage database

UC # UC Name Level Description Actor (s) Stakeholders Preconditions Success Guarantee Main Success Scenario

02 Manage database Abstract.

Ref:

Req. # 02

This use case manages the database system. DO DO, City Police Office, Courts/ Area Magistrate, General Public DO must have Criminal detail. Whole database is controlled by this use case. Action System Response

1. DO update record in system. 3. DO search record form database Extensions Special requirements Frequency of Occurrence Miscellaneous 1a. Invalid data entry. No As per requirement No

2. System update record. 4. System shows the required record. System asks to re-enter wrong entry.

1.2.3 Use Case Name: View record

UC # UC Name Level Description Actor (s) Stakeholders Preconditions Success Guarantee Main Success Scenario

03 View record Abstract.

Ref:

Req. # 03

This use case shows the criminal record. Accountant. SP,City Police Office, Courts/ Area Magistrate, General Public. SP must have Criminal detail. All criminal related issues managed by this use case. Action 1. SP view the record. System Response 2. System Shows the record. System asks to re-enter wrong password.

Extensions Special requirements Frequency of Occurrence Miscellaneous

1a. Invalid password. No As per requirement No

1.2.6 Use Case Name: View reports

UC # UC Name Level

06 View reports Abstract.

Ref:

Req. # 06

Description Actor (s) Stakeholders Preconditions Success Guarantee Main Success Scenario

This use case shows the report CPO City Police Office, Courts / Area Magistrate, General Public. CPO must have Criminal detail. All criminal related issues managed by this use case. Action 1. CPO views the report System Response 2. System generates the report. System asks to re-enter wrong password.

Extensions Special requirements Frequency of Occurrence Miscellaneous

1a. Invalid password. No As per requirement No

1.2.1 MANAGE CRIMINAL RECORD 1.2.1.a Use Case Name: View criminal record

UC # UC Name Level Description Actor (s) Stakeholders Preconditions Success Guarantee Main Success Scenario

01.1 View criminal record. Detailed

Ref:

Req. # 01

This use case provides the criminal record view. DO DO, City Police Office, Courts/ Area Magistrate, General Public Criminal record must already add in system. Criminal record is viewed by DO. Action 1. DO sign in to the system. System Response 2. System verifies access and provides main Interface. 4. System shows record to user. System asks to re-enter user name and password.

3. DO select view record control object. Extensions 1a. Invalid sign in data entry.

Special requirements Frequency of Occurrence Miscellaneous

No As per requirement No

1.2.1.b Use Case Name: Add criminal record

UC # UC Name Level Description Actor (s) Stakeholders Preconditions Success Guarantee Main Success Scenario

01.2 Add criminal information Detailed

Ref:

Req. # 01

This use case adds criminal detail to system. DO DO, City Police Office, Courts/ Area Magistrate, General Public DO must be signed in. The criminal record added successfully. Action 1. DO sign in to system. System Response 2. System shows the main interface after verification of success. 4. System shows the form to input information. System asks to re-enter sign in username and password. System asks to re-enter order correct detail.

3. DO trigger the add order information control object. Extensions 1a. Invalid data entry.

4a. Invalid data entry. Special requirements Frequency of Occurrence Miscellaneous No As per requirement. No

1.2.1.c Use Case Name: Generate report

UC # UC Name Level Description Actor (s) Stakeholders Preconditions Success Guarantee

01.3 Generate report Detailed This use case generates report DO

Ref:

Req. # 01

DO, City Police Office, Courts/ Area Magistrate, General Public Criminal record must already add in system. Report is generated.

Main Success Scenario

Action 1. DO sign in to system.

System Response 2. System shows the main interface after verification. 4. System shows the report. System asks to re-enter user name and password.

3. DO trigger the generate report control. Extensions 1a. Invalid data entry.

Special requirements Frequency of Occurrence Miscellaneous 1.2.2. MANAGE DATABASE 1.2.2.a Use Case Name:

No As per requirement No

Update Record.

UC # UC Name Level Description Actor (s) Stakeholders Preconditions Success Guarantee Main Success Scenario

02.1 Update Record. Detailed

Ref:

Req. # 02

This use case update the existing record in system. DO DO, City Police Office, Courts/ Area Magistrate, General Public DO must be sign in and database must have some record. Accurate updating is done. Action 1. DO sign in to system. System Response 2. System shows the main interface after verification. 4. System shows the criminal detail. 6. System saves the updated record. System asks to re-enter user name and password.

3. DO invoke the update record control. 5. DO update record. Extensions 1a. Invalid data entry.

Special requirements Frequency of Occurrence Miscellaneous

No As per requirement No

1.2.2.b Use Case Name: Search the record.

UC # UC Name Level Description Actor (s) Stakeholders Preconditions Success Guarantee Main Success Scenario

02.2 Search the record. Detailed

Ref:

Req. # 02

This use case searches the record. DO. DO, City Police Office, Courts/ Area Magistrate, General Public DO must be sign in. Record is search by the DO. Action 1. DO sign in to system. System Response 2. System shows the main interface after verification. 4. System shows the record

3. DO invokes the search record report control. Extensions 1a. Invalid data entry.

System asks to re-enter user name and password.

Special requirements Frequency of Occurrence Miscellaneous 1.2.2.d Use Case Name:

No As per requirement. No

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 1. DO sign in to system. System Response 2. System shows the main interface after verification. 4. System shows the report. System asks to re-enter user name and password.

3. DO invoke the view record report control. 1a. Invalid data entry.

No As per requirement. No

SYSTEM

DO 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.b

Add criminal record.

SYSTEM

DO 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.1.c

Generate Report.

SYSTEM

DO 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

MANAGE CRIMINAL DATA BASE.

1.3.2.a

Update record

SYSTEM

DO 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.b

Search the record.

SYSTEM

DO 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.c

View the record.

SYSTEM

DO DO Sign In to the System System verifies access and provides main Interface. DO invoke the view record report control.

System shows the record

1.3.2.d

View report.

SYSTEM

DO 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 :