CMS Ducument

Web Content Management System

Page 1

SHIVAJI UNIVERSITY, KOLHAPUR

A Project report on

Content Management System Submitted To,

DEPARTMENT OF COMPUTER SCIENCE SHIVAJI UNIVERSITY, KOLHAPUR.

In partial fulfillment of the degree

MASTER OF COMPUTER APPLICATION

SEM-VI (2014-15)

By

Mr. Swami Satvirayya Shankar

Miss.Ratnaparkhi Karuna Ramkrishna

Mr.Mulla MubinAhamd Bahadur

Under the guidance of

Tousif Sarguru

(Project Manger of Webby Technology)


Page 2

DEPARTMENT OF COMPUTER SCIENCE SHIVAJI UNIVERSITY, KOLHAPUR

CERTIFICATE

This is to certify that Mr. Swami Satvirayya Shankar,

Miss.Ratnaparkhi Karuna Ramkrishna,Mr.Mulla Mubinahmad Bahadur have satisfactorily completed the project entitled as Content Management System in the partial fulfillment of M.C.A. - III (Sem-VI) during the academic year 2014-15.

Place : Kolhapur.

Date : April 23, 2015

Examiner Dr. R. K. Kamat

Head Dept. of Computer Science Shivaji University, Kolhapur.


Page 3

To, The Coordinator,

Dept. of Computer Science, Shivaji University, Kolhapur. We hereby declare that the project entitled Content

Management System is the genuine work prepared by us and submitted to Department of Computer Science, Shivaji University, Kolhapur. Is the original work and conclusion drawn there, based on the data collected by us.

We declare that we have referred these books mentioned in the references during the completion of the project work and have not copied any part of any written material or its part there of this project work is purely created on my own and merit.

We do understand that our work is found to be copied then we liable to be punished by rule of shivaji university Kolhapur.

Place: Kolhapur Mr. Satvirayya S Swami ( )

Miss.karuna R Ratnaparkhi ( )

Mr.Mubinahmad B Mulla ( )

Date: April 23, 2015 (M.C.A.-III)(SEM-VI)


Page 4

We very glad to present my project report on the topic Content

Management System to the college authority as a part of our study

of M.C.A.

The success accomplished in my project would not have

been possible but for the timely help and guidance of many people.

We wish to express our sincere and heartfelt gratitude to all those who

have helped we in one-way or the other for the successful completion

of this project.

We take this opportunity to express our sincere gratitude

and indebtedness to the project guide for giving us timely suggestions

and directing us towards perfection. Without their guidance, advice

and constant encouragement, it would be very difficult for us to

complete this project work successfully.

We express our thanks to Dr. R. K. Kamat, Head of

Department of Computer Science, for kindly permitting us to carry

out this work and also for his motivation and support which he

provided.

Finally we thank one and all for extending their support for

helping us in successful completion of our project work.


Page 5

Table of Contents


Page 6

CONTENTS

SR.NO. PARTICULARS PAGE NO.

1 Introduction. Introduction to project Introduction to company Objectives of System. Scope of the System.

1-10

2 System Analysis

Basic Concept. Drawback of Existing System. Proposed System. Feasibility Study.

11-16

3 Techniques Used In

Front End. Back End.

18-21

4 System Design

System Diagram (DFD, ERD). System Flowchart

23-35

5 Testing 36-40

6 Screen Output 41-56

7 Conclusion 58

8 References 60


Page 7


Page 8

1.1 INTRODUCTION TO PROJECT

A Content Management System (CMS) is computer system that allows publishing,

editing, and modifying content as well as site maintenance from a central page. It provides a

collection of procedures used to manage workflow in a collaborative environment. These

procedures can be manual or computer-based. Content Management Systemshould be

convenient in usage for technical as well as non-technical users. This also helps non-technical

users in modifying the front end appearance of a website

There are three types of content management system:

Enterprise content management systems

Web content management systems,

Component content management systems.

A content management system is software that keeps track of every piece of content

on your website much like your local public library keeps track of books and stores them.

Content can be simple text, photos, music, video, documents or just about anything you can

think of. In reality a CMS is a concept rather than a product. It is a concept that embraces a set

ofprocesses. A major advantage of using a CMS is that it requires almost no technical skill or

knowledge to manage as CMS system itself manages it.

Web Content Management System:

A web content management system (WCMS)is a software system that provides

website authoring, collaboration and administration tools designed to allow users with little

knowledge of web programming languages, or markup languages to create and manage

website content with relative ease. A robust WCMS provides the foundation for collaboration,

offering users the ability to manage documents and output for multiple authors editing and

participation. Most systems use a content repository or a database to store page content,

metadata and other information assets that might be needed by the system. A presentation

layer displays the content to website visitors based on a set of templates. A WCMS allows

non-technical users to make changes to a website with little training. AWCMS typically

requires a systems administrator and/or a web developer to set up and add features, but it is

primarily a website maintenance tool for non-technical staff.


Page 9

1.2 PROBLEM DEFINATION

In 1990 Internet was introduced. A wave of websites appeared when each

business published its website for the world to see. These websites were created using

a HTML Editor. Website maintenance was costly and a tedious job. If the website is

not maintained properly its pages will become inconsistent, mismatching fonts and

colors and your website will look like a ransom note.

However, there were other problems associated with such websites. The websites

created using HTML editor were static in nature, because HTML editor doesnt

support dynamic websites. . Images and other objects were awkward to manage in

HTML Editors. To overcome these limitations a Web Content Management System

was introduced.

A Web Content Management System (WCMS) allows you to focus on the

business purpose of your website and not on the technical details of how it works. It

produces search engine friendly web pages automatically. It also provides a web

interface to manage website content, structure and look-and-feel. It delivers web pages

that behave consistently across all browser type (E.g. Internet Explorer, Safari,

Firefox, etc.). It automates the publication of images, audio, video and other media

and eliminates your day-to-day dependence on technical web staff. The entire website

can be changed by adjusting or replacing the template, making the website appear as if

it had been rebuilt from scratch. In actuality, only the appearance changed the content

is 100% preserved. In addition, the entire website or a particular webpage on website

can be scheduled for publication at a specific time and date in the future.

Administrator:

The role of an administrator holds the most weight in a web-based CMS. A

website administrator is responsible for the day-to-day operation and maintenance of the

website. Activities might include ensuring that the site is properly backed up; managing user

access; possibly installing extensions. He will also have responsibility for maintaining the

security of the website.

User: User will login, select layout for creation of website, adding, editing content to

website and then preview.


Page 10

1.3 BENEFITS OF PROPOSED SYSTEM

CMS tool can be modified to provide fully customized websites with simple and

interactive user friendly interface.

This interface will provide drag and drop functionality to users so that they can

create their website according to their needs and requirements.

In customized websites, adding background images can also be made possible with

less execution time.

A CMS allows multiple authors to update your site, as it grows, taking responsibility

for different sections.

.A CMS allows to manage the creation, modification, and removal of content from a

Web site without technical knowledge.

Speed up the creation and execution of web page.

Through a CMS, editing the content on website is as easy as using Microsoft Word!

One can simply type in the content through the CMS interface which is like typing in a

word processing software and the CMS will publish it in the website.

There is no need to learn programming languages such as HTML, PHP just to change

the content of website.


Page 11


Page 12

2.1 BASIC CONCEPTS

A web content management system (WCMS)is a software system that provides

website authoring, collaboration and administration tools designed to allow users with little

knowledge of web programming languages, or markup languages to create and manage

website content with relative ease.

A robust WCMS provides the foundation for collaboration, offering users the ability

to manage documents and output for multiple authors editing and participation. Most systems

use a content repository or a database to store page content, metadata and other information

assets that might be needed by the system. A presentation layer displays the content to

website visitors based on a set of templates. A WCMS allows non-technical users to make

changes to a website with little training. AWCMS typically requires a systems administrator

and/or a web developer to set up and add features, but it is primarily a website maintenance

tool for non-technical staff.

A Web Content Management System (WCMS) allows you to focus on the business

purpose of your website and not on the technical details of how it works. It produces search

engine friendly web pages automatically. It also provides a web interface to manage website

content, structure and look-and-feel. It delivers web pages that behave consistently across all

browser type (E.g. Internet Explorer, Safari, Firefox, etc.).

A Web Content Management System (WCMS) automates the publication of images,

audio, video and other media and eliminates your day-to-day dependence on technical web

staff. The entire website can be changed by adjusting or replacing the template, making the

website appear as if it had been rebuilt from scratch. In actuality, only the appearance changed

the content is 100% preserved. In addition, the entire website or a particular webpage on

website can be scheduled for publication at a specific time and date in the future.


Page 13

2.2 EXISTING SYSTEM

Drupal

Drupal is a free and open source software content management system.

The standard release of Drupal is known as drupal core, contains basic features

common to content management systems.

These include user account registration and maintenance, menu management, page

layout customization, and system administration.

Drupal runs on any computing platform that supports both a web server capable of

running PHP (including Apache, IIS, Lighted, Hiawatha , Cherokee or Nix) and

a database (such as MySQL , PostgreSQL, Microsoft SQL Server) to store content

and settings.

CK Editor is the successor to FCK editor and has its own CK Editor Module.

This module allows Drupal to replace text area fields with the FCK editor.


Page 14

2.3 PROPOSED SYSTEM

Modules

There are two modules of CMS system:

User

Admin

User:

User will have to create account in content management system. After creation of

account, user will login into system. After login user will select theme, add content to site,

preview site. There are sub modules in user module as follows:

Dashboard: User can add, edit, delete, and view menus and submenus.

Gallery: User can add,deleteand view images, videos.

Header content: User can add name, title to the selected layout.

Preview: User can preview the website.

Settings: User can change any information like address, phone number, email id, change

password.

Customized layout is also available. In which user he will decide the look and feel of his

website.

Admin: Admin will supervise the activities of user.

Admin will view the feedback given by user.


Page 15

2.4 REQUIREMENT ANALYSIS

Functional

We are developing the CMS system using the existing technology. We are

using the tools like Dreamweaver, Wamp Server. These are most popular tools

nowadays and are specially used for developing such systems. Use of these tools

minimizes the time required for development.

Operational Feasibility

CMS is operationally feasible as all the tools are easily available and can be

made operational by making use of them. This project is made considering all the

basic step of real world scenario. It isa software system which provides website authoring

and administration tools designed to allow users with little knowledge of web programming

languages or mark-up languages to create and manage the site's content with relative ease.It

enables users to quickly and efficiently build, deploy, and maintain content-rich web sites by

streamlining the web publishing process.Administration is typically done through browser-

based interfaces.Content Management Systems can reduce the need for costly site

maintenance and thus empower users to manage their own content.

Economical Feasibility

It is economical, as it does not require any tools as such which are expensive.

We can make use of free softwares which are easily available. As the software will be

open source users can easily download its installation file.Content Management Systems

can reduce the need for costly site maintenance and thus empower users to manage their own

content. A Content Management System allows anyone with little or no experience in web

design to update and maintain their own site by paying less cost or free of cost.

Technical Feasibility

Technically also CMS is feasible as it make use of all the known technologies

like PHP, HTML, and DBMS. The user requires only the installation file before start

working on the software. For clients those prefer to update and maintain their site

themselves, a web content management system is the ideal solution. From users point of view


Page 16

theydont need any prior technical knowledge and still can develop websites for personal or

professional use with ease. We dont require any complexity to run CMS as the

hardware tools required are easily available and are very common like Pentium 4 pc,

input/output devices, RAM etc.


Page 17


Page 18

Technology used

Front End Java

Like any programming language, the Java language has its own structure, syntax rules, and programming paradigm. The Java language's programming paradigm is based on the concept of object-oriented programming (OOP), which the language's features support.

The Java language is a C-language derivative, so its syntax rules look much like C's: for example, code blocks are modularized into methods and delimited by braces ({ and }), and variables are declared before they are used.

Structurally, the Java language starts with packages. A package is the Java language's namespace mechanism. Within packages are classes, and within classes are methods, variables, constants, and so on.

Java Features:-

Simple

Object-Oriented

Platform independent

Secured

Portable

Dynamic

Interpreted

High Performance

Multithreaded

Distributed

JavaServer Pages Technology

JavaServer Pages (JSP) technology provides a simplified, fast way to create dynamic web content. JSP technology enables rapid development of web-based applications that are server- and platform-independent. JSP technology lets you add snippets of servlet code directly into a text-based document.


Page 19

JavaServer Faces Technology

JavaServer Faces technology is a UI framework for building web applications. The main components of JavaServer Faces technology involve a GUI component framework, a flexible model for rendering components in various markup languages and technologies, and a standard RenderKit for generating HTML markup.

This functionality is available through standard Java APIs and XML-based configuration files. In addition, Sun Java Studio Creator IDE leverages JavaServer Faces technology in its drag-and-drop GUI tools, allowing you to use the technology without having to write or understand the underlying code.

JDBC API

The JDBC API allows you invoke database SQL commands from Java programming language methods. You can use the JDBC API in a servlet, JSP technology page, or an enterprise bean when you need to access the database.

The JDBC API has two parts: an application-level interface that application components use to access a database and a service provider interface to attach a JDBC driver to the Java EE platform.

The left side of Figure 2 shows how a client makes a direct call to the application server, usually through a servlet or JSP page, and that data is then sent to the database management system (DBMS) server. The right side of Figure 2 shows how a driver translates JDBC calls into the middleware vendor's protocol.

Back End Introduction

The operation of corporations, enterprises, and other organizations relies on the management, understanding and efcient use of vast amounts of information. This information may come from business applications nance, order processing, manufacturing, and customer relationship management systems that easily conform to standard data structures (such as rows and columns with well dened schema). Increasingly, business value and operations depend on management, analysis and understanding of information that is not readily accessible without human or machine based interpretation.

Common examples range from documents, XML, multimedia content, and web content to specialized information such as satellite and medical imagery, maps, and and geographic information, sensor data, and semantic web structures. Oracle Database 11g Release 2 includes a wide range of capabilities that allow for intelligent management and analysis of these forms of information. The ways in which these types of information are managed vary based on how the data are created and used:


Page 20

Huge volumes of data in desktop ofce systems (documents, spreadsheets and presentations) and specialized workstations and devices (geospatial analysis systems and medical capture and analysis systems) Multi-terabyte archives and digital libraries in government, academia and industry Image data banks and libraries used in life sciences and pharmaceutical research Public sector, telecommunications, utility and energy geospatial data warehouses Integrated operational systems including business or health records, location and project data, and related audio, video and image information in retail, insurance, healthcare, government and public safety systems Semantic data (triples) used in academic, pharmaceutical and intelligence research and discovery applications Advantages of Oracle Database Information Management Capabilities: Since the introduction of database management systems, database technology has been

used to address the unique problems encountered when managing large volumes of all forms of Oracle White PaperInformation Management with Oracle Database 11g 3information. Databases are often used to catalog and reference documents, images and media content stored in files through pointer-based implementations. To store this unstructured data inside database tables, Binary Large Objects, or BLOBs have been available as containers for decades. Beyond simple BLOBs, for many years Oracle Database has incorporated intelligent data types and optimized data structures with operators to analyze and manipulate XML documents, multimedia content, text, and geospatial information. With Oracle Database 11g, Oracle is once again breaking new ground in the management of this information through dramatic improvements in the performance, security, and types of content managed by Oracle Database.

There are many reasons organizations store all forms of information with Oracle

database management systems.

Robust Administration, Tuning and Management: Content stored in the database can be directly linked with associated data. Metadata and content are maintained in sync; they are managed under transactional control. The database also offers robust services for backup, recovery, physical and logical tuning. Simplicity of Application Development: Oracles support for a specific type of content includes SQL language extensions, PL/SQL and JAVA APIs, Xpath and Xquery (in the case of XML) and, in many cases, JSP Tag Libraries, as well as algorithms that perform common or valuable operations through built in operators. High Availability: Oracles Maximum Availability Architecture makes zero data-loss configurations possible for all data. Unlike common configurations where attribute information is stored in the database with pointers to unstructured data in files, only a single recovery procedure is required in the event of failure. Scalable Architecture: In many cases, the ability to index, partition, and perform operations


Page 21

through triggers, view processing, or table and database level parameters allows for dramatically larger datasets to be supported by applications that are built on the database rather than on file systems. Security: Oracle Database allows for fine-grained (row level and column level) security. The same security mechanisms are used for all forms of information. When using many file systems, directory services do not allow fine-grained levels of access control. It may not be possible to restrict access to individual users; in many systems enabling a user to access any content in the directory gives access to all content in the directory.


Page 22


Page 23

3.1 DATA FLOW DIAGRAMS

Fig. 3.1 Data Flow Diagram of User at level 0

Fig.4.2 shows data flow diagram of user at level 0 where there will be CMS interface

between user and admin.

Fig. 3.2 Data Flow Diagram of User at level 1


Page 24

Above Fig. 3.2shows data flow diagram of user. User will login to system which will

be validated from database, and then user can select any one theme and add contents to site.

Adding c contents will include:

Dashboard: User can add, edit, delete and view menus and submenus.

Gallery: User can add, edit,delete and view images.

Header content: User can add title, name to website.

Settings: User can change information like name, address, email and password.

Preview: User can preview the website.

Fig.3.3 Data Flow Diagram of Admin

Above Fig. 3.3 shows the data flow diagram of admin. Admin will supervise the

activities of user and can view feedback given by users.


Page 25

Above fig3.4 shows Entity Relationship Diagram of Content Mangement System


Page 26

4.1 IMPLEMENTATION

Module Specification

There are two modules of CMS system:

User

Admin

User:

User will have to create account in content management system. User will create

account by filling registration form which will contain fields like name, address, email,

date of birth, mobile and password. Fields of registration form are validated like name

should contain characters, email should be in valid format with proper position of dot and

special character, and mobile number field should contain 10 digits number, password and

confirm password need to be same. After creation of account, user will login into system.

After valid login user will select appropriate theme. The selected theme can be either

customized theme or any one from 10 layouts provided. After selection of theme user can

add content to site by selecting any one of this menu:

Dashboard: In this menu, user can add menus by filling form which will contain fields

menu name, menu order for order of menu, active for menu to be active or not and menu

description which will be displayed in main container. After adding menus, user can view

added menus. If user want to change menu then user can edit menu. User can add

submenu to any menu by following same procedure of menu. User can delete menu.

Gallery:In this menu, user will be asked first whether he wants gallery as a menu in

his website, if yes then only gallery will be added by using gallery name and menu order

entered by user. After adding gallery user can view and delete added gallery. User can

also add images to gallery. These images will be displayed in site container whenever the

gallery menu is selected.

Header content:In this menu, user can add header details like site name, site tile. If

user wants any change then user can edit it.

Preview:After adding all contents to site user can preview the site.


Page 27

Settings: User can change any information by editing form which will contain fields

name address, mobile, email id, date of birth and can change password.

Customize Layout: After login when user is about to select theme, user can select

theme from 10 layouts provided or can choose customized layout. After selecting

customized layout user can add menu by filling form which will contain menu name,

menu order for order of menu, active for whether menu to be displayed or not, menu type

will contain alignment top, left, or right accordingly menu will be displayed and menu

description will be displayed in container. Customized header will allow adding title,

logo, image etc. User can change background colour of header, menu, container and

footer.

Admin:

Admin will supervise activities of all users. Admin will provide feedback in questions

format which will be filled by user. Admin can view feedback given by users.


Page 28

4.2 FLOWCHART

Fig. 4.2 Flowchart

Fig.4.2 shows the flowchart. User will login to system, it will be validated and then user

can select any one menu from dashboard, gallery, header content, settings to add content. If

user is not valid user will not be able to login to the system.


Page 29

Fig. 4.3 Flowchart for Dashboard Module.

Fig. 4.3 shows the flowchart of dashboard module. In dashboard menu, the user can add,

edit, and delete menus as well as submenus.


Page 30

Fig.4.4 Flowchart for Gallery Module.

Fig. 4.4 shows the flowchart for gallery module. In gallery menu, user can add gallery if

gallery is not been previously created for that user. If gallery already exists then user can add

image into it.


Page 31

Fig. 4.5 Flowchart for Header Content Module.

Fig. 4.5 shows the flowchart of header content module. User can add, edit site name and

site title.


Page 32

Fig. 4.6Flowchart for Settings Module.

Fig.4.6 shows flowchart of settings module. User can change information like name,

address, email id and password.

4.6.1 SEQUENCE DIAGRAM


Page 33

Fig. 4.7 Sequence diagram for dashboard module.

Fig. 4.7 shows sequence diagram for dashboard module. After valid login user can

add, edit and delete menus and submenus.

Fig. 4.7 Sequence diagram for gallery module

Fig. 6.3 shows sequence diagram for gallery module. After valid login user can add

gallery. After adding gallery user can add, view and delete images from gallery.

Fig. 4.8 Sequence diagram for header module.

Fig.6.4 shows sequence diagram for header module. After valid login use add and edit site

name, site title.


Page 34

Fig. 4.9 Sequence diagram for settings module

Fig. 4.9 shows sequence diagram for settings module. After valid login user can

change information like name, address, email id, mobile number, date of birth and password.


Page 35

6.1 USE CASE DIAGRAM

Fig.4.8 Use Case Diagram.

Fig. 4.8 shows the use case diagram of the system. Application will provide interface

for creation of website, which will include menus like dashboard, gallery, header content and

theme. User will login to system and create his site using the application. Admin will

supervise the activities of all users and can view feedback given by users.


Page 36


Page 37

7.1 TESTING ENVIRONMENT

These are some sample test case examples which are performed in our project.

.

T.C.ID

Module Name

Test Case Input Data Expected Result

Actual Result

Status

1 To check functionality of menus.

Menu information is inserted, updated and deleted properly from database.

Menu name, menu order and menu description inserted by user.

Menu data inserted and on preview displayed properly.

Menu data inserted and on preview displayed properly.

OK

2 To check

functionality of sub menus.

Sub menu information is inserted, updated and deleted properly from database.

Sub menu name, menu order and menu description inserted by user.

Sub menu data inserted and on preview displayed properly.

Sub menu data inserted and on preview displayed properly.

OK

3 To check creation

and updating of gallery.

Images are inserted, deleted and displayed properly.

All types of images uploaded by user.

Images are uploaded, deleted and on preview displayed properly.

Images are uploaded, deleted and on preview displayed properly.

OK

4 To check

functionality of header.

Header contents are inserted, updated and deleted properly.

Header logo, header title and header name inserted by user.

Header contents are inserted properly in database and on preview displayed properly.

Header contents are inserted properly in database and on preview displayed properly.

OK

5 To check

functionality of setting module

User information along with password can be changed successfully.

Updated user information entered by user in settings form.

All information changes are successfully saved.

All information changes are successfully saved.

OK

Table: Sample Test Cases


Page 38

7.2 TESTING STRATEGIES

Tests are frequently grouped by where they are added in the software development

process, or by the level of specificity of the test.

Unit Testing

Unit testing refers to tests that verify the functionality of a specific section of code,

usually at the function level.

Thistype of tests are usually written by developers as they work on code (white-box

style), to ensure that the specific function is working as expected. One function might have

multiple tests, to catch corner cases or other branches in the code. Unit testing alone cannot

verify the functionality of a piece of software, but rather is used to assure that the building

blocks the software uses work independently of each other.

This type of testing we have used to check server side validation. In this firstly we

checked all the users should have unique email id so that no conflict will occur while login.

Secondly when user want to change his password he has to enter his old password correctly

then only his new password will be accepted.

Integration Testing

Integration testing is any type of software testing that seeks to verify the interfaces

between components against a software design. Software components may be integrated in an

iterative way or all together ("big bang"). Normally the former is considered a better practice

since it allows interface issues to be localized more quickly and fixed.

Integration testing works to expose defects in the interfaces and interaction between

integrated components (modules). Progressively larger groups of tested software components

corresponding to elements of the architectural design are integrated and tested until the

software works as a system.


Page 39

This type of testing we have used to check that each user is owns single theme. If any

user tries to change theme his all previous data will be deleted.

System Testing

System testing tests a completely integrated system to verify that it meets its

requirements.

This type of testing we have used to check that when any user logs in second time he

will be displayed his previously selected theme along with its content.

Regression Testing Regression testing focuses on finding defects after a major code change has occurred.

Specifically, it seeks to uncover software regressions, or old bugs that have come back. Such

regressions occur whenever software functionality that was previously working correctly

stops working as intended. Typically, regressions occur as an unintended consequence of

program changes, when the newly developed part of the software collides with the previously

existing code.

Common methods of regression testing include re-running previously run tests and

checking whether previously fixed faults have re-emerged. The depth of testing depends on

the phase in the release process and the risk of the added features. They can either be

complete, for changes added late in the release or deemed to be risky, to very shallow,

consisting of positive tests on each feature, if the changes are early in the release or deemed to

be of low risk.

Acceptance testing

A smoke test is used as an acceptance test prior to introducing a new build to the main

testing process, i.e. before integration or regression.

Acceptance testing performed by the customer, often in their lab environment on their

own HW, is known as user acceptance testing (UAT). Acceptance testing may be performed

as part of the hand-off process between any two phases of development.


Page 40

After handover CMS system to the user/admin they specify some changes in to the

CMS system. As per their requirement changes are performed.

Functional Testing

Functional testing refers to tests that verify a specific action or function of the code.

These are usually found in the code requirements documentation, although some development

methodologies work from use cases or user stories. Functional tests tend to answer the

question of "can the user do this" or "does this particular feature work".

Functional testing is generally used in CMS system for check whether different logical

functions are performed well or not.


Page 41


Page 42

8.1 SNAPSHOTS

Fig. 8.1 snapshot of home page

Fig. 8.1 shows the home page of CMS system. User can view the home page of WCMS.


Page 43

Fig.8.2 Snapshot ofabout us

Fig. 8.2 shows the home page of CMS system. User can view the about us page of

WCMS.


Page 44

Fig. 8.3 Feedback page

Fig. 8.3 shows the feedback page of CMS system. User can give feedback to the system.


Page 45

Fig. 8.4 Testimonial page

Fig. 8.4 shows the testimonial page of WCMS system. User can view testimonial page of

the system.

Fig.8.5 Snapshot of Contact us page

Fig. 8.5 shows the contact us page of WCMS system. User can view contact uspage of the

system.


Page 46

Fig. 8.6 Registration page (default.aspx)

Fig.8.6 shows the snapshot of registration form. User has to fill these fields: name,

email,address, user name,password, and confirm password,date of birth, mobile no, domain

name.


Page 47

Fig. 8.7Snapshot of login page.

Fig. 8.8shows the snapshot of login page. User will login to system by giving valid email

id and password.


Page 48

Fig. 8.8 Snapshot of Dashboard page.

Fig. 8.9 shows the snapshot themes. User can select any one theme suitable for their

website.


Page 49

Fig. 8.9Snapshot of View page.

Fig.8.10 shows the snapshot of view page. User can view added menus, can edit menu,

can add submenu.


Page 50

Fig. 8.11Snapshot of Add page.

Fig. 8.11 shows the snapshot form to add menus. User can add menu, user has to add

menu name, menu index, page description.

Fig. 8.10Snapshot of Add subpages.


Page 51

Fig. 8.11Snapshot of setting (title/header content) page

Fig. 8.12Snapshot of Change passwordpage


Page 52

Fig. 8.13Snapshot of Upload theme (if provided theme does not like)page

Fig. 8.14Snapshot of Admin login page


Page 53

Fig. 8.15:Snapshot of user list


Page 54

Fig 8.16:Snapshot of Admin (particular user information -grid view page)


Page 55

Fig. 8.17:Snapshot of user active/inactive


Page 56

Fig. 8.18: User First Page Fig. 8.22shows the snapshot of user website .This is a developed website by user with its

sub menusand corresponding data.

Fig. 8.19:Snapshot of Sub menu and data


Page 57


Page 58

CONCLUSION

CMS Helps you to achieve following:

A CMS can be a great tool for either personal or business use.

A CMS allows multiple authors to update your site, as it grows, taking responsibility

for different sections.

.A CMS allows to manage the creation, modification, and removal of content from a

Web site without technical knowledge.

Speed up the creation and execution of web page.

Through a CMS, editing the content on website is as easy as using Microsoft Word!

One can simply type in the content through the CMS interface which is like typing in a

word processing software and the CMS will publish it in the website.

There is no need to learn programming languages such as HTML, PHP just to change

the content of website.

Future Scope:

CMS tool can be modified to provide fully customized websites with simple and

interactive user friendly interface.

This interface will provide drag and drop functionality to users so that they can create

their website according to their needs and requirements.

In customized websites, adding background images can also be made possible with

less execution time.


Page 59


Page 60

REFERENCES

1. Md. Sadique Sheikh, VasundharaFegade, Modeling Essential of Content Management

System (CMS) for Web-Based MIS Application, in International Journal of Engineering and

Technology Volume 2 No. 3, March, 2012

2. Khalid S. Husain, Performance Evaluation Process of the Content Management

System:Case Study of KauMarz System, Middle-East Journal of Scientific Research 11 (1):

117-127, 2012

ISSN 1990-9233 IDOSI Publications, 2012

3. Ivan Voras, Kristijan Zimmer, Mario agar, A hierarchical file system interface to

database-based content management application, in Faculty of Electrical Engineering &

Computing, University of Zagreb,3, 10000 Zagreb, Croatia{ivan.voras, kristijan.zimmer,

mario.zagar}@fer.hr

4. He bah ElGibreen1* and Samar El-Masri2,Improving Web Content Management System:

Template personalization approach, Journal of Engineering and Technology Research Vol.

4(7), pp. 149-163, December 2012 Available online at http:// ww.academicjournals.org/JETR

DOI: 10.5897/JETR12.025 ISSN 2006-9790 2012 Academic Journals.

5. Yong-Gang Cao, A multimedia web content management system, in Information Reuse

and Integration, 2004. IRI 2004 Proceedings of the 2004 IEEE International Conference on,

8-10 Nov. 2004.

6. He Luido, Design and Implementation of web CMS, in Information Management and

Engineering (ICIME), 2010 The 2nd IEEE International Conference on, 16-18 April 2010.

7. LiamScanlan, Why use a Web Content Management System?A SiteLeads.net White

Paper, June 2008.

8. Web Content Management-Collaborative approach by Russell Nakano.

9. Drupal (2010), Understanding Drupal http://drupal.org/getting-started/before.

CMS Ducument

Documents

project work

project introduction

project report

project guide

company objectives of

drawback of existing

kolhapur certificate

genuine work