Content
Management System
Objective:
The objective is to develop a system for the enterprise organizations to
keep their websites up to date and follow the standard architecture to avoid
unauthorized data access.
Existing
System:
The current system, although semi
atomized, required manual processing of approval and editing before being
approved for the deployment. Transfer of
information content between different sections of the current system is in the
form of documents. Due to mismanagement, the work is delayed beyond the due
date.
Proposed System:
The information of the entire system
will be maintained at a centralized data base.
Notifications between sections are provided in terms of content list
notification in the user area. Provides Interactive interface through which a
user can interact with different areas of application easily. Disapproved
content is returned back to the lower levels for redesign. Approved content is
removed from the user list and made as part of the user’s list to which the
content is being notified. Deploy the application on a single system and make
it available on all the systems with in the network, there by reducing the
maintenance cost of software.
Modules:
The Modules proposed in the system are
Account
Management, Utilities, Authoring, Editing, Approving, Deployment
Account
management:
The administrator can create new
users and modify existing users. An administrator provides permissions to the
newly created user by placing the new user into set of roles such as author,
approver, editor or deployer. This part of the application is only accessible
to the administrator.
Utilities:
Utilities section of the application is used to shut down the site for
the end user and also to start up the site, back for its use. This is normally
done for site maintenance.
Authoring:
This part of the application
includes creating new content for the pages, which is normally done by the
developers or content writers. The newly created content may include number of
notes and explanations which will guide the editor at the time of editing the
content. The newly created content then can be posted to editor for editing.
Editor:
An
editor receives the content posted by the author. An editor can view the
content and later post the content to a new revision or to an existing
revision. If the content is found unsuitable then the content is returned back
to the author. The editor can withdraw the content from being hosted if found
unfit for hosting.
Approver:
An approver is a person who will
approve the contents to be hosted on the site. An approver can approve the
content and forward it to the deployment section or discontinue the content
usage or return the content back to the editor for revision. The returned
content should accompany with a message to the editor regarding the revision in
the content. This part of the application can be accessed by the administrator
who has an Approver privilege.
Deploy:
This area of the application includes the
deployment part of an application. A deployer can view the content before
deploying it. The person can also return the content if found unfit to be
hosted on the site. The returned content is sent back to the approver. The
deployment of the content includes the content to be placed in specific area of
the hosting environment. The hosting environment is divided into three
categories. The deploy content, the manager content, the protected content.
Software:
Technologies : ASP .Net and C# .Net
Database :
MS-SQL Server 2005/2008
IDE : Ms-Visual Studio .Net 2008
Hardware:
Processor :
Pentium
RAM : 1GB
