E-DIARY

Chapter 1
Software Requirement Specification

8th CE

SAL Institute Of Technology And Engineering Research

Page 1

E-DIARY

1.1 Introduction
This project is developed based on the Java and the phpMyAdmin database engine. Java is part
of the Open Source framework, which is an integrated and managed environment for the
development and execution of native code. Java is a platform for creating web applications that
run on any servers using the Xampp & Apache servers and web browsers.

1.1.1 Purpose: The purpose of the project is to secure the users all documents like marksheets,legel papers

etc.
User can see the all documents of them.
User can download the documents to other.
Just register yourself in our website and add all your document in safe side.
User can also see the news blog about some facts of india.
If user have any query than mail on our email address.

1.1.2 Scope Of Project:

The scope of my system is to provide efficient and easy way to get details.
This system is developed to provide convenience to user for download the documents online.
This system is also developed for to provide the details about news blog.
User can see government recruitment details
User can get details of event which is organized by government.

1.1.3 Project Planning:Our development of this project is divided into two parts one is analysis and one is the
implementation, as our curriculum is divided into two parts means in two semesters. So in first
phase of the application we have analyzed all the aspects of the system and requirements and
efforts for the system.

Project Development Approach:-

8th CE

SAL Institute Of Technology And Engineering Research

Page 2

E-DIARY
We are developing this project with the Spiral Development approach because it provides us flexibility to
move from any stage to any other stage, and this system is totally changeable at any instance of time, thus
to avoid the wastage of time and efforts it is most convenient to use spiral development approach for our
system.

Spiral Model:SDLC spiral Model includes the iterative nature of the prototyping model and the linear nature of the
waterfall model.
We can change requirements and stages in the even time of the development, means if we found
something wrong in any of the development stages then we can easily go backward and correct the logical
implementation as well as the codeIn each iteration of the spiral approach, software development process
follows the phase-wise linear approach. At the end of first iteration, the customer evaluates the software
and provides the feedback. Based on the feedback, software development process enters into the next
iteration and subsequently follows the linear approach to implement the feedback suggested by the
customer.
This approach is ideal for developing software that is revealed in various versions. Spiral model diagram
image is shown in the figure below:

Fig.1.1-Spiral Model

8th CE

SAL Institute Of Technology And Engineering Research

Page 3

E-DIARY

The process of iteration continues throughout the life of the software.An example of the spiral
model is the evolution of Microsoft Windows Operating system from Windows 3.1 to windows
2003. We may refer to Microsoft windows 3.1 Operating System as the first iteration in the spiral
approach.
The product was released and evaluated by the customers, which include the market large. After
getting the feedback from customers about the windows 3.1, Microsoft planned to develop a new
version of windows operating system. Windows95 was released with the enhancement and
graphical flexibility. Similarly, other versions of windows operating system were released.

1.2 General Description

The aim of this project was to develop a prototype the project Classified service using Open
Source technology.The objective was to explore the capabilities of this technology as compared
to the corresponding Java-based technology provided by Sun Microsystems.
There are some important issues in developing the project web application. First, the search time
should be kept to a minimum. This depends on choosing the appropriate development
environment and using good development techniques. Second, the web application should
provide the services that both user and library members. Third, the web application should have a
friendly user interface.
This project is developed based on the Java and the My SQL Workbench database engine. Java
is part of the Open Source framework, which is an integrated and managed environment for the
development and execution of native code. Java is a platform for creating web applications that
run on any servers using web browser.

1.2.1 Project Introduction:E-diary is your online personal documents diary. It is a system in which you can upload your
documents and other important legal papers. With e-diary you can securely upload, view, update
and share. With this website, you can see all the details of your documents whenever you want.
By unique id you can access your account. First you have to login with your id, upload your
documents, share the documents with other social networking sites. The project consists of two
modules:- 1. Administrator User 2. Registered User
8th CE

SAL Institute Of Technology And Engineering Research

Page 4

E-DIARY

Admin User :This type of user will be responsible to manage whole site & also content that will be published in site.
This type of users will be given special training for doing this if required. Admin user can post
the details of any government event, news blog and government recruitment details. Admin can
response to the complaint and feedback.
Registered User :This type of user will be able to visit our site and navigate to different pages to get information
they will not be able to change any content on website .They will be able to give feedback for
improvement of website. They can also post complaint to the system. Registered user can upload,
view, share and update their documents.

1.2.2Project Profile:Project definition

Project description

:
:

E-Diary
This project Web application provides functionalities for
both user and admin members. The user can browse the web
site with security and they can upload and see their
documents,legel papers etc. For the admin members, a
security issue is added. They need to create an account in the
system and every time he logs in. He can then delete any of
these, and he can add new ones.

Internal project Guide

Varsha G.Tank

Team Size

Hardware Configuration

512 MB RAM
Disk space: 2 GB
Processor Intel Pentium or higher

Front-End tool

JAVA,JSP,SERVLET

Back-End tool

XAMPP SERVER

8th CE

SAL Institute Of Technology And Engineering Research

Page 5

E-DIARY

1.3 Security and Reliability Requirements

Maintaining Security :There are three ways to deal with security in Java: using windows authentication, using forms
authentication and using passport authentication. This project uses forms authentication from
database. The root folder allows all users and the admin folder only allows authenticated user.
After developing the project, it is time to publish the completed web application on a web server
for client use. Also, it is important to monitor and maintain the application when it is in use. This
project uses Internet Information Server 5.0 on local machine as the web server to host and run
the deployed project.

Software System Attribute:There are a number of attributes of software that can serve as requirements. It is important that
required attributes by specified so that their achievement can be objectively verified. The
following items provide a list of software system attributes.

Reliability:Specify the factors required to establish the required reliability of the software system at time of
delivery.

Availability:The tool we use shall be available, up and running for 24*7 throughout the year except due to
the routine maintenance activities.

Security:Site Administrator and Users with valid credentials will be able to log in to the Web tool. Site
Administrator will have access to the database structures at back-end. Site Administrator will
have the rights for modifications as well as any Updation work for the datasets and website.
Access to the various subsystems will be protected by a user log in screen that requires a user
name and password.

Maintainability:-

8th CE

SAL Institute Of Technology And Engineering Research

Page 6

E-DIARY

The Web used tool is being developed using Open-Source technology. Therefore, minimal efforts
shall be required during the O&M activities through-out its life cycle and shall be easy to
maintain.

Portability:The Web tool shall run in any computer environment (such as, Microsoft Windows) which is
having Web Browser and Internet connection, as mentioned in section 2.1.1 i.e., System
Interfaces.

1.4 Organizational Requirements

1.4.1 User Requirements:User requirement are specifies requirement of the user of the system. The user
requirements are: User can register and make an account. For that user has to fill up the registration form and
submit the information to the database.
This system is developed for to provide convenience to user for read the details easily.
User has to fulfill all the details which are mandatory.
User can upload the documents by scanner.

1.4.2 System Requirements:The system requirements are:

Facility to delete profile after user login.
Easy to use for guest users.
Should work efficiently even on slow internet connections.

1.4.3 Implementation Requirements:It requires good skill for implementation of project. As this project is using 3-tier business
architecture. All the classes, functions, procedures and objects are created in the system wise
architecture. The three tiers are given below.
GUI
Business Logic Layer
Data Access Layer
8th CE

SAL Institute Of Technology And Engineering Research

Page 7

E-DIARY

Entire coding will be done using Eclipse and My SQL Workbench . Soft copy for the
documentation is provided in Microsoft Word Format. Entire coding would not be shown to the
client for any reasons. Implementation does not require any more software support without as
mentioned below in the system requirements.

1.4.4 Standards Requirements:Industry standards will be followed by us in any negotiation or deal related to the product
software. Coding, Documentation and final product delivery will be followed by the
standards.

1.5 External Requirements

1.5.1 Ethical Requirements:Product Software should be negotiated with human ethics and it is wished that the software
should be used with ethical requirements. Any non-ethical use of this software will be at the
users own risk.

1.5.2 Legislative Requirements: Privacy Requirements: Privacy of any particular things and strategy will be served based on

prior negotiation and it should be cleared purposed for that requirement.

Safety Requirements: Safety will be provided based on the requirement of the members and
necessary critical points

1.6 Study and weakness of current system

The current system works for some particular task. As we studied that in system you can only
upload, view and share your documents.
Security provided by current system is good but as of us point of view we can more expands
to the current system.
By study we observed that the users for current system are less in Gujarat.
Most people dont know that how to use it.
Guajarati is are most hesitate to use this type of website for security purpose
8th CE

SAL Institute Of Technology And Engineering Research

Page 8

E-DIARY

1.7 Requirement of new system

1.7.1 Feasibility study: Feasibility study is a process to check possibilities of system development. It is a method to check
various different requirements and availability of financial &technical resources.
There are three different ways feasibility can be tested;

1.7.1.1 Technical Feasibility:My website is developing in Java language. And we are using eclipse software for it. So, technically
development of website is feasible.

1.7.1.2 Operational Feasibility:-The project will be user friendly. And it will be meet all

the

functional requirements which mention above.

1.7.1.3 Economical Feasibility:-The software tools which are used in development are cost free
and easy to maintain.
1.7.1.4 Time Schedule Feasibility:-Time is a most effective factor while making a project like
this one. The system should b finished within the assign time. Otherwise the whole project will
delay. The e-diary system would work faster. It should be give result quickly because this is 21 st
generation and youngers of this generation cant wait for much time in loading page. This is the
important thing.
1.7.1.5 Implementation Feasibility:-Implementation feasibility is also a very effecting factor
while planning for a new system or module. The project manager will check whether the
developer can make the project in time and the specified requirements and best performance. The
project leader will also check that the given tools and technologies to the developer will make
the system a success or not.

1.7.2 Features of the new system:1.7.2.1 SAFETY AND SECURITY CONSIDERATION: This project is a component of a larger project
This project will deliver only the web services part of the larger project
We expected to complete the project within one year. This project will use resources in the
form of time and effort that will be spent developing the project.
The data available from the socket server is authentic and reliable
8th CE

SAL Institute Of Technology And Engineering Research

Page 9

E-DIARY

Users see the books.

1.7.2.2 INTERFACES TO OTHER APPLICATIONS:There is no requirement to do the interface the system to other application. If there may need to
do interface to the other application in the future, it can be done by using another web services.
User can share their documents to the other connections like gmail etc. We will think about this
also implement this thing in use.

1.8 Interface requirement

1.8.1 GUI:The readings collected in the database, are to be optimized by the web services. The web services
will be used by the GUI developers for various devices. With the addition of the Internet,
residential consumers will be able to monitor and control home energy usage by analyzing usage
patterns through PDA, mobile devices and websites.

1.8.2 Hardware Requirement:Features

Minimum Requirement
Operating System(OS)
32 or 64 bit
Processor
Pentium 4 or above
Random Access Memory(RAM)
512
Speed Of Processor
1.6 GHZ or higher
Table 1.1-Hardware Requirements

1.8.3 Software requirement

Features

Minimum Requirement
Windows XP,Vista etc.
Java,Jsp,Servlet,Html,Css,JavaScript
XAMPP Server,Apache Tomcat 7.0

Operating System
Front-End
Back-End

Server,Web Browser
Table 1.2-Software Requirements

1.9 Preliminary Schedule

8th CE

SAL Institute Of Technology And Engineering Research

Page 10

E-DIARY

Software project planning involves estimation of Money, - Effort, - Resources and Time it will
take to build a specific software base system.
PROJECT DEVELOPMENT APPROACH AND JUSTIFICATION:For the project development, we have chosen the spiral model. The Spiral Model is an
evolutionary software process model that couples the iterative nature of prototyping with the
controlled and systematic aspects of the Linear Sequential Model. It provides the potential for
rapid development of incremental versions of the software. Using the spiral model, software is
developed in a series of incremental releases. A spiral model is divided into a number of
framework activities, also called task regions. Typically, there are between three and six task
regions. Figure shows a Spiral model that contains six task regions:
User communication:-tasks required to establish effective communication between
developer and user
Planning:- tasks required to define resources, timelines,
Risk analysis:-tasks required to assess both technical and management risks.
Engineering:-tasks required to build one or more representations of the application.
Construction and release:-tasks required to construct, test, install, and provide user support
(e.g., documentation and training).

1.10 Overview of Java: History of Java

Java language was developed by James Gosling and his team at sun micro systems and released
formally in 1995. Its former name is oak. Java Development Kit 1.0 was

released in 1996. To

popularize java and is freely available on Internet.

Java
Java is loosely based on C++ syntax, and is meant to be Object-Oriented Structure of java is
midway between an interpreted and a compiled language. The java compiler into Byte Codes,
which are secure and portable across different platforms, compiles Java programs. These byte
codes are essentially instructions encapsulated in single type, to what is known as a java virtual
8th CE

SAL Institute Of Technology And Engineering Research

Page 11

E-DIARY

machine (JVM), which resides in standard browser.JVM verifies these byte codes when
downloaded by the browser for integrity. Jvms are available for almost all OS. JVM converts
these byte codes into machine specific instructions at runtime.

Features of Java

Java is object-oriented language and supports encapsulation, inheritance, polymorphism and

dynamic binding, but does not support multiple inheritances. Everything in java is an object
except some primitive data types.

Java is portable architecture neutral that is java programs once compiled can be executed on
any machine that is enabled.

Overview of JSP
The JSP technology will be used to interface HTML with Java. The JSP technology provides a
seamless connection with Java and presents an easy to use, Java-like programming constructs
that can be scripted within HTML files. Java Server Pages is a technology for developing web
pages that include dynamic content. A JSP page contains standard markup language elements,
such as HTML tags, just like a regular web page. A JSP page also contains special JSP elements
that allow the server to insert dynamic content in the web page.
Advantages of JSP

JSP supports both scripting and element-based dynamic content.

Allows developing custom tag libraries.

JSP pages are precompiled for efficient server processing.

JSP pages can be used in combination with servlets that handle the business logic.

High Security.

Can run on any J2EE compatible web Server.

It can run on any OS that have J2EE compatible web server.

JSP separates the dynamic and static parts.

High Quality tool supports.

8th CE

SAL Institute Of Technology And Engineering Research

Page 12

E-DIARY

Overview of Java Script

Java script is a general purpose, prototype based, object oriented scripting language developed
jointly by sun and Netscape and is meant for the WWW. Java script borrows most of its syntax
from java but also inherits from awk and perl, with some indirect influence from self in its object
prototype system.
Java Script is almost as easy to learn as HTML and it can be included directly in HTML
documents. Java Script was developed independently of java. Java script is a high level scripting
language that does not depend on or expose particular machine representations or operating
system services.

Features

Java script is embedded into HTML documents and is executed with in them.Java script is
browser dependent.

JavaScript is an interpreted language that can be interpreted by the browser at run time. Java
script is loosely typed language

Java script is an object-based language.

Java script is an Event-Driven language and supports event handlers to specify the
functionality of a button.

The Struts framework provides the flexibility to develop the much less coupled applications.
It generalizes and strictly implements MVC-model View Controller Architecture. That is the
basic need of our architecture.

Overview of Apache Tomcat

Apache Tomcat is a servlet container developed by the Apache Software Foundation (ASF).
Tomcat implements the Java Servlet and the JavaServer Pages (JSP) specifications from Sun
Microsystems, and provides a "pure Java" HTTP web server environment for Java code to run.
Tomcat should not be confused with the Apache web server, which is a C implementation of an
HTTP web server; these two web servers are not bundled together. Apache Tomcat includes tools
8th CE

SAL Institute Of Technology And Engineering Research

Page 13

E-DIARY

for configuration and management, but canalso be configured by editing XML configuration
files.

Overview of MySQL
MySQL is a multithreaded, multi-user SQL database management system (DBMS) which has,
according to Mysql AB, more than 10 million installations .Mysql is owned and
single for-profit firm, the Swedish company Mysql AB, which holds the

sponsored by a

copyright to most of

the codebase.
Libraries for accessing Mysql databases are available in all major programming languages with
language-specific APIs.In addition, an ODBC interface called MyODBC allows additional
programming languages that support the ODBC interface to communicate with a Mysql
database, such as ASP or Coldfusion. The Mysql server and official libraries are mostly
implemented in ANSI C.

8th CE

SAL Institute Of Technology And Engineering Research

Page 14

E-DIARY

Chapter 2
Data Dictionary

8th CE

SAL Institute Of Technology And Engineering Research

Page 15

E-DIARY

2.1 Introduction
A Data Dictionary is Catalog-Responsibility of the Element in a System. As the Name
Suggests, these Element are Structured around Data in a Way to Meet the Use and the
Organization Requirements.
A Data Dictionary is a List of Elements that composes all the Data Flow Process through the
System. It Stores Detail and Description of Data Flow, Data Store and Processes. If Analysts
Wants to Know by What Other Means is a Table or a Data Item Referenced in the System or
where it is Being Used the Answers are Properly Developing the Data Dictionary. The
Dictionary Id Developed during Data Flow Analysis Assists the Analysts involved in
Requirements. However its Content is used during System Design as Well.
A data dictionary, or metadata repository, as defined in the IBM Dictionary of Computing, is
a "centralized repository of information about data such as meaning, relationships to other
data, origin, usage, and format." The term can have one of several closely related meanings
pertaining to databases and database management systems (DBMS).
Technically, it is a database about a database. There is no one set standard in terms of layout
or the level of detail to which a data dictionary should be written. A data dictionary defines
the structure of the database itself (not that of the data held in the database) and is used in
control and maintenance of large databases. Among other items of information, it records (1)
what data is stored, (2) name, description, and characteristics of each data element, (3) types
of relationships between data elements, (4) access rights and frequency of access. Also called
system dictionary when used in the context of a system design.

2.2 Features of Data Dictionary

A 'data dictionary' describes the structure and attributes of data 'items' to be used within a
software application (usually a database).
Software development teams need a comprehensive data dictionary to refer to during the
development and maintenance of a new database. This is so that they are all working using
the same data formats when reading or writing data.
A data dictionary includes the names and descriptions of the tables and the fields contained in
each table. It also documents information about the data type, field length and other things

8th CE

SAL Institute Of Technology And Engineering Research

Page 16

E-DIARY

such as validation. The main purpose of the data dictionary is to provide metadata, or
information about data.
The Volume of Data in Most Information System is Substantial More than a Single Analyst
Can Easily Keep Track of the same. When the Teams of Analyst Work on Assistance the Task
of Co-Coordinating Data Definition Becomes More Complex. Individual Depends on the
Information provided by others with their Assumption and the Specification made by them.
Data Dictionary is Integral component of Structured Analysis. Since Data flow diagram by
them do not fully describe the subject of the Investigation. The Data Dictionary provides
additional information about system.

2.3 Database keys

Keys are very important part of Relational database. They are used to establish and identify
relation between tables. They also ensure that each record within a table can be uniquely
identified by combination of one or more fields within a table.

Super Key :Super Key is defined as a set of attributes within a table that uniquely identifies each record
within a table. Super Key is a superset of Candidate key.
An attribute or a combination of attribute that is used to identify the records uniquely is known
as Super Key. A table can have many Super Keys.

Candidate Key :Candidate keys are defined as the set of fields from which primary key can be selected. It is an
attribute or set of attribute that can act as a primary key for a table to uniquely identify each
record in that table.

Primary Key :Primary key is a candidate key that is most appropriate to become main key of the table. It is a
key that uniquely identify each record in a table.

Composite Key :Key that consist of two or more attributes that uniquely identify an entity occurrence is called
Composite key. But any attribute that makes up the Composite key is not a simple key in its own.

Secondary or Alternative key :8th CE

SAL Institute Of Technology And Engineering Research

Page 17

E-DIARY

The candidate key which are not selected for primary key are known as secondary keys or
alternative keys.

Foreign key :a foreign key (FK) is a field or group of fields in a database record that points to a key field or
group of fields forming a key of another database record in some (usually different) table.
Usually a foreign key in one table refers to the primary key (PK) of another table. This way
references can be made to link information together and it is an essential part of database
normalization
Table Name

: registration

Table Description : This table is used to register a user and to store the information of user.
Table 2.1 registration

Field name
Registration_id
Firstname
Middlename
Lastname
Birthdate
Gender
Email
Contact
Address
City
pincode
Username
Password
Securityque

Datatype
Int(10)

Constraint
Primary key,Auto

Description
User Registrations id

Varchar(15)
Varchar (15)
Varchar (15)
Varchar(15)
Varchar(10)
Varchar(15)
Varchar (10)
Varchar(50)
Varchar(10)
Varchar (10)
Varchar(15)
Varchar(20)
Varchar(20)

Increment
Not null
Not null
Not null
Not null
Not null
Not null
Not null
Not null
Not null
Not null
Not null
Not null
Not null

as per entry
Users first name
Users middlename
Users lastname
Users bithdate
Users gender
Users email
Users contact no.
Users address
Users city
Users pincode
Users username
Users password
Users security

Not null

question
Users security

Securityans

Varchar(10)

Status

Tinyint(1)

8th CE

Not null
Table 2.1

answer
Users status(0 or 1)

SAL Institute Of Technology And Engineering Research

Page 18

E-DIARY

Table Name

: document

Table Description : This table is used to upload users document.

Table 2.2 document
Field name
Documentid
Username
Title
Photo
Status

Datatype
Int (10)

Constraint
Primary key,Auto

Description
Upload id as per entry

Varchar (15)
Varchar(15)
Varchar(30)

Increment
Not null
Not null
Not null

in table.
Users Name
Documents Title
Documents Pic or

Not null

File
Documents Status(0

Tinyint(1)

or 1)
Table 2.2

Table Name

: contact_us

Table Description : This table is used to provide information from user to admin for some error
or any suggestions.
Table 2.3 contact_us

Field name
Contactusid
Fullname
Contact
Email
Msg
8th CE

Datatype
Int(10)

Constraint
Primary key,Auto

Description
Contatct_Us id as per

Varchar (30)
Varchar(15)
Varchar(15)
Varchar(50)

Increment
Not null
Not null
Not null
Not null

entry
Users name
Users Number
Users Email
Users message

SAL Institute Of Technology And Engineering Research

Page 19

E-DIARY

Table 2.3

Table Name

: content

Table Description : This table is used to post complaints of users.

Table 2.4 content
Field name
Contented
Title
Des

Datatype
Int (10)

Constraint
Primary key,Auto

Description
Contentid as per entry

Varchar (15)
Text

Increment
Not null
Not null

Contents Title
Description of
Content

Table 2.4
Table Name

: admin_login

Table Description : This table is used to logging into e-diary by admin.

Table 2.5 admin_login

Field name
Loginid
Username
Password

Datatype
Int(10)
Varchar (15)
Varchar (30)

Constraint
Primary key,Auto
Increment
Not null
Not null
Table 2.5

Description
Admins id as per
entry
Admins name
Admins password

Table Name

: news

8th CE

SAL Institute Of Technology And Engineering Research

Page 20

E-DIARY

Table Description : This table is used to store the information of news that can add by admin.
Table 2.6 news

Field name
Newsid

Datatype
Int(10)

Constraint
Primary key,Auto

Description
Newss id as per entry

Title
News_by
Date
Shortdes

Varchar (100)
Varchar (15)
Varchar(15)
Text

Increment
Not null
Not null
Not null
Not null

Newss title
Who write the news?
Newss date
Newss

Not null

ShortDescription
Newss

Longdes

Text

Photo

Varchar(30)

Table Name

Not null
Table 2.6

LongDescription
Newss Pic

: recruitment

Table Description : This table is used to store the information of news that can add by admin.
Table 2.7 recruitment

Field name
Recruitmentid

Datatype
Int(10)

Constraint
Primary key,Auto

Description
Recruitments id as

Title
Recruitment_by
Date
Shortdes

Varchar (100)
Varchar (15)
Varchar(15)
Text

Increment
Not null
Not null
Not null
Not null

per entry
Recruitments title
Who write this blog?
Recruitments date
Recruitments short

Longdes

Text

Not null

Description
Recruitments long

Photo

8th CE

Varchar(30)

Not null
Table 2.7

Description
Recruitments Pic

SAL Institute Of Technology And Engineering Research

Page 21

E-DIARY

Chapter 3
Diagrams

8th CE

SAL Institute Of Technology And Engineering Research

Page 22

E-DIARY

3.1 UML Diagrams

UML-Unified Modeling Language
In The Unified Modeling Language User Guide, the original developers of the UML-Grady
Booch, James Rum Baugh, and Ivar Jacobson--provide a tutorial to the core aspects of the
language in at wo-color format designed to facilitate learning. Starting with a conceptual model
of the UML, the book progressively applies the UML to a series of increasingly complex
modeling problems across a variety of application domains.
This example-driven approach helps readers quickly understand and apply the UML. For more
advanced developers, the book includes a learning track focused on applying the UML to
advanced modeling problems. Many of the designations used by manufacturers and sellers to
distinguish their products are claimed as trademarkswhere those designations appear in this
book, and Addison Wesley LongmanInc. Was aware of a trademark claim, the designations have
been printed in initial caps are all in caps.
The author and publisher have taken care in the preparation of this book, but make no expressed
or implied warranty of any kind and assume no responsibility for errors or omissions. No liability
is assumed for incidental or consequential damages in connection with or arising out of the use
of the information or programs contained herein.
To model a system the most important aspect is to capture the dynamic behaviour. To clarify a bit
in details, dynamic behaviour means the behaviour of the system when it is running
/operating.So only static behaviour is not sufficient to model a system rather dynamic behaviour
8th CE

SAL Institute Of Technology And Engineering Research

Page 23

E-DIARY

is more important than static behaviour. In UML there are five diagrams available to model
dynamic nature.
List of UML Diagrams Shown are as follows:
1.
2.
3.
4.
5.

Use Case Diagram

Activity Diagram
Sequence Diagram
Entity Relationship Diagram
Data Flow Diagram

3.1.1 Use Case diagram :-

8th CE

SAL Institute Of Technology And Engineering Research

Page 24

E-DIARY

ADMIN

Fig. 3.1 Use Case diagram for admin and user

8th CE

SAL Institute Of Technology And Engineering Research

Page 25

E-DIARY

3.1.2 Activity diagram :-

Log In

[ Do not meet criteria ]

[ meet criteriaSuccess
]

Post News

Post Recruitment

Response to Feedback

Post event

Response to Complaint

Log Out

Fig.3.2 Activity diagram for admin

and user

8th CE

SAL Institute Of Technology And Engineering Research

Page 26

E-DIARY

Do Registration

Log in

Suc

[ Do not meet criteria]

[meet criteria]

Upload Documents

View Document

Share Document

Upload document

Post complaint

Post feedback

Log Out

Fig.3.3 Activity diagram for user

and user
8th CE

SAL Institute Of Technology And Engineering Research

Page 27

E-DIARY

3.1.3 Sequence diagram:-

8th CE

SAL Institute Of Technology And Engineering Research

Page 28

E-DIARY

user

admin
Checks validity
Does registration
Request for login
Log in
Request for process

Checks
user

Upload
view
Share
Update

Post News
Display News
Display Recruitment Detalis
Display Upcoming Event Details

Recruitment
Event

User Log out

Fig.3.4 Sequence diagram

and user

8th CE

SAL Institute Of Technology And Engineering Research

Page 29

E-DIARY

3.2 Entity Relationship diagram

An Entity Relationship Diagram (ERD) is a visual representation of different data using
conventions that describe how these data are related to each other. In the diagram, the elements
inside rectangles are called entities while the items inside diamonds denote the relationships
between entities.
While able to describe just about any system, ER diagrams are most often associated with
complex databases that are used in software engineering and IT networks. In particular, ER
diagrams are frequently used during the design stage of a development process in order to
identify different system elements and their relationships with each other.In the diagram, the
information inside the oval shapes are attributes of a particular entity.
ER model as a conceptual modeling approach that views real world data as systems of entities
and relationships. Entities are data objects that maintain different relationships with each other.
Additionally, entities are also described further using attributes.
There are three basic elements in an ER Diagram: entity, attribute, relationship. There are more
elements which are based on the main elements. They are weak entity, multivalued attribute,
derived attribute, weak relationship and recursive relationship. Cardinality and ordinality are two
other notations used in ER diagrams to further define relationships.
1. Entities: Entities are Distinguishable Object that can be represented in the Database.
2. Relationship: It is meaningful interaction between the entities.
3. Attributes: It is nothing but properties of entities.
In E-R Diagram three types of Relationship exists:
1. One-to-One (1:1) : Relationship is associated between two objects.
2. One-to-Many (1: M or M: 1) : Relationship describes an entity that may more
Entities related to it.
3. Many-to-Many (M: M) : Relationship describes an entities multiple Relationship
with other entities.
E-R diagram contains following components :
1.Rectangle : This represents entity sets.
2.Ellipse : This represents attributes.
8th CE

SAL Institute Of Technology And Engineering Research

Page 30

E-DIARY

3.Diamonds : This represents relationship sets.

4.Line : Links attributes to entity sets and entity sets to Relationship sets.

8th CE

SAL Institute Of Technology And Engineering Research

Page 31

E-DIARY

gender
middlename

Ur_id
Is A

lastname

a_id

birthdate

*
1

firstname

User

email

state

Admin

can

address
a_password

a_name

city

username

password
r_id
n_id

n_title

r_title

Upload_id
upload

* posts
recruitment

news

n_date

Upload_pic

n_description

r_date
n_pic
r_description

*
event

e_description

c_id
gives

e_id
e_pic
e_title

Complaint

c_name

e_place
c_complaint

e_date
Feedback

f_id

f_feedback

f_name

Fig. 3.5 E-R diagram

8th CE

SAL Institute Of Technology And Engineering Research

Page 32

E-DIARY

3.3 Data flow diagram

Data flow diagrams (DFD) illustrate how data is processed by a system in terms of inputs and
outputs. DFDs are useful in modelling high-level systems and processes. These diagrams show
the way in which data flows between elements in a system and between the system and external
entities.
The top-level diagram is called context diagram and contains one Functional Transform, which
represents the entire system. The context diagram also shows the external entities that interact
with the system. Four Basic Elements of DFD are:

Data flows represented by named pipelines

Processes represented by circles
External Entities represented by rectangles
Data stores represented by open-ended rectangles.

The external entities are the sources and destinations of a systems input and output. They are
objects that are not within the system, but with which the system interacts. Data Storage
represents entities in the system in which the data is stored. Examples include databases and
files. Process represents an action taken on the data. This may include a calculation,
conversation, or other task performed. Process can send and receive control signals that help to
explain the control over the data flowing through the system. Data Flows represent the
movement of information through the system. Control signals connect control transforms to
other objects on the diagram and represent control over data.

Context level DFD :8th CE

SAL Institute Of Technology And Engineering Research

Page 33

E-DIARY

Post news

Registration
Request for login

Valid user

E-Diary
User

Log in

Check valid user

Admin
Post Recruitment details

Upload documents
view documents

Post event

share documents
Update documents

Fig. 3.6 Context level DFD

8th CE

SAL Institute Of Technology And Engineering Research

Page 34

E-DIARY

DFD level 1 :1.0

Open form
Admin

1.0.1
Verify admins details
Enter login details
admin_login

1.0
Open form

1.0.1
registration

User

2.0
login

user_registration

Stores user data

user_login

Fig.3.7 level 1 DFD

8th CE

SAL Institute Of Technology And Engineering Research

Page 35

E-DIARY

DFD level 2 :-

8th CE

SAL Institute Of Technology And Engineering Research

Page 36

E-DIARY

Admin

can

1.1
Post news

Current news
news

2.2
Post
event

Event information

Post recruitment
2.3
Post recruitments

event

details
recruitment

can

User

2.1
Upload document Save documents

2.2
Post complaints

Post complaints

upload

complaint

Fig.3.8 DFD level 2

3.4 System Flowchart

8th CE

SAL Institute Of Technology And Engineering Research

Page 37

E-DIARY

System flowchart describes the data flow for a data processing system. It provides a logical
diagram of how the system operates. It represents the flow of documents, the operations
performed in data processing system. It also reflects the relationship between inputs, processing
and outputs.
A graphical representation of the sequence of operations in an information system or program.
Information system flowcharts show how data flows from source documents through the
computer to final distribution to users. Program flowcharts show the sequence of instructions in a
single program or subroutine. Different symbols are used to draw each type of flowchart.
Following are the features of system flowcharts:
The source from which data is generated and device used for this purpose.
Various process steps involved
The intermediates and final output prepared and the device used for this storage.

8th CE

SAL Institute Of Technology And Engineering Research

Page 38

E-DIARY

Chapter 4
System Design

4.1 Admin Module

8th CE

SAL Institute Of Technology And Engineering Research

Page 39

E-DIARY

Fig.4.1 Login Page :-

It is admins LogIn Page. After entering right username and password he/she can access the
admin panel.

Fig.4.2 Welcome Page :8th CE

SAL Institute Of Technology And Engineering Research

Page 40

E-DIARY

It is homepage of admin panel. Here admin can navigate to other pages and changes the user
contents and insert/delete/update the new details.

Fig.4.3 News_Master Page :8th CE

SAL Institute Of Technology And Engineering Research

Page 41

E-DIARY

Admin can insert news details which are shown to the users.

Fig.4.4 Recruitment_Master Page:8th CE

SAL Institute Of Technology And Engineering Research

Page 42

E-DIARY

Admin enter the government recruitments details which shown to the user.

Fig.4.5 Content_Master :8th CE

SAL Institute Of Technology And Engineering Research

Page 43

E-DIARY

Admin can add content details to the title and description field.It will see at user side.

Fig.4.6 News Details Page :8th CE

SAL Institute Of Technology And Engineering Research

Page 44

E-DIARY

News are shown in proper manner to the admin. In which admin can edit or delete the news
information.

Fig.4.7 Recruitment Details Page :8th CE

SAL Institute Of Technology And Engineering Research

Page 45

E-DIARY

Recruitments are shown to admin in proper manner. In which admin can edit or delete the
recruitment information.

Fig.4.8 Content Details Page :-

8th CE

SAL Institute Of Technology And Engineering Research

Page 46

E-DIARY

It is content details which are shown in proper manner at admin side.In which admin can edit or
delete the content information.

Fig.4.9 Contact Details Page :8th CE

SAL Institute Of Technology And Engineering Research

Page 47

E-DIARY

User contact details at admin side.

Fig.4.10 All User Page :8th CE

SAL Institute Of Technology And Engineering Research

Page 48

E-DIARY

This page shows the user details to admin which are register in eDiary.

Fig.4.11 User Details :8th CE

SAL Institute Of Technology And Engineering Research

Page 49

E-DIARY

This page shows users all details to admin.

Fig.4.12 Active User Page :-

8th CE

SAL Institute Of Technology And Engineering Research

Page 50

E-DIARY

This page shows the number of active users on the site to the admin.

Fig.4.13 Deactive User Page :8th CE

SAL Institute Of Technology And Engineering Research

Page 51

E-DIARY

This page shows the number of deactive users to the admin.

Fig.4.14 Documents Page :8th CE

SAL Institute Of Technology And Engineering Research

Page 52

E-DIARY

This page show the all documents of users to the admin. Admin can see and give approval or
rejection.

4.2 User Module

8th CE

SAL Institute Of Technology And Engineering Research

Page 53

E-DIARY

Fig.4.15 User Homepage :-

This is homepage of the user. User can see the news blog at TODAYS INDIA section and see
the recruitment details. After login they can also upload the documents.

Fig.4.16 About Page :8th CE

SAL Institute Of Technology And Engineering Research

Page 54

E-DIARY

In this page all the information about the eDiary is shown.

Fig.4.17 Contact Page:-

8th CE

SAL Institute Of Technology And Engineering Research

Page 55

E-DIARY

This page shows the contact details of the members who invented this site. User also send the
message related to the website to the admin.

Fig.4.18 News Details Page :8th CE

SAL Institute Of Technology And Engineering Research

Page 56

E-DIARY

This page shows the news details to the user.

Fig.4.19 Recruitment Details Page :8th CE

SAL Institute Of Technology And Engineering Research

Page 57

E-DIARY

This page shows the recruitment details to the user.

Fig.4.20 User SignUp page :8th CE

SAL Institute Of Technology And Engineering Research

Page 58

E-DIARY

This is User registration page. In which user add their details and register themselves to the
eDiary.

8th CE

SAL Institute Of Technology And Engineering Research

Page 59

E-DIARY

Fig.4.21 User LogIn Page :-

This is User logIn page. In which user enter username and password. After authentication they
can access to eDiary.

Fig.4.22 User Panel Page :8th CE

SAL Institute Of Technology And Engineering Research

Page 60

E-DIARY

This is welcome page of user side.In which user navigate to the other pages and add,see and
download the documents.

Fig.4.23 Upload Document Page :8th CE

SAL Institute Of Technology And Engineering Research

Page 61

E-DIARY

User can upload their documents to eDiary.

Fig.4.24 MyDocument Page :8th CE

SAL Institute Of Technology And Engineering Research

Page 62

E-DIARY

This is the manner wise list of users documents shown to the user which can approved by the
admin.

8th CE

SAL Institute Of Technology And Engineering Research

Page 63

E-DIARY

Chapter 5
Implementation

8th CE

SAL Institute Of Technology And Engineering Research

Page 64

E-DIARY

5.1 Implementation Environment

Multi User: This is a web-application, and so inherently it is multi user application.
There will be concurrent access to the system from all over the globe.
Uniform User design: As any website must have uniform design, this one also has.
Uniform design is necessary for increasing user convenience.
Efforts have been made to make the design browser independent.

5.2 Security Features

Security is an important aspect of any software development. Without reasonable level of
security, the availability, the reliability and safety may be compromised if external attack
damage to the system. For security purpose we have various validations.
Validation provided to every input ensures there are no take entries and redundant data.
Authorization at the time of login enables access to valid users. Other security feature we
have used is OTP. Its a one time password security. When user wants to log in then system
sends user a otp on their email, then by applying this otp user can securely login.
We have provided login for users for authentication purpose.

5.3 Coding Standards

The coding standard is well defined and standard style of coding. With the help of coding
standards any person can find the exact meaning of code and understand the working of the
system. A coding standard includes the way the variables are to be named, the code that is to be
laid out, the comments that are to be described etc. To develop reliable and maintainable
applications, you must follow coding standards and best practice.
General Coding Standard:The coding standard we have used is Pascal case that includes proper naming and programming
conventions. It includes first letter in identifier as capital letter and first letter of each subsequent
concatenated word also capitalized.
File Naming Conventions:-

8th CE

SAL Institute Of Technology And Engineering Research

Page 65

E-DIARY

The files created in the project are named in such a way that all letters are in small. The files in
the same module are grouped together in a folder with appropriate name. This makes it easier for
the developer to navigate to the appropriate file. Thus it is a good coding technique that enables
faster access to the files.
Creating Source Code:The regions are used to describe a module or function and are given a specific name. This makes
it quite easier for any user to understand and debug the code in case of any errors.
The region names are descriptive and thus describe the working of the function. This makes it
quite clear to any person who needs to understand the code. This feature also allows testing and
debugging easier. It can help to find errors faster and with lesser effort.
We have also used try catch feature in our coding. This enables the debugging easier and
efficient. The catch module will generate any sort of messages related to an error that occurred
during the execution. This technique helps a developer to find error in code during
unit testing.
Identifier Standard:The object instance must itself give an idea what it describes and also must start with a
underscore.

8th CE

SAL Institute Of Technology And Engineering Research

Page 66

E-DIARY

Chapter 6
Testing

8th CE

SAL Institute Of Technology And Engineering Research

Page 67

E-DIARY

6.1 Testing Plan

The aim of the testing process is to identify all defects existing in software Product. However for
most practical systems, even after satisfactorily carrying out the testing phase, it is not possible
to guarantee that the software is error free. This is because of the fact that the input data domain
of most software products is very large. It is not practical to test the software exhaustively with
respect to each value that the input data may assume. Even with this practical limitation of the
testing process, the importance of testing should not be underestimated.
It must be remembered that testing does expose many defects existing in a Software product.
Thus testing provides a practical way of reducing defects in a System and increasing the users
confidence in a developed system.
System Testing is an expensive but critical process that can take as much as 50 % of the budget
for the program development. The common view of testing held by user is that it is performed to
prove that there are no errors in a program. However this is virtually impossible since analyst can
not prove that is software is free and clear of errors. Software testing is a critical element of
software quality assurance and represents the ultimate review of specification design and coding.
Some of the Testing Objectives are:

Testing is a process of executing a program with the intend of finding the errors.
A good test case is one that has a high probability of finding undiscovered errors.
A successful test on the other hand is one that uncovers all the undiscovered errors.
Testing is set of activities that can be planned in advance and conducted systematically to
carry out the testing procedures of the proposed system.

Testing is generally done at two levels- Testing of individual screens and testing of the entire
system. Testing is the process of executing a program with the explicit intention of finding errors,
which makes the program fail. The tester is actually trying to make the program fail. A successful
test is the one that find an error. During Systems testing, the system is used experimentally to
ensure that the software does not fail, i.e. that it will run according to its specifications and in the
way users expect.
A test case is a set of data that the system will process as normal input. However, the data are
created with the express intend of determining whether the system will process them correctly or
not.
Following features are tested:8th CE

SAL Institute Of Technology And Engineering Research

Page 68

E-DIARY

All the functional features specified in the System Requirement specification are tested.
System level integration for the various screens that were developed has been done.
Performance testing has been done for acceptable response and correctness of data.
Functional Testing :The testing technique that is going to be used in the project is black box testing. In black box
testing the expected inputs to the system are applied and only the outputs are checked. The
working or the other parameters of the functionality are not reviewed or tested on the black box
testing technique. There is a specific set of inputs for each and every module which is applied
and for each set of inputs the result or the output is verified and if found as per the system
working this testing is termed or result is declared as pass.
If the set of inputs that are provided to each module are not giving the outputs as per the
expected results from the module then the result of that testing is to be declare failed. Moreover
the bottom up integration of the modules is applied herein so that each module can be verified at
the initial stage and if it is found that the independent module is perfectly alright, only then it is
going to be integrated with other related modules otherwise the module is checked for flaws and
then if it satisfies all the specific requirements of the module, is integrated to other related
modules to form and incorporate a system.
In the black-box testing approach, test cases are designed using only the functional specification
of the software, i.e. without any knowledge of the internal structure of the software. For this
reason, black-box testing is known as functional testing.
Structural Testing:In the white-box testing approach, designing test cases requires thorough knowledge about
the internal structure of software, and therefore the white-box testing is called structural
testing.

8th CE

SAL Institute Of Technology And Engineering Research

Page 69

E-DIARY

Fig:-6.1 Testing Process

6.2 Testing Strategy

The black box testing is going to be used for the project. The entire module is going to be
checked for the specific inputs and the output is going to be checked. We are going to test the
modules individually and thereafter if found to be working as per the expectations they are going
to be integrated with other successfully tested modules and then on integrated. At last all the
modules are integrated and thereafter it is checked on a broader basis and all the requirements
which are specified are checked for each integrated system modules. If all the functionalities are
successfully satisfied than the entire integrated system is found to be working perfectly alright.
The integration is going to be in a bottom up manner where in each individual modules are going
to be checked for the first time initially. Later on as and when other modules are developed and
are in a working condition than they are integrated and the entire system is going to be generated.
As mentioned before these entire system will finally be tested as per the requirements specified
by the customer if any flaws are seen they are immediately required to be solved. In short the
entire system should be working as per the requirements with no unexpected results.

8th CE

SAL Institute Of Technology And Engineering Research

Page 70

E-DIARY

Unit testing :The starting point of testing is unit testing. In this, each and every module is tested separately
and is often performed by the developer himself simultaneously along with the coding of the
form. Each and every in the software is tested for consistency and attempt is made to make the
software error free. In the Login Form it is checked that the user exist and the password entered
is correct, otherwise the error message is developed and the system waits for the correct input.
Proper messages are displayed on occurrence of errors.
In each and every form it is checked that the information provided by the user is valid and
complete, otherwise it will display proper message and system waits for the correct input. Proper
messages are displayed on occurrence of errors. In every form it is checked that if the user has
rights to perform the specific action and if user doesnt have rights then that action will not be
performed.
Integration testing :After unit testing the forms are gradually integrated into subsystems which are then integrated to
eventually form the entire system. During integration of forms, integration testing is performed
to detect design errors by focusing on testing the interconnection between forms. After linking of
each forms integration testing is performed. In this testing it is checked that the user can not
directly visit the forms, which cant be visited without login. E.g. User cant view, Inert, Update
or verify entries without login into the system.
Security testing :This is testing which is conforms that the program can restrict access authorized personal and
that authorized personal can access the function available to that level. User cannot visit or
perform action for which he is not given access rights. As the system is role based so security is
provided based on role.
Compatibility testing :Compatibility Testing is testing whether software is compatible with other element of a system
with which it should operate. Ex. Browser, hardware or Operating Systems. Compatibility testing
is performed by running it on different browsers. Here it is verified that the display or
functionality of controls is not changed when used in other projects.

8th CE

SAL Institute Of Technology And Engineering Research

Page 71

E-DIARY

6.3 Testing Methods

Involve execution and implementation of the software with test data and examining the outputs
of the software and its operational behavior to check that it is performing as required.
6.3.1 STATISTICAL TESTING:Used to test the programs performance and reliability and to check how it works under
operational conditions. Tests are designed to reflect the actual user inputs and their frequency.
The stages involved in the static analysis are follows.
Control flow analysis

Unreachable code
Unconditional branches into loops

Data use analysis

Variable used before initialization

Variables declared but never used
Variables assigned twice but never used between assignments
Possible array bound violations
Declared variables

Interface analysis

Parameter type mismatches

Parameter number mismatches
Non-usage of the results of functions
Uncalled functions and procedures

Storage management faults

Unassigned pointers
Pointer arithmetic

6.3.2 DEFECT TESTING:Intended to find inconsistencies between a program and its specification. These inconsistencies
are usually due to program faults or defects.
We have tested our functions of component to check the specification of our
components.
We selected input set to test the components like in query process we gave the
different kinds of inputs to examine their output.
We test software with sequences that have only a single value.
We used different sequences of different sizes in different tests.
8th CE

SAL Institute Of Technology And Engineering Research

Page 72

E-DIARY

Derived tests so that the first, middle and last elements of the sequence and accessed
to reveal the problems at partition boundaries.
Black Box Testing:Black box testing alludes to test that are conducted at the software interface. Although they are
design to uncover errors, black box tests are used to demonstrates that software functions are
operational, that input is properly accepted and output is correctly produce, that the integrity of
external information is maintained. Black Box Testing, also called behavioral testing, focuses on
the functional requirements of the software. That is, black box testing enables the software
engineer to derive sets of input conditions that will fully exercises all functional requirements for
a program. Black Box Testing is not an alternative to White Box techniques. Black- Box testing
attempts to find errors in the following categories:

Incorrect or missing functions.

Interface errors.
Errors in data structures or external database access.
Behavior or performance errors.
Initialization and termination errors.

White Box Testing:White box testing of software is predicted on close examination of procedural detail. Logical
parts through the software are tested by providing test cases that exercises specific sets of
conditions and /or loops. The Status of the program may be examined at various points to
determine if the expected or asserted status corresponds. White-Box testing sometimes called
Glass-Box testing; it is a test case design method that uses the control structure of the procedural
design to derive test cases. Using white-Box testing methods, the software engineer can derive
test cases that: Guarantee that all independents paths within a module have been exercised at
least once.
Exercise all logical decisions on their true and false sides.
Execute all loops at their boundaries and within their operational bounds.
Exercise internal data structures to ensure their validity.

Test Case : 1
Module Name : Login form
Test Title

: Verify login with valid username and password

Description

: Testing the login form.

8th CE

SAL Institute Of Technology And Engineering Research

Page 73

E-DIARY

Pre Conditions : User has valid username and password

Test

Description

Input

Expected Result

Actual Result

Status

Username

Naman1995

Password

naman@123

Control passes to
password field.
Control passes
successfully to
user home page if
status is also 1.

PASS

Control passes to
password field.
Verify inputs

PASS

Post Conditions: User is validated with database and successfully login to account. The account
session details are logged in database.

Test Case : 2
Module Name : SignUp form
Test Title

: Verify the registration information of user.

Description

: Testing the user signup form.

Pre Conditions : User entering valid information details.

Tes
t
1

Description
Firstname

Input
Naman

Expected Result

Actual Result

Statu

Control passes to the

Control passes

s
PASS

Middlename Field

to the
Middlename

8th CE

Middlename

Lastname

Birthdate

Gender

Shashikantbhai

Zinzuvadiya

27Jan 1995

Male

Control passes to the

Field
Control passes

Lastname field

to the

Control passes to the

Lastname field
Control passes

Birthdate field

to the

Control passes to the

Birthdate field
Control passes

Gender field

to the Gender

Control passes to the

field
Control passes

Address Field

to the Address

SAL Institute Of Technology And Engineering Research

PASS

PASS

PASS

PASS

Page 74

E-DIARY

6
7

Address

Khodaldham

Control passes tothe

Field
Control passes

City

Soc.,Liliya Road
Amreli

City field
Control passes to the

tothe City field

Control passes PASS

Pincode field

to the Pincode

Control passes to the

field
Control passes

EmailID field

to the EmailID

Pincode

365601

EmailID

Zinzuvadiya.naman3 Control passes to the

field
Control passes

8@gmail.com

to the

ContactNo field

PASS

PASS

PASS

ContactNo
10

ContactNo

8980704168

Control passes to the

field
Control passes

Username field

to the

PASS

Username
11

12

Username

naman1995

Password

naman@123

Control passes to the

field
Control passes

Password field

to the

Control passes to the

Password field
Control passes

SecurityQuestion

to the

Field

SecurityQuesti

PASS

PASS

on
13

SecutityQuesti

Who Is Your

Control passes to the

Field
Control passes

on

Favourite Heroine?

SecurityAnswer field

to the

PASS

SecurityAnsw
14

SecurityAnsw
er

Behaty Prinsloo

User clicks on submit

er field
Account will

PASS

button & account should be created &

be created.

user login
page is
displayed.

8th CE

SAL Institute Of Technology And Engineering Research

Page 75

E-DIARY

Post Conditions: User is validated with database and successfully account is created if admin
will approve his/her status.

8th CE

SAL Institute Of Technology And Engineering Research

Page 76

E-DIARY

Chapter 7
Limitations and
Future Enhancement

LIMITATION: Software or application can be error free but never be failure free i.e. software of application can
be syntactically correct but semantically it can have some shortcomings. Failure is not only
concerned with the syntax error of our program, but is also concerned with our logical error or
requirement omission.

8th CE

We cant view a financial report of past financial year.

It allows only one user therefore it is not provide a high security.
Not have a better search option for finding available product of government.
Special training needed for using the system.
OTP(one time password) code is not possible in localhost server.

SAL Institute Of Technology And Engineering Research

Page 77

E-DIARY

FUTURE ENHANCEMENTS:As we have discussed earlier in previous section, software or application is continuously
changing entity. Software or application should be reflected with new features whenever new
requirements emerge. Evolution and Enhancement are big phases in any softwares or application
lifecycle. We have to project towards some newly emerged and previously ignored functionality
in way to enhance the system.
Once system is implemented and installed into its essential environment, we have to examine
newly emerging requirements, misinterpretation of older requirements, impact due to omission of
some important requirements, and failure of some features.
Try to remove all above limitation from our project.
I will also keep in touch with the citizens and government so that I can understand the

new
demands of them try to apply that features in to my system.
I will try to add more functionality in my system so that user can easily operate this
system with security.
We will also develope an OTP(one time password) code for user login. This will provide
more security to the web application.

8th CE

SAL Institute Of Technology And Engineering Research

Page 78

E-DIARY

Chapter 8
Conclusion

Conclusion
Making this project is a good way to possess knowledge. Though this way I got to know many
things on eDiary. eDiary helps people to add their documents (For Example, Legel Papers,
Driving License, Marksheets etc.) and download it anytime anywhere with the help of internet
access. In future, User will have to aceess by OTP(One Time Password). OTP will provide
maximum security to the system. And I want to thank my internal guide for giving me a
knowledge about this project and i am sure that the knowledge I gained from this project will
help me further. I have tried my best to make this project easy and understandable, but still I
apologize for any kind of discrepancies. Thank you.

8th CE

SAL Institute Of Technology And Engineering Research

Page 79

E-DIARY

Chapter 9
Reference

8th CE

SAL Institute Of Technology And Engineering Research

Page 80

E-DIARY

REFERENCES
BOOKS REFERRED:Title
1.Object Oriented Design

Author
James Rambaugh

Description
Study of activity & state
transition diagram

2.Software Engineering

Pressman

Study of Data Flow

Diagram

3.Database Design

Korth

Study of Entity
Relationship Diagram

4.The Unified Modelling

James Rambaugh

To study the basic UML

concepts.

5.Language Reference

Ivar Jacobson

Manual

6.UML in an Instance

Thomas . A. Pendar

To study UML Diagrams

Implementations.

7.Sams Teach yourself

SQL in 24 hours

Ryan stephens & arie D.

Jones

To study SQL
Implementations

8.JSP for Begineers, SPD

Publication

Ivan Bayross

To study core concepts of

Advance JAVA.

9.Teach yourself Java

Joseph ONeil & Herb

To study Core java.

8th CE

SAL Institute Of Technology And Engineering Research

Page 81

E-DIARY

Schildt

WEBSITES VISITED:www.hitech-in.com
www.edccts.com/in/platforms-and-products/products
www.telegraph.co.uk/
electronic-diary.software.informer.com
www.caclubindia.com
www.lucasheigh-h.schools.nsw.edu.au/e-learning
www.ncbi.nlm.nih.gov/pubmed

8th CE

SAL Institute Of Technology And Engineering Research

Page 82