Professional Documents
Culture Documents
Raksha Infotech
No 826, 9th Main
RPC Layout, Vijayangar II Stage,
Bangalore - 40. Ph : 9243101428.
www.rakshainfotech.com
email : rakshainfotech@gmail.com
Contact us for more details
Content
Abstract
This document fully and formally describes the requirements of the proposed said
project system. It sets out the functional and non-functional requirements and
includes a description of the user interface and documentation and training
requirements.
An SRS is basically an organization's understanding (in writing) of a customer o
r potential
client's system requirements and dependencies at a particular point in time (usu
ally)
prior to any actual design or development work. It's a two-way insurance policy
that
assures that both the client and the organization understand the other's require
ments
from that perspective at a given point in time.
The SRS document itself states in precise and explicit language those functions
and
capabilities a software system must provide, as well as states any required cons
traints by
which the system must abide. The SRS also functions as a blueprint for completin
g a
project with as little cost growth as possible. The SRS is often referred to as
the "parent"
document because all subsequent project management documents, such as design
specifications, statements of work, software architecture specifications, testin
g and
validation plans, and documentation plans, are related to it.
It's important to note that an SRS contains functional and nonfunctional require
ments
only; it doesn't offer design suggestions, possible solutions to technology or b
usiness
issues, or any other information other than what the development team understand
s the
customer's system requirements to be.
A well-designed, well-written SRS accomplishes four major goals:
It decomposes the problem into component parts. The simple act of writing down
software requirements in a well-designed format organizes information, places
borders around the problem, solidifies ideas, and helps break down the problem
into its component parts in an orderly fashion.
It serves as an input to the design specification. As mentioned previously, the
SRS
serves as the parent document to subsequent documents, such as the software
design specification and statement of work. Therefore, the SRS must contain
sufficient detail in the functional system requirements so that a design solutio
n can
be devised.
It serves as a product validation check. The SRS also serves as the parent
document for testing and validation strategies that will be applied to the requi
rements
for verification.
SRS are typically developed during the first stages of "Requirements Development
,"
which is the initial product development phase in which information is gathered
about
what requirements are needed--and not. This information-gathering stage can incl
ude
onsite visits, questionnaires, surveys, interviews, and perhaps a return-on-inve
stment
(ROI) analysis or needs analysis of the customer or client's current business
environment. The actual specification, then, is written after the requirements h
ave
been gathered and analyzed.
The National Bureau of Standards, IEEE (Standard No: 830-1984), and the U.S
Department of Defense have all proposed candidate formats for software requireme
nts
specifications. The general structure is implemented with the related software
application.
Introduction
This office is a Regional Transport Office a government organization.
The main activity of the RTO office is issuing the LL, DL, Vehicle
registration, Vehicle ownership transfer etc.., We proposed the
computerized method managing all the data. Because it brings
efficiency in the organization.
Purpose
The purpose of this document is to specify requirements and to give
guidelines for the development of above said project. In particular it
gives guidelines on how to prepare the above said project.
This document is intended to be a practical guide for people who
developing this software.
Scope
This is of pilot project prepared RTO office to maintain all the
records like issuing the LL, DL, Vehicle registration, Vehicle
ownership transfer etc. Once all these get computerized to work
efficiency of the employee will get increases.
Goal
The main goal of the project is to maintain the records of issuing
the LL, DL, Vehicle registration, Vehicle ownership transfer etc.
References
Existing System
At present all records are maintained manually.
Proposed System
In the proposed system will help them to manage day to day operation very smooth
ly
It is having different modules to pul fill the requirement of the organization.
Hardware and Software Requirements
Hardware Requirements
Processor : Pentium III 400MHz and Above
RAM : 128MB RAM
Monitor : 15 Color Monitor
Keyboard
Mouse
Software Requirements
Operating System. : Windows 2000/XP
Developing Tool : Visual Basic 6.0
Database : MS Access
Functional Specification
The problem under study is being divided into several modules/functions discuss
ed
below to understand the approach to the solution in the broader way:
Main Screen and login Screen
Vehicle Registration From
Learner s Licence Registration Form
Driving Licence Registration Form
Change of Address Form
Tax Collection Form
Vehicle Renewal Form
Change of ownership form
External Interfaces
The interfaces in this section are specified by documenting: the name and descri
ption
of each item, source or input, destination or output, ranges, accuracy and toler
ances,
units of measure, timing, display formats and organization, and data formats.
· User Interfaces: Describes all major forms, screens, or web pages, including
any complex dialog boxes. This is usually best done via simulated, non-functioni
ng
screen shots (such as PowerPoint slides), and may take the form of a separate
document.
The navigation flow of the windows, menus, and options is described, along with
the
expected content of each window. Examples of items included are screen resolutio
ns,
color scheme, primary font type and size. Discussion also includes how input
validation will be done, and how data will be protected from accidental changes.
Specific items are described for each screen such as input fields, control butto
ns,
sizing options, and menus.
· Hardware Interfaces: Describes the equipment needed to run the software,
and also other output or input devices such as printers or handheld devices.
Pentium III or above, 128MB RAM or above
· Windows Operating system.
Performance
Program is written such way that it gives ultimate performance for user. And it
is a
single user. So there is not much complexity in the project. Normally database w
ill
grow slowly. If the performance is not up to the mark, and it take long time the
n,
Open MS Access database run repair database tool.
Design Constraints
Examples of constraints that affect software design choices are items such as me
mory
constraints involving minimum and maximum RAM and hard disk space, and
limitations arising from hardware, software or communications standards.
Attributes
· Security: Project level security is set. User need to login when they start the
program, option is also provided to create the additional user and also the user
level
security. Presently user level security is not set but can be implemented with f
ew
modifications.
·
Reliability, Availability, Maintainability: It is very user friendly software,
Data is secured, There is not much maintenance. Project can be upgraded as
per the requirement step by step.
·
Configuration and Compatibility: Describes requirements such as those
connected with individual customization or operation in specific computing
environments.
·
Installation: Provided with the set files. User can easily install to the system
.
Describes the planned method for installation: done by the user independently,
done by customer company internal IT services, done by an external contractor.
Specifies the handling of such items as data transfer from prior releases, and
the presence of software elements from prior releases.
·
Usability: Describes items that will ensure the user-friendliness of the
software. Examples include error messages that direct the user to a solution,
input range checking as soon as entries are made, and order of choices and
screens corresponding to user preferences. More ideas on software usability
elements are found in:
Software Design Specification
The Software Design Specification (SDS) given in this outline are guidelines to
the
contents of your SDS. The document should present the conceptual and detailed
technical design of the software/module that you are developing.
Introduction
Purpose of this Document
This Software Design Specification (SDS) document contains a statement of the
design of the above title project. In an SDS, the designers are supposed to prov
ide an
unambiguous design of the product. The design should contain an explanation of a
way to carry out each of the product specifications written in the Software
Requirements Specification (SRS). The design then serves as a guide to the
developers who write the code and actually create the product. The SDS discusses
how the program is separated into modules, how the modules interact with each
other, and how users see the program. The SDS also looks into several design
considerations, including design tradeoffs and code reusability.
Scope of the Development Project
The project Tool is a new project which creates an interactive and easy program.
The
package serve to the end user customers. Eventually, we hope to reach a broader
audience.
Definitions, Acronyms, and Abbreviations
· ActionScript - ActionScript is a tool used to write the code that controls the
actions in animated Flash presentations.
· Asp.net Microsoft web based project development tool
· C, C++ - The names of two object oriented programming languages commonly
used in industry.
· CEO - Chief Executive Officer.
· Form is object holder in Visual Basic Language. Defines single screen.
· HTML - Hypertext Markup Language. A language used to create Web
documents.
· IIS Internet Information Server 5.0
· Internet Explorer Microsoft Internet Browser version 6.0
· MS Access Microsoft developed Database Program.
· Oracle Oracle Corporation RDBMS database program.
· SDS - Software Design Specification document.
· SQL Server Microsoft RDBMS software.
· SRS - Software Requirements Specification document.
· Visual Basic 6.0 Programming Language
· VB.net Microsoft dot net Programming tool
System architecture description
Document Outline
Here is the outline of the proposed template for software design specifications.
Please
note that many parts of the document may be extracted automatically from other
sources and/or may be contained in other, smaller documents. What follows is jus
t
one suggested outline format to use when attempting to present the architecture
and
design of the entire system as one single document. This by no means implies tha
t it
literally is a single document (that would not be my personal preference):
Major Screens
Main Screen and login Screen
Vehicle Registration From
Learner s Licence Registration Form
Driving Licence Registration Form
Change of Address Form
Tax Collection Form
Vehicle Renewal Form
Change of ownership form
Detailed description of components
The proposed system is developed using Visual Basic as the front end and MS Acce
ss as
the back end.
Visual Basic
A very user friendly very robust application to build the customized application
s. It can
support various other platforms also.
· It encompasses object oriented programming that creates and use the object as a
fundamental part of development process.
· Object is a basic element, which helps to build the application.
· Standard database formats for many applications are in built.
· Database creation is very simple and is done in a GUI environment.
· Modifications can be easily done to the created database.
A design description of an object in Visual Basic has a protocol description th
at
establishes the interface of an object by defining each event that the object ca
n receive
and the related operation that the object can perform when the particular event
is fired.
It has an implementation description that shows implementation details for each
operation implied by an event that is processed to an object. That implementatio
n details
about the objects private part i.e., the internal details about the data structu
re and
procedural, functional details that describe the operations.
FEATURES
The following are the various features of Visual Basic that made to select this
software for
the project.
IMPROVED RELIABILITY:
The Visual Basic takes the core achievements originally made in Windows 2000 and
brings
them to new levels. With advanced ways of monitoring the health of running appli
cations,
as well as isolating applications from each other, applications built using the
Visual Basic
stay up-and-running longer than ever before.
Developer Productivity:
Developers of all backgrounds are finding that they can rapidly get up to speed
on the
Visual Basic. The intuitiveness of the programming model, the amount of code alr
eady
provided in the class libraries, and the amount of work that the Visual Basic ha
ndles
behind the scenes in areas such as memory management have enabled Visual Basic
developers to reap huge productivity gains.
Powerful, Granular Security:
The code access security technology in the Visual Basic was designed for today's
Internet
environments. The Visual Basic can collect evidence about the origin and author
of an
application. The Visual Basic run-time environment can then combine that evidenc
e with
administrator-set or default security policies to make fine-grained decisions ab
out
whether to run that application or enable it to access a particular resource. It
can even
"negotiate" with the application, for example, denying it the permission to writ
e to a
protected directory and enabling the application to choose whether it will run,
given that it
has been denied that permission.
Support for Other Programming Languages:
The Visual Basic supports the integration of over other programming languages in
a way
unimagined previously, enabling developers to choose the right programming langu
age
for the task at hand. All programming languages target a single, extensive, and
extensible set of class libraries. Components written in different languages sup
ported by
the Visual Basic can interact seamlessly, with no COM plumbing required.
FLEXIBLE DATA ACCESS:
The Visual Basic technology for interacting with data, ADO (ActiveX Data Object)
, is
designed for today's Web-based style of data access. Using ADO, developers have
the
option of working with a platform-neutral, XML-based cache of the requested data
,
instead of directly manipulating the database. This approach to data access free
s up
database connections and results in significantly greater scalability.
MS Access
A Dataflow Diagram also known as Bubble Chart is used to clarify System requiremen
ts
and identifying major transformations that all become programs in System Design
SYMBOLS
Data Source/Destination
Process
Data Storage
Flow of data
Data Flow Diagram
ENTITY RELATIONSHIP DIAGRAM
Entity
Relationship
Attribute
Key Attribute
Entity Relationship Diagram
Data Dictionary
COAMain
DLNo
oname
fname
padd1
padd2
padd3
ppin
tadd1
tadd2
tadd3
tpin
CVMain
RegNo
oname
fname
padd1
padd2
padd3
ppin
Name
PName
tadd1
tadd2
tadd3
tpin
DLMain
DLNo
LLNo
oname
fname
padd1
padd2
padd3
ppin
tadd1
tadd2
tadd3
tpin
edate
idate
vdate
IBY
RNO
RAmt
LLMain
LLNo
oname
fname
padd1
padd2
padd3
ppin
tadd1
tadd2
tadd3
tpin
ed
Aincome
Imark
bgroup
testtype
MaxMarks
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Date
Date
Date
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
MVMain
vno Text
oname Text
fname Text
padd1 Text
padd2 Text
padd3 Text
ppin Text
tadd1 Text
tadd2 Text
tadd3 Text
tpin Text
cov Text
mname Text
btype Text
yom Text
nocy Text
cno Text
eno Text
rdate Date
TaxMain
RegNo Text
oname Text
fname Text
padd1 Text
padd2 Text
padd3 Text
ppin Text
regdate Date
myear Text
hpower Text
rno Text
ramt Text
TWMain
vno Text
oname Text
fname Text
padd1 Text
padd2 Text
padd3 Text
ppin Text
tadd1 Text
tadd2 Text
tadd3 Text
tpin Text
cov Text
mname Text
btype Text
yom Text
nocy Text
cno Text
eno Text
rdate Date
VRMain
RegNo Text
oname Text
fname Text
padd1 Text
padd2 Text
padd3 Text
ppin Text
regdate Date
myear Text
Normalization
DEFINITION
In relational database design, the process of organizing data to minimize redund
ancy is
called normalization. Normalization usually involves dividing a database into tw
o or more
tables and defining relationships between the tables. The objective is to isolat
e data so
that additions, deletions, and modifications of a field can be made in just one
table and
then propagated through the rest of the database via the defined relationships.
There are
three main normal forms, each with increasing levels of normalization:
1. First Normal Form
First Normal Form (1NF): Every cell I the table must have only one value i.e. it
should not
have multiple values.
2. Second Normal Form
Second Normal Form (2NF): All non-key attributes must be fully functionally depe
ndent
on the primary key and not just the part of the key.
3. Third Normal Form
Third Normal Form (3NF): The database must be in the second normal form and no n
on-
prime attribute should be transitively dependent on the primary key.
4. Fourth Normal Form
It deals with multiple valued dependencies
5. Fifth Normal Form
It deals with joined dependencies
6. Boyce Codd Normal Form
It states that no inverse partial dependencies should exist in the database
The Inventory Management System of a Music Store is developed using the second
normal form where the primary key of one table acts as a foreign of another tabl
e and all
the attributes of the table are dependent on the primary key and not the part of
the key.
Testing
Introduction
This document is intended to be used throughout the coding and testing phases of
the
project. It outlines the procedures used for testing and verification of the cod
e. The
document also describes the integration procedures and the order in which module
s
will be coded, and describes the test procedures and results of testing.
This section deals with the details of the classes of tests which must be conduc
ted to
validate the functions, performance, and the constraints. This is achieved basic
ally by
the means of testing which plays a vital role in the development of the software
. The
various low level testing which can be grouped on a broader sense are discussed
as
below:
There are three levels of testing:
1. Unit Testing -- Each module will be tested separately to ensure that it is
working before being combined with other modules.
2. Integration Testing -- Related modules will be integrated and tested
together before being placed into the system.
3. System Testing -- The entire system will be tested together after
integration is complete. System testing includes function, acceptance,
installation and regression testing. System testing will involve some beta
testing by the client.
Notes
All testing has been carried out using some sample data.
Each section in the remainder of this document has lists of test criteria that m
ust be
satisfied for the system to have passed that section of testing. In front of the
each
criterial test Passed or Failed is written.
Unit Testing
The purpose of unit testing is to uncover errors in the smallest software unit -
- the
routine. Each routine will be tested individually using black box-oriented tests
. The
programmer of each module will design a set of test cases for that module and en
sure
that the module is fully tested. Important or complex routines will also be test
ed by at
least one other person.
The following Forms are tested for the functionality
Main Screen and login Screen
Vehicle Registration From
Learner s Licence Registration Form
Driving Licence Registration Form
Change of Address Form
Tax Collection Form
Vehicle Renewal Form
Change of ownership form
Integration Testing
This section describes the integration strategy and procedures for the system. I
t gives
the order in which modules will be developed and how they will be integrated. It
also
describes the specific tests that will be performed on integrated sets of module
s.
Note: It is important that each module be thoroughly tested as a unit before bei
ng
integrated with other modules.
Integration testing of unit tested modules is necessary to ensure that:
· modules interface correctly with each other;
· one module does not have inadvertent, undesirable effects on another
module;
· submodules (routines) combine to produce the desired functions of the
major module;
· interfaces to, and use of global data structures are consistent.
Tested the Stock form correct updation
System Testing
Functional Requirements Testing
The functionality tests should be performed by the application representatives a
nd
treat the whole system as a black box using the actual applications or middlewar
e.
The aim of these tests is to verify the overall functionality of the system.
This will be performed by a section by section walkthrough of the SRS functional
requirements section. All functional requirements in the SRS must be fulfilled.
Beta Testing
Method
This will be performed by the client, and by potential users of the system at th
e
Bureau of Meteorology. Users will be given a copy of the system to try out. Any
problems with the system will be reported back to the group.
Beta Testing
To help us achieve the best possible result with our project, we have decided to
get as
much input as possible from potential users of our system.
Bugs.
If unexpected events happen while using project,
Alterations.
If there is anything missing from the system, that you would like to see there,
we
would also like to know about it. Most likely we will not be able to implement t
he
changes to the current system (due to time restraints), but when the full system
is
written next year, it will most likely be present.
Results
Comments received from the customers:
Alpha testing - prototype 2 of system
Performance and Stress Testing
A set of tests have been developed for performance and stress testing. Performan
ce
tests will ensure that the system responds in a reasonable time to user input (a
s
defined in the SRS). The aim of stress testing is to try to break the program by
giving
it abnormal or extreme input quantity, frequency or volume.
missing dependencies.
Installation tests test the installation and configuration procedures. These tes
ts are a
set of scripts that automatically download all necessary packages and install th
em.
Acceptance testing will be repeated after installation of the system at the Cust
omer
Place. This is to ensure that the system works correctly in the Customer Place.
Note: System has not been installed for the client yet. Will be installed this w
eek.
Some specific points that also need to be tested are:
1. Directory paths for data and help files are set up correctly and can be found
by
the system.
2. Check for necessary third party controls.
3. All IDL library functions can be found by the system.
4. All fonts for the text tool can be found and loaded -- beta testing uncovered
some problems loading some fonts.
5. Check Printer drivers are installed properly.
Regression Testing
The selective retesting of a software system that has been modified to ensure th
at
any bugs have been fixed and that no other previously working functions have fai
led
as a result of the reparations and that newly added features have not created
problems with previous versions of the software. Also referred to as verificatio
n
testing, regression testing is initiated after a programmer has attempted to fix
a
recognized problem or has added source code to a program that may have
inadvertently introduced errors. It is a quality control measure to ensure that
the
newly modified code still complies with its specified requirements and that unmo
dified
code has not been affected by the maintenance activity.
Regression testing was not usually necesary, because most of the errors detected
were very localised, and did not affect other functions in an adverse manner.
User Manual
And
Screen Shots
Main Screen and login Screen
Vehicle Registration From
1
2
3 6 7
5
84
Follow the below steps enter the Data
1. Click on New button to enter the new record
2. Enter details in each box.
3. To save the record click on Save Button
4. Click on find button to see the find the required vehicle details
5. Enter the vehicle number in the box and then click ok
6. If any changes need to be done then make changes and then click Modify button
7. If you want to delete the record then click on Delete button
8. To close the form click on Close button.
The same method is applicable to all other forms.
Learner s Licence Registration Form
Driving Licence Registration Form
Change of Address Form
Tax Collection Form
Vehicle Renewal Form
Change of ownership form