IBM BS029ML Self Help Guide - Page 28

System Component / Roles Administrators Content Developers Content Authors Content Approver PDM WCM TAM System A System B Description Administrators are responsible for the management of the Portal. They are responsible for adding new portlets, new pages, new administrative users, and so on. Content Developers are responsible for creating Web Content Management (WCM) design artifacts, such as site frameworks, and authoring and presentation templates. Content Authors are a subset of Authenticated Users that are delegated the responsibility of creating WCM content. Content Approvers are a subset of Authenticated Users that are delegated the responsibility of approving WCM content. Such users approve or reject content prior to releasing the content for delivery. Portal Document Manager (PDM) is a subcomponent of WebSphere Portal Server responsible for archiving and managing documents. Web Content Management (WCM) is a subcomponent of WebSphere Portal Server responsible for the complete life cycle of Web content information. Tivoli Access Manager (TAM) is an External Security Manager responsible for providing enterprise wide security. System A is responsible for function X. System B is responsible for function Y. 2.1.5 Addressing non-functional requirements Capturing the non-functional requirements is a preliminary task that not only provides a starting point for selecting and sizing the physical components of a Portal solution, but also establishes such key aspects as availability, backup and recovery, disaster recovery, and systems management. In terms of the former aspects, a resulting sizing estimate is normally calculated based on those non-functional requirements giving an approximation of the physical resources required to support the proposed implementation. Of course, many factors influence the selection of the physical resources and actual experiences will vary from that of the sizing estimate for many reasons; the degree of variability can range from the small to the very significant. For those latter aspects, which by no means are exhaustive, the required solution characteristics and capabilities take shape and drive the selection of the hardware and software technologies needed to deliver the proposed implementation, within the constraints of technology, skills, and budget. Unfortunately, the non-functional requirements of a solution also tend to be treated as "second-class citizens" because they do not add any new or improved functionality. Thus, they typically do not receive the proper attention of executives, the project manager, or even the technical team. However, a project must address the likes of availability and performance in all phases of a project life cycle to be successful. For those customers finding themselves in the unfortunate situation of having selected and purchased "bare metal: systems, without having undertaken a thorough non-functional requirements study, the degree of usefulness attributed to fully capturing the non-functional requirements at a later stage is somewhat limited. There remain a number of key objectives that the implementation should strive to meet. 14 IBM WebSphere Portal V6 Self Help Guide