From MIKE2.0 Methodology
Revision as of 18:39, 7 July 2009 by Andreas.rindler
-> You are here: MIKE2:FAQs
Listed below are Frequently Asked Questions related to the MIKE2.0 Methodology. Feel to add your questions to this article's talk page
I’m new to MIKE2.0, where should I start?
The best place to start is the Introduction and Overview and Key Concepts before reviewing some of the Introductory Training presentations. To get a more detailed view, you should begin looking at detailed activities in the Overall Implementation Guide or MIKE2 Solutions in your particular area of interest. Finally, it makes sense to review the approach behind the Data Governance and Management Consortium and Licensing Model.
What industries has MIKE2.0 been built for?
MIKE2.0 has not been built for any specific industry. BearingPoint, for example, has applied at MIKE2.0 at clients from industries as diverse as Banking, Telecommunications and the Public Sector. MIKE2.0 Business Solutions link industry-independent content to specific business problems. As of December 2006, MIKE2.0 Business Solutions are in the early stages development.
Is MIKE2.0 specific to any technology?
MIKE2.0 focuses on the area of Enterprise Information Management, starting at a conceptual and logical level. MIKE2.0 Vendor Solutions and Open Source Solutions links this content into specific technology.
Who created MIKE2.0?
A team from BearingPoint initially created MIKE2.0 and released this content as part of the Baseline Release. BearingPoint has released this content under the Creative Commons Attribution License and is formulating the Data Governance and Management Consortium to manage this content. Any extensions beyond the initial Baseline Release are the result of the wider community.
Why did BearingPoint make MIKE2.0 Open Source?
There were a number of reasons, explained in more detail in the Open Source MIKE2.
Who do I contact with questions about MIKE2.0?
You can directly contact the author of any content. If you have questions about MIKE2.0 overall, then contact the MIKE2 Leadership Team.
Is MIKE2.0 affiliated with Wikipedia?
No, but there are some similarities between MIKE2.0 and Wikipedia.
Why should I become a registered user of the MIKE2.0 Methodology?
Only registered members can add content to the methodology and we want to encourage feedback as much as possible. By adding to MIKE2.0, you have the opportunity to directly ask questions, suggest changes and create your own content. In addition, we hope that many of our users will become active members within the Consortium and take on more senior roles.
How do I configure my account?
The preferences tab allows users to configure their own settings that override system defaults related to search parameters, editing configuration and change tracking. Account passwords are also changed in user preferences.
Where can I find the planned changes for future releases of MIKE2.0
The best place to go is the MIKE2.0 Product Roadmap which contains a list of planned future functionality and projected release dates.
This means that an article does exist yet for that page. You can help out by starting a new page on this subject.
How do I add new articles to MIKE2.0?
Refer to Adding a New Article to MIKE2.0 for an overview.
Changes and Releases
Why are some pages in MIKE2.0 Protected?
As MIKE2.0 is a methodology, there needs to be some stability with the core content that can only be achieved by releasing content in a controlled fashion and by protecting content. At the same time, we wanted to encourage users to offer as much feedback as possible and be able to add Supporting Assets at any point in time. We believe are our current model provides us with this flexibility; the approach is explained in more detail in the Release Methodology.
Isn't protecting pages contradictory to the use of a wiki?
Because of the nature of MIKE2.0 as a methodology, the MIKE2.0 Leadership Team believed it was necessary to have these controls in place. This approach is currently being trialled during the initial Beta Period and may undergo some revisions based on its effectiveness. Users should note that although there are a number of pages that are currently protected, this is because the Baseline Release delivered much of the Overall Implementation Guide and Framework. In the future, most of the new content that is added to the wiki will not be protected until it reaches a significant level of maturity.
Alternative Release Methodologies are also being investigated.
Why is some of the content incomplete?
MIKE2.0 is built in a collaborative, iterative fashion and some articles are built out over time. The Release Methodology explains this approach in more detail.
I don’t know what a term means, where can I find it described?
The Glossary provides a list of term definitions, you may also want to link explicitly to the page.
Do I need to agree to specific terms to contribute to MIKE2.0?
Yes. These terms appear at the bottom of the page whenever you try and edit an article. Contribution Guidelines for MIKE2.0 provide additional detail on the standards that should be followed around contributing content.
This is quite straightforward as we’ve picked an industry-standard license with few restrictions. Members must adhere to the terms of the creative commons attribution license, which means they should say where they got the content from, just like a reference in any other published document. If you are referencing a specific article, you should link to the article; otherwise you can just reference the overall approach. This article summarises the approach to licensing.
Can I still make money from our work if it is made available under a Creative Commons licenses?
Yes, there are no commercial restrictions on the approach we have chosen.
Do Creative Commons licenses affect fair use, fair dealing or other exceptions to copyright?
No, fair use still applies.
No, not with the version of the license (attribution only) we have chosen.
Are users allowed to make derivative works from our content?
Yes, as long as they give proper attribution.
MIKE2.0 Solutions Questions
Does MIKE2.0 cover semi-structured and unstructured content?
Yes, although its currently a bit stronger on the structured side. The goal of MIKE2.0 is provide a methodology for Information Development that also covers semi-structured and unstructured content. The current form of the Overall Implementation Guide provides a number of activities that can be applied equally to semi-structured and unstructured content and the SAFE Architecture is comprehensive in its coverage of information management capabilities. A number of starter Core Solution Offerings are included in MIKE2.0 that give comprehensive coverage to Enterprise Information Management and Contributors are encouraged to add to these Offerings and their underlying assets.
MIKE2.0 looks to be target more for a large enterprise, can I use MIKE2.0 for a tactical project?
Yes, definitely. MIKE2.0 can be applied for tactical or strategic projects and not all tasks need to be applied. Usage Models and Core Solution Offerings and their recommendation of tasks to be used from the Overall Implementation Guide are only recommendations, some users may choose to only use small aspects of the methodology. It should be noted, however, that the Leadership Team believe the greatest value in MIKE2.0 is its application as an overall Information Management competency.
Are the strategy activities required for each solution offering?
For many solution offerings, the activities from the Blueprinting phases are shown as being required. The Overlap of Blueprint Activities explains this approach.
Activities are mapped to solutions in the following fashion:
Every task in MIKE2.0 effectively results in a deliverable although in some cases the tendency will be to combine deliverables from multiple tasks within an activity. There will always be at least one deliverable per activity. The approach can vary in the context of a project, examples include:
The rationale for this approach is to move away from document-based artifacts and to better support a model-driven approach to software development. This can, however, be somewhat confusion to users that are used to document templates. There are also arguably some leveling issues in MIKE2.0 and over time we will aim for better consistency in this area.
Therefore, the MIKE2.0 approach is different than some methodologies in that we tend to describe the activity more than shown an exact output. MIKE2.0 also has some deliverables for which there are templates and some for which we have examples.
Are the boundaries of each offering well defined and do the offerings compliment one another?
As best as possible solution offerings have defined boundaries and many of the offerings are complementary.
Do solution offerings overlap one another?
There is some overlap, particularly between offerings within the same group. We have tried to do the same but have blurred the lines a bit more. Part of the reason for this is we wanted to define solutions for how the market classifies different Information Management problems. As solutions re-used common assets (activities, supporting assets, architecture components) then we don’t consider the overlaps to be an issue.
There generally isn’t too much overlap between offerings from different offering groups but if there is it is referred to this as a Composite Solution Offering
Wiki asset search