Model Informasi

Step 1: Define the dimensions of your Information Model

We begin by defining the dimensions to identify the categories in your Information Model. These categories become the metadata we will use to label the content and make it modular.

First, the dimensions must be based on business information requirements. For example, we may categorize different product types and models, market segments, or subject matter.

Second, the dimensions must be based on author requirements. For example, we may categorize information by author, title, ID, editor, approver, original date, revision dates, version number, source and so on.

Third, we base the dimensions on user requirements. For example, we may categorize information by user job, skill level, experience, language, country, and so on.

We find it useful to develop use cases or scenarios of use, narratives that describe how authors, business analysts, and users will interact with information in the future. The more use cases we are able to construct, the better your solutions are likely to be. Not only will use cases allow us to define author, user, and content requirements more precisely, but they will provide us with a valuable way to evaluate tools and technology.

Your Information Model provides the terminology (taxonomy) to identify all the elements in your repository. One of the unexpected benefits of the process is discovering additional opportunities to improve your content, workflow, and reuse. It is much easier and less expensive to discover these opportunities early rather than later in the process. Using our expertise is likely to result in significantly lower future costs.

Step 2: Identify your information types

Then, we move on to identifying your information types. Information types define the kind of content your authors create and how the details are organized. Each information type will be based on the needs of your user community. A typical set of information types for technical information includes concepts, procedures, and reference modules. More specific information types can be derived from these basic types. For example, your organization might need different information types for maintenance procedures and end-user procedures.

Step 3: Review your delivery requirements

Next, we review your delivery requirements. What can be automated? What can be personalized or customized? What media must be supported now and in the future?

Step 4: Identify the content units

Once we have identified a minimal set of information types, we go inside the types and identify the content units that authors will use to construct the types. The content units are the components of the subject matter that will guide the development of formal Document Type Definitions (style sheets in XML or SGML) if you plan to use structured authoring systems.

Step 5: Investigate technology solutions

At the same time that we are defining the three-tiered structure of your Information Model (dimensions, information types, content units), we may begin to investigate technology solutions. However, we strongly recommend waiting until after your Information Model is quite firm to define the technology you need. Until you know in some detail how you want to deliver information to your user community and we formulate your Information Model, you are not ready to make a sound technology decision.

Step 6: Write a functional requirements document

We use all of the information we have gathered thus far to write a functional requirements document. We detail how you want to support your authors with authoring and workflow capabilities, what the content-management system must include so that you can store, manage, and retrieve modules from the repository, and, most important, how you should assemble and deliver information to your users.

We do not specify and design solutions. We stick to requirements alone. We identify and explain what you have to do. We let the vendors explain how they will accommodate your needs. We try not to place unnecessary limits on the technology solution. There will be new developments in the field that you have not anticipated.

Step 7: Ask vendors to submit a request for proposal

We ask vendors to respond to your functional requirements (as a request for proposal). After we have analyzed the responses for completeness and clarity, we ask for presentations. We use your requirements document to question the vendor representatives and be sure that you get satisfactory answers. Be aware that everyone exaggerates their capabilities to some extent. We ask for clear statements in writing about what is standard and what needs to be customized. We are very specific about compatibilities between your requirements and each tool you are considering. We ask about ease of integration between tools because integration problems can sink an otherwise sound specification.

Step 8: Visit other organizations

At the same time, we visit other organizations that are using the technology. We talk with people in the same roles as your team and find out about all the benefits and pitfalls they have encountered.

Step 9: Request a proof of concept

When you have selected a small group of final vendors, we ask for a "proof of concept" in which the vendors prepare and present their solution with your own information. Recognize that you might have to pay fees for the "proof of concept," because the development process may be quite expensive for the vendors.

One effective technique we use is to write scenarios to test with the products. We know that some scenarios might be impossible to simulate without a good deal of customization work but we are sure to try out standard scenarios for authoring, storing and retrieving, content assembly, and possibly publishing. The assembly and publishing scenarios are likely to be the most difficult to simulate and are the areas in which technologies are most likely to fall apart. If we don't test your assembly and publishing solutions, we may not discover the problems until you are deep into implementation (and your warranty period has expired).

Step 10: Meet with the implementation team

You should be comfortable with the people on the vendor's team. As you narrow your choices, we ask to meet with the implementation team if they haven't already been involved. In many cases, we meet with the sales team initially, but they are often not involved with your implementation. We are certain to communicate your requirements again to the implementation team. They might not be fully versed about your specific needs.

We can save you many problems. We will ask the right questions and we have the skills and experience to help you avoid the pitfalls. We find, when our organization works with an internal team, that our information architects ask questions no one else has asked. Because we have experience with so many implementations—more than any individual company could have—we generally help people anticipate situations that they don't know might present problems.

Content Management for Dynamic Web Delivery

An Information Model provides the framework for organizing your content so that it can be delivered and reused in a variety of innovative ways. Once you have created an Information Model for your content repository, you will be able to label information in ways that will enhance search and retrieval, making it possible for authors and users to find the information resources they need quickly and easily.

The Information Model is the ultimate content-management tool.
Creating your Information Model requires analysis, careful planning, and a lot of feedback from your user community. The analysis takes you into the world of those who need and use information resources every day. The planning means talking to a wide range of stakeholders, including both individuals and groups who have information needs and who would profit from collaboration in the development of information resources. Getting feedback requires that you test your Information Model with members of your user community to ensure that you haven't missed some important perspectives.

You need to learn

• what an Information Model is
• why an Information Model is critical to the success of your content-management system
• how to create an effective and usable Information Model

It's very easy to tell when a Web site you're trying to navigate has no underlying Information Model.
Here are the tell-tale characteristics:

• You can't tell how to get from the home page to the information you're looking for.
• You click on a promising link and are unpleasantly surprised at what turns up.
• You keep drilling down into the information layer after layer until you realize you're getting farther away from your goal rather than closer.
• Every time you try to start over from the home page, you end up in the same wrong place.
• You scroll through a long alphabetic list of all the articles ever written on a particular subject with only the title to guide you.

Sound familiar?
What does it feel like when a well-designed Information Model is in place? Oddly enough, you generally don't notice a well-conceived Information Model because it simply doesn't get in the way of your search.

• On the home page, you notice promising links right away.
• Two or three clicks get you to exactly what you wanted.
• The information seems designed just for you because someone has anticipated your needs.
• You can read a little or ask for more -- the cross-references are in the right places.
• Right away you feel that you're on familiar ground -- similar types of information start looking the same.

Did all of these pleasant experiences happen by accident? Not in the least. Finding the information you needed quickly and easily requires a great deal of advance planning. The basic planning and design tool is the Information Model.

What is an Information Model?

An Information Model is an organizational framework that you use to categorize your information resources. The framework assists authors and users in finding what they need, even if their needs are significantly different and personal. The framework provides the basis on which you base your publishing architecture, including print and electronic information delivery.

An Information Model might encompass the information resources of one part of an organization. For example, your Information Model might provide a framework for categorizing your corporate training materials or the technical and sales information that accompanies your products. Your Information Model might include engineering information produced during product development, policies and procedures used internally in the day-to-day conduct of business, information about customers used in your sales cycle or about vendors used in your supply chain. Some of the information resources you bring under content management might be available across the corporation for internal use, such as human-resources information. Other information resources might be specific to the needs of one department or division of your organization.If an Information Model is clearly defined and firmly established, users will be on a fast track finding and retrieving the information they need.

As you plan what to include under content management and what to exclude, you must consider a wide range of dimensions through which you will categorize and label your information. Some of the dimensions will be specific to the needs of information authors. Others will meet the requirements of your products and services. Still others will explicitly meet the needs of internal and external users of information.

As you design your Information Model, consider how large an information body it must encompass. Some Information Models are very small, specific, and limited in scope. Others stretch across entire organizations, encompassing thousands or millions of pages. In the next section, you start with a small, personal Information Model. In subsequent sections, you consider larger, more complex models for larger bodies of information.

The three-tiered structure of an Information Model

The Information Model you build will have a three-tiered structure. At base, the first tier of the Information Model consists of the dimensions that identify how your information will be categorized and labeled for both internal and external use in your organization. The second tier sorts your information assets into information types. The third tier provides structure for each information type, outlining the content units that authors use to build information types. Figure 4-1 illustrates the three-tiered structure. In this chapter, you learn how to determine the basic dimensions of your Information Model. In Chapter 5, Developing Information Types and Content Units, you learn how to identify your information types. And, in Chapter 6, Using Content Units to Structure Information Types, you learn how to identify the content units that provide the internal structure for each information type.


The three-tiered structure of an Information Model


The dimensions you identify as the foundation of your Information Model become the attributes and values of the metadata you will use to label your modules of content in your repository. The information types will provide your authors with the basis for creating well-structured modules that represent a particular purpose in communicating information. The content units will describe the chunks of content that are used to construct each information type.

In the next section, you will look at an extended example of the process one might use to begin the development of an Information Model. Throughout the core design Chapters 4, 5, and 6, I refer to this extended example to provide you with a model for developing the Information Model for your organization.



Starting with a personal view of an Information Model

Here is a typical example of how an Information Model might be applied. At home, I have a large collection of cookbooks and cooking magazines, plus lots of recipes cut out of newspapers or sent by friends and relatives. Yet, every time I want to find a particular recipe I remember having used or look for a new recipe for a dish I want to try, I'm stymied by the very books that are such a valuable resource. Where is that recipe? Which book or magazine was it in? Was it last year or ten years ago? Is it in the small green file box or the large cookie tin?

When a sound Information Model is in place, it assists users in finding the answers to their questions.

The cookbooks I own are organized in various interesting ways. Some are organized by month, based on the original magazine issues. Sunset Magazineô, for example, publishes a cookbook annual in which each chapter contains a month's worth of recipes from its magazine. Other cookbooks are organized alphabetically by ingredient or by country of origin. Still other cookbooks are organized by the main ingredient or a part of a complete meal. Several books I own have sections focusing on chicken, pork, beef, or vegetables. They also have sections on soups, desserts, and appetizers. All these different organizations are interesting and effective individually. However, as a complete collection, they fail. They fail because they lack a comprehensive Information Model to support the organization of their content.

How might I improve the organization of the recipes in the cookbooks? First, I would need to understand how I or another amateur cook might search for and use the information. If I'm organizing the content for myself, I might want recipes organized by ingredients, parts of the meal, country of origin, and time to complete. I might also want to organize them by recipes already tried, successful recipes, unsuccessful recipes, new recipes that look interesting but remain untried. All of these categorizes would facilitate searching for just the right recipe for an occasion. In fact, by assigning one or more categories to each recipe, I would be building an Information Model to fit my conceptual view of the cookbook world. If I wanted to include others in my Information Model, I'd need to know something about the categories that would be interesting to them.

The Information Model also assists authors in retrieving information for reuse and revision. It helps us answer questions like

• Where is that explanation of what cornstarch does in a recipe?
• Where are the recipes for pasta with asparagus?
• Don't you have an instruction for cutting a chicken into pieces for frying?

Just what is cornstarch and what is it doing in my recipe?
By following a link from Cooking 101, the amateur chef locates an explanation in the Ingredients Encyclopedia on a well-organized Web site. A comprehensive Information Model underpins the Web site design.

An organizational Information Model

Several years ago, I conducted an interesting and significant test of an organization's informal Information Model. A state department of vocational rehabilitation needed to answer questions from its constituencies, which included disabled individuals seeking job assistance and companies inquiring about hiring and supporting the disabled. Much of the information to answer these questions could be found somewhere in the large volumes of government regulations and policy statements maintained in the organization's library, in the offices of staff members, and in the heads of key employees. Unfortunately, the right person with the right information to respond to a question wasn't always available. Or, the person taking the question would not always know whom to ask. As a result, some customer questions were not being handled as well as management wanted. They needed a content-management system to support their goal of being responsive to their constituencies. I conducted an Information Audit of their responses to provide a design concept and cost justification for the new system.

The audit was simple and interesting to conduct. Based on a well-researched list of typical questions developed by the experienced managers, members of my staff called at random with requests for information. They recorded how long it took to obtain the right answer. Most of the time, the department staff was very effective. Calls were answered promptly; often the person taking the call could provide the correct answer immediately or within a few minutes. But, at times, callers were shifted around to several individuals without obtaining a satisfactory answer to the questions. In other cases, the promised materials never arrived in the mail. Sometimes the materials received weren't the right ones. Although the staff was very competent as a whole, better internal access to information resources was sorely needed.

People use many sources to find the information they need: other people, the library, books nearby on office shelves, sources in other organizations. A sound Information Model ensures that the sources of information are effectively categorized according to the users' conceptual model of the information.

An Information Model could be built so that it facilitated ease of access and accuracy of response. In this instance, much of the information needed to answer questions was available, although not always quickly available. In cases where the correct information was not available at all, the gap meant that new information assets should be developed.

The investigation showed that a content-management system was needed. To be effective, the content-management system needed to be based on a sound Information Model, one that would become the eventual framework for a content-management system. The immediate goal was to make the information resources readily available to the staff members. The long-term goal was to make the information resources available to the outside customers through an Internet site. If it was well designed, the Web site would allow the agency's constituents to find their own answers even more quickly and easily than by calling in.

A place for everything

One way to think about an Information Model is as a large filing system -- a place for everything and everything in its place. In fact, you have the real life example of the library as a content-management system that embodies a particular Information Model. Through familiarity, people learn to make effective use of a common and consistent Information Model to find what they need.

At university, I learned how to use the graduate library which was organized according to the Library of Congress' Information Model. I knew exactly where to find the books I needed, often without using the electronic catalog system that had recently replaced the old paper card catalog system. I knew which floor the eighteenth century history books were on and where to find the art history as well. In fact, I could walk into any university library and pretty much find my way around. The Information Model on which these libraries are based is quite uniform among higher-education institutions. It gives you a nice, comfortable feeling of continuity. The books are where you expect them to be. Each book has a number that identifies its place on the shelves, and experienced users who have learned how the system works feel very much at home.

Unfortunately, not all libraries are the same. Going to a different kind of library is as disconcerting as venturing into a new Web site.

In recent years, I have used the local community library far more often than I use the university library. My local library was at first really confusing; nothing was where I expected it to be. The reason -- they manage their content using a different Information Model, a different arrangement of categories, based on the Dewey Decimal system, which is often used to organize community libraries. I was frustrated to discover that the books by my favorite author were in one location while the books about the author were in quite a different location. Eventually I figured out the system but I have never felt quite at home with it.

Information Models not only facilitate fast search and retrieval, they also create a sense of familiarity and belonging for their users. As experienced users of a content-management system based on a sound Information Model, you know where to find what you need. It's right there in the same place it was last time and exactly where you expected. As a library user, the Information Model underlying the library's content-management system allows you to manage the content effectively for yourself.

Even familiar models are challenging for newcomers

Unfortunately, Information Models that are quite understandable by experienced individuals are often equally obscure to newcomers. The vocational rehabilitation department could create an organization for their information resources that would be easily accessible to trained personnel working on the inside. But would the same organization of information work for the outsiders, the people with the questions? Most likely, the answer would be "no."

The problem is that the content-management system that is useful for the authors of the information is not usable by users of the information who do not understand the underlying Information Model.

Take the case of the library. The typical catalog makes information available in several ways, typically by the name of the author, the title of the work, and keywords and descriptions associated with its subject matter. If you know the author's name or the title of the work, the search can be reasonably quick and easy. But lacking that critical information, the opportunities for frustration abound. How do you find information when you have no title and no author? How do you, for example, find out about the insect that bit you in the jungle of Guatemala and is causing you excruciating pain? Is it listed in a guide to Central American entomology? What about a book on tropical diseases? Just where do you begin? If you were an expert on insects or tropical diseases, you would know where to look. But without an expert's knowledge of the underlying Information Model, the solution would probably be too long in coming. If you were on a Web site, you would be tempted to click out before you wasted any more time becoming frustrated.

To be usable by a wide range of individuals with different experiences and expectations, an Information Model must be designed by those who take the time to study and understand the prospective users. By organizing information resources through our analysis of the users and envisioning the user experience you expect for the future, you have a chance at being successful in helping your users reach their goals quickly.

Information Models based on static categories can be difficult to learn

The problem with the libraries is that to gain familiarity with their Information Models, you need help and experience. In fact, you even need to have some training in school about how to find things in the library. The libraries employ quite sophisticated help systems, often in the person of reference librarians, to help naive users find what they need. The reference librarians are taught methods of asking the right questions of the users in order to point them in the right direction. Unfortunately, when your customers visit your Web sites, there are no helpful librarians -- so all the assistance has to be immediately obvious to them. The Information Model you design provides the framework for that assistance.

An Information Model is based upon the categories you select to label and organize your information resources. These categories must emerge organically from your analysis of user requirements. Otherwise, your users will experience some of the same problems that occur in the library -- a set of formal categories that is based more on the categorizer's view of the nature of the information resources than upon the users' needs.

The information architects of the public and university libraries made decisions based on a formal categorization of the material in the collections. The primary organization follows academic, classical subjects -- history, art, music, literature, science, and so on. The secondary and tertiary organizations are based on author's name or time period (centuries) or geographic locations and a host of other possibilities, depending on the nature of the subject. The organization appears to mirror the organization of the academies, especially in the university libraries. The people in the History Department are sure to find much of the information they need in the history category. For novices to become experts, they have to learn the system. The system doesn't change in response to the users' needs.

The more the Information Model reflects the way that users think and work, the more effective it will be in delivering the right information to them.

About JoAnn T. Hackos

JoAnn Hackos, PhD, is President of Comtech Services, a content-management and information-design firm based in Denver, which she founded in 1978. In her new book, "Content Management for Dynamic Web Delivery," Dr. Hackos explains the content-management strategy that she developed for companies such as Nortel, Motorola, Cisco, and others and walks readers through the stages of effective Web content management.


Source : http://www.graphic-design.com

Content Management

Pengertian dari Sistem manajemen konten (Inggris: Content Management System, disingkat CMS), adalah perangkat lunak yang memungkinkan seseorang untuk menambahkan dan/atau memanipulasi (mengubah) isi dari suatu situs Web. Umumnya, sebuah CMS (Content Management System) terdiri dari dua elemen:

• aplikasi manajemen isi (Content Management Application, [CMA])
• aplikasi pengiriman isi (content delivery application [CDA]).

Elemen CMA memperbolehkan si manajer isi -yang mungkin tidak memiliki pengetahuan mengenai HTML (HyperText Markup Language)-, untuk memenej pembuatan, modifikasi, dan penghapusan isi dari suatu situs Web tanpa perlu memiliki keahlian sebagai seorang Webmaster. Elemen CDA menggunakan dan menghimpun informasi-informasi yang sebelumnya telah ditambah, dikurangi atau diubah oleh si empunya situs web untuk meng-update atau memperbaharui situs Web tersebut. Kemampuan atau fitur dari sebuah sistem CMS berbeda-beda, walaupun begitu, kebanyakan dari software ini memiliki fitur publikasi berbasis Web, manajemen format, kontrol revisi, pembuatan index, pencarian, dan pengarsipan.

Sumber : http://id.wikipedia.org/wiki/Sistem_manajemen_konten