1 / 11

Prof. Adriaan ( Adrie ) J.M. Beulens and Huub Scholten Wageningen Universit y

CMS 2004. An Ontological Framework for Structuring Process Knowledge for the Process of Model-Based Problem Solving. Reference: HarmoniQua. Prof. Adriaan ( Adrie ) J.M. Beulens and Huub Scholten Wageningen Universit y Social Sciences Group, Information technology Group. September 1, 2004

chibale
Download Presentation

Prof. Adriaan ( Adrie ) J.M. Beulens and Huub Scholten Wageningen Universit y

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CMS 2004 An Ontological Framework for Structuring Process Knowledge for the Process of Model-Based Problem Solving. Reference: HarmoniQua Prof. Adriaan (Adrie) J.M. Beulens andHuub Scholten Wageningen University Social Sciences Group, Information technology Group.September 1, 2004 File:TranspCMS01092004

  2. Contents • Problem statement • Generic Project Aims. • Main project phases. • Dimensions for project Management. • Generic Process Specification. • Requirements for Automatic Project Support. • Reference Strategy and Ontological Approach. • Results sofar. • Detail in presentation by Huub Scholten.

  3. Problem Statement • How to manage effectively Development and Design Projects? • How to make these projects transparent?

  4. Generic project goals: • A product and service with integrity and quality attributes as envisaged, negotiated and agreed upon in proposal.It is assumed that there are a #of measures associated with product, execution and management process of the project.These in terms of: • What activities need to be done. • What are best practices in a disciplinary community for executing these activities related to problem (+domain). • How can one evaluate merits of (alternative) approaches for an activity. • Timely Delivery of Product and Service (quality assurance). • Delivery within budgets and using allowed resources. • Project administration and reporting. Accountability, auditing and quality assurance and control  necessity to closely monitor execution of process by proper administrations about project execution and resources used. This involves: • Activities executed. • Methods, tools, models, data resources and systems used. • Associates executing activities (with skills). • Time and other resources used in activities. For costs and (accrued) benefits.

  5. Major Project phases: • Initial Project Definition, Proposal and Acquisition. • Project Execution and Delivery. • Commonalities: • Problem Statement • Cost benefit • Approach to execute and manage phase of project. • Differences: • Level of abstraction (less detailed– very detailed) • Norm resources versus specific resources during execution. • Choice of methods, models and tools not specific, allowed choice versus detailed choice during execution. • Etc. • Remainder: look at execution .

  6. Dimensions of project management • Process Dimension: Participants need shared understanding of problem (domain) and process to tackle it. • Content dimension: Choices of disciplinary contributions (models and approaches). Manage gap between what is needed, available and possible. • Transparency and Quality dimension. • Acquisition phase: shared understanding about what to achieve (product, quality and process) and at what cost and when. • Execution phase: • Do as agreed upon--- • Administrate and be able to show that team has performed as agreed.

  7. Main Components of Research Process.

  8. Supporting Project Management task Elements of PMT: • Making specifications of project phases. • Followed by execution and obtaining Meta Data about execution for monitoring and control. Automated support calls for: • Formal and precise description of specification . • A specification using terms and relationships that are unambiguous for man and machine. That is obtained via ontological approach. • A specification that is derived form a generic one in the (sub) problem domain. A generic one that is seen as ‘best practice’. This is called using a reference strategy.

  9. Ontological approach Ontology: Formal specification of a Shared conceptualization. Develop ontological structure which is the frame of the intended knowledge base. That is the ‘data structure’ for a certain domain. Some vocabulary terms in this context: • Terms/concepts and relations used to describe domain. • Relations organize concepts in a hierarchical or some self-defined structure. • Instance: actual knowledge. • See Gruber, Borst, Uschold, Chandreskaran.

  10. Project results to date. • Detailed ontological framework for development of a knowledge base for process models. • A generic process ontology in area Water Management. Ontology and knowledge base are proof of principle. • Qualitative evaluation: approach can be used in other domains. • Evaluations by partners: objectives of transparency and quality assurance can be met by approach.

  11. Concluding remarks • Rest of story by Huub.

More Related