Professional Documents
Culture Documents
of Stop Goble
of Stop Goble
Page 1
the most catastrophic effects of global warming, others say it must be reached by 2030.
Zero waste is very important, but even more important is purchasing less, especially
things that have been shipped from long distances. Or if you have to buy something, if
possible buy from a thrift store or borrow from a friend. If you have access to a yard, grow
your own food.
The bottom line is to look at everything you do from a carbon footprint perspective.
Reduce your consumption of fossil fuels in every possible way, from less driving to shorter
showers to fewer airplane flights (vacation locally!). Install solar thermal panels on your roof
to heat your hot water plus solar electric PV panels to power your house, charge your electric
car, and send surplus electricity back into the grid.
1.2. SCOPE:
Global warming is the major issue in the present generation that are facing if it
continues then definitely the future generation cannot survive. For this we have to introduce
eco friendly interface between human and nature. For this it is one of the method to control
global warming we are creating the awareness to people by sending the reports weekly
monthly to the registered users. In this reports it includes how to save water, paper and natural
resources and also it tells the users how to use the natural resources scarce fully then the
future generations can make use of it. the registered users. In this reports it includes how to
save water, paper and natural resources and also it tells the users how to use the natural
resources scarce fully then the future generations can make use of it.
Page 2
3.
Collaborates with CPCB in organizing the training of persons to prevention and control of
water/air pollution and to organize mass education programs.
i)
ii)
technologies:
For instance Will the current printer be able to handle the new reports and forms required
for the new system?
OPERATIONAL FEASIBILITY:
Proposed projects are beneficial only if they can be turned into information systems
that will meet the organizations operating requirements. Simply stated, this test of feasibility
asks if the system will work when it is developed and installed. Are there major barriers to
Implementation? Here are questions that will help test the operational feasibility of a project:
Is there sufficient support for the project from management from users? If the current system
is well liked and used to the extent that persons will not be able to see reasons for change,
there may be resistance.
Are the current business methods acceptable to the user? If they are not, Users may welcome
a change that will bring about a more operational and useful systems.
Have the user been involved in the planning and development of the project?
Page 3
ECONOMIC FEASIBILITY:
Economic feasibility attempts 2 weigh the costs of developing and implementing a new
system, against the benefits that would occur from having the new system in place. This
feasibility study gives the top management the economic justification for the new system.
A simple economic analysis which gives the actual comparison of costs
and benefits are much more meaningful in this case. In addition, this proves to be a useful
point of reference to compare actual costs as the project progresses. There could be various
types of intangible benefits on account of automation. These could include increased
customer satisfaction, improvement in product quality better decision making timeliness of
information, expediting activities, improved accuracy of operations, better documentation and
record keeping, faster retrieval of information, better employee morale.
2.4.
SOFTWARE
AND
HARDWARE
REQUIREMENT
SPECFICATIONS:
SOFTWARE INTERFACE:
Client on internet
Client on intranet
Web server
Database server
End
HARDWARE INTERFACE:
Page 4
system(any)
CLIENT SIDE
INTERN
ET
EXPLOR
ER 6.0
PROC
ESSO
R
R
A
M
PENTI
UM II
AT
500
MHz
6
4
M
B
PENTI
UM III
AT 1
GHz
5
1
2
DI
S
K
SP
A
C
E
1
G
B
SERVER SIDE
WEB
SPHERE
APPLICA
TION
SERVER
V5.0
D
B
2
V
8.
1
PENTI
UM III
AT 1
GHz
M
B
5
1
2
M
B
2
G
B
J2EE:
Java
Platform,
Enterprise
Edition or Java
EE is a widely
1GB(EX
CLUDIN
G DATA
SIZE)
used platform
for
server
programming
in
the
Java
programming
language. The
Java platform (Enterprise Edition) differs from the Java Standard Edition Platform (Java SE)
in that it adds libraries which provide functionality to deploy fault-tolerant, distributed, multitier Java software, based largely on modular components running on an application server.
Web server WASCE: Web Sphere Application Server Community Edition (from now on
WASCE) is a free, certified Java EE 5 server for building and managing Java applications. It
is IBM's supported distribution of Apache Geronimo that uses Tomcat for servlet container
Page 5
and Axis 2 for web services. Over 15 WASCE developers are committers in the Apache
Geronimo project.
Development tool RAD:IBM Rational Application Developer for Web Sphere Software
(RAD) is an integrated development environment (IDE), made by IBM's Rational Software
division, for visually designing, constructing, testing, and deploying Web services, portals,
and Java (J2EE) applications.
Database platform DB2:DB2 Database is the database management system that delivers a
flexible and cost effective database platform to build robust on demand business applications
and supports the J2EE and web services standards.
2. Process: People, procedures, or devices that use or produce (Transform) Data. The
physical component is not identified.
Page 6
Page 7
System.
ARCHITECTURAL DIAGRAM:
Page 8
3.1.CLASS DIAGRAM:
Anonymous user
name : string
emailid : string
Member|Registeredu
ser
name : string
emailid : string
read()
mebershiprequest()
feedback()
download()
terminate()
gov/nongovsgencies
govt name : string
address : string
nongovname : string
generate reports()
distribute reports()
councelling()
Admin
admin name : string
unique id : number
view log()
update resources()
manage Group()
approve updates()
Page 9
read
ananymous user
use resources
membership request
read
member
use resources
feedback
terminate
Page 10
approve members
admin
view details
approve activity
update resources
Page 11
Page 12
4. Government/non-government agencies
MODULES DESCRIPTION:
1. Anonymous User:
i.
Read: He can read the information available and can access all the textual resources
ii.
iii.
2. Member:
i.
Login: A member can login or log out of his personal account using his unique id and
ii.
iii.
password.
Change: He can change the personal information provided to the website.
Terminate: He can terminate his membership anytime. A notification will be sent to the
iv.
v.
vi.
vii.
3. Administrator:
i.
Account: The administrator has the highest authority amongst all the actors that exist.
ii.
He gets the notifications regarding any new activity that happens over the website.
Manage members: Administrator has the rights to approve or disapprove any
iii.
membership request. He can keep a closed watch over all the members activities.
Administrator login: he can personally login and approve of the changes that are pending
iv.
his approval.
Manage groups: He can manage groups also, besides managing the individual accounts.
v.
vi.
requirements.
View all details: He can view all details about individual members, their email ids,
Page 13
addresses etc.
Account: They can maintain their individual accounts and can control activities over
ii.
iii.
Anonymo
us users
Display error
Page 14
Pollution
details
Manage pollution
Anti-pollution awareness
Page 15
Awareness
program
Control
pollution
Stop
global
View system
user
Page 16
Manage
system users
Create system
users
Update details
of users
View the list of system users in a role and view the details of roles, tasks and
Page 17
System user
Details of roles,
tasks.
To study Pollution
causes
Government
or non
government
agencies
To generate
Awareness
programs
To know Prevention
and controls
Pollution type
Page 18
service calls
Subject
Feedback
Anti-pollution activities
Display solutions
Page 19
In order to achieve consistency in the Testing style, it is imperative to have and follow a
set of testing principles. This enhances the efficiency of testing within SQA team
members and thus contributes to increased productivity. The purpose of this document is
to provide overview of the testing, plus the techniques.
At SDEI, 3 levels of software testing is done at various SDLC phases
Unit Testing: in which each unit (basic component) of the software is tested to verify that
the detailed design for the unit has been correctly implemented
Page 20
Beta testing comes after alpha testing. Versions of the software, known as beta versions,
are released to a limited audience outside of the company. The software is released to
groups of people so that further testing can ensure the product has few faults or bugs.
Sometimes, beta versions are made available to the open public to increase the feedback
field to a maximal number of future users.
It should be noted that although both Alpha and Beta are referred to as testing it is in fact
use emersion. The rigors that are applied are often unsystematic and many of the basic
tenets of testing process are not used. The Alpha and Beta period provides insight into
environmental and utilization conditions that can impact the software.
Regression testing: is used to refer the repetition of the earlier successful tests to ensure
that changes made in the software have not introduced new bugs/side effects.
Page 21
determine the appropriate outputs. This is analogous to testing nodes in a circuit, e.g. in-circuit
testing (ICT).
While white box testing can be applicable at
the unit, integration and system levels of the software testing process, it is usually done at the
unit level. It can test paths within a unit, paths between units during integration, and between
subsystems during a systemlevel test. Though this method of test design can uncover many
errors or problems, it might not detect unimplemented parts of the specification or missing
requirements.
White-box test design techniques include:
i.
ii.
iii.
iv.
White box testing is a test case design methods that uses the control structure of the
procedural design to derive test cases.
Testing cases in this testing are:
1. All the independent paths within the module have been executed at least once.
2. Exercise all logical decisions on their true and false sides,
3. Execute all loops at their boundaries and within their operational bounds.
4. Exercise internal data structure to ensure their validity.
Page 22
though usually functional. The test designer selects valid and invalid inputs and determines
the correct output. There is no knowledge of the test object's internal structure.
This
method
of
test
can
be
applied
to
all
levels
of
software
testing: unit, integration, system and acceptance. It typically comprises most if not all testing
at higher levels, but can also dominate unit testing as well.
Typical black-box test design techniques include:
Decision table testing
All-pairs testing
State transition tables
Equivalence partitioning
Boundary value analysis
Black box testing focuses on the functional requirements of the software. This testing finds
errors in the following categories.
1.
2.
3.
4.
5.
Types of Testing:
Smoke Testing: is the process of initial testing in which tester looks for the availability of all
the functionality of the application in order to perform detailed testing on them. (Main check
is for available forms)
Sanity Testing: is a type of testing that is conducted on an application initially to check for
the proper behaviour of an application that is to check all the functionality are available
before the detailed testing is conducted by on them.
Regression Testing: is one of the best and important testing. Regression testing is the process
in which the functionality, which is already tested before, is once again tested whenever some
new change is added in order to check whether the existing functionality remains same.
Re-Testing: is the process in which testing is performed on some functionality which is
already tested before to make sure that the defects are reproducible and to rule out the
environments issues if at all any defects are there.
Static Testing: is the testing, which is performed on an application when it is not been
executed. ex: GUI, Document Testing
Page 23
formal testing
where in test case document is used, with out that test case document testing can be done of
an application, to cover that testing of the future which are not covered in that test case
document. Also it is intended to perform GUI testing which may involve the cosmotic issues.
Page 24
Description
screen
must
contain
all
the
features
Check
for
the The
objects
as
per t
the validations
should
be
in
proper
way
T.C.No
Description
Expected
value
1
2
Page 25
Actual value
Result
T.C.No
Description
Expected
value
Try
to
modify Modification
date
and allow
time
2
Page 26
Actual value
Result
Page 27
Page 28
Page 29
Page 30
Page 31
WORK DONE:
CSE, MITS (2008-2012).
Page 32
The INDIAN WILDLIFE amusing website is successfully designed and is tested for accuracy and
quality.
During this project we have accomplished all the objectives and this project meets the needs of the
organization. The developed will be used in searching, retrieving and generating information for the
concerned requests.
GOALS
Reduced entry work.
Easy retrieval of information
Reduced errors due to human intervention
User friendly screens to enter the data
Portable and flexible for further enhancement
Web enabled.
Fast finding of information requested
Future Enhancements:
It is not possible to develop a system that makes all the requirements of the user. User requirements keep
changing as the system is being used. Some of the future enhancements that can be done to this system are:
Page 33
As the technology emerges, it is possible to upgrade the system and can be adaptable to desired
environment.
Because it is based on object-oriented design, any further changes can be easily adaptable.
Based on the future security issues, security can be improved using emerging technologies.
sub admin module can be added
An in-built web browser can be added
APENDIX:
I.
References:
Cay S. Hortsman
Gary Cornell
Cay S. Hortsman
Gary Cornell
Eric Freeman
OReilly SPD
Elisabeth Freeman
Thau
SPD
Page 34
Joshua Bloch
George Reese
OReilly SPD
Norman Richards
OReilly SPD
Sam Griffith
Page 35