INDORE

TECHNICAL BLOG

A Project Report Submitted at

Medi-Caps University, Indore
In partial fulfillment of the degree
of
Master of Computer Application

Submitted by

JYOTI RAJAK [EN19CA501040]

ARTI AHIRWAR [EN19CA501022]
JINISHA SHAH[EN19CA501039]

MCA Department
Medi-Caps University Indore-453 331
Aug-Dec, 2020-2021

[Type text]
 Medi-Caps University
A. B. Road, Pigdamber, Rau, Indore-453 331

CERTIFICATE

This is to certify that

Ms. JYOTI RAJAK [EN19CA501040]
Ms. ARTI AHIRWAR [EN19CA501022]
Ms. JINISHA SHAH [EN19CA501022]

have/has completed their/his/her project entitled TECHNICAL BLOG. The

project work is the requirement of Fourth Semester of the degree of Master of
Computer Application (MCA).

Signature:…………. Signature:………….
Name: Mr. Govinda Patil
Mr. Amit Sharma Name: Mr. Anil Patidar
(Project Guide) (Head of Department)

The report has been examined and valued by us.

Signature:…………. Signature:………….
Name: Mr. Gopal Solanki Name:……………...
(Internal Examiner) (External Examiner)

[Type text]
Date: Date:
ACKNOWLEDGEMENT

We are very grateful and thankful to professors of my college. Who give me a good guidance
and gives suggestion about each and every topic which we study and research.

They give me guidance about my current TECHNICAL BLOG project.

We are grateful to our project guides Mr. Govinda Patil and Mr. Amit Sharma for the guidance,
inspiration and constructive Suggestions that helpful us in the preparation of this project.

We are taking this opportunity to express our gratefulness to the Head of Department and All
staff.

We also thank our colleagues and that entire person who has directly helped us in the preparation
of this project.

Thank you to all person involved in this TECHNICAL BLOG project.

[Type text]
 1. INTRODUCTION

1.1 Description of Project:

A blog is a basically a web site which is used for chronological listing of

blog posts.

A blog is the most recent content shown first followed by the previously
updated content.

In a blog there are multiple categories and posts written by number of

authors.
Blogging has become such a mania that a new blog is being created every second of every
minute of every hour of every day. A blog is your best bet for a voice among the online crowd.
Blogs were usually the work of a single individual occasionally of a small group, and often
covered a single subject. . Blog can also be used as a verb, meaning to maintain or add content to
a blog. Blog contain the Information of various things related to Technology, Education, News,
International, Business, Sports, Entertainment and ongoing college activities. The main aim of
this project is to provide data to students in only one site. Students can gather the information
from one site as well as give their feedback and create their own blog. Students can post their
views and thought and analyze themselves. Besides all such core functionalities, the application
also includes features like comments, request, feedback etc. so as to provide a satisfactory user
experience.

(1.2) WHY WE CHOOSE THIS PROJECT:- In recent past time Blogs are store in the paper
files and difficult to search or modify any information, for expanding the Blogs infrastructure,
Awareness of environmental issues or any other issues related to education, health, digital
technology, and search for greater safety give to information to all persons in all age groups and
a new role within the education system, I choose this project. As a result of these project
initiatives phenomenal growth has taken place in all the activities of blogs and any user can share
its information related to any topic to all users.

[Type text]
 (1.3.1) EXISTING SYSTEM:- Existing system is manual system. It requires a lot of file work
to be done. It is a time consuming system. All customer information is maintained manually.
Any searching requires so much effort manually.

There is no way of spreading the information so fast and in cheapest manner. In previous system
all information does not get in one place. Here people can write whatever they want to write.

(1.3.2) DRAWBACKS OF EXISTING SYSTEM:-

a) Data redundancy and formatting: The various files are likely to have different formats and
therefore lead to redundancy and inconsistency.

b) Maintaining registers is costly: Traditionally documents have been stored in batches and they
field in file cabinets and boxes. A numerical system is they assigned. Specifically a consumer
number assigned to organize the files.

c) Error prone: Existing systems are error prone, since manual work is required. More time is
consumed and errors may propagate due to human mistakes.

d) Low security feature: Due to maintenance's of records manually and shared and could view
easily by anyone. Also these could be possible loss of data and confidential information due to
some disaster in the form of fire, theft etc.

1.4.1 Benefits of Project

This is a very simple design and implement. It has got following features:

1. Data can be saved safely.

2.No other person cannot view other person’s detail 

3.Greater efficiency .

4. User friendliness.

5.Minimum time required .

6.Free of cost.

1.4.2Applications

WEBLOG enables the users to create innovative and attractive information with photos in just
few simple steps. The user just needs to upload some images of his choice and can also upload

[Type text]
the information or can select from the given category list. This website will provide a
personalized environment that would contain the data in motion with images.

1.4.3 Scope of the Project

 To use the personal images in greeting our loved ones.

 To use the music of our choice to greet in the language we want.

2. SYSTEM MODULE:-

2.1The modules involved in this project are:

1. User
2. Admin

1. User
In this module:
 User can signup
 User can login
 User can upload multiple images
 User can choose images from database
 User can add information
 User can add comments
 User can select any categories

2. Admin
In this module:
 Admin can block user id
 Admin can resume user id
 Admin can see all pages
 Admin can maintain all records of user
 Admin can maintain all site
 Admin can access and process all requests
 Admin can delete/update/select users.
 Admin Provide all information related to any topic

2.2 Other Functionalities: -

System will also provide other functionalities like:

[Type text]
◦ Feedback
◦ Request
◦ Comment etc.

2.3 Inputs Requirements of the System:-

User Information
Log in Information
Comment Information
Categories Information
Recent Posts Information
Registered Information
Topic Information
Feedback
FAQ
Request

2.4 Output Requirements of the System

• Blog Information
• Novel Information
• Assigned information of users
• Categories information
• FAQ
• Request

2.5 Maintenance: -
The system allows following Maintenance processes
◦ Manage Blogs
◦ Manage Blogs Categories
◦ Manage Recent posts
◦ Manage users
◦ Manage images
◦ Manage Comments
◦ Manage news
◦ Security Questions
◦ Manage Contact us

3. SYSTEM ANALYSIS
[Type text]
3.1 DATA ANALYSIS
Before developing this project, we first analyse existing system of study. In existing
system all greetings are given manually. As we know, now a day computer is used in
every field. We can remove the manual work by using automatic system. We see it first
that if it is feasible or not whether technically, economically, operationally. We test that
whether it properly works or not. Its technical requirements are feasible or not. We
analysed the system properly and then start designing it. After designing, we implement
this project that whether this project works properly or not. After implementing the
project, we check that whether there is any problem for the user while using this project.
Prior to stating whether the system we have to develop is feasible or not we believe that

[Type text]
we should emphasize on what is implied by the word “Analysis”. Analysis is the measure
of how beneficial or practical the development of the system will be to the organization.
It is a preliminary survey for the systems investigation. It aims to provide information to
facilitate a later in-depth investigation.

Types
There are various measures of analysis that helps to decide whether a particular project is
feasible
or not.
These measures include –
Operational Analysis
Technical Analysis
Economic Analysis
Each of these types will be explained in detail throughout the project report

3.1.1Operational analysis
A proposed system is beneficial only if it can be turned into an information
system that will meet the operational requirements of an organization. A system
often fails if it does not fit within existing operations and if users resist the
change. Important issues a systems developer must look into are:
Will the new system be used if implemented in an organization?
Are there any major barriers to implementation or is proposed system
accepted without destructive resistance?
The whole purpose of computerizing it is to handle the work much more
accurately and efficiently with less time consumption. There will be additional
work to be completed, because now the website will have to maintain database
of both their admins as well as their Customers. Compared to the semi -
computerized system the chances of avoiding errors in a computerized system is
much higher because the user need not stress himself unnecessarily resulting in
recklessness. Unlike the semi-computerized system there would be backup data
for all the information concerning the daily transactions occurred. Another
important fact to be regarded is the security control, which is handled by the
system. Since data regarding each Customer is confidential, security is a key
issue. Information falling into the wrong hands could jeopardize the entire
website organization. Unlike in semi-computerized systems, the proposed
system offers adequate control to protect against fraud and embezzlement and
guarantees the accuracy and Security of data and information. This is handled
by the system providing individuals with separate login names and passwords.
The new system is user-friendlier, which enables the end-user to complete
his/her work efficiently and accurately with interest. After taking the above fact
into consideration we can state the operating of the proposed system is feasible.

[Type text]
3.1.2 Economical Analysis
In making recommendations a study of the economics of the proposed system should
be made. Even though finding out the costs of the proposed project is difficult we
assume and estimate the costs and benefits as follows. According to the
computerized system we propose, the costs can be broken down in two categories.
1. Costs associated with the development of the system.
2. Costs associated with operating the system.

3.1.3 System Security

System security is a vital aspect when it comes to developing a system. The system
should ensure the facility of preventing unauthorized personnel from accessing the
information and the data within the system. The system should provide total protection
for each user’s information so that the integrity of data is sustained and also prevent
hackers from hacking the system. The proposed system ensures the security and the
integrity of data. This is done by providing a password login system for each authorized
users. And for example the System Administrator has access to all kinds of information.
By providing this facility information is properly managed and information is protected.
For example the system administrator’s day to day tasks are lessened and easier because
he doesn’t have to have a constant eye on the system and worry about hackers hacking
the system.
The Analysis Phase is where the project lifecycle begins. The Analysis Phase is where
you break down the deliverables in the high-level Project Charter into the more detailed
business requirements. The Analysis Phase is also the part of the project where you
identify the overall direction that the project will take through the creation of the project
strategy documents.
Gathering requirements is the main attraction of the Analysis Phase. The process of
gathering requirements is usually more than simply asking the users what they need and
writing their answers down. Depending on the complexity of the application, the process
for gathering requirements has a clearly defined process of its own. This process consists
of a group of repeatable processes that utilize certain techniques to capture, document,
communicate, and manage requirements. This formal process, which will be developed in
more detail, consists of four basic steps.

1. Elicitation – I ask questions, you talk, I listen

2. Validation – I analyze, I ask follow-up questions
3. Specification – I document, I ask follow-up questions
4. Verification – We all agree

Although gathering requirements is the main focus during the Analysis Phase, there are
other important activities during this phase as well. One is to create a Requirement
Management Plan to define how the requirements will be documented, communicated,

[Type text]
tracked and changed throughout the rest of the project lifecycle. This plan will
specifically address establishing a baseline, a change control process, and a way to track
the requirements through the rest of the lifecycle. Another important activity is to set the
overall direction for work that does not take place until later. This is accomplished
through a series of direction-setting strategy documents. For instance, once you have your
requirements, you can start to set the overall direction for training in a Training Strategy
document. The strategies are at a high-level and are later defined at a lower level before
they are finally implemented toward the end of the project.

4. PLATFORM

TECHNOLOGIES TO BE USED:-
4.1 Hardware:-
1. Processor: - Any basic (minimum core i3)
2. Hard Disk: - 10GB Minimum
3. RAM: 256MB or More

4.2 Software
Software’s used are – NetBeans IDE11.0 , MySQL,
Pre-Conditions to run the software are:-
1. Operating System: - An OS capable of running a modern web browser which supports
NetBeans IDE version 8.2 or higher like Windows XP or Windows.
2. Backend Programming Language: - JAVA
3.Frontend Languages:-Html , CSS , Javascript , Bootstrap.
4. Database: - MYSQL

4.3.1 JAVA:-

Java is a popular programming language, created in 1995.

It is owned by Oracle, and more than 3 billion devices run Java.

[Type text]
It is used for:

 Mobile applications (specially Android apps)

 Desktop applications
 Web applications
 Web servers and application servers
 Games
 Database connection
 And much, much more!

 Java works on different platforms (Windows, Mac, Linux, Raspberry Pi,

etc.)
 It is one of the most popular programming language in the world
 It is easy to learn and simple to use
 It is open-source and free
 It is secure, fast and powerful
 It has a huge community support (tens of millions of developers)
 Java is an object oriented language which gives a clear structure to
programs and allows code to be reused, lowering development costs
 As Java is close to C++ and C#, it makes it easy for programmers to
switch to Java or vice versa.

4.3.2 HTML:
HTML is a language for describing web pages.
HTML stands for Hyper Text Markup Language
HTML is a markup language
A markup language is a set of markup tags
The tags describe document content
HTML documents contain HTML tags and plain text
HTML documents are also called web pages

HTML Tags:
HTML markup tags are usually called HTML tags.
HTML tags are keywords (tag names) surrounded by angle brackets like <html>
HTML tags normally come in pairs like <b> and </b>
The first tag in a pair is the start tag, the second tag is the end tag
The end tag is written like the start tag, with a forward slash before the tag name
Start and end tags are also called opening tags and closing tags
<Tag name>content</Tag name>

4.3.3 CSS:

[Type text]
CSS stands for Cascading Style Sheets
Styles define how to display HTML elements
Styles were added to HTML 4.0 to solve a problem
External Style Sheets can save a lot of work
External Style Sheets are stored in CSS files
CSS Syntax:
A CSS rule has two main parts: a selector, and one or more declarations:
The selector is normally the HTML element you want to style.

Each declaration consists of a property and a value.

The property is the style attribute you want to change. Each property has a value.

4.3.4 MY SQL:-:
MySQL is an open-source relational database management system (RDBMS); in July
2013, it was the world's second most widely used RDBMS, and the most widely used
open-source client–server model RDBMS. The SQL acronym stands for Structured
Query Language.
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. Applications that use the MySQL
database include: TYPO3, Joomla, WordPress, php BB, My BB, Drupal and other
software.
MySQL is a database server.
MySQL is ideal for both small and large applications.
MySQL supports standard SQL.
MySQL compiles on a number of platforms.
MySQL is free to download and use.
The data in MySQL is stored in database objects called tables.
A table is a collection of related data entries and it consists of columns and rows.
Databases are useful when storing information categorically. A company may have a
database with the following tables: "Employees", "Products", "Customers" and "Orders".

[Type text]
4.3.5 JAVASCRIPT: JavaScript is a prototype-based scripting language that is dynamic,
weakly
typed and has first-class functions. It is a multi-paradigm language, supporting object
oriented,
imperative, and functional programming styles. JavaScript was formalized in the
ECMA Script language standard and is primarily used in the form of client-side
JavaScript,
implemented as part of a Web browser in order to provide enhanced user interfaces and
dynamic websites. This enables programmatic access to computational objects within a
host environment. JavaScript's use in applications outside Web pages — for example in
PDF documents, site-specific browsers, and desktop widgets — is also significant. Newer
and faster JavaScript VMs and frameworks built upon them (notably Node.js) have also
increased the popularity of JavaScript for server-side web applications. JavaScript uses
syntax influenced by that of C. JavaScript copies many names and naming conventions
from Java, but the two languages are otherwise unrelated and have very different
semantics.
The key design principles within JavaScript are taken from the self and Scheme
programming languages.
JavaScript was basically used for client-side validation.
JavaScript is compatible with all versions of Microsoft Internet
Explorer and Netscape Navigator.

5. FEASIBILTY STUDY:-

(5.1) INTRODUCTION:-
Feasibility is the measure of how beneficial or practical the development of the system
will be to the organization. It is a preliminary survey for the systems investigation. It
aims
to provide information to facilitate a later in-depth investigation.
The report produced at the end of the feasibility study contains suggestions and reasoned
arguments to help management decide whether to commit further resources to the
proposed
project.
Within the scheduled duration we were assigned to study both the positive and negative
aspects of the current manual system, in which we have come up with a number of
drawbacks that prevent the progress of the clinic if it is continued to function manually.
Having gone through all measures of feasibility we report to the management to figure
out
[Type text]
if the objectives of the new system are met.
For e.g.: –
Is the system within the budget allowed for it?
Will the organization’s needs, be met by the new proposed system as originally
envisaged?

(5.2) TYPES OF FEASIBILITY:

There are various measures of feasibility that helps to decide whether a particular project
is feasible or not. These measures include:
Technical Feasibility
Operational Feasibility
Economical Feasibility
Each of these types will be explained in detail throughout the project report.

(5.2.1) TECHNICAL FEASIBILITY

Based on the outline design of system requirements in terms of inputs, outputs, files,
procedures and staff, the technical issues raised during technical feasibility include:
Does the necessary technology exist to do what is proposed?
Does the proposed equipment have the technical capacity to hold the data required
to use in the new system?
Adequate responses provided by the proposed system?
Is the system flexible enough to facilitate expansion?
Is there any technical guarantee of accuracy, reliability, ease of access and data
security?

(5.2.2) OPERATIONAL FEASIBILITY:-

A system often fails if it does not fit within existing operations and if users resist the
change.
Important issues a systems developer must look into are:
Will the new system be used if implemented in an organization?
Are there major barriers to implementation or is proposed system accepted without
destructive resistance?
If we are considering the performance and response time for each task, it is very much
faster since there is less paper work to be completed. When entering data into the system
to relieve the user from additional work and typing incorrect data, the system provides
options such as combo boxes, check boxes, option buttons and etc. if the users type in
incorrect data they would be informed immediately about the error by the error detection
control.
Another important fact to be regarded is the security control , which is handled by the
system. Since data regarding each user is confidential, security is a key issue. Here, in
this

[Type text]
system, data regarding users is stored in database which can only be accessed by the
authorized administrator.
The new system is more user-friendly, which enables the end-user to complete his/her
work
efficiently and accurately with interest. After taking the above fact into consideration we
can state the operating of the proposed system within the organization is feasible.

(5.2.3) ECONOMICAL FEASIBILITY:-

The proposed system must be justifiable in terms of cost and benefit, to ensure that the
investment in a new/changed system provide a reasonable return.
Even though finding out the costs of the proposed project is difficult we assume and
estimate the costs and benefits as follows.
According to the computerized system we propose, the costs can be broken down to two
categories:
1. Costs associated with the development of the system.
2. Costs associated with operating the system.

.
6. S/W DEVELOPMENT LIFE CYCLE:

Every software development consists several phases, have certain predefined works and
at
the end of each phase document is prepared. This phase is based on certain Software
Development Model.

Software Development Model :

Software engineering is a discipline that integrates process, methods, and tools for the
development of computer software. To solve actual problems in an industry setting,
software engineer or a team of software engineers must incorporate a development
strategy
that encompasses, methods, and tools. This strategy is often referred to as a process
model
or a software-engineering paradigm.
A number of different process models for the software engineering have been proposed,
each exhibiting strengths and weaknesses, but all having a series of generic phases in
common. Some of the commonly used software process models are:
The linear sequential model
The prototyping model
The RAD model
The incremental model
[Type text]
The spiral model
A particular process model for software engineering is chosen on the nature of the project
and the application at hand, the methods and the tools to be used, and the controls are
required.
All software development can be characterized as a problem-solving loop in which four
distinct stages are encountered:
Status Quo
Problem Definition
Technical Development
Solution Integration

Software Requirement Analysis:

The requirements gathering process is intensified and focused specifically on software.
To
understand the nature of the program(s) to be built, the software engineer (“analyst”)
must
understand the information domain for the software, as well as required function,
behavior,
performance, and interfacing. Requirements for the both the system and the software are
documented and reviewed with the customer.

Design:
Software design is actually a multi-step process that focuses on four distinct attributes of
a
program: data structures, software architecture, interface representations, and procedural
(algorithm) detail. The design process translates requirement into a representation of the
software that can be assessed for quality before code generation begins.

Code Generation:
The design must be translated in to a machine-readable form. The testing process focuses
on the logical internals of the software, assuring that all statements have been tested and
on the functional externals that is, conducting tests to uncover errors and ensure that
defined inputs will produce actual results that agree with required results.

Testing:
Once code has been generated, program testing begins. The testing process focuses on the
logical internals of the software, assuring that all statements have been tested and on the
functional externals that is, conducting tests to uncover errors and ensure that defined
inputs will produce actual results that agree with required results.

[Type text]
Maintenance
Software will undoubtedly undergo change after it is delivered to the customer (A
possible
exception is embedded software).Change will occur because errors have been
encountered,
because the software must be adapted to accommodate change in its external environment
(e.g. A change required because of a new operating system or peripheral device), or
because the customer requires functional or performance enhancements.

Fig. shows SDLC phases

7 .DATA FLOW DIAGRAM (DFD):-

Data flow diagrams model the flow of data into, through, and out of an information
system:
• Show the processes that change or transform data
• Show the movement of data between processes

[Type text]
• Represent a system as a network of processes which transform data flowing between
them.

7.1 CONTEXT DATA FLOW DIAGRAM

[Type text]
LOGIN

MANAGE USER

[Type text]
8. System Requirements
The only link to an external system is the link to the MySQL Database to verify the
membership of a Customer and to store all the data provided by the customer . The
Admin
believes that a member is much more likely to be an effective reviewer and has imposed
a membership requirement for a Reviewer. The Database fields of interest to the Admin
are member’s name, membership (ID) number, contact numbers and e-mail addresses.
The details of new members signing up for the events can be added in the list of the
previous members and the amendments can be made to the list accordingly.
The requests of each customer can be inserted in the database so that the admin can
process it for further use.

8.1 Functional and Data Requirements

The requirements gathering process is intensified and focused specifically on software.
To understand the nature of the program(s) to be built, the software engineer (“analyst”)
must understand the information domain for the software, as well as required function,
behavior, performance, and interfacing. Requirements for the both the system and the

[Type text]
software are documented and reviewed with the customer.

8.2Non-Functional Requirements
The software developed here assumes the use of PHP for connection between the Front
End and the database. The speed of the User’s connection will depend on how fast they
approach the site. The Admin will run the users requests and will have an access to
database.
Reliability- The system is reliable i.e. it’s well trusted.
Security- The system is well secured, i.e. admin and user both have their unique
ID and password to login into the system.
Maintainability- Our project is well maintained with all required features
involved.
Portability- The system is portable i.e. it can work on any other system of the
admin.
The only requirement is the Internet connection.

8.3 Use Case Diagram

Use cases are used during the analysis phase of a project to identify system
functionality. They separate the system into actors and use cases. Actors represent
roles that are played by users of the system. Users may be humans, other computers,
or even other software system.

Customer Use Case

Use Case: Upload Data
Brief Description:

A use case diagram at its simplest is a representation of a user’s interaction with the
system that shows the relationship between the user and the different use cases in which the user
in involved. A use case is a methodology used in system analysis to identify, clarify, and
organize system requirements.

Use case Diagram Notation

System: Draw your system's boundaries using a rectangle that contains use cases. Place actors
outside the system's boundaries.

System Name System Name

[Type text]
 Use Case: Draw use cases using ovals. Label the ovals with verbs that represent the system's
functions.

Use case Use case

Actors: Actors are the users of a system. When one system is the actor of another system, label
the actor system with the actor stereotype.

Actor

Relationships: Illustrate relationships between an actor and a use case with a simple line.
For relationships among use cases, use arrows labeled either "uses" or "extends.

signup

LOGIN

Upload photos and videos of

event

manage photos and

videos of event

View Like

User
View comments by
[Type text] Facebook plugin

logout
 Figure 8.3.a : Use case diagram

LOGIN

MANAGE USERS

MANAGE
PHOTOS

MANAGE
VIDEOS

MANAGE
ADMIN EVENTS

[Type text]
MANAGE
NOTIFICATION
 Figure 8.3.b : Use case diagram

8.4 Activity Diagram

Activity diagram is defined as a UML diagram that focuses on the execution and flow of the
behavior of a system instead of implementation. It is also called object-oriented flowchart.
Activity diagrams consist of activities that are made up of actions which apply to behavioral
modeling technology.

Activity Diagram Notations

 Initial states: The starting stage before an activity takes place is depicted as the initial
state.

Initial-State

 Final states: The state which the system reaches when a specific process ends is known
as a Final State.
Final-State

 State or an activity box:

Action 1 Action -box

[Type text]
  Decision box: It is a diamond shape box which represents a decision with alternate paths.
It represents the flow of control.

Decision- box

8.5 ER Diagram

An entity relationship model, also called an entity-relationship (ER) diagram, is a graphical

representation of entities and their relationships to each other, typically used in computing in
regard to the organization of data within databases or information systems.

[Type text]
9. System Design
[Type text]
Database
Data base is used to store the relevant information of the individuals. A database is a
collection of rows and columns in which rows indicates the tuple and column indicates
the
domain of table. Database design is the process of producing a detailed data model of a
database. This logical data model contains all the needed logical and physical design
choices and physical storage parameters. Need to generate a design in a data definition
language, which can then be used to create a database. A fully attributed data model
contains detailed attributes for each entity. The term database design can be used to
describe many different parts of the design of an overall database system. Principally, and
most correctly, it can be thought of the logical design of the relation of the base data
structures used to store the data. In the relational model these are the classes and named
relationships. However, the term database design could also be used to apply to overall
process of designing, not just the base data structure, but also the forms and queries used
as part of the overall database application within the database management system
(DBMS).

Fig. shows database of weblog

It includes eight tables namely
Admin
Blogs
Category
Comment
Contact
User registration.

USER TABLE

[Type text]
CATEGORY TABLE

LIKED TABLE

[Type text]
POST TABLE

10.OUTPUT

(INTERFACE DESIGN)
ADMIN REGISTRATION PAGE

[Type text]
ADMIN LOGIN PAGE

In this page admin LOGIN with valid username and password

[Type text]
ADMIN HOME PAGE
In this admin page and user will redirect to this page after log in.

PROFILE PAGE

[Type text]
BLOG PAGE
In this admin can add blog and choose images from folder and select any
Category related to blog.

POST PAGE

[Type text]
COMMENT PAGE

In this page, Facebook by plugin.

11. System Implementation

11.1 Implementation
Implementation is the stage in the project where the theoretical design is turned into the
working system and is giving confidence to the new system for the users i.e. will work
efficiently and effectively. It involves careful planning, investigation of the current
system
and its constraints on implementation, design of method to achieve the changeover, an
evaluation, of change over methods. A part from planning major task of preparing the
implementation is education of users. The more complex system is implemented, the
more

[Type text]
involved will be the system analysis and design effort required just for implementation.
An
implementation coordinating committee based on policies of individual organization has
been appointed. The implementation process begins with preparing a plan for the
implementation for the system. According to this plan, the activities are to be carried out,
discussions may regarding the equipment has to be acquired to implement the new
system
Implementation is the final and important phase. The most critical stage is in achieving a
successful new system and in giving the users confidence that the new system will work
and be effective. The system can be implemented only after thorough testing is done and
if it found to working according to the specification. This method also offers the greatest
security since the old system can take over if the errors are found or inability to handle
certain types of transaction while using the new system.
The major elements of implementation plan are test plan, training plan, equipment
installation plan, and a conversion plan.
There are three types of implementation:
Implementation of a computer system to replace a manual system.
Implementation of a new computer system to replace an existing system.
Implementation of a modified application to replace an existing one, using
the same computer.
Successful implementation may not guarantee improvement in the
organization using the new system, but improper installation will prevent it.
It has been observed that even the best system cannot show good result if the
analysts managing the implementation do not attend to every important
detail. This is an area where the systems analysts need to work with utmost
care.

12.System Testing
System testing is a critical element of quality assurance and represents the
ultimate review of analysis, design and coding. Test case design focuses on a set of
techniques for the creation of test because that meet overall testing objective. When a
system is developed it is hoped that it performs properly. The main purpose of testing an
information system is to find the errors and correct them. The scope of system testing
should include both manual and computerized operations. System testing is
comprehensive
evaluation of the programs, manual procedures, computer operations and controls.
System testing is the process of checking whether the developed system is working
according to the objective and requirement. All testing is to be conducted in accordance
to the test conditions specified earlier. This will ensure that the test coverage meets the
[Type text]
requirements and that testing is done in a systematic manner.

TEST CHARACTERS :
1. A good test has a high probability of finding an error.
2. A good test is not redundant.
3. A good test should be “best of breed”.

Table 12.1 Levels Of Testing

BLACK BOX TESTING:

The method of Black Box Testing is used by the software engineer to derive the required
results of the test cases:
1. Black Box Testing alludes to test that are conducted at the software interface.
Client Needs Acceptance Testing
Requirements System Testing
Design Integration Testing
Code Unit Testing
2. A Black Box Test examines some fundamental aspect of a system with little regard for
the internal logic structure of the software.
3. A limited number of important logical paths can be selected and exercised.
Black box testing was performed to find errors in the following categories: -
Incorrect or missing functions
Graphics error.
Errors in data in binary format.
Error in data in integer format.
File error.
Pointer error
Variable error

WHITE BOX TESTING:

White Box Testing is sometimes called Glass Box Testing. Using White Box Testing
methods the software engineer can derive the following test cases:
1. Guarantee that all independent paths within a module have been exercised at least
once.
2. Exercise all logical decisions on their true and false sides.
3. Execute all loops at their boundaries and within their operational bounds.
In White Box Testing efforts were made to handle the following:-
• Number of input parameters equal to number of arguments.
•Parameters and arguments attributes match.

[Type text]
• Number of arguments transmitted is called modules equal to attributes of parameters.
•Unit system of argument transmitted is called modules equal unit system of parameter.
• Number of attributes and order of arguments to build in functions correct.
•Any references to parameters not associated to build in functions correct.
•Input only arguments altered.
•Global variable definition consistent across module.
•Files attributes correct.

Unit Testing
Code testing was carried out to see the correctness of the logic involved and the
correctness
of the modules. Tests were conducted based upon sample and live data as well. All the
modules are checked separately for assuming correctness and accuracy in all the
calculations.

Specification Testing
It examines the specification stating about what program should do and how it performs
under various conditions. This testing strategy is better strategy since it focuses on the
way
the software is expected to work.
Integration Testing
The next level testing that was performed is often referred to as integration testing.
During
this phase many unit tested modules were combined into subsystems, which were then
tested. The goal here was to see if modules can be integrated properly. Here the emphasis
was on testing interfaces between different constituent modules of system.

Functionality Testing
Here the entire software system was tested. The reference document for this process is
the
requirements document, and the goal was to see if software solution meets its
requirements.
This level of testing is essentially a validation exercise, and in many situation it is the
only
validation activity.

Stress Testing
Proxy server developed for the specified purpose was testing under heavy load, i.e. a
large
no. of clients were made to sit in lab and were asked to send requests for logging in and
then were asked to request for text on internet. System responded to request as desired.

[Type text]
Acceptance Testing
Acceptance was performed in the real environment with realistic data of the client to
demonstrate if the software developed is working satisfactorily. Here the main focus was
on the external behavior of the system; the internal logic of the program was not
emphasized.

Test Data and Test Cases

The primary objective of test case design is to derive a set of tests that have the highest
likelihood of uncovering errors in software. The test case specification is the major
activity
in the testing process. Careful selection of test cases that satisfy the criterion on approach
specified is essential for proper testing. Various characteristics of test cases that are
required for portal are:
A good test has a high probability of finding an error.
A good test is not redundant.
A good test should be “Best of Breed”.
A good test should be neither too simple not too complex.

Overview of Testing
1. Testing: Testing involves executing the program (or part of it) using sample data and
inferring from the output whether the software performs correctly or not. This can be
done
either during module development (unit testing) or when several modules are combined
(system testing).

2. Direct Testing: Defect testing is testing for situation where the program does not meet
its functional specification. Performance testing tests a system's performance or reliability
under realistic loads. This may go some way to ensuring that the program meets its
nonfunctional
requirements.

12.2Debugging
Debugging is a cycle of detection, location, repair and test. Debugging is a hypothesis
testing process. When a bug is detected, the tester must form a hypothesis about the cause
and location of the bug. Further examination of the execution of the program (possible
including many returns of it) will usually take place to confirm the hypothesis. If the
hypothesis is demonstrated to be incorrect, a new hypothesis must be formed. Debugging
tools that show the state of the program are useful for this, but inserting print statements
is
often the only approach. Experienced debuggers use their knowledge of common and/or
[Type text]
obscure bugs to facilitate the hypothesis testing process. After fixing a bug, the sys tem
must be reset to ensure that the fix has worked and that no other bugs have been
introduced.
This is called regression testing. In principle, all tests should be performed again but this
is often too expensive to do.

Test Planning
Testing needs to be planned, to be cost and time effective. Planning is setting out
standards
for tests. Test plans set out the context in which individual engineers can place their own
work. Typical test plan contains:

Interface Testing: Usually done at integration stage when modules or sub-systems are
combined. Objective is to detect errors or invalid assumptions about interfaces between
modules. Reason these are not shown in unit testing is that test case may perpetuate same
incorrect assumptions made by module designer. Particularly important when OO
development has been used.
Four Types Of Interface
1. Parameter: data (or occasionally function references) passed from one unit to another.
2. Shared memory: block of memory shared between units (e.g. global variable) .One
places data there and the other retrieves it.
3. Procedural: Object-Oriented or abstract data type form of interface, encapsulating
several procedures.
4. Message passing: one sub-system requests a service by passing a message. Client-
server
interface also used by some OO architectures.

Typical levels of testing:

Acceptance testing - whole system with real data (involve customer, user, etc) .Alpha
testing is acceptance testing with a single client (common for bespoke systems). Beta
testing involves distributing system to potential customers to use and provide feedback.
In,
this project, Beta testing has been followed. This exposes system to situations and
errors that might not be anticipated by us.

12.3 Maintenance

Once the website is launched, it enters the maintenance phase. All systems need
maintenance. Maintenance is required because there are often some residual errors
remaining in the system that must be removed as they are discovered. Maintenance

[Type text]
involves understanding the effects of the change, making the changes to both the code
and
the documents, testing the new parts and retesting the old parts that were not changed.
Maintenance is mainly of two types:
1. Corrective Maintenance
2. Adaptive Maintenance

Corrective Maintenance
Almost all software that is developed has residual errors or bugs in them. Many of these
surfaces only after the system have been in operation, sometimes for a long time. These
errors once discovered need to be removed, leading to the software to be changed. This is
called Corrective Maintenance.

Adaptive Maintenance
Even without bugs, software frequently undergoes change. The software often must be
upgraded and enhanced to include more features and provide more services.

Perfective Maintenance - This includes modifications and updates done in order to keep
the software usable over long period of time. It includes new features, new user
requirements for refining the software and improve its reliability and performance.

Preventive Maintenance - This includes modifications and updating to prevent future

problems of the software. It aims to attend problems, which are not significant at this
moment but may cause serious issues in future.

Cost of Maintenance
Reports suggest that the cost of maintenance is high. A study on estimating software
maintenance found that the cost of maintenance is as high as 67% of the cost of entire
software process cycle.
On an average, the cost of software maintenance is more than 50% of all SDLC phases.
There are various factors, which trigger maintenance cost go high, such as:

Software-end factors affecting Maintenance Cost

Structure of Software Program
Programming Language
Dependence on external environment
Staff reliability and availability

[Type text]
13. How to Contact us & about us
Contact Us
If user want to contact us he/she can contact us through the contact us option in the main
menu. Our E-mail id and contact no. is provided. User can contact us through any of the
above links.
About Us
If user want to know anything about this website then he/she can know about us through
the about us option in the main menu. Our website’s brief information is provided there.

14. Conclusion

While developing the system a conscious effort has been made to create and
develop a software package, making use of available tools, techniques and
resources – that would generate a proper system for cases.
While making the system, an eye has been kept on making it as user-friendly.
As such one may hope that the system will be acceptable to any user and will
adequately meet his/her needs. As in case of any system development process
where there are a number of short comings, there have been some
shortcomings in the development of this system also.

15. Bibliography

Core Java Complete Reference – Herbert Schildt

SQL Practical guide for developers –Gregory D. Speegle
E-Study:
www.wikipedia.com
www.javatpoint.com
Text Books:
Java2: The Complete Reference-Herbert Schildt

[Type text]
[Type text]
[Type text]
[Type text]
[Type text]
[Type text]