From MIKE2 Methodology
| A Creation Guide exists that can be used to help complete this article. Contributors should reference this guide to help complete the article.
|
Introduction
The Web Content Management Solution Offering provides techniques for building, managing and delivering web-based content to the internet. The offering includes specific techniques and technologies for browser-oriented content as well as a focus on areas of particular complexity for web channel delivery such as security and usability. New “Web 2.0” technologies as well as more traditional technologies receive coverage within the offering.
Executive Summary
Solution Offering Purpose
This is a Core Solution Offering. Core Solution Offerings bring together all assets in MIKE2.0 relevant to solving a specific business and technology problem. Many of these assets may already exist and as the suite is built out over time, assets can be progressively added to an Offering.
A Core Solution Offering contains all the elements required to define and deliver a go-to-market offering. It can use a combination of open, shared and private assets.
Solution Offering Relationship Overview
This Solution Offering is part of the ECM Solution Group
MIKE2.0 Solution Offerings provide a detailed and holistic way of addressing specific problems. MIKE2.0 Solution Offerings can be mapped directly to the Phases and Activities of the MIKE2.0 Overall Implementation Guide, providing additional content to help understand the overall approach. The MIKE2.0 Overall Implementation Guide explains the relationships between the Phases, Activities and Tasks of the overall methodology as well as how the Supporting Assets tie to the overall methodology and MIKE2.0 Solutions. Users of the MIKE2.0 Methodology should always start with the Overall Implementation Guide and the MIKE2.0 Usage Model as a starting point for projects.
Relationship to Solution Capabilities
The MIKE2.0 Collaboration, Knowledge Capture and Communities of Interest Solution Offering is primarily focused on Information Development. It uses a number of activities from the Overall Implementation Guide to see a project through from strategy to implementation.
Relationship to Enterprise Views
This solution is primarily about enabling Information Development in a knowledge context. It provides the ability to access primarily unstructured content and bring it together for users in a fashion that makes it easy to understand, communicate and learn.
Mapping to the Information Governance Framework
The Information Governance Solution Offering is required across all Solution Offerings. For this offering it is particularly important that the governance models focus on security for accessing information as this can be an area of significant complexity. The scope should cover structured data and unstructured content, with appropriate roles related to taxonomic development, standard lexicons and priorisation of information based on relevancy.
Mapping to the SAFE Architecture Framework
For an web content management programme, a number of components may be required from the SAFE Architecture. All components within Enterprise Content Management are particularly relevant to this offering. In addition, a Search capability is a priority area.
Mapping to the Overall Implementation Guide
A typical Collaborative and Knowledge Management Search engagement will involve a large number of the Activities from the Overall Implementation Guide. Users of MIKE2.0 should review each activity as a starting point to see if they are required based on the scope of the project requirements.
The Usage Model for Enterprise Content Management provides a list of all the required activities for this offering. Shown below are the most important activities for a typical programme and how they relate to the overall approach.
Phase 1 - Business Assessment and Strategy Definition Blueprint
For a comprehensive, top-down programme a number of the activities are required from this phase to define the overall Business Strategy. Some programmes can be quite tactical but generally should cover these tasks at a very high level. Some strategy activities may not be needed if they were already done as part of part of an enteprise programme, as described in the Enterprise Content Management Strategy Solution Offering.
Enterprise Information Management Awareness
The Enterprise Information Management Awareness activity is important to introduce concepts related to collaboration. This is an area that has undergone significant technology changes over the past few years and users typically benefit from education related to community-based content development, security and web-based collaboration.
Overall Business Strategy for Information Development
In the Overall Business Strategy for Information Development activity, the strategic business initiatives are defined in the context of information requirements. For collaboration and knowledge development, this activity defines the scope of information to be shared and collaboratively developed, as well as the ultimate knowledge goals for the organisation.
Future State Vision for Information Management
The Future State Vision for Information Management is an important activity for defining the strategic conceptual architecture for collaboration and knowledge development As this typically involves a number of different conceptual components, a systematic approach to architecture is important. High Solution Architecture Options should also be defined at this stage.
This activity also defines the future-state business processes for information management. This process is critical for knowledge development; at this stage it is focused on high level processes and processes should be re-engineered to improve the mechanism for developing knowledge capital most effectively.
Phase 2 - Technology Assessment and Selection Blueprint
For a comprehensive, top-down programme a number of the activities are required from this phase to define the overall Technology Strategy. Some programmes can be quite tactical but generally should cover these tasks at a very high level. Some strategy activities may not be needed if they were already done as part of part of an enteprise programme, as described in the Enterprise Content Management Strategy Solution Offering.
Strategic Requirements for Technology Backplane Development
In the MIKE2.0 Methodology, Enterprise Content Management technologies are seen to reside along the Technology Backplane of Information Development and Infrastructure Development. This activity is used to define the capabilities that are needed for the strategic implementation of these programme.
Strategic Non-Functional Requirements
Strategic Non-Functional Requirements for Collaboration and Knowledge Management are defined at a overarching level in this activity. There is a particular focus on usability, performance and ability to scale to meet future business volume growth requirements.
Current-State Logical Architecture
The Current-State Logical Architecture assesses the current capabilities in the environment for Collaboration and Knowledge Exchange. This activity specifically defines which technologies can be re-used and the scope of any content that should be migrated.
Future-State Logical Architecture and Gap Analysis
The Future-State Logical Architecture and Gap Analysis builds on the conceptual architecture that is already defined and takes it to the level of detail required to make strategic technology decisions. A gap analysis can then be conducted be conducted between the current-state and future-state to determine which technologies can be re-used.
Future-State Physical Architecture and Vendor Selection
Through defining the Future-State Physical Architecture and Vendor Selection, logical capabilities are mapped to specific product options. This mapping is then used to make technology decisions, often through an RFP-based selection process.
Phase 3 - Information Management Roadmap and Foundation Activities
Within Phase 3, the scope of the solution for a specific increment is defined and the overall content model begins to take shape.
Detailed Business Requirements
When developing the Detailed Business Requirements for collaboration and knowledge development, the focus is on the scope of information to be shared and defining the business goals for collaboration. This activity builds off the strategic set of requirements, adds more detail and prioritises business requirements for the increment of work to be implemented.
Taxonomy Design
The Taxonomy Design activity defines the structures for relating content to one another. For collaboration and knowledge environment, the development of this taxonomy is one of the critical aspects of the solution. Taxonomy design may range from a formally designed structure to one that grows more organically.
Phase 4 - Design Increment
For Web Content Management, a number of design activities are required which are described below.
Information Security Design
Information Security Design defines which information can be seen by users within the collaborative environment. The most important aspects of security design relate to how information is accessed and who can edit content. Group-based access control is typically used to implement security rules.
Infrastructure Management Process Design
The Infrastructure Management Process Design applies to the back-end environment that stores content. It also applies to the management processes and technology responsible for holding backup content from the collaboration environment and making it quickly available in the case of a recovery scenario.
Collaborative Framework Design
Collaborative Framework Design is one of the most important activities for this Solution Offering and all tasks are needed. It is the activity that defines how users will interact with one another, how internal and external assets will be brought together in the collaborative environment and how users may specifically classify content.
User Interface Design
The User Interface Design activity defines the front-end interface in which a user will interact with the collaborative system. From a search perspective, the simplicity of this interface design is essential. Simple data re-engineering steps such as lemmatisation and spell checking may be interactively provided through this interface.
Also critical is the ability for users to be able to quickly make decisions from the large amounts of information that is returned. Users need to be able to visualise information results through graphical views, categorisation of results and personalisation.
Phase 5 - Develop, Test & Deploy Increment
Through development, testing and deployment activities the solution the prototyped is hardened and implemented into production.
Technology Backplane Development
The Technology Backplane Development activity covers the development of integration and information management components for Collaboration, Knowledge Capture and Communities of Interest. This includes development of interfaces, web components and security technologies.
Testing Activities
Depending on the complexity of the solution, different testing activities will be required although testing is generally not complex. Functional Testing and some level of System Integration Testing will be required at a minimum; SVT is are also important. Perhaps most important is UAT; it should be ensured that are users are actively engaged throughout the development and testing process. Testing for collaboration and knowledge exchange technologies is much quicker than other types of engagements.
Mapping to Supporting Assets
Logical Architecture, Design and Development Best Practices
Product-Specific Implementation Techniques
Product Selection Criteria
Relationships to other Solution Offerings
Extending the Open Methodology through Solution Offerings
Extending the Open Methodology through Solution Offerings
Listed below are proposed extensions to the Overall Implementation Guide to meet the requirements for this Solution Offering:
Potential Activity Changes
Overall Business Strategy for Information Development
The Business Strategy for web content management should involve knowledge exchange requirements.
Solution Architecture
This activity will likely be generalised to better cover solution offerings
BlogMarks
del.icio.us
digg
Furl
Simpy
smarking
