1.1background Introduction

Download as doc, pdf, or txt
Download as doc, pdf, or txt
You are on page 1of 37

zWebbed

Chapter 1
Introduction
1.1Background Introduction
The purpose of a website is to inform your visitors about current business offerings and
keep them updated of the latest addition and the easiest way to achieve all this is through
the use of a CMS. Descriptive and well thoughtful informative content about your
products and services is the key that can make your business grow to new heights. To
attract and retain your potential customers you have to provide the fresh and up to date
content to your visitors.
Content Management System is a complex web application containing tools which enable
you to add, update & delete pages and content on your website from within a web
browser and without any understanding of HTML or other similar technologies. So if you
have an ecommerce site CMS is the best solution that you can give your business.
Therefore, by having fresh and updated content on your website you can attract and retain
the prospective customers. Search engine optimized content increase your chances to get
free traffic and helps you to transform your traffic into your customers.
zWebbed allows developing web pages dynamically in the way the user wants. Our
project has been undertaken in a professional manner, so that the project is not only going
to be of academic in nature but also ultimately a useful cloud based web application to be
used .
The system provides different templates, which will decide the format of the page i.e.
where an image is placed, where logo is placed etc. When the user selects any templates,
automatically it has to design a page according to the selected template. The
administrator is responsible to add templates.

zWebbed

1.2Motivation
Nowadays cloud is rapidly becoming the new normal in industries. Software as a
Service (SaaS) is a reliable alternative to the standard software installation. With the SaaS
model, you do not pay for the software license, but for the possibility of using it for an
agreed time period, with lower costs and high flexibility.
According to IDC, 27.8% of the enterprise software market will be SaaS by the end of
2018. The estimated value of the SaaS market is more than $50.8 billion. Gartner defines
SaaS as software that is owned, delivered and managed remotely by one or more
providers. The provider delivers software based on one set of common code and data
definitions that is consumed by all contracted customers at any time on a pay-for-use
basis or as a subscription based on use metrics.

1.3 Problem Definition


A customer needs to visit a web designing company to create their websites whether it is
small or big. They have to interact with the designer or related person to start the process
and provide feedback till the end. Some people feel this it would be easier if they can
create a website themselves but they are not trained. Therefore, we are introducing our
platform zWebbed where people having zero designing skill can create their own
websites.

1.4 Objective
The objectives of our project are as follows:i) Allow users to create their personal website with zero programming and designing
skills.
ii) Provide cloud hosting service.

zWebbed

1.5 Scope
Our project zWebbed will have the scope of SaaS based cloud application. The users of
this system are customers who want to create a website within few minutes. The
functions of the system are stated below:i) A user will be able purchase a plan and then select a suitable template for their website.
ii) A user will be able to add their contents via system.
iii) Host websites on our cloud servers and download templates.

zWebbed

Chapter 2
Literature Review
2.1 History
Looking back over the history of CMS development it seems there are three clear phases
in the time since the late 1990s when the first internet websites were hard coded and
published online.
2.1.1 The early years
Claims about what or who wrote the first CMS are many and varied including Roxen
(1994) and Blitzen (mid 90s), Ingeniux (1999) and Vignette. The main features were a
very structured development environment and you had to use tags and templates because
there was no WYSIWYG. Clients had to be pretty technology-savvy, if you couldnt do
HTML you probably werent going to edit your site. Happily they are all now quietly
consigned to the site redevelopment waste basket. Most were written by web design
agencies rather than software companies and every agency had their own - until they
worked out that it was probably not a core skill and so with the dot.com crash came a
refocus as most marketing agencies pulled back from coding development and focusing
on design [which most did better than code anyway]. Vern Imrich frorm Percussion puts
it neatly Back in the late 90s the concept was too undefined - part app dev, part portal
and tons of Web 1.0 bloat, you name it, you could build it! [1]
2.1.2 Rebuilding during the noughties
The second stage of CMS development was led by software houses who took over the
functionality ideation and started to build the grandaddies of todays CMS. Key features
which were slowly built in included WYSIWYG text editing; search, improved HTML
and the addition of features like survey tools and podcasts. [2]
The growth of the specialists was led by early stage leader, RedDot and others like
DotNetNuke and Mambo which later metamporphosed into Joomla and like DotNetNuke
is still around today.
4

zWebbed
This was when the open source movement got started, deterred by the multi-thousand
dollar fees for enterprise software and so a split between paid and free applications
developed which continues to this day.
Choice burgeoned and CMS got feature-rich. Every website needed a CMS and so web
agencies needed both the techie skills as well as designers to adapt each client site into
the CMS frameworks.
Suddenly, software coders ruled the roost and their skill enabled many designers to access
web platforms but conversely, this limited the range of designs that were possible.
As the opensource movement got going, the skills of coders and designers divided on one
side into templates for popular open source apps like Wordpress coming to the fore. Built
by coders but implemented by designers by the end of this period many agencies were
using designers to create the site layouts but having their work put into place by coders.
Today the industry split into enterprise document management (EDMS) and web content
management (WCMS) which itself is further divided into free, opensource and paid-for
solutions. The number of CMS systems available is high and has become even more
segmented. Each application is targeted broadly at enterprise, mid-sized companies or
small firms/private use; the bottom end dominated by free software like Wordpress,
Joomla, Drupal and SilverStripe. Coders favorite free applications include Umbraco,
Contao and ModX; a proliferation of open source offerings now has its own annual
market share report and active global developer communities. [3]
2.1.3 Getting to the next stage for CMS
We are once again at a turning point for content management but this time the pivot is
based on an individuals ability to code versus their skill at design.
This shift has been brought about by some well publicized hacks on open source
platforms leading commentators to question the appropriateness of open source for
commercial use. Its ubiquity it has become a haven for hackers keen to earn their spurs
by disabling sites and inserting malware into ecommerce platforms to harvest credit card
details. [4]
At the same time, a move away from coders and back to design-led website development
has been enabled by the new third generation of web CMS tools. The key features are
5

zWebbed
1.

a hosted platform

2.

resold exclusively by design agencies or affiliates

3.

integration with CRM, database, e-commerce, email as modules not plug-ins

4.

Modular development so theres minimal custom coding for integration

5.

SaaS pricing model including reseller/affiliate earnings

Becoming designer-led illustrates the growing separation for the CMS industry between
software written for professional web designers and those for the open source coder
market or blog-writing consumers and the variation in expertise and expectations for
support offerings.
What in the past had to be done with server-side, back-end code is now achievable with
front end client-side code. This is highly accessible and should now be part of the
competency of a modern website designer. [5]

2.2 Software as a Service


Software as a service (or SaaS) is a way of delivering applications over the Internetas a
service. Instead of installing and maintaining software, you simply access it via the
Internet, freeing yourself from complex software and hardware management. SaaS
applications are sometimes called Web-based software, on-demand software, or hosted
software. Whatever the name, SaaS applications run on a SaaS providers servers. The
provider manages access to the application, including security, availability, and
performance.
The ability for each user to easily customize applications to fit their business processes
without affecting the common infrastructure. Because of the way SaaS is architected,
these customizations are unique to each company or user and are always preserved
through upgrades. That means SaaS providers can make upgrades more often, with less
customer risk and much lower adoption cost.

Chapter 3
Requirement Analysis
6

zWebbed

3.1 Project Requirements


3.1.1 External Interface Requirements
External interface requirements specify hardware, software, or database elements with
which a system or component must interface. This section provides information to ensure
that the system will communicate properly with external components.

3.2.1 User Interface

All the users will see the same page when they enter in this website. This page
asks the users a username and a password.

After being authenticated by correct username and password, user will be redirect
to their corresponding profile where they can do various activities.

The user interface will be simple and consistence, using terminology commonly
understood by intended users of the system. The system will have simple
interface, consistence with standard interface, to eliminate need for user training
of infrequent users.

3.2.2 Hardware Interface

No extra hardware interfaces are needed. The system will use the standard
hardware and data communication resources. This includes, but not limited to,
general network connection at the server/hosting site, network server and network
management tools.

3.2.3 Software Interface

Operating System: Microsoft Windows, Linux, Mac OS

Frontend: HTML5, CSS3, JavaScript

Backend: PHP(Laravel Framework)

Database: MySQL
7

zWebbed

Web Browser: Firefox, Chrome, Safari, etc.

3.2.4 Communication Interface:

This system use communication resources which includes but not limited to,
HTTP protocol for communication with the web browser and web server and
TCP/IP network protocol with HTTP protocol.

This software will communicate with the database that created to hold website
information can contact with server side through HTTP protocol by means of a
function that is called HTTP Service. This function allows the application to use
the data retrieved by server to fulfill the request fired by the user.

3.1.2 Functional Requirements


These are statements of services the system will provide, how the system reacts to
particular inputs, and how the system behaves in particular situations. It specifies the
software functionality that the developers must build into the product to enable users to
accomplish their tasks.
When the requirements document for the software to be developed is available the design
activity begins. The main aim of design process is to produce a model or representation
of the system, which can be used later to bind the system. The produced model is called
design of the system. A system design is a top down approach to minimize complexity
and make a problem manageable by subdivided it into smaller segments.
The most changing phase of the system development of life cycle is system design. It
refers to the technical specification that will be applied in implementing the candidate
system. The design phase is a translation from user oriented document to document
oriented to programmers. The potential objects are thoroughly analyzed. Class hierarchies
are to check whether the system is behaving the way it has to. There after the classes are
individually tested and subsequently they are integrated from the overall system. This
level focuses on deciding which modules are needed for system the specifications for
those modules and how these modules are that interconnected.

3.1.3 Non Functional Requirement

zWebbed
A non-functional requirement is a requirement that specifies criteria that can be used to
judge the operation of a system, rather than specific behaviors. This should be contrasted
with functional requirements that define specific behavior or functions.

3.4.1 Usability

The system provides a help and support menu in all interfaces for the user to
interact with the system.

The user can use the system by reading help and support.

3.4.2 Security

The system provides username and password to prevent the system from
unauthorized access.

3.4.3

The staffs password must be greater than eight characters.

Performance
The system response time for every instruction conducted by the user must not
exceed more than a minimum of 10 seconds.

The system will have high performance rate when executing users input and
should be able to provide response within a short time span usually 50 second for
highly complicated task and 20 to 25 seconds for less complicated task.

3.4.4 Availability

The system will always be available for access at 24 hours, 7 days a week. Also in
the occurrence of any major system malfunctioning, the system should be
available in 1 to 2 working days, so that business process is not severely affected.

3.2 Feasibility Study


9

zWebbed
All projects are feasible when given unlimited resources and infinite time. It is both
necessary and prudent to evaluate the feasibility of a project at the earliest possible time.
Feasibility and risk analysis is related in many ways. If project risk is high, the feasibility
of producing quality software is reduced. The development of a computer based system is
more likely to be plagued of resources and difficult delivery dates feasibility study is not
warranted for a system in which economic justification is obvious, technical risk is low,
few legal problems are expected, and no reasonable alternative exists. Three key
considerations are involved in the feasibility analysis-economic, behavioral and
operational
3.2.1 Operational Feasibility
Proposed projects are beneficial only if they can be turned into information system that
will meet organization's operating requirements. People are inherently resistant to change
and computers have been known to facilitate change .An estimate should be made of how
strong a reaction the user staff is likely to have towards Development of a computerized
system .It is common knowledge that computer installations have something to do with
turnover, transfers, retraining and changes in job status.
This system reduces the workload of the front office executive and gives a clear picture
of the total network that makes the front office executed happier than before. Therefore
there is no resistance to using the system. So the management would readily use this
package. Hence this system is operationally feasible.

3.2.2 Technical Feasibility


The technical issues raised during the feasibility stage of investigation include existence
of necessary technology to support the proposed system, the prospects of ability to
expand the system if developed etc. - Technical feasibility centers on the existing system
10

zWebbed
and to what extent it can support the proposed addition. For e.g. If the current system is
operating at 80% capacity then running another application could overload system or
requires additional hardware. This involves financial considerations to accommodate
technical enhancements. If the budget is a serious constraint, the project is judged not
feasible. To reduce the costs the investment required for this project is so less .So this
project is technically feasible.
3.2.3 Economic Feasibility
Among the most important information contained in feasibility study is cost-benefit
analysis-an assessment of the economic justification for a computer based system project.
Cost-benefit analysis delineates costs for project development and weighs them against
tangible (i.e., measurable directly in dollars) of a system. Economic feasibility is the most
frequently used method for evaluating the effectiveness of equipment information system.
More commonly known as cost/benefit analysis, the procedure is to determine the
benefits and savings that are expected from equipment information system and compare
them with costs. If benefits outweigh cost, then decision is made to design and implement
the system. Otherwise, further justification or alternation in the proposed system will
have to be made if it is to have a chance of being approved. This package reduces the
operating costs in terms of time by automating the process. A chance of errors is
minimized and the benefits to the organization are more. Hence this package is
economically feasible.
As this package is technically, economically and operationally feasible, this system is
judged feasible.

Chapter 4
System Design and Methodology
4.1

The Waterfall Model


11

zWebbed

Fig: The Waterfall Model

The waterfall model is a popular version of the systems development life cycle model for
software engineering. Often considered the classic approach to the systems development
life cycle, the waterfall model describes a development method that is linear and
sequential. Waterfall development has distinct goals for each phase of development.
Imagine a waterfall on the cliff of a steep mountain. Once the water has flowed over the
edge of the cliff and has begun its journey down the side of the mountain, it cannot turn
back. It is the same with waterfall development. Once a phase of development is
completed, the development proceeds to the next phase and there is no turning back.
In Royce's original waterfall model, the following phases are followed in order:
1. System and software requirements: captured in a product requirements document
2. Analysis: resulting in models, schema, and business rules
3. Design: resulting in the software architecture
4. Coding: the development, proving, and integration of software
5. Testing: the systematic discovery and debugging of defects

12

zWebbed
6. Operations: the installation, migration, support, and maintenance of complete
systems
Thus the waterfall model maintains that one should move to a phase only when its
preceding phase is reviewed and verified.
Various modified waterfall models (including Royce's final model), however, can include
slight or major variations on this process. [3] These variations included returning to the
previous cycle after flaws were found downstream, or returning all the way to the design
phase if downstream phases deemed insufficient.

4.2

System Design

When the requirements document for the software to be developed is available the design activity
begins. The main aim of design process is to produce a model or representation of the system,
which can be used later to bind the system. The produced model is called design of the system. A
system design is a top down approach to minimize complexity and make a problem manageable
by subdivided it into smaller segments.
The most changing phase of the system development of life cycle is system design. It refers to the
technical specification that will be applied in implementing the candidate system. The design
phase is a translation from user oriented document to document oriented to programmers. The
potential objects are thoroughly analyzed. Class hierarchies are to check whether the system is
behaving the way it has to. There after the classes are individually tested and subsequently they
are integrated from the overall system. This level focuses on deciding which modules are needed
for system the specifications for those modules and how these modules are that interconnected.

Process
es

Databa
se

The process shows a transformation or


manipulation of dataflow with in a system. A
process transforms in coming data flow into out
going data flow.

A database is a holding place for information


within the system it is represented by an open
ended narrow rectangle.

External entities are outside the system but they


either supply input data into the system or use
13

zWebbed
External entity

the system output. External entities are


represented by rectangle.

a dataflow shows flow of information form


source to destination a data flow represented by
a line, with arrow heads showing the direction
of the flow.

Dataflow

Data store

Table: Symbols used in Data flow diagram

4.3

Description of the program

The customer switch diagram for online Web Builder is shown in the figure below.
The input and output of this section is shown in the diagram, however no of details about the
function of the online Web builder system is given here. Using this as a starting point, a logical
DFD of the system is developed.

4.2.1 Context flow diagram:


The environment in which the software used is depicted in this picture. The CFD shows
the external entity action on the software is shown here in CFD as a single process.

14

zWebbed

2.2 Top level DFD


Top level DFD shows the functional component in the software package. Each component
shown in the top level DFD is described in the subsections of 2.3

15

zWebbed

2.3 Description of the components


2.3.1 Functional component 1: Members
Input: The member inputs user id and password.
Process definition: Checks id and password is valid or not
Output: Views members web account

16

zWebbed

17

zWebbed
2.3.2 Functional component 2: Admin

Input: Users can add webpages,photos,setting,webaccount etc.


Process definition: It updates new records to website.
Output:View uploaded website.

18

zWebbed

2.3.3 Functional component 3: Webpage

Input: Users can add webpages,photos,setting,webaccount etc.


Process definition: It updates new records to website.
Output: Views uploaded website.

4.3 Sequence Diagram


19

zWebbed

Fig: Sequence Diagram for Customer

Fig: Sequence Diagram for Administrator


20

zWebbed

4.4 Database Design


Database Name: zwebbed
This Database contain following tables.
Table Name: user
Field

Type

Null Description

UserId

int(10)

No

User Id

Username varchar(50) No

Enter User name

Password

Enter Password

varchar(20) No

Table Name: admin


Field

Type

Null Description

adminid

int(11)

No

Administrator id

adminname varchar(15) No

Enter administrator name

username

varchar(30) No

Enter the username to login

password

varchar(30) No

Input the pass word to login

Table Name: contact


Field

Type

Null Description

contactid

int(10)

No

Contact Id

contactname varchar(30) No

Contact name

message

Write message

text

No

21

zWebbed

Field

Type

Null Description

Id

int(11)

No

Status Id

UserId

int(10)

No

User Id

No

Total visitors

Totalvisitors int(255)
Lastvisitor

varchar(50) No

Recent visitors

Field

Type

Null Description

id

int(11)

No

title

varchar(30) No

Page Id
Title of the page

pagename varchar(30) No

Name of the page

messages

Write message

text

No

Table Name: manage pages

Table Name: registration


Field

Type

Null Description

User_id

int(11)

No

Desired_address

varchar(30) No

website name

Email_id

varchar(30) No

E-mail Id

Desired_password varchar(20) No

password

User id

22

zWebbed

4.5 ER Diagram
Data Objects: A data object is a representation of almost any composite information that
must be understood by the software. Composite information refers to something that has
a number of different properties or attributes. A data object can be an external entity (e.g.
anything that produces or consumes information), a thing (e.g. a report or a display), an
occurrence (e.g. telephone call) or event (e.g. an alarm), a role (e.g. salesperson), an
organizational unit (e.g. accounting department), a place (e.g. a warehouse), or structure
(e.g. a file).
Attributes: Attributes define the properties of a data object and take on one of the three
different characteristics. They can be used to (1) name an instance of the data object, (2)
describe the instance, or (3) make reference to another instance in another table.
In addition, one or more of the attributes must be defined as an identifier-that is, the
identifier attribute becomes a key when we want to find an instance of the data object.
Relationships: It indicates the manner in which data objects are connected to one
another.
Cardinality: The data model must be capable of representing the number of occurrences
objects in a given relationship. The cardinality ratio constraint specify the number of
relationship instances an entity can participate in. The three types of cardinality ratio for
binary relationships are 1:1, 1: N and N: M representing one-to-one, one-to-many, manyto-many associations respectively.

Table: Symbols Used in E-R Diagram


23

zWebbed

ENTITY

ATTRIBUTE

RELATIONSHIP

24

zWebbed

Chapter 5
Implementation Details
25

zWebbed
Implementation is the process of having systems personnel checking and put new
equipment into use, train areas, install the new applications and construct any files of data
needed to use it. Regardless of implementation strategy used, developers strive to ensure
that the system initially use is trouble free. Implementation is an ongoing process.
Implementation is the stage is not carefully planned and controlled, it can be chosen.
Thus it can be considered to be the most crucial stage in achieving a successfully new
system and in the giving the users confidence that the new system will work effectively.
The implementation stage involves careful planning and preparation. The following
points are to be considered for the implementation of new system. The implementation of
the system environment. Resource available such as equipment. Alternatively method of
change over.

Chapter 6
Testing
6.1 Introduction
26

zWebbed
Testing is the process of running a system with the intention of finding errors.
Testing enhances the integrity of a system by detecting deviations in design and
errors in the system. Testing aims at detecting error-prone areas. This helps in the
prevention of errors in a system. Testing also adds value to the product by
conforming to the user requirements.
The main purpose of testing is to detect errors and error-prone areas in a system.
Testing must be thorough and well-planned. A partially tested system is as bad as
an untested system. And the price of an untested and under-tested system is high.
The implementation is the final and important phase. It involves user-training,
system testing in order to ensure successful running of the proposed system. The
user tests the system and changes are made according to their needs. The testing
involves the testing of the developed system using various kinds of data. While
testing, errors are noted and correctness is the mode.

6.2 Objectives of Testing


The objectives of testing are:

Testing is a process of executing a program with the intent of finding


errors.

A Successful test case is one that uncovers an as- yet-undiscovered error.

6.3 Types of Testing


6.1. Unit Testing
Unit testing focuses efforts on the smallest unit of software design. This is known
as module testing. The modules are tested separately. The test is carried out during
programming stage itself. In this step, each module is found to be working
satisfactory as regards to the expected output from the module.

6.2 Integration Testing


27

zWebbed
Data can be lost across an interface. One module can have an adverse effect on
another, sub functions, when combined, may not be linked in desired manner in
major functions. Integration testing is a systematic approach for constructing the
program structure, while at the same time conducting test to uncover errors
associated within the interface. The objective is to take unit tested modules and
builds program structure. All the modules are combined and tested as a whole.

6.3 System Testing


System testing is the stage of implementation. This is to check whether the system
works accurately and efficiently before live operation commences. Testing is vital
to the success of the system. The candidate system is subject to a variety of tests:
on line response, volume, stress, recovery, security and usability tests. A series of
tests are performed for the proposed system is ready for user acceptance testing.

6.4 User Acceptance Testing


User acceptance of a system is the key factor for the success of any system. The
system under consideration is tested for the user acceptance by constantly keeping
in touch with the prospective system users at the time of developing and making
changes whenever required.
Validation:
At the culmination of the integration testing, Software is completely assembled as
a package. Interfacing errors have been uncovered and corrected and a final series
of software test begin in validation testing. Validation testing can be defined in
many ways, but a simple definition is that the validation succeeds when the
software functions in a manner that is expected by the customer. After validation
test has been conducted, one of the three possible conditions exists.
a) The function or performance characteristics confirm to specification and
are accepted.
b) A deviation from specification is uncovered and a deficiency lists is
created.
28

zWebbed
c) Proposed system under consideration has been tested by using validation
test and found to be working satisfactory.
Output Testing:

After performing the validation testing, the next step is output testing of the
proposed system, since no system could be useful if it does not produce the
required output in a specific format. The output format on the screen is found to be
correct, the format was designed in the system design time according to the user
needs. For the hard copy also; the output comes as per the specified requirements
by the user. Hence output testing did not result in any correction for the system.
Login:
S.No

Input
Values

Test case

Conditional being checked

Result

User name

Empty

Please Enter valid Username

Successful

User name

Already
Login ID should be unique
Exists or
not

Successful

Password

Empty

Successful

Password

If wrong Enter Password


Password

Password

Length

Please Enter valid Password

Successful

Length should be less than or Successful


equal to 10 charecter

Registration:
Sl

Input Values

Test case

Conditional being checked

Result

1.

Desired
address

Empty

It must not be empty

Successful

Email

Empty

Enter valid Email ID.

Successful

No

29

zWebbed
address
3

Repeat
mail

e- Empty

Enter valid Email ID.

Repeat
mail

e- invalid

Entered Email address and Successful


repeat mail should be same.

Desired
password

Terms
and Select
Conditions

Empty

Please Enter valid password

Successful

Successful

Please agree for terms and Successful


condition.

Edit Design
Sl

Input Values

Test case

Conditional being checked

Result

1.

Base Design

Null

Please select Base Design

Successful

Titlenavigation Empty
column

Navigation column must not Successful


be empty

Right
Title

Box Empty

Right Box title must not be Successful


empty

Right
Content

Box Empty

Right box content must not Successful


be empty

No

Manage Images
Sl

Test case

Conditional being checked

Result

No

Input
Values

1.

Category

Null

Please select category

Successful

30

zWebbed
2

Selecte
pictures

Null

Please select pictures

Category
title

Empty

Please enter
category

Test case

Conditional being checked

No

Input
Values

1.

View page

null

Please select
update.

Add
page

new null

Please enter name for new Successful


webpage.

Add
page

new Special
character

Please enter numbers


characters only.

Insert image

the

Successful
title

of Successful

Manage pages:
Sl

Rresult

webpage to Successful

and Successful

Null

Please select image to insert or Successful


click to cancel.

Input
Values

Test case

Conditional being checked

1.

Contact
form

Null

Please select at least one Successful


option to contact form

Visitor
counter

Reset

Please click reset button to Successful


reset

Select extra

Empty

Please select extras

Successful

Test case

Conditional being checked

Result

No

Input
Values

1.

Delete

Null

Please select message to delete

Successful

Reply

Null

Please select reply id to send Successful


message

Manage Extras:
Sl
No

Result

Messages:
Sl

Personal preferences:
31

zWebbed
Sl

Input
Values

Test case

Conditional being checked

1.

Homepage
title

Empty

Please enter
homepage

of

the Successful

E-Mail

Empty

Please enter email address

Successful

New
Password

Empty

Please enter new password

Successful

New
Password

Length

Length should be less than or Successful


equal to 10 charecter

Repeat new Empty


password

Please Enter valid Password

Repeat
password

Invalid

Entered new password and Successful


repeat new password should be
same.

Age

Empty

Please enter the age

Successful

ICQ number

Empty

Please enter ICQ number

Successful

AIM Name

Empty

Please enter AIM Name

Successful

10

MSN
address

Empty

Please enter MSN address

Successful

11

MSN
address

String

Please enter Email address Successful


should
be
like
name@companyname.com

12

Yahoo name

Empty

Please enter Yahoo name

Successful

13

City

Empty

Please enter City

Successful

14

Professions

Empty

Please enter Professions

Successful

15

Interests

Empty

Please fill Interest field

Successful

16

Signature in Empty
board

No

title

Result

Successful

Please fill Signature in board Successful


field

32

zWebbed

Chapter 7
Result and Analysis

33

zWebbed

Chapter 7
Conclusion and Future Work
7.1 Conclusion
This is major project, which is done in PHP where the database used is MSQL. This
application is web based. This application provides cloud based accessibility for the user
and enable the user to create personal websites without needing any programming and
designing skills. The intended goal for the project is to provide a fast accessing web
based system for the users wanting to create their own websites. The front-end HTML,
CSS with JS as back-end has been found to be very efficient for this system. The system
is expected to function as per the requirements. The system design provides facility to
enhance its features. The current system has user-friendly features and makes it easy to
the database and applications.

7.2 Limitations

34

zWebbed

7.3 Future Enhancement


Each and every module in this project is individual and independent from other modules.
All modules are called from the main form. Any new operation or activity can be added
to the project as new module or existing one can be enhanced without disturbing the data.
Hence the project can be extended according to the requirements.
For linking database data controls, data access objects are used and for querying purpose
structured query language is used. So Unstructured Query (NoSQL) can be used as back
end without modifying the existing system. Thus the system gives the scope for further
application.

35

zWebbed

Reference
[1] Andreas Mauthe; Peter Thomas (2004), Professional Content Management Systems:
Handling Digital Media Assets, John Wiley & Sons, ISBN 978-0-470-85542-3.
[2] Paul Boag (2009-05-05). "10 Things To Consider When Choosing The Perfect CMS".
SMASHING MAGAZINE. Archived from the original on 2009-05-05. Retrieved 201407-07.
[3] Santa Clara, "Towards a Restful Plug and Play Experience in the Web of Things,"
USA, 2008.
[4] Lawrence B. Holder and Djane J. Cook, Moving Media Storage Technologies:
Applications & Workflows for Video and Media Server Platforms, Department of
Computer Science Engineering, University of Texas, Arlington, 2011.

36

zWebbed

Bibliography
[1] Roger S. Pressman, Software Engineering: A Practitioners Approach, 7th Edition,
McGraw Hill, 2010.
[2] Harry Henderson, Encyclopedia of computer science and technology, Facts on File,
2009.
[3] Kifer, M., Arthur J. Bernstein, and Philip M. Lewis. Database Systems: An
Application-oriented Approach. Boston: Pearson/Addison-Wesley, 2006.

37

You might also like