Web Dynamics
About Project
In an era where having a website of your own is a matter of
prestige for some and necessity for others. Management of these websites is
still an area which is ignored or done in traditional manner. In a changing
world no corporate company or any website owner would like to host a static
content over their site. We in a
system called ‘Web Dynamics’ provide a structural mechanism of building
the content for your site. It also provides us a testing area where the created
content is being hosted.
The structural mechanism provides in this system requires
personnel with specialization in different areas. The entire content is grilled through various
phases before being made available for the website. The content being created
or hosted can be placed into different categories available with the system.
The crucial content can even be placed in a protected zone which can be
accessed by only the registered users.
This application provides most of the features required to
manage the projects developed in a software development firm.
This volume presents the manner in which the software was
developed and how the various problems are tackled at the different levels to
convince the user.
We hope that this package would prove to be an excellent
environment for Content Management and simpler for end user.
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.
Selection of a person for a task is done by manually approaching the person and
confirming the availability of the person. Due to mismanagement the work is
delayed to later date than the due date.
Proposed System
The information of the entire system will be maintained at a
centralized data base.
Notifications between sections is provides in terms of
content list notification in the users area. Provide Interactive interface through
which a user can interact with different areas of application easily.
Disapproved content is returned back to the lower 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 is available on all the systems with in
the network, there by reducing the maintenance cost of software.
Module Description
The complete system can be divided into five halves on basis
of access levels.
Ø Account Management
Ø Utilities
Ø Authoring
Ø Editing
Ø Approving
Ø Deployment
Account management:
Using this part of an application the administrator can view
the list of users and their area of specialization. The administrator can create
a new users, modify existing user. An administrator provides permission to the
newly created user by placing the new user into set of roles such as a author,
approver, editor or deploy. 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 normal person to browse as well as to up the site back for its
use.
Authoring:
An administrator or a person with the author privileges can
access this part of the application. This part of the application includes
creating new content in the form of stories which is normally done by the
developers or content writers.
The newly created content may include no of notes 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 a content is found unsuitable to the cause the content
is returned back to the author. This
part of the application can be explored only by an administrator or the users
who possess an editor privilege. 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 to the deploy 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 of the person who possess an Approver privilege.
Deploy:
This area of the application includes the deployment part of
an application. A deploy person 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. These categories are subdivided into
no of sections.
Administrator:
An administrator has all the privileges that of the guest as
well as the normal registered user. Along with this common features an
administrator has the administrator related features such as creating new users
and granting roles to those newly created users. The roles granted by the
administrator cannot be changes by the user. An administrator can create new
user as a guest or as an user or an administrator. The access levels are as per
the grants done by the administrator.
An administrator can also be part of a team and could lead a
project team this is possible only if administrator when building a team
includes himself in the team section. If included as a manager he is not a part
of the team but supervisor of the team.
The register option on the homepage of the application is
provided only to register a new user as a guest.
SOFTWARE & HARDWARE REQUIREMENT SPECIFICATION:
The software requirements specification is produced at the
culmination of the analysis task. The function and performance allocated to the
software as a part of system engineering are refined by establishing a complete
information description, a detailed functional and behavioral description, and
indication of performance requirements and design constraints, appropriate
validation criteria and other data pertinent to requirements.
Software Requirement
WINDOWS NT 4 | 2000 | 9.X | ME
Visual Studio .Net 2002 Enterprise Edition
Internet Information Server 5.0
Visual Studio .Net Framework (Minimal for Deployment)
Hardware Requirement
PIII 500MHZ or
above
128MB RAM
100MB Free Hard disk space
STD Color Monitor
Network interface card or Modem (For Remote Sources)
LAN Network (For Remote Sources)
No comments:
Post a Comment