Академический Документы
Профессиональный Документы
Культура Документы
Specification
Civil Registry
by
Gaurav Pawar (153)
Mustufa Merchant(156)
Balaji Kole(1)
Table of Contents
Table of Contents.........................................................................................................................................2
List of figures..............................................................................................................................................3
1. Introduction...........................................................................................................................................4
1.1 Purpose...........................................................................................................................................4
1.2 Document Conventions...................................................................................................................4
1.3 Intended Audience and Reading Suggestions..................................................................................4
1.4 Product Scope.................................................................................................................................5
1.5 References......................................................................................................................................5
2. Overall Description...............................................................................................................................6
2.1 Product Perspective.........................................................................................................................6
2.2 Product Functions...........................................................................................................................6
2.3 User Classes and Characteristics.....................................................................................................6
2.4 Operating Environment...................................................................................................................7
2.5 Design and Implementation Constraints.........................................................................................7
2.6 User Documentation.......................................................................................................................7
2.7 Assumptions and Dependencies......................................................................................................7
3. External Interface Requirements...........................................................................................................8
3.1 User Interfaces................................................................................................................................8
3.2 Hardware Interfaces........................................................................................................................8
3.3 Software Interfaces.........................................................................................................................8
4. System Features....................................................................................................................................9
4.1 Functional Requirements................................................................................................................9
5. Other Nonfunctional Requirements.....................................................................................................14
5.1 Performance Requirements...........................................................................................................14
5.2 Safety Requirements.....................................................................................................................14
5.3 Security Requirements..................................................................................................................14
6. Key Milestones....................................................................................................................................15
7. Other Requirements.............................................................................................................................16
List of figures
Figure 1 - System Environment......................................................................................................6
Figure 2 User Interfaces...............................................................................................................8
1. Introduction
1.1 Purpose
The primary objective of this web site is to give awareness about the government or legal
documents and its registration details as well as to help to register or apply for those documents.
This also acts as a consultancy agency to assist the public. The main purpose of the web site is to
reduce the effort by the candidate and save his time and avoid unwanted rushes at the
government offices and assure a smooth working schedule at government offices.
3. Overall Description
2.1 Product Perspective
This system is providing online facility to apply for different official documents together which
were not present before. This will increase the popularity of the system and it will reach to a
large mob. This will provide a way to attract citizens so that it will be easy for them to register or
apply for those documents anytime as well as any where according to their availability. Here
anyone can register and apply for government records.
Administrator: They will have total access of the system; will do verification and approval of
users request as well as controls official documents.
Visitors: They can give there feedback or can enquire for requirement regarding any official
document
a server-side Web
application
framework designed
for Web
development to
produce dynamic Web pages. VB .NET is built on the Common Language Runtime (CLR),
allowing programmers to write VB.NET code using any supported .NET language. The
VB.NETextension framework allows VB.NET components to process SOAP messages. This is a
web application so platform will not be a barrier for this system.
The computers must be equipped with web browsers such as Internet explorer
This system is not only accessible to limited peoples rather it can be used by students
also.
4. System Features
4.1 Functional requirements
System provides user login, admin login, Registration, feedback, mailer. These features form the
body of the application and include any features that are essential to the functionality of the web
portal. These features must be implemented in order to have a fully-functioning application.
Additional features, however, are not required for the portal to function. They include any
features which, if time permits, will be added to the application in order to provide extra
functionality.
Consider the following use cases.
1) User login
Use Case Id :
01
User login
Brief Description :
Actor :
User
Precondition :
Basic Flow:
Alternative Flow :
Exception Flow :
Post Condition :
2) Admin login
Use Case Id :
02
Admin login
Brief Description :
Actor :
Admin
Precondition :
Basic Flow:
Alternative Flow :
Exception Flow :
Post Condition :
3) display options
Use Case Id :
03
Display Options
Brief Description :
Actor :
User,Admin
Precondition :
Basic Flow:
Alternative Flow :
No
Exception Flow :
Post Condition :
4) Registration
Use Case Id :
04
Registration
Brief Description :
Actor :
User, Admin
Precondition :
Basic Flow:
Alternative Flow :
5.Register
No
Exception Flow :
the registration
Post Condition :
5) Feedback
Use case Id :
Use case name :
Brief description :
5
Feedback
User can give his/her feedback about the services provided
Pre-condition :
Basic flow :
Alternate flow :
Exceptional flow :
Output :
Post conditions :
6) Contact us
Use case Id :
Use case name :
Brief description :
Pre-condition :
Basic flow :
6
Contact us
Third party/visitors can obtain contact information.
Third party/visitors should click on contact us.
1. User selects contact us.
2.System displays contact details such as:
i) Address of main office
ii) Contact no.
Alternate flow :
Exceptional flow :
Output :
Post conditions :
dont lose the information. The design addresses some of the vulnerabilities, such as buffer
overflows, which have been exploited by malicious software. Additionally, .NET provides a
common security model for all applications.
.NET has its own security mechanism with two general features: Code Access Security (CAS),
and validation and verification. Code Access Security is based on evidence that is associated
with a specific assembly. Typically the evidence is the source of the assembly (whether it is
installed on the local machine or has been downloaded from the intranet or Internet). Code
Access Security uses evidence to determine the permissions granted to the code. Other code can
demand that calling code is granted a specified permission. The demand causes the CLR to
perform a call stack walk: every assembly of each method in the call stack is checked for the
required permission; if any assembly is not granted the permission a security exception is
thrown.
6. Key Milestones
Milestone
SRS document
Deadline
24/01
Comments
Abstract done by Dec 24, so a presentation can be
06/02
created
Designs should be done a week in advance of
Interface Design
Finalized
10/02
Algorithm Design
SDD document
15/02
Server Setup
18/02
created
This should be done in the beginning of the
Interface &
04/03
Finalized
Algorithm
Implementation
Software Festival
7. Other Requirements
Necessary details required for issuing official documents are required.