AUTOMATED GREETING SYSTEM

PROJECT REPORT

Submitted by

MOHD AFZAL JEELANI

(1400118073)
&
MOHD FAISAL
(1400118083)
in partial fulfillment for the award of the degree
of
Bachelor of Computer Application

INTEGRAL UNIVERSITY LUCKNOW

MAY 2017

1
 INTEGRAL UNIVERSITY LUCKNOW

CERTIFICATE

Certified that this project report “ AUTOMATED GREETING SYSTEM ” is the

bonafide work of “ MOHD AFZAL JEELANI & MOHD FAISAL ” who carried out
the project work under my supervision.

Mr. Arshad Ali

Assistant Professor
Department of Computer Application
Integral University , Lucknow

2
 INTEGRAL UNIVERSITY LUCKNOW

CERTIFICATE

Certified that this report “ AUTOMATED GREETING SYSTEM ” is the bonafide

work of “ MOHD AFZAL JEELANI & MOHD FAISAL ” who have successfully
carried out the project.

Mr. Mohd Faisal Dr. Mohd Faizan Farooqui

Project Coordinator Head
Department of Computer Applications Department of Computer Applications
Integral University, Lucknow Integral University, Lucknow

3
 DECLARATION

“ I hereby declare that this submission is my own work and that, to the best of my
knowledge and belief, it contains no material previously published or written by another
person nor material which has beenaccepted for the award of any other degree or
diploma of the university or other institute of higher learning, except where due
acknowledgement has been made in the text ”

Date …..................................
MOHD AFZAL JEELANI

…...................................
MOHD FAISAL

4
 ACKNOWLEDGEMENT

It give me great pleasure to present before you my final year project report on
“ AUTOMATED GREETING SYSTEM ” strictly under the guidance of
Mr. ARSHAD ALI. He had made sincere efforts to make the final year project
more meaningfull, complete, compact and comprehensive. It's a great pleasure to
you know that I have put my feeling into practice.
At last we give our special thanks to our batch mates for all the valuable
support.

THANK YOU

5
 Table of Contents

Sr.no. Topics Page

No.
1 Abstract 7
2 Chapters
2.1 Introduction 8
2.2 Hardware & Software Requirement 15
2.3 Discription of Software Specification
2.4 Problem Identification 16
2.5 System Analysis & User Requirement
2.6 Feasibility Study 19
2.7 System Planinning
2.8 Designing 22
2.9 Testing 23
3 Review of Previous work 28
4 Proposed Work 29
41 Data flow Diagram 30
42 Contex Diagram
4.3 Flow Chart
4.4 ER Diagram 32
4.5 Snapshot 37
5 Charts 47
5.1 Gantt Chart

5.2 Pert Chart

6 Conclusion & Future Scope 49

7 Reference

8 Bio Data of Group Member 50

6
 ABSTRACT

The project automated greeting system concerns with development of a system that is
simple and easy to use yet a powerful web application for greeting, greetinging on
Intranet/internet in a secure environment. By using this Greeting system users can send
the greetinges and greeting toTheir friends and known people. They can send the
greeting Through this system any time, at the greetinged date the Greetinges will send
by the application.Login id and password will be given to the user by the admin. As the
user logs into the system a home page will be displayed. Here the user can view
Remainder option. When the user clicks on the remainder option a new windows form is
opened. They can send the greeting Through this system any time, at the greetinged date
the Greetinges will send by the application.

7
 INTRODUCTION

ABOUT PROJECT

The project Automated Greeting System concerns with development of a system that is
simple and easy to use yet a powerful web application for greeting, Greetinging on
intranet/internet in a secure environment.
By using this Greeting System users can send the Greetinges and greeting to their
friends and known people. They can send the Greeting through this system any time, at
the Greetinged date the Greetinges will send by the application. This project is just the
purpose of fun and also acts as a remainder. Login id and password will be given to the
user by the admin. As the user logs into the system a home page will be displayed. Here
the user can view Remainder option. When the user clicks on the remainder option a
new windows form is opened. The user can enter the date as he/ she has to be reminded
every yearn name of the occasion saying it’s a birthday or a wedding anniversary or
anything you Greeting and the time to be reminded must be entered. During the date of
the occasion, a notification will be sent to the mail ID or to the system.

8
 INTRODUCTION TO TECHNOLOGY

INTRODUCTION TO JAVA

Java is an object-oriented programming language with a built-in application

programming interface (API) that can handle graphics and user interfaces and that can
be used to create applications or applets. Because of its rich set of API's, similar to
Macintosh and Windows, and its platform independence, Java can also be thought of as
a platform in itself. Java also has standard libraries for doing mathematics.

Much of the syntax of Java is the same as C and C++. One major difference is that Java
does not have pointers. However, the biggest difference is that you must write object
oriented code in Java. Procedural pieces of code can only be embedded in objects. In the
following we assume that the reader has some familiarity with a programming language.
In particular, some familiarity with the syntax of C/C++ is useful.

In Java we distinguish between applications, which are programs that perform the same
functions as those written in other programming languages, and applets, which are
programs that can be embedded in a Web page and accessed over the Internet. Our initial
focus will be on writing applications. When a program is compiled, a byte code is
produced that can be read and executed by any platform that can run Java.

Characteristics of Java

The target of Java is to write a program once and then run this program on multiple
operating systems.

Java has the following properties:

Platform independent: Java programs use the Java virtual machine as abstraction and do
not access the operating system directly. This makes Java programs highly portable. A
Java program which is standard complaint and follows certain rules can run unmodified
on all supported platforms, e.g. Windows or Linux. Object-orientated programming
language: Except the primitive data types, all elements in Java are objects. Strongly-
typed programming language: Java is strongly-typed, e.g. the types of the used variables
must be pre-defined and conversion to other objects is relatively strict, e.g. must be done
in most cases by the programmer. Interpreted and compiled language: Java source code
is transferred into the bytecode format which does not depend on the target platform.
These bytecode instructions will be interpreted by the Java Virtual machine (JVM). The
JVM contains a so called Hotspot-Compiler which translates performance critical
bytecode instructions into native code instructions. 9
  Automatic memory management: Java manages the memory allocation and de-
allocation for creating new objects. The program does not have direct access to
the memory. The so-called garbage collector deletes automatically objects to
which no active pointer exists.

JavaServer Pages
JavaServer Pages (JSP) is a technology that helps software developers create
dynamically generated web pages based on HTML, XML, or other document types.
Released in 1999 by Sun Microsystems,[1] JSP is similar to PHP, but it uses the Java
programming language.

To deploy and run JavaServer Pages, a compatible web server with a servlet container,
such as Apache Tomcat or Jetty, is required.

Architecturally, JSP may be viewed as a high-level abstraction of Java servlets. JSPs are
translated into servlets at runtime; each JSP's servlet is cached and re-used until the
original JSP is modified.

JSP can be used independently or as the view component of a server-side model–view–

controller design, normally with JavaBeans as the model and Java servlets (or a
framework such as Apache Struts) as the controller. This is a type of Model 2
architecture.

JSP allows Java code and certain pre-defined actions to be interleaved with static web
markup content, with the resulting page being compiled and executed on the server to
deliver a document. The compiled pages, as well as any dependent Java libraries, use
Java bytecode rather than a native software format. Like any other Java program, they
must be executed within a Java virtual machine (JVM) that integrates with the server's
host operating system to provide an abstract platform-neutral environment.

JSPs are usually used to deliver HTML and XML documents, but through the use of
OutputStream, they can deliver other types of data as well.[4]

The Web container creates JSP implicit objects like pageContext, servletContext,
session, request & response.

10
INTRODUCTION TO JAVA SERVLETS
Java Servlets are server side Java programs that require either a Web Server or an
Application Server for execution. Examples for Web Servers include Apache?s Tomcat
Server and Macromedia?s JRun. Web Servers include IBM?s Weblogic and BEA?s
Websphere server. Examples for other Server programs include Java Server Pages (JSPs)
and Enterprise Java Beans (EJBs). In the forthcoming sections, we will get acquainted
with Servlet fundamentals and other associated information required for creating and
executing Java Servlets.

Basic Servlet Structure

As seen earlier, Java servlets are server side programs or to be more specific; web
applications that run on servers that comply HTTP protocol. The javax.servlet and
javax.servlet.http packages provide the necessary interfaces and classes to work
with servlets. Servlets generally extend the HttpServlet class and override the
doGet or the doPost methods. In addition, other methods such as init, service and
destroy also called as life cycle methods might be used which will be discussed in
the following section.

A Servlet?s Life Cycle

The first time a servlet is invoked, it is the init method which is called. And remember
that this is called only once during the lifetime of a servlet. So, you can put all your
initialization code here. This method next calls the service method. The service method
in turn calls the doGet or doPost methods (whichever the user has overridden). Finally,
the servlet calls the destroy method. It is in a sense equivalent to the finally method. You
can reset or close references / connections done earlier in the servlet?s methods (e.g. init,
service or doGet /doPost). After this method is called, the servlet ceases to exist for all
practical purposes. However, please note that it is not mandatory to override all these
methods. More often than not, it is the doGet or doPost method used with one or more of
the other life cycle methods.

11
MYSQL
MySQL is (as of 2008) the world's most widely used open source relational database
management system (RDBMS) that runs as a server providing multi-user access to a
number of databases. It is named after co-founder Michael Widenius' daughter, My. The
SQL phrase stands for Structured Query Language.

The MySQL development project has made its source code available under the terms of
the GNU General Public License, as well as under a variety of proprietary agreements.
MySQL was owned and sponsored by a single for-profit firm, the Swedish company
MySQL AB, now owned by Oracle Corporation.

MySQL is a popular choice of database for use in web applications, and is a central
component of the widely used LAMP open source web application software stack (and
other 'AMP' stacks). LAMP is an acronym for "Linux, Apache, MySQL,
Perl/PHP/Python." Free-software-open source projects that require a full-featured
database management system often use MySQL.

MySQL is a relational database management system (RDBMS), and ships with no GUI
tools to administer MySQL databases or manage data contained within the databases.
Users may use the included command line tools,or use MySQL "front-ends", desktop
software and web applications that create and manage MySQL databases, build database
structures, back up data, inspect status, and work with data records. The official set of
MySQL front-end tools, MySQL Workbench is actively developed by Oracle, and is
freely available for use.

Command line
MySQL ships with many command line tools, from which the main interface is 'mysql'
client. Third-parties have also developed tools to manage, optimize, monitor and backup
a MySQL server, some listed below. All these tools work on *NIX type operating
systems, and some of them also on Windows.

 Maatkit - a cross-platform toolkit for MySQL, mercached and , developed in

Perl. Maatkit can be used to prove replication is working correctly, fix corrupted
data, automate repetitive tasks, and speed up servers. Maatkit is included with
several GNU/Linux distributions such as CentOS and Debian and packages are
available for Fedora and Ubuntu as well. As of late 2011, Maatkit is no longer
developed, but Percona has continued development under the Percona Toolkit
brand.

12
  XtraBackup - Open Source MySQL hot backup software. Some notable features
include hot, non-locking backups for InnoDB storage, incremental backups,
streaming, parallel-compressed backups, throttling based on the number of IO
operations per second, etc.[30]

 MySQL::Replication - a replacement for MySQL's built-in replication, developed

in Perl. MySQL::Replication can be used to create a peer-to-peer, multi-master
MySQL replication network.

NETBEANS

NetBeans is an open-source project dedicated to providing rock solid software

development products (the NetBeans IDE and the NetBeans Platform) that address the
needs of developers, users and the businesses who rely on NetBeans as a basis for their
products.

In June 2000, NetBeans was made open source by Sun Microsystems, which remained
the project sponsor until January 2010 when Sun Microsystems became a subsidiary of
Oracle. Please see our History section for more information.

The two base products, the NetBeans IDE and NetBeans Platform, are free for
commercial and non-commercial use. The source code to both is available to anyone to
reuse as they see fit, within the terms of use. The legal section contains information
regarding licensing, copyright issues, privacy policy and terms of use. Complete product
information can be found in the Products section.

The NetBeans project is also a vibrant community where people from across the globe
can ask questions, give advice, make various contributions, and ultimately share in the
success of our products. On our mailing lists and forums, you will find posts from
students, developers from top companies, and individuals looking to expand their skills.

With over 18 million downloads of the NetBeans IDE to date, and over 800,000
participating developers, the NetBeans project is thriving and continues to grow, thanks
to the individuals and partner companies. To be a part of the community, simply register
for free.

13
HARDWARE AND SOFTWARE REQUIREMENT

The Following are the Minimum Hardware and Software requirement to run the
proposed system.

Minimum Hardware Requirement:

1. Processor : Intel Core Processor 3

2. RAM : 128 MB

3.Keyboard/Mouse : Compatible

4. Monitor : Compatible

MINIMUM SOFTWARE REQUIREMENT:

SERVER SYSTEM

1. Operating System : Windows 2000 SERVER

2. Software for system : a) NetBeans IDE 8.0-windows

b) Apache Tomcat7.0.50

CLIENT SYSTEM

1. Operating System : Windows 7and later versions

2. Software for system : a) Internet Explorer

b) Google Chrome

c) Mozilla Firefox

14
PROBLEM STATEMENT

Existing system:

1) This existing system is not providing secure registration and profile management of
all the users properly.

2) This system is not providing on-line help.

3) This system doesn’t provide tracking of users activities and their progress.

4) This manual system gives us very less security for saving data and some data may be
lost due to mismanagement.

5) This system is not providing the storage information for the users.

6) The existing system is not providing on date greeting technique.

7) The existing system not providing specific types of greetinging opportunity.

15
REQUIREMENT ANALYSIS

Systems analysis is the study of sets of interacting entities, including computer systems
analysis. This field is closely related to requirements analysis or operations research. It
is also "an explicit formal inquiry carried out to help someone (referred to as the
decision maker) identify a better course of action and make a better decision than he
might otherwise have made.
System development can generally be thought of having two major components:
systems analysis and systems design. In System Analysis more emphasis is given to
understanding the details of an existing system or a proposed one and then deciding
whether the proposed system is desirable or not and whether the existing system needs
improvements. Thus, system analysis is the process of investigating a system,
identifying problems, and using the information to recommend improvements to the
system.

DISADVANTAGES OF OLD SYSTEM

As we know the manual processing is quite tedious, time consuming, less accurate in
comparison to computerized processing. Obviously the present system is not is
exception consultant encountering all the above problems.

1) This existing system is not providing secure registration and profile management of
all the users properly.

2) This system is not providing on-line help.

3) This system doesn’t provide tracking of users activities and their progress.

4) This manual system gives us very less security for saving data and some data may be
lost due to mismanagement.

5) This system is not providing the storage information for the users.

6) The existing system is not providing on date greeting technique.

7) The existing system not providing specific types of greetinging opportunity.

16
ADVANTAGES OF NEW SYSTEM

In new computerized system I tried to give these facilities.

1.The development of this new system contains the following activities, which try to
automate the entire process keeping in the view of database integration approach.

2. This system maintains userâ„¢s personal, address, and contact details.

3. User friendliness is provided in the application with various controls provided by

system rich user interface.

4. Various classes have been used for maintain the details of all the users and catalog.

5. Authentication is provided for this application only registered users can access.

6. The users information can be stored in centralized database which can be maintained
by the system.

7. The system provides the users to send Greetinges through application any time.

8. The system providing the facility for the users they can send Greetinges any time or
any date. The Greeting mail is sends to the receiver on the particular day only.

9. The user can controls the authentication of their mails management provided by this
system.

10. The system is providing accessibility to the administrator to control all the user
information.

17
FEASIBILITY STUDY

All projects are feasible given unlimited resources and infinite time! Unfortunately, the
development of computer based system is more likely to be plagued by a scarcity of
resources and difficult delivery dates. It is both necessary and prudent to evaluate the
feasibility of the project at the earliest possible time. Months or years of effort, Money
loss and untold professional embarrassment can be averted I few better understand the
project at its study time.
This type of study determines if an application can and should be developed. Once it
has been determining that, application is feasible. After that analyst can go ahead and
prepares the project specification, which finalizes project requirements. Feasibility
studies are undertaken within tight time constraints.

1. Technical Feasibility

2. Operational Feasibility

3. Economic Feasibility

4. Legal Feasibility

TECHNICAL FEASIBILITY
As we know the technical feasibility is concerned with specifying equipment and
software that will successfully satisfy the user requirement. The technical needs of the
system may vary considerably, but might include:
 The facility to produce outputs of advertisements, shopping and mailing in a given
time for ease of use.
 Response time under certain condition is minimal.
 Ability to process a certain volume of transaction at a particular speed.

18
 Facility to communicate data to distinct location.
In examining the technical feasibility, configuration of the system is given more
importance than the actual make of hardware. The configuration should give the
complete picture about the system’s requirements- how many workstations are required,
how these units are interconnected so that they could operate and communicate
smoothly.

OPERATIONAL FEASIBILITY
Proposed projects are beneficial only if they can be turned into information system that
will meet the financial management requirements of the business/organization. This test
of feasibility asks if the system will work when it developed and installed. Are there
major barriers to implementation?
Some of the important questions that are useful to test the operational feasibility of a
project are given below:
 Is there sufficient support for the project from the implementation? From user? If the
present 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 current business methods acceptable to the user? If they are not, user may
welcome a change that will bring about a more operational and useful system
 Have the user been involved in the planning and development of the Project? If they
are involved at the earliest stage of project development, the chances of resistance can
be possibly reduced.
 Will the proposed system cause harm? Will it produce poorer result in any case or
area?
 Will the performance of staff member fall down after implementation? Issue that
 Appears to be quite minor at the early stage can grow into major problem after
Implementation.
19
ECONOMICAL FEASIBILITY
Economic analysis is the most frequently used technique for evaluating the effectiveness
of the proposed system. More commonly known as cost/benefits analysis, the procedure
is to determine the benefits and savings that are expected from the purposed system and
compared with costs.
If benefits outweigh cost, a decision is taken to design and implement the system.
Otherwise, further justification or alternative of the proposed system will have to be
made if it has a chance of being approved. This is an ongoing effort that improves in
accuracy at each phase of the system life cycle. The analysis part also clears the doubt of
economic problems which could be possible in developing the system. As already
mentioned that the company has to just pay the developed software cost and not other
investment is needed at the time of implementation of the new system as the preliminary
requirements already exist in the company.

LEGAL FEASIBILITY

In the legal feasibility is necessary to check that the software we are going to develop is
legally correct which means that the ideas which we have taken for the proposed system
will be legally implemented or not so , it is also an important step in feasibility study.

20
SYSTEM DESIGN

Systems design is the process of defining the architecture, components, modules,

interfaces, and data for a system to satisfy specified requirements. One could see it as
the application of systems theory to product development. There is some overlap with
the disciplines of systems analysis, systems architecture and systems engineering. If the
broader topic of product development "blends the perspective of marketing, design, and
manufacturing into a single approach to product development," then design is the act of
taking the marketing information and creating the design of the product to be
manufactured. Systems design is therefore the process of defining and developing
systems to satisfy specified requirements of the user. Until the 1990s systems design had
a crucial and respected role in the data processing industry. In the 1990s standardization
of hardware and software resulted in the ability to build modular systems. The
increasing importance of software running on generic platforms has enhanced the
discipline of software engineering. Object-oriented analysis and design methods are
becoming the most widely used methods for computer systems design. The UML has
become the standard language in objectoriented analysis and design. It is widely used for
modeling software systems and is increasingly used for high designing non-software
systems and organizations

21
TESTING

OBJECTIVE OF TESTING

Software testing is an investigation conducted to provide stakeholders with information

about the quality of the product or service under test. Software testing can also provide
an objective, independent view of the software to allow the business to appreciate and
understand the risks of software implementation. Test techniques include, but are not
limited to, the process of executing a program or application with the intent of finding
software bugs (errors or other defects). Software testing can be stated as the process of
validating and verifying that a software program/application/product:
1. meets the requirements that guided its design and development;
2. works as expected; and
3. can be implemented with the same characteristics.
Software testing, depending on the testing method employed, can be implemented at any
time in the development process. However, most of the test effort traditionally occurs
after the requirements have been defined and the coding process has been completed
having been shown that fixing a bug is less expensive when found earlier in the
development process. Although in the Agile approaches most of the test effort is,
conversely, on-going. As such, the methodology of the test is governed by the software
development methodology adopted.
Different software development models will focus the test effort at different points in the
development process. Newer development models, such as Agile, often employ test
driven development and place an increased portion of the testing in the hands of the
developer, before it reaches a formal team of testers. In a more traditional model, most
of the test execution occurs after the requirements have been defined and the coding
process has been completed. Testing can never completely identify all the defects within
software. Instead, it furnishes a criticism or comparison that compares the state and
behavior of the product against oracles—principles or mechanisms by which someone
might recognize a problem. These oracles may include (but are not limited to)
specifications, contracts, comparable products, past versions of the same product,
inferences about intended or expected purpose, user or customer expectations, relevant
standards, applicable laws, or other criteria.
Every software product has a target audience. For example, the audience for video game
software is completely different from banking software. Therefore, when an organization
develops or otherwise invests in a software product, it can assess whether the software
product will be acceptable to its end users, its target audience, its purchasers, and other
stakeholders. Software testing is the process of attempting to make this assessment.

22
TYPES OF TESTING

TESTING

Testing Techniques Used we will continuously test our project to insure thet it is fully
functional. In order to perform testing test cases are designed with the intent of finding
the errors in the project and help in removing those errors. Testing begins at the module
level and is conducted systmatically . It is generally conducted by independent test
groups or third party.
Testing is done in our project remort controlling PC with help of black box testing that
exrcise all the functional requirement of the project test cases are designed using this
approaches by providing set of inoput conditions to get the expected output.

Black Box Testing

Black-box testing treats the software as a "black box"—without any knowledge of

internal implementation. Black-box testing methods include: equivalence partitioning,
boundary value analysis, all-pairs testing, fuzz testing, model-based testing, exploratory
testing and specification-based testing.

 Specification-based testing: Specification-based testing aims to test the functionality

of software according to the applicable requirements. Thus, the tester inputs data into,
and only sees the output from, the test object.
This level of testing usually requires thorough test cases to be provided to the tester, who
then can simply verify that for a given input, the output value (or behavior), either "is"
or "is not" the same as the expected value specified in the test case. Specification-based
testing is necessary, but it is insufficient to guard against certain risks.

 Advantages and disadvantages: The black-box tester has no "bonds" with the code,
and a tester's perception is very simple: a code must have bugs. Using the principle,
"Ask and you shall receive," black-box testers find bugs where programmers do not. On
the other hand, black-box testing has been said to be "like a walk in a dark labyrinth
without a flashlight," because the tester doesn't know how the software being tested was
actually constructed. As a result, there are situations when (1) a tester writes many test
cases to check something that could have been tested by only one test case, and/or (2)
some parts of the back-end are not tested at all.
Therefore, black-box testing has the advantage of "an unaffiliated opinion", on the one
hand, and the disadvantage of "blind exploring", on the other

23
WHITE BOX TESTING

White-box testing is when the tester has access to the internal data structures and
algorithms including the code that implements these.
Types of white-box testing
The following types of white-box testing exist:

 API testing (application programming interface) - testing of the application using

public and private APIs

 Code coverage - creating tests to satisfy some criteria of code coverage (e.g., the test
designer can create tests to cause all statements in the program to be executed at least
once)

 Fault injection methods - improving the coverage of a test by introducing faults to test
code paths

 Mutation testing methods

 Static testing - All types

Test coverage
White-box testing methods can also be used to evaluate the completeness of a test suite
that was created with black-box testing methods. This allows the software team to
examine parts of a system that are rarely tested and ensures that the most important
function points have been tested.
Two common forms of code coverage are:

 Function coverage, which reports on functions executed

 Statement coverage, which reports on the number of lines executed to complete the
test they both return a code coverage metric, measured as a percentage.

FUNCTIONAL TESTING

 Functional testing refers to activities that verify a specific action or function of the
code. These are usually found in the code requirements documentation, although some
development methodologies work from use cases or user stories. Functional tests tend to
answer the question of "can the user do this" or "does this particular feature work."

24
 Non-functional testing refers to aspects of the software that may not be related to a
specific function or user action, such as scalability or other performance, behavior under
certain constraints, or security. Testing will determine the flake point, the point at which
extremes of scalability or performance leads to unstable execution. Non-functional
requirements tend to be those that reflect the quality of the product, particularly in the
context of the suitability perspective of its users.

SYSTEM TESTING

 System testing of software or hardware is testing conducted on a complete, integrated

system to evaluate the system's compliance with its specified requirements. System
testing falls within the scope of black box testing, and as such, should require no
knowledge of the inner design of the code or logic.

 As a rule, system testing takes, as its input, all of the "integrated" software
components that have successfully passed integration testing and also the software
system itself integrated with any applicable hardware system(s). The purpose of
integration testing is to detect any inconsistencies between the software units that are
integrated together (called assemblages) or between any of the assemblages and the
hardware. System testing is a more limited type of testing; it seeks to detect defects both
within the "interassemblages" and also within the system as a whole.

VARIOUS LEVEL OF TESTING

Before implementation the system is tested at two levels:
Level 1
Level 2

LEVEL 1 TESTING (ALPHA TESTING)

Alpha testing is simulated or actual operational testing by potential users/customers or

an independent test team at the developers' site. Alpha testing is often employed for off-
theshelf software as a form of internal acceptance testing, before the software goes to
beta testing.
LEVEL 2 TESTING (BETA TESTING)

Beta testing comes after alpha testing and can be considered a form of external user
acceptance testing. Versions of the software, known as beta versions, are released to a
limited audience outside of the programming team. 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.
25
REVIEW OF PREVIOUS WORK

Automated Greeting System concerns with the development of a system that is simple
and easy to use yet a powerful web application for greeting, Greetinging on
intranet/internet in a secure environment.
By using this Greeting System users can send the Greetinges and greeting to their
friends and know people. They can send the Greeting through this system any time, at
the Greetinged date the Greetinges will send by this application.

OBJECTIVES

EXISTING SYSTEM:

1.This existing system is not providing secure registration and profile management of all
the users properly.

2.This system is not providing on-line Help.

3.This system does not provide tracking of users activities and their progress.

4.This manual system gives us very less security for saving data and some data may be
lost due to mismanagement.

5.This system is not providing email over the internet.

6.This system is not providing the storage information for the users.

7.The existing system is not providing on date Greeting technique.

8.The existing system not providing specific types of Greetinging opportunity.

26
PROPOSED SYSTEM

In new computerized system I tried to give these facilities.

1.The development of this new system contains the following activities, which try to
automate the entire process keeping in the view of database integration approach.

2. This system maintains userâ„¢s personal, address, and contact details.

3. User friendliness is provided in the application with various controls provided by

system rich user interface.

4. Various classes have been used for maintain the details of all the users and catalog.

5. Authentication is provided for this application only registered users can access.

6. The users information can be stored in centralized database which can be maintained
by the system.

7. The system provides the users to send Greetinges through application any time.

8. The system providing the facility for the users they can send Greetinges any time or
any date. The Greeting mail is sends to the receiver on the particular day only.

9. The user can controls the authentication of their mails management provided by this
system.

10. The system is providing accessibility to the administrator to control all the user
information.

27
DATA FLOW DIAGRAM

A Data Flow Diagram (DFD) is a graphical representation of the "flow" of data

through an nformation system, modelling its process aspects. A DFD is often used as a
preliminary step to create an overview of the system, which can later be
elaborated.DFDs can also be used for the visualization of data processing (structured
design).
A DFD shows what kind of information will be input to and output from the system,
where the data will come from and go to, and where the data will be stored. It does not
show information about the timing of process or information about whether processes
will operate in sequence or in parallel (which is shown on a flowchart). Data flow
diagrams were proposed by Larry Constantine, the original developer of structured
design, based on Martin and Estrin's "Data Flow Graph" model of computation. Starting
in the 1970s, data flow diagrams (DFD) became a popular way to visualize the major
steps and data involved in software system processes. DFDs were usually used to show
data flows in a computer system, although they could in theory be applied to business
process modelling. DFD were useful to document the major data flows or to explore a
new high-level design in terms of data flow.

TYPES OF DFD:

There are two types of DFDs, both of which support a top-down approach to systems
analysis, whereby analysts begin by developing a general understanding of the system
and gradually break components out into greater detail:
 Logical data flow diagrams - are implementation-independent and describe the
system, rather than how activities are accomplished.
 Physical data flow diagrams - are implementation-dependent and describe the actual
entities (devices, department, people, etc.) involved in the current system. DFDs can
also be grouped together to represent a sub-system of the system being analyzed.

COMPONENTS OF DFD :

Data flow Diagram shows the flow of data. It is generally made of symbols given
below :

(1) A square shows the Entity : -

(2) A Circle shows the Process: -

28
(3) An open Ended Rectangle shows the data store : -

(4) An arrow shows the data flow :-

 The DFD can be up to several levels. The 0 level DFD states the flow of data in
the system as seen from the outward in each module.

 The first level DFD show more detail, about the single process of the 0 level
DFD.

 The second level DFD can show even more details and so on.

Administration Automated Greeting System User

0-Level DFD

29
ERD(ENTITY RELATIONSHIP DIAGRAM)

DEFINITION:

An entity-relationship (ER) diagram is a specialized graphic that illustrates the

interrelationships between entities in a database. ER diagrams often use symbols to
represent three different types of information. Boxes are commonly used to represent
entities. Diamonds are normally used to represent relationships and ovals are used to
represent attributes.

ENTITY RELATIONSHIP (ER) DIAGRAM:

This diagramming technique is used to visually present a database schema or data model
and was original proposed by Chen in the 1970s. There are many different data
modeling notations; some are very similar to UML class diagrams (with the exception of
operations). However, the notation the used here is slightly different, as proposed by
Elmasri, et al.
The database schema for this system is shown in figure. The table object has been left
out of the diagram because the table management feature set had been dropped from the
requirements before this stage of the design process.
Some important database design decisions are as follows:
- To store the total price of an order with the order rather than calculating it on the fly
when looking at past orders. This is because the price of menu items could change at any
time, so the total price at the time of ordering must be stored so that the total price is not
incorrectly calculated in future.
Similar to the previous point, the order receipt is stored as a hard-copy and not
regenerated when reviewing past orders because things such as the restaurant name or
VAT percentage are subject to change. Receipts stored need to be exactly the same as the
customer copy in case of dispute.

30
 Number of users
Password

Name Login ID Users ID Number of receivers

Contact Number Kind of wish

User Registers in Automated Wish System

Sign in

Sends

Selects Wish

By mail Type

By SMS

E-R Diagram

31
DATABASE DESIGN

A Database may be thought of a set of related files. Related files mean that the record of
one file may be associated with the records in another file . The conventional file based
systems emphasized that the application and files where built around it. The Database
environment emphasizes that data independently of the application that use the data. The
applications are allowed evolve around a database design such that it can adopt the
changing needs. Data becomes the central resource in the database environment.
Information System is built around this central resource to give flexible access to date.
Special software called Database Management System often referred the database
operations. The three different approaches are: Hierarchical database management
system, Network database management and Relational database management

APPROACH

The database of the “Automated Greeting System Web Application” uses a relational
model approach . In this model the fields are called attributes, records occurrences are
called tuples and fields are referred as tables. The Relational Approach is used because it
simplifies the overall view of the data store. Through one relational model scheme
design is also relatively easy and built around the entity relationship diagram. Five tables
have been identified for this website. Tables have been related to each other through the
reference key attributes pointing to the records of other tables. The attribute , Primary
Keys, foreign keys and other details of the table are given MySQL has been used for
Database Management System of “Automated Greeting System Web Application” for
easy interacting.

DATA STRUCTURE

TABLES

Table 1: Registration table

Table 2:FriendList table
Table 3:Sent table
Table 4: Received table
Table 5:Image table

32
TABLE DESCRIPTION

The detailed data structures of the tables are as follows:

Table Name—Registration

Attribute Name Datatype Constraints

fname Varchar(15) Not Null
lname Varchar(15) Not Null
mname Varchar(15) Not Null
gender Varchar(15) Not Null
uname Varchar(15) Not Null
pass Varchar(15) Primary Key
eid Varchar(15) Not Null
Date Date Not Null
Cnumb Number(10) Not Null
Security Varchar(50) Allows Null
Ans Varchar(15) Allows Null
Add1 Varchar(30) Not Null
Add2 Varchar(30) Not Null
State Varchar(20) Not Null
thought Varchar(15) Not Null

Table Name—FriendList
Attribute Name Datatype Constraints
Uname Varchar(15) Not Null
Name Varchar(15) Not Null

Table Name—Sent
Attribute Name Datatype Constraints
ID Number(100) Primary Key
name Varchar2(20) Not Null
uname Varchar2(20) Not Null
date Date Not Null
msg Varchar(100) Allows Null
greet Blob Allow Null

33
Table Name—Received
Attribute Name Datatype Constraints
ID Number(100) Primary Key
name Varchar2(20) Not Null
uname Varchar2(20) Not Null
date Date Not Null
msg Varchar(100) Allows Null
greet Blob Allow Null

Table Name—Image
Attribute Name Datatype Constraints
Uname Varchar(20) Not Null
img Blob Allows Null

35
SNAPSHOT

Home Page

35
Registeration Page

36
Profile Page

37
Edit Profile

38
Friend List

39
Invite Friends

40
Change Password

41
Send Greeting

42
44
Received Greeting

44
About Us

45
Contact Us

46
 Charts

GANTT CHART REPRESENTING FOR NEXT SEMESTER

Task Task Jul- Aug- Nov- Nov- Jan- Feb- Mar-

No. Aug Nov Dec Dec Feb Mar April
1 Requirement
Analysis
2 Design

3 Coding

4 Testing

5 Documentatio
n
6 Implementati
on
7 Final Review

47
PERT CHART

A PERT chart is a project management tools used to schedule, organize, and coordinate
tasks within a project. PERT stands for Program Evaluation Review Technique. A
PERT chart presents a graphic illustration of a project as network diagram consisting of
numbered nodes(either circles or rectangles) representing events, or milestones in the
project linked by labeled vectors (directional lines) representing tasks in the project.

The direction of the arrows on the lines indicates the sequence of tasks.

Programming Beta Testing

Alpha Testing

SRS And Design

3 5 8 10

10 15 30 10 10
1 2

4 6 7 9 11
3 10 10 10 5

Buy Hardware Writing

Manuals User Test
User
Requirement And
Analysis Installation Training

48
CONCLUSION

• This Web Application provides the fastest way to send different kinds of
Greetinges over internet. The system effectively automated the functions involved
in the processes being handled manually before.

• The cost & benefit analysis shows that the system was quite successful in saving
costs over the way employed before in writing long letters and sending & generate
equivalently huge benefits

• The system is secure & scalable. The system design has been done keeping
userfriendliness and efficiency in mind.

49
 BIODATA OF GROUP MEMBER

BIO DATA OF GROUP MEMBER 1:

MOHD AFZAL JEELANI
Mob : 8948211386
mdafzaljeelani@gmail.com
Vill : Parsa , Post : Kathwatiya Alam
Distt : Siddharth Nager

Qualification
Bachelor of Computer Application (Integral University Lucknow 2017 ) - 67.6%
High School (UP Board 2012)– 79.3%
Intemediat (UP Board 2014) – 69%
Mini Project
Online Bus Ticketing Management
(With Visual Basic as front end and MS Access as back end)
Pharmacy Aoutomation
(with Core Java and MySql)

Techmical Skills
Operating System : DOS,Windows 2000,Windows XP,Windows 7,Windows 8 and
8.1,Windows 10, Unix/Linux
Application Software : Office 2003,Office XP,Office 2007,Open Office,LibreOffice
4.2,Adob Photoshop,Coral Draw,Photoshop CS4 ,etc.
Programming Skills : C Language,HTML,CSS,core Java,MySql,Learning JavaScript
and Advance Java

Personal Information:
A young, determined hard and smart working person. I believe in task based roles and
complete ownership of work.Languages Known:English, Hindi,UrduHobbies:I love
reading IT related books, playing Chess and Cricket,listening music, surfing Internet,
self-learning.

Other Information
Area of Interest:Software Development, Programming,Coding, App Development,
Technical Support, Support Engineer, Client service.
Personal profile
Father's Name : Mr. Hafizullah
Date of Brith : 01-05-1997
Declaration
I hereby declare that the details furnished above are true and correct to the best of my
knowledge and belief.

Date:
Place: Lucknow (Mohd Afzal Jeelani) 50
Bio Data of Group Member 2:
MOHD FAISAL
Mob : 8874311581
faisalidrisi07@gmail.com
Tehsil Fatehpur -225305
Barabamki

Qualification
Bachelor of Computer Application (Integral University Lucknow 2017 ) - 61.25
High School (UP Board 2011)– 52.16%
Intemediat (UP Board 2013) – 56.80%
Mini Project
Library Management System
(With Visual Basic as front end and MS Access as back end)
Pharmacy Aoutomation
(with Core Java and MySql)
Techmical Skills
Operating System : DOS,Windows 2000,Windows XP,Windows 7,Windows 8 and
8.1,Windows 10,Learning Unix/Linux
Application Software : Office 2003,Office XP,Office 2007,Open Office,LibreOffice
4.2,Adob Photoshop,Coral Draw,Photoshop CS4
Programming Skills : C Language,HTML,CSS,core Java,MySql,Learning JavaScript
and Advance Java
Personal Information:
A young, determined hard and smart working person. I believe in task based roles and
complete ownership of work.
Languages Known : English, Hindi,Urdu
Hobbies :I love reading IT related books, playing Chess and Cricket,listening music,
surfing Internet, self-learning.
Other Information
Area of Interest:Software Development, Programming,Coding, App Development,
Technical Support, Support Engineer, Client service.
Personal profile
Father's Name : Mr. Mohd Naeem Idrisi
Date of Brith : 17-12-1995
Declaration
I hereby declare that the details furnished above are true and correct to the best of my
knowledge and belief.

Date:
Place: Lucknow (Mohd Faisal)

51