| In recent times I have gone through an article on | | | | developers would work with Human Resources to |
| intranet where it has been reflected in the sense that | | | | create the application. The problem with centralized |
| an artistic method feasible to intranet can be put side | | | | control and formal approval processes is that they |
| by side to a composition process where we can | | | | put creativity and timeliness in thumbscrews. |
| endeavor to construct the roof of the house before | | | | Following a decentralized model, each department |
| we place the underpinning, and we may facade | | | | within the organization is responsible for its section of |
| somber problems. Let us dispense the concrete for | | | | the intranet. All departments that want to create |
| the foundation of the house before we put in the | | | | intranet services will have to set up, design and |
| necessary plumbing for water and sewer access, and | | | | administer their own intranet servers. Each |
| have to spend more money than we bulldoze for. | | | | department will also be responsible for creating the |
| We can build a house one footstep at a time and as | | | | publications and applications used by the department. |
| such we can make certain the house which has a | | | | When we can draw on a decentralized model, we |
| strong foundation. Buildings with strong nitty-gritty | | | | hack out the prescribed endorsement procedure for |
| tending to a certain period. When we have more or | | | | new publications, applications, and services. This |
| less done with the frame of the house, we build a | | | | means anyone can create intranet resources. Greater |
| roof. Although the roof of the house is the top of | | | | freedom and few controls means that new services |
| the structure, we do not stop there. It takes more | | | | can be set up quickly by anyone who wants to set |
| than a covered frame to make a house. We hire an | | | | them up. This freedom and lack of controls can also |
| electrician to do the wiring and bring back the | | | | lead to abuse of the intranet resources. When |
| plumber to finish the plumbing. Afterward, we hang | | | | someone publishes potentially offensive material or |
| plaster board, add insulation, finish the exterior, add | | | | when the usefulness of the intranet deteriorates |
| fixtures, and before we know it, we have a house | | | | because so much junk has been created? By |
| that we can call home. We build an intranet in the | | | | adopting elements of both the centralized and |
| same way, one step at a time. We can initiate on the | | | | decentralized model that fit the needs of the |
| intranet is about as glamorous as the water and | | | | organization, we might be able to balance the need |
| sewer pipes waiting for the foundation to be poured | | | | for strict control with our artistic self-determination. |
| around them; for just when we are ready to roll | | | | For paradigm, we could create an intranet with a |
| back our sleeves and dive into the intranet creation | | | | centralized Web server that links together |
| process with both feet, we might discover we need | | | | departmental servers. The IS staff would be |
| to conduct research, planning, or consider the | | | | responsible for maintaining the central server and |
| requirements of the intranet. When we finally flesh | | | | updating links to resources throughout the |
| out the foundation of the intranet, we start to build | | | | organization. The individual departments would be |
| the framework. The basic components of any | | | | responsible for maintaining their own servers. To |
| intranet are the hardware and software that make it | | | | ensure the intranet is not abused, one person within |
| work. The hardware used in the intranet is focused | | | | each department could be responsible for that |
| to determine the way the intranet is operated. | | | | department's intranet resources. |
| The software our intranet uses will determine what | | | | The real stars on our intranet are the applications we |
| the intranet is used for. Eventually, we finish designing | | | | plan to develop. Still, we will need content for our |
| the intranet, but find we still have to develop the hot | | | | intranet. Most of our content will be in the form of |
| Java-powered applications for the intranet. Even | | | | hypertext documents that are served by our Web |
| when we have completed the design and | | | | server and displayed by our chosen Web browser. |
| development processes, the intranet still is not over | | | | As we consider the type of content we want to |
| and done with in order to check the structure of the | | | | publish on our intranet, think about how we will |
| work for flaws. We make sure we have used the | | | | organize that content. We can organize hypertext |
| right structure and created the best tools. Once all | | | | documents in many ways. The structure that is best |
| this is done, we finally have an intranet worthy of | | | | for a particular document depends on the complexity |
| the CEO's wholehearted embrace. Try to build the | | | | of the material we plan to present. For a small |
| whole house at once and we will be overwhelmed. | | | | document with limited complexity, a simple structure |
| The same is true for any creative process. When we | | | | is often best. Simple structures include linear and linear |
| are building our intranet and its applications, we need | | | | with alternative paths. The simplest way to structure |
| to manage many things on a level of general | | | | a hypertext document is in a linear fashion. Using a |
| organization and on a more specific level. If we | | | | pure linear structure, we can create a hypertext |
| mismanage expectations, our intranet might not turn | | | | publication with a structure resembling a traditional |
| out as we plan. Our potential anticipation and the | | | | print publication. Readers move forward and |
| opportunity of our superiors might be totally | | | | backward in sequence through the pages of the |
| different. Before we start to design the intranet and | | | | publication. An alternative path structure gives |
| the Java-powered applications for the intranet, make | | | | readers more options or paths through a document. |
| sure our prospect and the expectations of our | | | | By providing alternative paths, we make the |
| administrator network. A good way to do this is to | | | | structure of the publication more flexible. Instead of |
| ensure that the infrastructure channels are open and | | | | being able to move only forward and backward |
| used. | | | | through the publication, readers can follow a branch |
| To make certain that our scheme is a devastating | | | | from the main path. In a linear structure the branches |
| success; we should argue outlook throughout the | | | | will rejoin the main path at some point. The |
| progress of the intranet, principally as we develop our | | | | hierarchical structure is the most logical structure for |
| intranet applications. If we develop a rapid prototype | | | | a publication of moderate complexity. In this |
| of key applications, our superiors should be the ones | | | | structure, we organize the publication into a directory |
| to verify that the designs meet their expectations. If | | | | tree. Readers can navigate through the publication, |
| the model does not meet their outlook, maybe the | | | | moving from one level of the publication to the next, |
| prototypes were an example of what not to do, or | | | | more detailed, level of the publication. They can also |
| maybe the expectations of management are | | | | go up the tree from the detailed level to a higher |
| unrealistic. If our prototypes meet or exceed the | | | | level and possibly jump to the top level. |
| expectations of our superiors, we have a green light | | | | The information bank tree intimately look a lot like |
| and our project is well on its way to a successful | | | | the way we store files on our hard drive in a main |
| implementation. We should also manage our personal | | | | directory with subdirectories leading to files. We could |
| expectations for the intranet and its applications. Our | | | | also think of the hierarchy as a representation of an |
| expectations play a major role in the success of the | | | | actual tree. If we invert the tree, the trunk of the |
| intranet. Realistic expectations ensure the success of | | | | tree would be the top level of the publication. The |
| our intranet. If we perceive the intranet as an | | | | trunk could be the overview of the publication. The |
| impossibly large undertaking, we might cripple by | | | | large boughs leading from the trunk would be the |
| virtue of wide range of knowledge in this regard. If | | | | next level of the document structure. The boughs |
| we perceive the intranet as a trivial undertaking, we | | | | could be chapter overview pages. Branches leading |
| will not produce the best possible structure and tools | | | | from the boughs would be the next level, or the |
| for our organization. It is best to find a balance in our | | | | pages within chapters. A combined linear and |
| perceptions about the intranet. As we begin to | | | | hierarchical structure is one of the most used forms |
| design the intranet, keep in mind that the intranet | | | | for hypertext publications. This is because it is an |
| creation process is a team effort. Few individuals will | | | | extremely flexible, but still highly structured method. |
| be able to handle all aspects of creating the intranet | | | | Readers can move forward and backward through |
| and its applications. For this reason, we should have | | | | individual pages. They can navigate through the |
| an accurate perception of our abilities and know | | | | various levels of the publication by moving up a level |
| when it is in the best interest of the project to | | | | or descending to the next level. They can also follow |
| delegate tasks. | | | | parallel paths through the document. The most |
| Generating an intranet is exhilarating and demanding | | | | complex structuring method is the integrated web. |
| and as such we have to break a new ground, making | | | | This method lets the reader follow multiple paths |
| efforts for new things, and carry out research work | | | | from many options. This is a good method to use |
| with a new-fangled request. Managing the intranet is | | | | when we want the reader to be able to browse or |
| the creation of an amazing process in whatever way | | | | wander many times through the publication we have |
| some one will motivate us. If one way of thinking | | | | created. Each time through the publication, readers |
| about the intranet is not motivating we, change | | | | will probably discover something new. After |
| tactics. Do whatever it takes to get the job done. | | | | considering the various styles for hypertext |
| We do not limit a few strategies or stick with one | | | | documents, we should examine the various tools we |
| strategy when it obviously is not working. Make a list | | | | will need to develop the intranet. A tool is anything |
| of strategies. If one strategy is not working, switch | | | | that supports the task we are working on. The tools |
| to a new one. If we do not have a new one, create | | | | for unleashing the power of our intranet are based |
| a new one. The strategy we use can be very basic. | | | | on the existing tools for the Internet itself, which |
| A great strategy to start with is to plan to work on | | | | includes protocols, resource tools, and information |
| the project every day until it is completed. In addition | | | | services. TCP/IP (Transmission Control Protocol |
| to this strategy, we should add planning to involve | | | | Internet Protocol) is the foundation of the worldwide |
| both management and users in the development | | | | Internet. We must install TCP/IP on our network to |
| process. The degree of participation for management | | | | enable intranet services. A protocol is a set of rules |
| and users might need to be adjusted throughout the | | | | for programs communicating on the network. It |
| development process. Our role in the project should | | | | specifies how the programs talk to each other and |
| be a part of our strategy. Initially, we might want to | | | | what meaning to give to the data they receive. |
| work closely with the development team. Later, we | | | | Without TCP/IP setting the rules for our network |
| might discover that our best role is to manage the | | | | communications, we cannot use Internet |
| development at a higher level. Or if we are the top | | | | technologies. The good news is that if our |
| programmer or network administrator, we might find | | | | organization already has access to the World Wide |
| that we need to work on application design rather | | | | Web; we might already have the necessary TCP/IP |
| than the actual programming. Adapting our role as | | | | structure in place. Additionally, TCP/IP is built in to |
| necessary can help the project flourishing. | | | | some operating systems, including Windows 95, |
| When we start working on the intranet design and | | | | Windows NT, and most variants of UNIX. If we have |
| creation process, one of the first things we should | | | | an operating system where TCP/IP is not built in and |
| do is develop goals. Our goals should take into | | | | do not have TCP/IP installed, we will need to |
| consideration the complexities and nuances of the | | | | purchase TCP/IP software. Fortunately, TCP/IP |
| intranet we plan to develop for our organization. | | | | software is widely available from software vendors. |
| Goals should be clear and relevant to the problem at | | | | An intranet without Web services is like a world |
| hand. Set major goals relevant to the purpose, | | | | without water. The key to the World Wide Web is |
| scope, and audience of the intranet. Also, set minor | | | | the hypertext transfer protocol. HTTP offers a |
| goals or milestones for the stages of the intranet | | | | means of moving from document to document, or of |
| development and its applications. Goals and milestones | | | | indexing within documents. Accessing documents |
| help define the intranet development process as a | | | | published on our intranet involves communications |
| series of steps or achievements. One major goal | | | | between browsers and servers. In a browser, such |
| could be to complete the planning of the intranet; | | | | as the Netscape Navigator, the HTTP processes are |
| another major goal could be to complete the design | | | | virtually transparent to the user. All the user really |
| of the intranet. The series of steps necessary to | | | | has to do is activate links to move through our Web |
| complete the major goals are the minor goals or | | | | presentation. The browser takes care of interpreting |
| milestones. Our first milestone will be to start work | | | | the hypertext transfer commands and communicating |
| on the intranet. Another milestone might be to select | | | | requests. The mechanism on the receiving end, which |
| and purchase the necessary intranet software, such | | | | is processing the requests, is a program called the |
| as Web server software, browser software, and a | | | | Hypertext Transfer Protocol Daemon (HTTP). A |
| Java Development environment. Our goals are to | | | | daemon is a UNIX term for a program that runs in |
| complete the major steps of the development | | | | the background and handles requests. The HTTP |
| process, such as planning and design. In designing a | | | | daemon resides on our Web server. Before setting |
| constructive intranet system, the intranet designer | | | | up or installing server software, we must determine |
| may create or provide rules that pertain specifically | | | | what platform the Web server will run on. Until |
| to the intranet's law or scope of control, such as the | | | | recently, our choices were limited, but this changed |
| Information Systems department that will have | | | | rapidly as the World Wide Web grew in popularity. |
| overall responsibility for the intranet after completion. | | | | Today, Web server software and server |
| As we start to create the intranet, these rules might | | | | management tools are available for almost every |
| seem perfectly acceptable. However, as we conduct | | | | platform. And, like other software developed for use |
| planning for the intranet and its applications, we might | | | | on the Internet, this software is available as |
| find that the overall responsibility of the intranet | | | | freeware, shareware, and commercial software. We |
| should be divided amongst the departments that will | | | | will find that UNIX platforms have the most options |
| set up intranet servers. If these early rules cannot be | | | | for server software. Until recently, there was only |
| modified to fit the current situation, we will have | | | | one good choice for the Windows NT environment, |
| problems. We might encounter delays due to loss of | | | | but this has changed. There are now many excellent |
| efficiency or the final product might not be what was | | | | commercial and freeware choices for Windows NT. |
| expected. | | | | For other platforms, there is generally only one |
| No rule should ever be considered absolutely and | | | | choice in server software. Having only one choice of |
| even the best of rules should be interpreted as | | | | server software for the Windows system which |
| guidelines that can vary depending on the situation. | | | | doesn't mean the quality of the server software is |
| Rules for a complex project like our intranet should | | | | poor. Quite the contrary, the quality of the software |
| be flexible and make sense. A rule that conflicts with | | | | is often quite good. Tools are an essential part of |
| something we are trying to do should be reexamined. | | | | any operation. Resource tools provide the means for |
| The rule might be inappropriate for the situation we | | | | sending and retrieving information. There are three |
| are trying to apply it and as such our intranet will | | | | basic tools of intranet working: |
| never be put into action if we avoid working on it. | | | | Electronic mail is a great way to communicate. Think |
| Putting off work until something is due is a poor | | | | of e-mail as a way to send letters to anyone within |
| practice. Relinquish when things do not go our way or | | | | the company instantly. Many e-mail programs enable |
| when we seem to have a block is another poor | | | | delivery of mail to single users or groups of users. |
| practice. Even if we flourish on cut-off date, sketch | | | | Some e-mail programs even provide ways to |
| to work toward intranet's goals and milestones | | | | automate responses. Most browser packages are |
| regularly-every day if necessary and possible. We | | | | packaged with e-mail software. File transfer protocol |
| should also plan to work on the intranet and its | | | | provides the basic means for delivering and retrieving |
| applications during those times when our thoughts | | | | files around the network. The files can be text, |
| are not flowing. Everyone has bad days and good | | | | sound, or graphics. FTP provides a springboard for |
| days. Some days we take more breaks. Some days | | | | many information-based approaches to retrieving |
| we work straight through the day and into the night. | | | | information. Many higher level tools that have |
| We might tend toward other destructive behavior | | | | friendlier interfaces use FTP or a protocol similar to |
| besides avoiding or putting off work. Sometimes | | | | FTP to transfer files. Just about every browser |
| programmers go to the opposite extreme. They tear | | | | currently available supports FTP. Telnet lets our |
| things apart impulsively before letting the work cool | | | | intensive log into another system and browse files |
| off so they can look at it objectively. Never hack our | | | | and directories on that remote system. Telnet is |
| code just because a few users didn't like our | | | | valuable because it is easy to use and basic to the |
| application's interface. Managing the aspects of the | | | | network. When we telnet to another computer, we |
| intranet's design and creation is only the beginning. | | | | can issue commands as if we were typing on the |
| The next step is to determine the best organization | | | | other computer's keyboard. On some platforms, like |
| for our intranet. Over the years, three models have | | | | UNIX, telnet is a built-in resource. On other platforms, |
| developed for information systems like our intranet: | | | | we will need a telnet tool. The basic resource tools |
| centralized, decentralized, and a combination of | | | | are indispensable when used for the purpose that |
| centralized and decentralized. The three computing | | | | they were designed for. They even provide the |
| models are really driven by the types of computers | | | | fundamental basis for many high-level resource tools, |
| in use at an organization. | | | | but they simply weren't designed for the advanced |
| Following the centralized model, all computer | | | | manipulation of the wealth of information available on |
| resources are centered in one location and under the | | | | the Internet. This is why dozens of information |
| management of one organization. When we think of | | | | resource tools have been designed to manipulate |
| centralized computing, think of mainframes and | | | | networked data. |
| computer centers. With the introduction of file server | | | | At this juncture, there will be a list of high-level |
| and client server computing, most organizations | | | | resource tools we might want to use on our intranet: |
| moved away from the centralized model toward a | | | | A system to automatically gather, index, and serve |
| decentralized model. In decentralized computing, | | | | information on the Internet. Archie is a great tool for |
| computer resources are spread throughout the | | | | searching our intranet's file archives. Once we set up |
| organization and under the management of the | | | | Archie services, users can access Archie resources |
| departments in which the computers are located. | | | | with their browser. A distributed information service |
| When we think of decentralized computing, think of | | | | that enables us to move easily through complex |
| the high-power workstations and servers. After the | | | | webs of network resources. Gopher uses a simple |
| big move to decentralize computer resources and | | | | protocol that enables a Gopher client to access |
| dismantle massive computer centers, many managers | | | | information on any accessible Gopher server. Most |
| had a rude awakening to the anarchy decentralized | | | | browsers directly support Gopher. An automated |
| computing can cause. Let us imagine an organization | | | | mailing list distribution system. Users can subscribe to |
| where each department sets the rules and decides | | | | LISTSERV lists we set up on the intranet, which |
| the standards, like what hardware and software to | | | | enables them to read e-mail posted to the list or to |
| purchase and how that hardware and software | | | | post e-mail to the list. Once we set up a LISTSERV |
| should be set up. Then imagine the nightmare of | | | | server, users can join lists and participate in lists using |
| trying to support the gauntlet of software and | | | | standard Internet e-mail software. Most browser |
| hardware installed throughout an organization the size | | | | packages include e-mail software. A bulletin board |
| of AT&T. Because of a lack of control with | | | | system of discussion groups called newsgroups. Users |
| decentralized computing, many organizations are | | | | can participate in newsgroups posting messages to |
| moving to the happy middle ground of a mixed | | | | the group and can read messages posted by other |
| computing model. In this mixed model, a centralized | | | | newsgroup members. Once we set up a newsgroup |
| Information Systems management sets broad policy, | | | | server, users can browse newsgroups and post |
| such as the direction and purpose of key computing | | | | information to newsgroups using a newsgroup reader. |
| initiatives, and the individual departments are free to | | | | Most browser packages include a newsgroup reader. |
| work within those guidelines. | | | | A distributed information service for searching |
| As we thrash out the accomplishment of the intranet | | | | databases located throughout the network. It offers |
| with management, we should consider keeping the | | | | indexed searching for fast retrieval and an excellent |
| three working out models in mind. While our | | | | feedback mechanism that enables the results of initial |
| organization might currently use a specific model, we | | | | searches to influence later searches. WAIS servers |
| can apply any of the models to the design of our | | | | are best accessed via CGI scripts, which allow users |
| intranet and should egg on administration to prefer | | | | to search databases using their browser. Using HTML |
| the mock-up that wills finest hand round our institute. | | | | development tools, we can quickly and easily create |
| In an ideal world, the concluding pronouncement will | | | | HTML documents for our intranet. HTML editors have |
| be based on the necessary responsibility and control | | | | features similar to our favorite word processor and |
| of the intranet resources. Subsequent a centralized | | | | enable us to easily create documents in HTML |
| model, a specific department within the organization | | | | format. Typically, these editors enable us to select |
| will be responsible for the intranet. This identical | | | | HTML elements from a pull-down menu. The menu |
| division will be accountable for the setup, design, and | | | | has brief descriptions of elements we can add to the |
| administration of our intranet servers. The | | | | document. The editor places the element in the |
| department will also be responsible for creating the | | | | document in the proper format, which frees us from |
| necessary publications and applications based on user | | | | having to memorize the format. When creating |
| requests. With a centralized model, there will usually | | | | complex forms, we 'all find HTML editors especially |
| be a formal approval process for new publications, | | | | useful. HTML templates enable us to add the |
| applications and services. This means that if the | | | | functionality of an HTML editor to our favorite word |
| Human Resources department wanted an application | | | | processor. The great thing about templates is that |
| to track employee files, a formal request would be | | | | we can use all the word processor's features, which |
| required. Once the request is approved, the intranet | | | | could include checking grammar and spelling. |