Content Management System-CMS

Utility describes whether a system can perform functionality what is needed and on the other hand usability of the system defines how well users can use the functionality of the system and by combining these two features it can be assessed or measured that how much useful a system is or can be or in other words it can be said that utility and usability bring the usefulness feature in the system (Nielsen 1993).

Quesenbery (2001, 2002, 2004) has presented a new variation with regards to five usability attributes discussed above. These are also called as 5Es.

As there are five attributes of usability which make a system usable there are also five human factors which should also be considered while designing the interface of the system. And these are not taken in the context of usability of the system. These human factors are:

1.3 Usability Evaluation
There are a number of methods available that can be used for usability evaluation. Some of these will be discussed here as these can be used while assessment of my project. Heuristic evaluation is the most informal method and involves having usability specialist judge whether each dialogue element follows established usability principles (the “heuristics”). Cognitive walkthroughs use a more explicitly detailed procedure to simulate a user’s problem solving process at each step through the dialogue, checking if the simulated user’s goals and memory content can be assumed to lead to the next correct action. Formal usability inspections use a six-step procedure with strictly defined roles to combine heuristic evaluation and a simplified form of cognitive walkthroughs. Pluralistic walkthroughs are meetings where users, developers, and human factors people step through a scenario, discussing each dialogue element. Feature inspection lists sequence of features used to accomplish typical tasks, checks for long sequences, cumbersome steps, steps that would not be natural for users to try and steps that require extensive knowledge experience in order to assess a proposed feature set. Consistency inspection has designers representing multiple projects inspect an interface to see whether it does things in the same way as their own designs. Standards inspection has an expert on some interface standard ‘inspect the interface for compliance (Nielsen, 2004).

2. Content Management System
As the size of web increasing rapidly and its hard to manage the contents on the web specially the sites which have dynamic contents in them such as news portal and search engines because these are becoming more and more complex by the passage of time. This also includes both basic services such as searching and finding related pages, and advanced applications such as Web-scale data mining, community extraction, constructions of indices, taxonomies, and vertical portals. Applications are beginning to emerge that are required to operate at various points on the “petabyte curve”—billions of Web pages that each have megabytes of data, tens of millions of users in a peer-to-peer setting each with several gigabytes of data, etc (Stephen and Ravi et al, 2002).

A content management system (CMS) is a computer software system for organizing and facilitating collaborative creation of documents and other content (Wikipedia, 2006). There are several recognised types of content management systems:

Web content management systems assist in automating various aspects of web publishing, such as wikis.
Transactional content management systems (T-CMS) assist in managing e-commerce transactions.
Integrated content management systems (I-CMS) assist in managing enterprise documents and content.
Publications management systems (P-CMS) assist in managing the publications (manuals, books, help, guidelines, references) content life cycle.
Learning management systems (L-CMS) assist in managing the web-based learning content life cycle. See also managed learning environment.
Document imaging systems are also generally considered under the family of general content management.
Enterprise content management systems (E-CMS) vary in their functionality. Some support both the web and publications content life cycle, while others support the web content life cycle and either transactional content or customer relationship management content. The definition of AIIM for ECM includes methods and tools that "capture, manage, store, preserve and deliver" content across an enterprise. "Manage" contains components like document management, collaboration, business process management, records management, email management, workflow and web content management. The ECM concept is not restricted to web based technologies but includes client/server and hosted/On-demand solutions (Wikipedia, 2006).

2.1 Need of Content Management System
The data management on web is becoming very complex for the organisations. Organisations are trying to develop such solutions for the common software domains these days. For this purpose; to manage data properly and handing over the contents to the client they are appreciating such developments which can lead to reduce their work load and to satisfy their customers by giving them and effective and usable product. So organisations today are feeling the need (Teresa , 2006).

2.2 Advantages of Content Management System
In today’s life as I discussed before, that the size of web is increasing rapidly and people are bringing their business on the web for better marketing purposes to expand their business domain. Software organizations are thinking to develop a generic solution for the development of systems which are from same domain so content management systems are thought as a solution to certain type of required systems. These bring reliability and consistency in development and are helpful in empowering business users. These are also helpful to cut the price of resources which are needed for development and further more the solution is generic and flexible (Teresa, 2006).

3.0 XHTML
XHTML is a family of current and future document types and modules that reproduce, subset, and extend HTML 4 [HTML4]. XHTML family document types are XML based, and ultimately are designed to work in conjunction with XML-based user agents. The details of this family and its evolution are discussed in more detail in [XHTMLMOD]. XHTML 1.0 (this specification) is the first document type in the XHTML family. It is a reformulation of the three HTML 4 document types as applications of XML 1.0 [XML]. It is intended to be used as a language for content that is both XML-conforming and, if some simple guidelines are followed, operates in HTML 4 conforming user agents. Developers who migrates their content to XHTML 1.0 will realize the following benefits:

XHTML documents are XML conforming. As such, they are readily viewed, edited, and validated with standard XML tools.
XHTML documents can be written to operate as well or better than they did before in existing HTML 4-conforming user agents as well as in new, XHTML 1.0 conforming user agents.
XHTML documents can utilize applications (e.g. scripts and applets) that rely upon either the HTML Document Object Model or the XML Document Object Model [DOM].
As the XHTML family evolves, documents conforming to XHTML 1.0 will be more likely to interoperate within and among various XHTML environments.
The XHTML family is the next step in the evolution of the Internet. By migrating to XHTML today, content developers can enter the XML world with all of its attendant benefits, while still remaining confident in their content's backward and future compatibility (W3C, 2002).