Professional Documents
Culture Documents
II SYNOPSIS
1. INTRODUCTION
OVERVIEW
NEEW FOR THE SYSTEM
2. ORGANIZATION PROFILE
3. BACKGROUND STUDY
EXISTING SYSTEM
PROPOSED SYSTEM
4. SYSTEM STUDY AND PROBLEM FORMULATION
MAIN OBJECTIVE
PLATFORM SELECTION
HARDWARE SPECIFICATION
SOFTWARE SPECIFICATION
4.3. REASONS FOR SELECTING PLATFORM
5. SYSTEM ANALYSIS
FEASIBILITY STUDY
TECHNICAL FEASIBILITY
ECONOMICAL FEASIBILITY
OPERATIONAL FEASIBILITY
6. SYSTEM DESIGN
INPUT DESIGN
OUTPUT DESIGN
CODE DESIGN
DATABASE DESIGN
VALIDATION CHECKS
7. SYSTEM TESTING
TESTING
UNIT TESTING
INTEGRATION TESTING
SYSTEM TESTING
8. SYSTEM IMPLEMENTATION
9. SYSTEM SECURITY
10.
11.
BIBLIOGRAPHY
APPENDICES
A. ACTIVITY DIAGRAM
B. USE CASE DIAGRAM
C. DATA FLOW DIAGRAM
D. E-R DIAGRAM
E. SCREEN SHOTS
F. REPORT
SYSNOPSIS
1. INTRODUCTION
that
the
software
element(s)
satisfies
its
Software
Engineering
data
regarding
the
Login.
Administration
Mail System
MODULE DESCRIPTION:
LOGIN:
A well-design login takes care of the authenticated users
by providing different views. When a user logs in, his role is verified. If he
is an administrator he is personal with an administrator view to achieve
his personal tasks. If he logs in as any other user then he is prompted for
a project code. The project code uniquely identifies the role of the user
with in the software.
ADMINISTRATION:
Here Administrator plays a vital role in this tool. He is the
person responsible for creating or removing authenticated users on
demand. He is also responsible to add/remove projects and to enter
author details for a project.
He is provided with a well defined graphical interface to achieve these
tasks.
Defect
sheet.
details
like
number
of
Major,
Minor
and
Attend meetings.
Here Author & Inspector plays vital roles in this tool. The author
deals with the following functions.
relevant.
Attend Meetings.
expectations are not met the document will have to be re-inspected again.
The scribe logs accepted comments.
Brainstorm on improving the inspection process with all the
reviewers
.Moderator
will
verify
the
incorporation
of
Inspection
comments. Moderator feels that the review expectations are not met the
document will have to be re-inspected again.
MAIL SYSTEM:
A simple mailing subsystem deals with the mails within the
software. A user can register him self to receive or send the mails. A welldefined graphical user interface is provided for these tasks. A user is
informed during all the important stages in the inspection process
through this mail address.
2. ORGANIZATIONAL PROFILE
SDSOFT
in
the
fields
of
website
and
application
design
and
E-learning
Financial Services
E-business
Application Engineering
Healthcare
Total Quality
We make sure that all products and services we deliver pass
through the most stringent testing and review process and that they are
100% defect free. We wont stop at good enough because GOOD is not
enough for our customers, and we wont stop at anything less than BEST
for our customers. At SDSOFT, Quality is not just about implementing a
system or working towards a set of standards. It is an attitude, a way of
working, which not only improves businesses but the way people work
and live. We strive to facilitate and promote the use of quality to add
value
to
our
customers
and
enhance
the
standing
of
quality
develops
and
designs
state-of-the-art
web
page
applications on new age technologies for its clients. All these applications
have been critically acclaimed globally and have created a benchmark in
their respective fields. The credit for all this goes to our highly specialized
software development team who through their time tested development
technology deliver all the projects in time and according to the budget. All
the activities in business analysis, design, development and testing are
conducted through the flexible and module based approach which
ensures minimum client risk and also implementation of clients'
requirements as per accepted international standards. Thus, we comply
best with our committed deliverables and provide the best solution to our
clients.
3. BACKGROUND STUDY
Time Consumption.
4. PROBLEM FORMULATION
4.1. MAIN OBJECTIVE:
The system study is use of the users to do more flops of data entry,
modification, deletions and report preparation. This makes each and every
data with more functionally and security.
As mentioned in the SDLC concepts, the first step is to study
the existing system and to confirm whether the proposed system is
feasible. We studied the system closely, thus performing the function of
an analyst. We sorted out different functions performed by different
people in the system.
We studied the whole activities related to the inspection process
carried out at each phase of SDLC. We thought of the possibilities of
automation to be brought out in the new system and its feasibility
concerns. Various activities performed, personnels involved, the steps
involved and responsibilities of various persons in the inspection process
in the existing system are as follows
Cross Check
After completion of document the author sends the document
for cross check to the identified crosscheck team. Cross check team
project
planning
phase
by
the
Project
Manager
as
per
Inspection team
agreed and a commitment from the reviewers is taken for the same.
Specialization roles are assigned to the reviewers; defect rate and logging
rate are also agreed upon. It is preferable to induct a new member for the
Inspection and brief about the inspection process. Agreed logging date,
defect rate and specialization roles are filled in the Inspection Master
Plan template.
Logging Meeting
As per the agreed schedule Inspectors assemble for the logging of defects.
Inspection comments are logged in the Inspection Issues log as per the
sequence identified by the moderator.
The scribe logs accepted comments. If there is any repetition of the
comments among the inspectors then those comments are not logged.
The scribe obtains statistics like Individual Effort Spent on the
inspection and defect details like number of Major, Minor and
Observations from the Inspectors before starting the logging. Defects are
logged page wise or section wise as per the identified sequence.
Incorporating Logging Comments
On completion of logging meeting author shall incorporate all the
comments and any rejected Comments will have to be justified by the
author. If any clarifications are required author will consult the
Inspectors.
will
verify
the
incorporation
of
Inspection
comments.
Moderator will also check for the adequacy of the Inspection by verifying
with the goals identified in the SDP. In Case Moderator feels that the
review expectations are not met the document will have to be reinspected again.
The study of the existing system was the base to create a new system.
The main objectives for the proposed system were
: 32 BIT, Pentium IV
RAM
: 256 MB
HARD DISK
: 40 GB
MONITOR
SVGA
Monitor
(800
RESOLUTIONS)
CLOCK SPEED
KEYBOARD
MOUSE
FLOPPYDRIVE
: 266 MHz
: 101 KEYS
: Logitech
: 1.44 MB
: Windows 2000/XP.
: XML, HTML, DHTML
MIDDLEWARE
: J2EE
BACK END
: Oracle 8i
SERVER
600
J2EE ARCHITECTURE
JAVA CODE
Intermediate compilation
JAVA BYTE
CODE
Runtime VM interpretation
WIN32
HP-VX
Solaris
Application Components
Application clients
Clients are generally stand alone applications written in java. They
run within a virtual machine and can use the J2EE services to access
components located within another tier.
Applets
Applets are similar to application clients but execute within a web
browser.
Web Components
They are server side components generally used to provide the
presentation layer to be returned to a client. 2 types of web components
exist
Servlets.
Java servlets fall into the first category, while Java server pages belong to
typically comprise of
and
are
designed
to
increase
the
efficiency
in
which
It is true that both servlets and JSP pages have many features in
common
and
can
be
used
for
serving
up
dynamic
web
Server Components
Server components can be in form of EJBs (Enterprise Java
beans). EJBs executes within a container that manages the runtime
behavior of EJBs.
presentation logic.
ORACLE:
Oracle is a trademark of Oracle Corporation and in common
usage refers to the database engine (which actually looks for the data)
and the range of front-end products. Oracle 8i is the largest selling SQLbased RDBMS and a most commercially useful product.
Performance
Speed of Oracle 8i database is quite well managed. Even with large
database oracle 8i refers to more than 100GB databases and the
performance is only raw. But includes consideration of performance
with locking and transaction control.
Compatibility
Oracle 8i software is compatible with industry standard and
industry standard operating systems. The applications developed can be
used on any systems with little or no modification.
Connect ability
Oracle 8i software allows different computers and operating
systems to share information across networks.
Security
Oracle 8i provides powerful security features to limit and monitor
data access. These features make it easy to manage even the most
complex design of data access.
Products of Oracle 8i
The following are some of the products of Oracle:
SQL * PLUS
SQL * DBA
SQL * FORMS
SERVER SPECIFICATION:
developing,
integrating,
deploying,
and
managing
large-scale,
Provides
the
most
comprehensive
implementation
of
the
connection
is
shared
across
all
bidirectional
Management
BEA
WebLogic
provides
centralized
5. SYSTEM ANALYSIS
and
development.
no
reasonable
alternative
needed
for
the
project
6. SYSTEM DESIGN
6.1.
INPUT DESIGN
Users are prompted with specified input box to obtain prior
input from the user. They are designed in such a way that the users can
cope up with the outputs that has been requested.
The input design must be in such a way that it must control
the amount of input, avoid delay etc. It must be simple. The input design
must ensure user-friendly screens, simplicity, providing ease of viewing
and entering the data. The main objective of designing input focus on
Controlling errors
Avoiding errors
6.2.
OUTPUT DESIGN
Content
The content of the output must be in such a way that it
must prevent redundancy, the data produced must be accurate, reliable
and the output must furnish relevant data.
Format
The format has been designed in analysis according to user
need and in importing table output formats as standard.
Frequency
The frequency of the output should be maintained according to the
users needs.
Data base design is concerned with the data focus from the
perspective of the system designer. The end product is called a database
schema, a technical blueprint of database.
Database design translates the data models that were developed
for the system users during the definition phase in to data structures
supported by the choosen database technology. The goals of database
design are as follows
CREATE_EMP
FIELD
ename
empid
DATA TYPE
Varchar2(50)
Varchar2(5),primary
DESCRIPTION
Employee name
Employee
Identification
key
Varchar2(30)
number.
Employee email within the
specialization Varchar2(30)
Software.
Specialization
Grade
employee.
Grade of the employee
Varchar2(3)
of
the
PROJECT
FIELD
proj_name
proj_id
DATA TYPE
VARCHAR2(50)
VARCHAR2(20),primary
key
author_name
VARCHAR2(50)
proj_document VARCHAR2(50)
CONSTRAINTS
Name of the project
Project code
Name of the author
File names for the
project
INSPECTION TEAM
FIELD
project_code
project_ name
emp_code
emp_name
email_id
DATA TYPE
VARCHAR2(20)
VARCHAR2(30)
VARCHAR2(5)
VARCHAR2(30)
VARCHAR2(50)
CONSTRAINTS
Project code
Project name
Employee Code
Employee Name
Email id of the employee
DEFECT_LOGGING
FIELD
Proj_name
Proj_doc
DATA TYPE
VARCHAR2(20)
VARCHAR2(30)
CONSTRAINTS
Project name
Project file name
Defect_severity VARCHAR2(5)
Defect_class
VARCHAR2(30)
Defect_root
VARCHAR2(30)
Injected_phase VARCHAR2(30)
Defect_state
Desc
VARCHAR2(30)
VARCHAR2(100)
MAILDETAILS
FIELD
Firstname
Lastname
Address
State
Zipcode
Username
Hintq
Hans
DATA TYPE
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
CONSTRAINTS
NotNull
NotNull
NotNull
NotNull
NotNull
Primary key
NotNull
NotNull
DESCRIPTION
First name
Last name
Address
State
Zipcode
Mail id of user
Hint question
Hint answer
7. SYSTEM TESTING
7.1. TESTING
White-box Testing
Black-box Testing
Unit Testing
Integration Testing
Validation testing
Output Testing
performs
according
to
specification
and
all
internal
By the test cases each of the JIS modules have executed at least
once and tested for bugs. All the logic decisions on their true and false
sides are executed so that the system will perform well.
7.1.2 BLACK-BOX TESTING
All the functions in the system are tested one after another and the
desired tasks are fulfilled. Input values should lie in the data values size
and these must check before processing. All the boundary values are
tested.
On screen format
Print format
The screen is found to be correct as the format designed
according to the user needs for the hard copy also; the output comes out
as specified by the user. Hence output testing doesnt result in any
correction in the system.
ADMIN LOGIN
Unit
Test
Description
Excepted result
Actual result
remarks
case
In
UT01
this
login
page, The
should
displayed.
Admin The
Admin
Home
be will
displayed.
page
be
No
Remarks
In
UT02
this
Homepage
Hyperlinks
displayed
on
No
are displayed.
Form will be
the
displayed.
Remarks
want
to
department
go The
department The
Form will be
link.
displayed.
No
user
displayed.
will
be
displayed.
You
UT05
want
Homepage
Home link.
to
click
go The
Remarks
No
Remarks
on Homepage
should
Homepage will
be be displayed.
displayed.
No
Remarks
DESIGNATION
Unit
Test
Case
Description
Excepted Result
Actual Result
Remarks
new New
No
new be
created.
The be
created
designation successfully.
new
designation should
and
click
be
if
Create" button.
Select
message.
the Before
checkboxes
shows
going
to The
selected No
deleted
click
on
button.
want
to
delete
particular
designation
click
OK button.
you
UT03
want
to
Admin The
UT04
go The
want
go The
Login
DEPORTMENT
should Homepage
be displayed.
to
displayed
Admin No
will Remarks
be displayed.
page The Login page No
be will
displayed
be Remarks
Unit
Test
Description
Excepted Result
Actual Result
Remarks
Case
In
this The
department
create
created.
new new
The successfully.
if
department,
should
be
enter
on the department it
shows
the Before
checkboxes
which
UT02
you
going
to The
deleted
selected No
to
delete.
"Delete" Particular
button.
department
click
OK button.
UT03
Admin The
should Homepage
on "Home "link.
be displayed.
Login
Admin No
will Remarks
be displayed.
page The Login page No
be will be displayed Remarks
Unit
Test
Description
Expected Result
Actual Result
Remarks
Case
In
this
Injuries The
new
Injury New
Injury The
new
be existing
Injury created
injury
and
click
"Create" button.
Select
the Before
checkboxes
which
UT02
you
going
no-shows
Injury the
is
already message
exist
it
not it
gives
show
some
message
error.
to The
is
selected No
"Delete" want
button.
to
particular
delete
Injury,
Homepage
Admin The
Admin No
displayed.
will
Remarks
be
displayed.
UT04
Login
page The
Login No
on "Logout "link.
displayed
INJURY
BODY PART
Unit
Test
Description
Expected Result
Actual Result
Remarks
Case
In this Body part The
new
should
part,
enter
Body
part
if
Body part
No
in
the
shows
same message.
page.
UT02
Select
the Before
checkboxes
going to The
on
button.
selected No
"are
you successfully.
delete
particular
part
deleted
body
click "OK"
Remarks
button.
You
UT03
want
to
go The
Admin The
should
Admin No
Homepage
will
Remarks
be be displayed.
displayed.
you
UT04
want
Login
page
to
click should
on "Logout" link.
be will
displayed
be
Remarks
displayed
HOW CODE
Unit
Test
Description
Excepted Result
Actual Result
Remarks
Case
UT01
Code,
will
be Remarks
Code
is
already exist it
how
shows
it
happens,
No
enter
new
Code,
message.
the Before
checkboxes
going
to The
selected No
will Remarks
deleted
on
button.
want
to
particular
delete
incident
click OK button.
you
UT03
want
to
Admin The
UT04
go The
want
Login
page
be displayed.
to
go The
Login
Admin No
be displayed.
page The Login page No
on "Logout" link.
will
be Remarks
displayed
USER CREATION
Unit
Test
Case
Description
Excepted Result
Actual Result
Remarks
In
this
How
new
created Remarks
means
UT01
be
what How
occur the
Code
No
exist
If
is
it
in
the
selected No
"Delete" button.
"are
you successfully.
You
to
delete
particular
incident
click
OK button.
You
UT03
want
to
go The
should
Admin The
Admin No
displayed.
You want to go Login The Login page The Login page No
UT04
page
click
"Logout" link.
on should
displayed
be will be displayed
Remarks
Unit
Test
Description
Excepted Result
Actual Result
Remarks
Case
In
this
UT01
injury
registered
successfully.
fields
and
"Create"
click
button.
No
on
Here
UT02
particular
injury search,
on The
details,
click
on details
Search"
link.
The be displayed.
search
will
be
based
injury No
should displayed
done
on
Employee/Name.
You want to reset the The form values The
UT03
UT04
form No
button.
cleared.
you
want
to
go The
Admin The
Admin No
Homepage
click
on Homepage
Home "link.
should
displayed.
Homepage
be will
displayed
be
displayed.
Remarks
Login No
EMPLOYEE LOGIN
Unit
Test
Description
Excepted Result
Actual Result
Remarks
Case
In this login page, The
UT01
enter
username
valid Homepage
should Home
and be displayed.
password.
be
displayed.
will
page Remarks
all Homepage
Hyperlinks
are be displayed.
be displayed.
displayed on the
admin Header.
UT03
click Homepage
No
on Home link.
be displayed.
Login
be displayed.
page The
be page
displayed
Login No
will
be Remarks
displayed
Unit
Test
Description
Excepted Result
Actual Result
Remarks
Case
In this Time Lost The no of days for The total no of No
Details
page,
know
the
many
days
to respective
how will
the
for Remarks
work respective
respective employee
UT01
left
employee days
employee
will
be displayed.
page,
to should be displayed.
know
the
how
many
days
the
days
will
be Remarks
displayed
respective
UT02
employee, return to
normal duties click
on the respective
"no of days return
to work" text box,
the respective days
will be displayed.
In this page, if you The
UT03
page investigation
the
page
person
for
displayed.
more
will
Remarks
be
to
the
respective
"investigation "page
UT04
the
"Submit" on
button.
the
investigation
"Submit" investigation
The button.
click employee
investigation
details respective
Remarks
details
registered
in
the database
database
You want to clear The few investigation The
the
form
click
UT05
on
values, details
should
few No
be investigation
Remarks
button.
the"Timelost
Details"
table
in
the
database
You want to clear The
the
UT06
form
click
on
form
values The
form No
"Reset"
cleared.
button.
You
UT07
want
to
go The
Admin The
Admin No
displayed
displayed
INCIDENT REGISTRATION
Unit
Test
Case
Description
Excepted Result
Actual Result
Remarks
In
this
Incident The
Registration
incident Incident
UT01
No
Details
successfully.
incident
Details
based
on
click
on
"Submit" button.
If incident date and If date and time date and time are No
incident
time matches,
matches
the Remarks
registered
UT02
the matches,
will
be
,the
details
will
be the
"no
which incident
"no
The records
such
found"
details message.
same page.
the
form
click
on
values, should
be will be cleared.
Remarks
"Reset" cleared.
button.
UT04
You
want
to
go The
Admin The
Admin No
"Home" link.
be displayed.
displayed.
8. SYSTEM IMPLEMENTATION
The
software,
which
was
designed
in
design
and
9. SYSTEM SECURITY
this project brings out the complete analysis of the token ring and the
complete design, development, testing and implementation of the project.
I hope that the analysis will be useful to others those who read them in
future.
11. BIBLIOGRAPHY
BOOKS
JavaScript
- David Flanagan (OReilly)
ONLINE SUPPORT
www.sun.com
www.apache.com
www.openbravo.com
www.google.com
www.wikipedia.com
APPENDICES
A. ACTIVITY DIAGRAM
ADMINISTRATOR:
Register
Login
Fail
Success
Change
Password
Create
EMP
Remove
EMP
Logout
MODERATOR:
Add Project
Remove Project
Register
Login
Fail
Success
View
Emp details
Selecting
Team
Creating
Master plan
Logout
View
Doc, Proj
status
Conducting
Meetings
DATAFLOW DIAGRAM
LEVEL 0:
ADMINISTART
OR
AUTHOR
INSPECTION
TOOL
MODERATOR
INSPECTOR
LEVEL 1:
ADMINISTRATOR
E PROJECT
CREATE
EMP &
PROJEC
T
DOC
EVENT
AUTHOR
MODERATOR
INSPECTOR
LEVEL 2:
ADMINISTRATOR
CREATE
EMP &
PROJEC
T
DOC
AUTHO
R
EMP PROJECT
SELECT
TEAM
REMOVE
EMP &
PROJECT
MODERATOR
DEFECT
LOGGING
SHEET
INSPECTOR
CHAT
MEETING
CHAT
SCRIBE
INSPECT
DOC
CHAT
CHAT
C. USE-CASE DIAGRAM:
Login
Change
password
Created
Emp
Remove
Emp
Add
project
Admin
Remove
project
Logout
Login
View
profile
Selecting
inspection
team
Creating
master
plan
View
doocs
Moderator
Conduct
meetings
View proj
Status
View emp
details
Logout
ER-DIAGRAM:
LOGIN_TAB
Login
ID
Password
Login
CREATE_EMP_TAB
EMPID
Name
E-mail
Specialization
Grade
PROJECT_TAB
view
Rel-01
INSPECT_TEAM_TAB
EMPID
Proj_Name
Proj_code
Emp_Name
E-mail
Foreign_key_Index
Create_Emp_tab
View
Rel-01
A
D
M
I
N
I
ST
R
A
T
O
R
view
Proj_ID
Proj_Name
Author_Name
Proj_Doc
Rel-03
View
DEFECT_LOGGING
Proj_Name
Proj_doc
Defect_Severity
Defect_Class
Defect_root
Injected_phase
Defect_status
Desc
Foreign_key_Index
Project_Tab
SCREEN LAYOUT
Rel-02
HOME PAGE-login
Inspection Tool
HOME PAGE
Login:
User Id:
Password:
abhik
*******
Help
Login
ADMINISTRATOR PAGE
USER-SIGNUP
CREATE USER
CREATE PROJECT
USER DETAILS
PROJECT DETAILS
INSPECTION SCHEDULE
RAISE EXCEPTION
LOG SUGGESTION
LOG VIEW
REMOVE USER
REMOVE PROJECT