<Company Name>

<Project Name>
Use Case Specification: <Use-Case Name>

Version <1.0>
<Project Name> Version: <1.0>
Use Case Specification: <Use-Case Name> Date: <10/10/2010>

Revision History
Date Version Description Author
<10/10/10> <1.0> <details> <IT Group 13>

Confidential <Company Name>, 2010 Page 62

 <Project Name> Version: <1.0>
Use Case Specification: <Use-Case Name> Date: <10/10/2010>

Table of Contents

1. Use Case Name 63

1.1 Brief Description 63

Confidential <Company Name>, 2010 Page 63

<Project Name> Version: <1.0>
Use Case Specification: <Use-Case Name> Date: <10/10/2010>

Confidential <Company Name>, 2010 Page 64

 <Project Name> Version: <1.0>
Use Case Specification: <Use-Case Name> Date: <10/10/2010>

1. Smart Government

Confidential <Company Name>, 2010 Page 65

 <Project Name> Version: <1.0>
Use Case Specification: <Use-Case Name> Date: <10/10/2010>

1.1 Brief Description : The main purpose of use-case modelling is to get to the core of what a
system must do to meet the stakeholders’ needs. To achieve this, we must first focus on who
(the Actors) will use it, or be used by it, and then on what functionality the system must
provide to give value to the user. In relation to this, this artifact captures the model of the
system’s intended functions and its environment and serves as a contract between the
customer and the developers. It is used as an essential input to activities in Analysis and
Design, Implementation, and Test.

Confidential <Company Name>, 2010 Page 66

<Project Name> Version: <1.0>
Use Case Specification: <Use-Case Name> Date: <10/10/2010>

Register

Login

Birth/Death Certificate

Ration Card

Domicile

PPO

Admin

Driving Licence

Citizen

Vehicle Registration

FIR status check

Police/Criminal Records

e-Society

Accept/Reject/Frwd

Agriculture Market Updates

Confidential <Company Name>, 2010 Page 67