Académique Documents
Professionnel Documents
Culture Documents
CONTENTS
Abstract
Abstract
1. DESIGN STRATEGY
1. INTRODUCTION
Architecture
of the System
Organizational
Profile
Data Flow Diagram
General
Overview of the Problem
Data Dictionary
Problem
Definition Diagram
Entity Relationship
Analysis
the Problem
SequenceofDiagram
Proposed
SequenceSolution
diagramStrategy
for insert
Sequence diagram for updating
2. SOFTWARE
REQUIREMENTS
Sequence
diagram for
view
SPECIFICATION
Sequence
diagram for deletion
Overall
Description
Class Diagram
Product Perspective
Product
Functions
2. IMPLEMENTATION
DETAILS
User
Characteristics
Pseudo
Code for each Subroutine
General Constraints
Specific
Requirements
3. RESULTS
AND DISCUSSION
External
Interface
Requirements
Testing
Functional Requirements
Non-functional
Requirements
4. FINAL USER
MANUAL
Performance
Requirements
Usage Manual
Design Constraints
5. SUMMARY AND CONCLUSION
3.
PROJECT
PLAN
Summary
of Achievements
Life
Cycle
Model Encountered
Main
difficulties
Team
Structure
& role
of member
Limitation
of the
Project
Resource
Requirements
Future Scope
of Work
Development Schedule
Cost6.Estimation
BIBLIOGRAPHY
Page No.
Page No.
24-33
1-6 25
2 26
5 27
5 28
6
6 29
30
7-14 31
32
8 33
8
9 34-50
10
10 51-54
10 52
12
13 55-61
14 56
15-2362-64
16 63
19 63
20 64
21 64
22
65
Introduction:A Smarter Work Management system can be much larger and more
powerful given the combined capabilities of the management
components, than combinations of stand-alone systems. It is most
reliable database. It is named as smarter because IBM has taken such
initiatives of doing things using smart grids. This is a difficult goal to
achieve because of the complexity of the interactions between
simultaneously running components Utilities throughout the world
have invested hundreds of millions of dollars over the last few
decades to deploy Automatic Meter Reading (AMR) systems to
collect billing information from electricity, gas and water meters.
More recently, utilities have begun to invest comparable amounts in
deploying Advanced Meter Infrastructure (AMI) systems that can
send more flexible Time of Use (TOU) metering data to the utility's
data center a good step toward a smarter grid. While useful, both
systems are single-application systems that were not designed with the
idea of being integrated with other devices and applications to deliver
the information needed to build a smarter smart grid. Replacing these
solutions before the end of their useful life is usually not an option.
Without a way to integrate the useful information from these systems
into the next-generation smart grid infrastructure, some utilities are
considering delaying or scaling back their smart grid plans.
All the state capitals have mini computers. Each of the district
computer centers has a super AT systems for providing services to
the district administration as well as gathering information on
monitoring scheme and other socio-economic data required by the
State Planning Agencies and for the decision support to the Central
Government. All problems are analyzed in-depth and careful
system studies are carried out and appropriate computer based
information system are designed, developed and implemented for
the user.
IBM ACE provides services to the user departments through a
number of application divisions, which are responsible for
conducting feasibility study in the user department, creating
appropriate information system for providing awareness on the
usage of computer as a tool for decision support and developing
Management Information System. These divisions are organized in
the following sectors: Finance, Financial Recourses, Industry,
Commerce, Natural Resources, Energy, Health, Urban and Rural
Development, Socio-Economic, Planning, etc.
System for
1.4 Analysis of the Problem:ABC Corp involves 10,000 employees across cities for doing
banking jobs.Presently the employees of the company increased to
20,000.So it becomes harder to maintain all the records of the
employee which is time consuming and requires lot of manpower.
1.5 Proposed Solution Strategy:Here the user has to provide his/her username and password at the
login fields.If that matches then the use can submit his working
hours daily and the total working hours is calculated and stored in
the database.It doesnot match then then the use does the sign
up/registration and gets a userid.
Email template:-
Registartion template:-
2.SOFTWARE REQUIREMENT
SPECIFICATION
2.1 Overall Description:2.1.1 Product Perspective:The product is aimed towards a heavy industry having a large no
of employees which can upgrade its database storing facilities of
the employees working details efficiency so that it can send the
meter reading with consumer id and to the MQ so that SWMS can
fetch the messages from the MQ.
SWMS is intended to be not a stand-alone product and should
depend on the availability of other software like if the MQ fails
then entire system will collapse. It should run on both UNIX and
Windows based platform.
ii)
iii)
server
2.2.1 External Interfaces Requirements:Their preferred application server is Websphere application server and
Websphere MQ for message oriented middleware. They use IBM DB2
for RDBMS.
2.2.2 Functional Requirements:The SWMS should process the incoming information based on
the employee working hours and store in the database for the
respective customers.
Interface Details
User login
SWMS
Result
Displayed
Table of requirement
Flow
and
store
in
the
to
provide
the
The following are the NFRs that ABC sets as an expectation: The system should be 24X7 but can have planned outages.
The system should capable of handling 500 user / second.
2.2.5.2
2.2.5.3
Websphere
Application Server, MQ server, and DB2.
2.2.5.4
2.2.5.5
displays
with the WAS application engine.
2.2.5.6
supplied by
the application.
2.2.5.7 The application require an Internet connection to email
the billing informations to the consumer.
2.2.5.8
user
saved as
a separate Win32 DLL file.
2.2.5.10 The control module that the WAS executable calls,
and
controls the database processing and file generation
shall
be implemented and saved as a separate Win32DLL
file.
2.2.5.11 All programming logic and processing shall be
implemented using WAS.
2.2.5.12 HTML generation module shall be implemented using
Dreamweaver, saved as a separate Win32 DLL file.
2.2.5.13 No error condition shall cause the application to exit
prematurely.
3. Project Model
Life cycle model :A life cycle model forms a common understanding of the activities
among the software engineers and helps develop software in a
systematic and disciplined manner. Other advantages of a
documented life cycle model are that it enhances the understanding
of the process among the developers and mandates the software
development organization to accurate define every activity in the
life cycle.
A structured sequence of phases for implementing an information
system is system design life cycle of that system. The various steps
involved in the system design life cycle are as follows: Feasibility study: (Evaluation of existing system and procedures analysis of
alternative candidate systems cost estimation)
The feasibility study is a formal proposal for a new system. Before
the project is to begin, the project is studied to determine what
exactly the user wants depending upon the result of initial
investigation. The survey is expanded to more detailed study.
Feasibility study can be understood by giving the answer/solution
of the requirements: -
Integration and System Testing :Integration is normally carried out incrementally over a number of
steps. During each integration step, the partially integrated system
is tested and set a previously planned modules are added to it.
Finally, when all the modules have been successfully integrated
and tested, system testing is carried out.
Maintenance :Apart from the bugs, the programmer has to maintain the program
he /she have created. Program maintenance is a term used for the
updating of a program after the program after the program is put
into use. This updating may be a result of the users request or a
change in the way the program needs to operate.
members are :
Sukumar Behera
Bikash Kumar Rath
Manoranjan Mahallick
Hrishikesh Mohapatra
Partha Sarathi Pati
Debaranjan Pradhan
The roles are :
Manoranjan : Create HTML page.
Hrishikesh : Class diagram, DFD,ER-diagram, Usecase diagram
Debaranjan And Partha : Documentation.
Sukumar And Bikash : Coding Using Java and Database
Scenario
Developing
case
&
Use
UML
related activites
Development
Product
IBM
Rational
Description
All the UML
Software Modeler,
specs
(RSM)
developed
IBM
only.
The
Rational
related
needs
to
using
development
be
RSM
of
Application
Java/J2EE
Developer(RAD)
should be on RAD or
OR
WID only
WebSphere
artifacts
Integration
Database
Developer (WID)
IBM DB2 V 8.1 or
For
higher
all
the
DB
IBM
ClearCase
Rational
only
The project team should
share
there
between
them
artifacts
using
1.
DESIGN STRATEGY
Final DFD:-
CONSUMER DETAIL:-
Column name
Username
Data type
VarChar
Size
Null
95
Description
Not null,
Primary key
Password
Weekdays
Varchar
Varchar
98
48
Not null
Not null
To calculate
Total Hrs
Mupdateservlet
Viewservlet
consumer_id
password
customer_id
password
update_mail_id()
Customer registration
Pupdateservlet
Aupdateservlet
consumer_id
password
consumer_id
password
update_password()
update_addrs()
Password update
Update mail-id
Address update
delete account
8.2 Future Scope of Work:This project can be improved to one more step to make it more
efficient and more userfriendly.
9. BIBLIOGRAPHY
WebSphere MQ on Developer Workshttp://www.ibm.com/developerworks/websphere/zones/busi
nessintegration/wmq.html
WebSphere Application Server on Developer Workshttp://www.ibm.com/developerworks/websphere/zones/was/
Rational Application Developer for WebSphere Softwarehttp://www.ibm.com/developerworks/rational/products/rad/
Rational Modelerhttp://www.ibm.com/developerworks/rational/products/mod
eler/
Rational Clear Casehttp://www.ibm.com/developerworks/rational/products/clear
case/
WebSphere Integration Developerhttp://www.ibm.com/developerworks/websphere/zones/busi
nessintegration/wps/wps.html
IBM DB2http://www.ibm.com/developerworks/data/products/db2/inde
x.html?S_TACT=105AGX11&S_CMP=FP