How are the offerings going to be correlated to deliverables?
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: • Overall Business Strategy for Information Development For this activity the tendency is for each task to produce a separate deliverable that can stand on its own • ETL Logical Design Some of the tasks may be combined in the output of a single document. In addition this tends to be done multiple times (i.e. logical design for each source-to-target mapping or each service) 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
