Académique Documents
Professionnel Documents
Culture Documents
Table of Contents
Vision and Scope Document....................................................................................... 5
1. BUISSNESS REQUIRMENT:.................................................................................... 5
1.1 BACKGROUND:............................................................................................... 5
1.2 BUISNESS OPPORTUNITY:............................................................................... 5
1.3 BUISNESS OBJECTIVEES AND SUCCESS CRITERIA:.........................................5
1.4 CUSTOMER OR MARKET NEEDS:.....................................................................6
1.5 BUISNESS RISKS:............................................................................................ 6
2: VISION OF THE SOLUTION:..................................................................................7
2.1 VISION STATEMENT:........................................................................................ 7
2.2 MAJOR FEATURES:.......................................................................................... 7
2.3 ASSUMPTIONS & DEPENDENCIES:..................................................................8
3. SCOPE AND LIMITATION:...................................................................................... 8
3.1, 3.2 SCOPE OF INITIAL AND SUBSEQUENT RELEASE:......................................9
3.3 LIMITATION & EXCLUSION:..............................................................................9
4. BUISNESS CONTEXT:............................................................................................ 9
4.1 STAKE HOLDER PROFILES:............................................................................10
4.2 PROJECT PRIORITIES:.................................................................................... 10
4.3 OPPERATING ENVIRONMENT:........................................................................11
UML Diagrams.......................................................................................................... 12
Data Flow Diagram:............................................................................................... 12
Level 0:.............................................................................................................. 12
Level 1:.............................................................................................................. 13
Level 2:.............................................................................................................. 14
Level 3:.............................................................................................................. 15
Level 4:.............................................................................................................. 15
Entity-Relationship Diagram:................................................................................. 17
State Transition Diagram:...................................................................................... 18
Dialog Map:........................................................................................................... 21
Class Diagram:...................................................................................................... 22
Decision Tables and Decision Trees:......................................................................24
2
Introduction:.................................................................................................... 31
1.1 Purpose:....................................................................................................... 31
1.2 Document Conventions:...............................................................................31
1.3 Intended Audience and Reading Suggestions:.............................................31
1.4 Project Scope:.............................................................................................. 31
1.5 Reference:.................................................................................................... 31
2.
Overall Description:........................................................................................ 31
2.1 Product Perspective:..................................................................................... 32
2.2 Product Features:......................................................................................... 32
2.3 User Classes and Characteristics:................................................................32
2.4 Operating Environment:............................................................................... 32
2.5 Design and Implementation Constraints:.....................................................32
2.6 User Documentation:................................................................................... 33
2.7 Assumptions and Dependencies:.................................................................33
3 System Features:................................................................................................ 33
3. x System Feature X:....................................................................................... 33
4 External Interface Requirements:.......................................................................34
4.1 User Interfaces:............................................................................................ 34
4.2 Hardware Interfaces:.................................................................................... 34
4.3 Software Interfaces:..................................................................................... 35
4.4 Communication Interfaces:..........................................................................35
5 Other Nonfunctional Requirements:...................................................................35
5.1 Performance Requirements:.........................................................................35
5.2 Safety Requirements:................................................................................... 36
5.3 Security Required:........................................................................................ 36
5.4 Software Quality Attributes:.........................................................................36
6 Other Requirements:.......................................................................................... 36
Appendix A: Glossary:............................................................................................ 36
Appendix B: Analysis Models:................................................................................36
3
1. BUISSNESS REQUIRMENT:
To record the details of Prisoners and Jailors, policemen, cells, crime details
etc.
1.1 BACKGROUND:
At initial stage we had got a manual system .In which it was hard to
search a single data of any prisoner, overwriting and time consuming,
chance of data loss, too much space occupied because of too many
registers which are present in hard form and it was non secure,
because of these draw back we introduce a solution for it by building
/constructing a software for the prison which keep all those records in
efficient way. It will be easy to access no tendency problem, full secure
and easily searchable.
BO-1:
BO-2:
BO-3:
BO-4:
SC-1:
SC-2:
FINANCIAL:
Our estimation about the sale of this product is that, this product will
capture a market share of 80% within 6 months, because it will be easy
to use, easy to enter new record and easily, understandable. This
Computerized system was introduced because in current manual
system data redundancy could occur and risk of losing data is high.
NON FINANCIAL:
It will be good rated because of such requirements that fulfill all the
needs for a long period. This system is more reliable as compared to
the current manual system.
RI-2:
RI-3:
FE-2:
Can search, create, delete and update all the prisoners records.
FE-3:
Will use unique labels like astaric (*) to record the details of a
prisoner as a functional requirement and access the record of the
prisoners in the form of report as a user requirement.
FE-4:
FE-5:
FE-6:
FE-7:
Each prison will have their own interface with the facility to deal all
data related to them which can be access by their prison ID.
FE-8
Can search, delete, create and update all the jailors record.
With the prison management system the jailor may expect that he
want software along with a website.
AS-2:
The jailor may want the medical report of the prisoner for the purpose
of remand.
DE-1:
further case. For the interior minister they can get all the details from
this prison management system on one click if these are other request
from jailer out-of-scope then these request will be checked if these
request or valuable ,they will be added otherwise rejected.
FE-2:
FE-3:
FE-4:
FE-5
Release 1
The requirement like
Name,
types
of
crime, age, address,
location which are
very essential they
should
be
implemented at initial
release.
Release 2
Features like medical
report of a prison are
hard to add at initial
release so we will add it
now.
Not implemented
Prisoners details should be
given to the jailor and
interior minister.
To record the daily base
schedule of the policemen
and provide the report to
the jailor on weekly base.
To show the time table for
food of the prisoners.
Fully Implemented
Details should also be given to
the affiliated lawyers related
to the different cases.
FE-6
To
provide
weekly
base
medical report and working
credit hours of a prisoners in a
prison.
LI-2:
4. BUISNESS CONTEXT:
The project business issues are to record the details of the prisoners,
jailors and the lawyer and the prison we will include the profiles of
major stake holders like developers, analyst customers, and head of
organization etc.
Lawyer
Benefit
Benefit from
this system
for jailer is,
that he can
access,
search,
delete, and
update the
record of all
prisoners.
The Lawyer
can get the
complete
report of his
concern
prisoner.
Attitude
Attitude of
the jailer
should be
positive
towards this
system.
Constraint
This system
must be
reliable and
provide
reports of
prisoners
without error.
Interest
The Jailer
may have
interest to
access all
and
individual
record by one
click.
Should be
positive as
the lawyers
can access
the records
which will
help them in
their cases.
The system
should
provide
complete bio
data of the
prisoners to
the lawyers.
The lawyers
may have
interest to
have the final
report of
prisoners so
that they can
proceed
further.
10
Interior
Minister
He can
access the
individual
record if he
want to know
about any
prisoner bio
data.
Should be
positive as
he can
access the
records
which he
wants for his
use.
The Minister
should also
be provided
with the
complete
data he
wants.
He will have
interest as he
can get and
report the
prisoners
records for
his use.
Dimensi
on
Schedul
e
Feature
s
Driver
Constraint
Degree of Freedom
As this system is
building for the Prison
for the first time to
replace the manual
system so it could go
beyond the planned
schedule.
Here all the
authorities are will
developers who will
decide to exclude the
unimportant
features in initial
release like if they
want a software in
two months but we
11
Staf
Cost
We hire a staff of 20
people instead of 10
to build a reliable and
error free system.
If they demand
for the medical
report of the
prisoners .we
will check it if
its cost is not
too much
expensive then
we will
implement
that feature for
him.
12
UML Diagrams
Data Flow Diagram:
A data flow diagram (DFD) is a graphical representation of the
"Stream" of data through an information system, modeling its process
aspects. A DFD is frequently utilized as a preparatory step to make a review
of the system, which can later be elaborated. DFDs can likewise be utilized
for the representation of data processing (structured design).
Expected Users:
Interior Minister, Jailer, Lawyer and the prisoner but the prisoner will
interact with jailer to ask for prisoner details.
Level 0:
Example:
Figure 1 is a level 0 Data Flow Diagram (DFD) which illustrates the
initial requirements (business requirements) Prison Management System. It
includes the details about user which are; Interior Minister, Jailer, Lawyer and
the Prisoner in which the user requests to the system and result is shown.
13
Figure 1
Level 1:
Example:
Figure 2 is a level 1 Data Flow Diagram (DFD) which illustrates the
record of prisoner in which user can; Add, Update, Delete, Generate report,
Preview prisoner details, Edit police men details.
Figure 2
Level 2:
Example:
Figure 3 is a level 2 Data Flow Diagram (DFD) which illustrates the user
check the details of; Prisoner, Lawyer and Jailer.
14
Figure 3
Level 3:
Example:
Figure 4 is a level 3 Data Flow Diagram (DFD) which illustrates the user
can preview; Prisoner details and Case details.
Figure 4
Level 4:
Example:
15
Figure 5
16
Figure 6
Entity-Relationship Diagram:
An Entity-Relationship Diagram, or ERD, is a chart that visually shows
the relationship between database elements. ERDs model an organization's
data storage necessities with three primary segments: entities, attributes,
and relationships.
Example:
Figure 7 is an Entity-Relationship Diagram, or ERD which illustrates the
relationship between the entity; Jailer, Prisoner, Lawyer, PMS and Interior
Minister.
17
Figure 7
Figure 8
18
Figure 9(a)
19
Figure 9(b)
Notations:
20
Figure 10
Dialog Map:
Demonstrates a user interface (screens, windows, dialog boxes, HTML
pages) and the possible navigation paths among the interfaces components.
Example:
Figure 11 is a Dialog Map which illustrates the external behavior of the
PMS. How the user like Jailer, Interior Minister, Prisoner and Lawyer interact
with the PMS.
21
Figure 11
Class Diagram:
A class diagram is an outline of the relationships and source code
dependencies among classes in the Unified Modeling Language (UML). In this
context, a class characterizes the methods and variables in an object, which
is a particular entity in a program or the unit of code representing to that
entity.
Example:
A figure 12 is a Class Diagram which illustrates the different classes
and their objects in the PMS.
22
Figure 12
Notations:
23
Figure 13
Figure 14
25
Figure 15
26
Figure 16
Activity Diagram:
Activities diagrams are graphical representations of work processes of
stepwise exercises and actions with backing for decision, emphasis and
simultaneousness. In the Unified Modeling Language, movement outlines are
planned to display both computational and authoritative procedures (i.e.
workflows). Activity charts demonstrate the general stream of control.
EXAMPLE:
Figure 17 illustrate that it include the details about login process if an
id is valid then login success and search the record if record is found then
generate the searched report. If not found then enter the new record.
27
Figure 17
28
Figure 18
Sequence Diagram:
A Sequence diagram is a connection chart that shows how procedures
work with each other and in what request. It is a build of a Message
Sequence Chart. A sequence diagram shows object collaborations
orchestrated in time arrangement. It portrays the articles and classes
included in the situation and the succession of messages traded between the
items expected to do the situation's usefulness. Arrangement graphs are
normally connected with use case acknowledge in the Logical View of the
framework a work in progress. Succession outlines are now and then called
occasion charts or occasion situations.
EXAMPLE:
Figure 19 illustrate that user executes the PMS system then the user
will be prompt to login after that the user is logged in the request is granted
29
to the user then the data sequence is ready the next sequence will start PMS
system working.
Figure 19
Notations:
Figure 20
30
1.1 Purpose:
This is the prison management system and the purpose of this
system is to record the details of the data in computerized form
not like a previous way i.e. Manual form.
31
1.5 Reference:
The project will be linked with a Google map and it will show the
locations of different branches of the prisons. In this project we
are using the IEEE standard.
2. Overall Description:
To record the details of Prisoners and Jailors, policemen, cells,
crime details etc. The constraints are: We will use .Net
Framework to establish this software. The software will only run
on windows Operating System. The documentation should be
recorded in English language.
Description
Prisoner
Interior
Minister
Lawyer
AS-3
3 System Features:
3. x System Feature X:
The features will be named as below:
33
Record feature will be named as 3.1 and its subsections like updating the
record will be named as 3.x.1
FR-2
FR-3
UI-2
UI-3
SI-2
SI-3
SI-4
CI-2
35
PE-2
SR-2
Security
36
6 Other Requirements:
Fine payment will be written in Pakistani Rupees. We will use
English (US) language.
Appendix A: Glossary:
The developer should know about the abbreviation of P.M.S that is
prison management system.
37