© 2012 | The Logic Factory R 247 / G 150 / B 72 R 38 / G 157 / B 192 R 35 / G 41 / B 66 Knowledge Acquisition and Modelling Practical use in projects Lecture.

Slides:



Advertisements
Similar presentations
Calyxinfo Walking through Calyx Info The Organisation.
Advertisements

Achieve Benefit from IT Projects. Aim This presentation is prepared to support and give a general overview of the ‘How to Achieve Benefits from IT Projects’
Applying the Human Views for MODAF to the conception of energy-saving work solutions Dr Anne Bruseberg Systems Engineering & Assessment Ltd, UK on behalf.
PERFORMER WP2 INTRODUCTION 13th of September 2013 CSTB Sophia Antipolis, France.
NML/436/L1-1 Nazareth Northwestern Mutual Life Participants in IS Development l A team of people comprising: l Project Manager l Systems Analysts l Specialists.
C2-SENSE WP2 Bojan Božić, Gerald Schimak, Refiz Duro C2-SENSE WP2 Meeting Paris
Ch 3: Unified Process CSCI 4320: Software Engineering.
© Tally Solutions Pvt. Ltd. All Rights Reserved 1 Shoper 9 Implementation in Chain Store March 2010.
IS Theories & Practices Systems Architecture & Infrastructure IS 655: Supplementary Note 1 CSUN Information Systems.
Information Systems Analysis and Design
ARCH-01: Introduction to the OpenEdge™ Reference Architecture Don Sorcinelli Applied Technology Group.
Chapter 1 Assuming the Role of the Systems Analyst
Internet Management Consultants and Solution Providers Outstanding CMS Projects Lessons from the Front Line.
Panorama Consulting Group LLC ERP Assessment, Selection, and Planning SAMPLE APPROACH.
Introduction to Knowledge Engineering
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Lecture 13 Revision IMS Systems Analysis and Design.
Review 4 Chapters 8, 9, 10.
Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition.
APPLICATION DEVELOPMENT BY SYED ADNAN ALI.
Supporting Decision Making Chapter 10 McGraw-Hill/IrwinCopyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
IMS Information Systems Development Practices
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
McGraw-Hill/Irwin ©2005 The McGraw-Hill Companies, All rights reserved ©2005 The McGraw-Hill Companies, All rights reserved McGraw-Hill/Irwin.
Software projects Management & Development Alireza Saebi
Enterprise Architecture
Project Life Cycle Introduction and Overview © Ed Green Penn State University All Rights Reserved.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 1 The Systems.
Introduction to Information System Development.
Software Development Process
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
Bina Nusantara 2 C H A P T E R INFORMATION SYSTEM BUILDING BLOCKS.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
Information Systems Analysis and Design
BMAN Integrative Team Project Week 2 Professor Linda A Macaulay.
Software Requirements Engineering CSE 305 Lecture-2.
Chapter 10 Information Systems Analysis and Design
Learning by Doing (LBD) based Course Content Development (in Areas of CS and ECE) International Institute of Information Technology Hyderabad, India 1.
1-1 System Development Process System development process – a set of activities, methods, best practices, deliverables, and automated tools that stakeholders.
University of Southern California Center for Systems and Software Engineering Model-Based Software Engineering Supannika Koolmanojwong Spring 2013.
1 Introduction to Software Engineering Lecture 1.
Prepared By Dr. Ahmet KABARCIK IE 101 – Indutrial Engineering Orientation Information Systems and Technology
Software Acquisition and Project Management Lesson I: Introduction.
ELOGMAR-M Review Meeting, Shenzhen, 31/03/ First Review Meeting - Web-based and Mobile Solutions for Collaborative Work Environment with Logistics.
Capturing the requirements  Requirement: a feature of the system or a description of something the system is capable of doing in order to fulfill the.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
Chapter 4 Decision Support System & Artificial Intelligence.
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
Main tasks of system analysis ? 1-study exit=sting information system 2-identify problem 3-spelify system requirement 4-asalysis decision ========= How.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Switch off your Mobiles Phones or Change Profile to Silent Mode.
Ondřej Přibyl L3: System Development Life Cycle page 1 Lecture 3: System Development Life Cycle Doc.Ing. Ondřej Přibyl, Ph.D. Department of applied mathematics.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
C_ITIP211 LECTURER: E.DONDO. Unit 1 : The Systems Development Environment.
People-Oriented Methodologies
Chapter 1 The Systems Development Environment
TPS Kick-Off Presentation
TECHNOLOGY GUIDE FOUR Intelligent Systems.
Chapter 1 The Systems Development Environment
Description of Revision
MBI 630: Systems Analysis and Design
Fereshte Shabany Moghadam
Introduction To software engineering
Course: Module: Lesson # & Name Instructional Material 1 of 32 Lesson Delivery Mode: Lesson Duration: Document Name: 1. Professional Diploma in ERP Systems.
DSS Concepts, Methodologies and Technologies
Chapter 1 The Systems Development Environment
{Project Name} Organizational Chart, Roles and Responsibilities
Presentation transcript:

© 2012 | The Logic Factory R 247 / G 150 / B 72 R 38 / G 157 / B 192 R 35 / G 41 / B 66 Knowledge Acquisition and Modelling Practical use in projects Lecture Knowledge Acquisition and Modelling course Utrecht University ( )

© 2012 | The Logic Factory Curriculum Vitae Roel van den Broek Sinds 2008: Business Consultant en lid directie van The Logic Factory 2001 – 2008: Management consultant bij Capgemini Consulting (IT & Consultancy bedrijf) 1999 – 2001: Knowledge Analyst bij Bolesian (gespecialiseerd in Artificial Intelligence and Knowledge Based solutions) 1995 – 1999: Universiteit van Amsterdam: Artificial Intelligence. – Computational intelligence and artificial life. ‘Development of LeDoux’ dual-route architecture in artificial neural networks using genetic algorithms’. Eerste project gedaan in de verzekeringswereld, maar daarna snel gaan werken voor bedrijven met echte “assets”, zoals fabrieken, treinen, vrachtwagens, schepen of vliegtuigen.

© 2012 | The Logic Factory 3 Facts Focus Offices Selected Customers History Partners Originate from Bolesian and Capgemini Background in Logistics, Manufacturing, Off-shoring and Artificial Intelligence Quintiq (Supply Chain Planning & Optimisation) The Logic Transport (TMS & Mobile solutions) HQ in ‘s-Hertogenbosch, the Netherlands Development Center in Ahmedabad, India Founded 2007, 100% privately owned by founders Currently 35 employees

© 2012 | The Logic Factory

Vision presentation Initial contact Initial meetingScan Contract signingProject Maintenance Scope discussion (SoW)  Training  User test  Parallel test  Acceptance test  Going live Project kick-off 100% live SCP&O 95% version 70% version QBA document  Process analysis  Knowledge analysis  Constraint definition  Interface design  Infrastructure setup  Defining optimisers  Interactive testing  Iterative modelling  Integration testing  Implementation plan preparation  Testing optimisers  Acceptance optimisers  System modelling  Interface development  Knowledge completion  Test plan preparation  Modeling optimisers  Supporting planners  Monitoring KPIs GO LIVE Analysis Phase 1 Modeling Phase 2 Initiation Phase 0 Iterative development Phase 3 Implement Phase 4 Post go-live support Phase 5 Our Project Methodology: combining best of both worlds

© 2012 | The Logic Factory CommonKADS

© 2012 | The Logic Factory CommonKADS vs. Our Project Methodology (1) CommonKADS Principle ‘Not just mining from an expert’s head, but about constructing different aspect models of the knowledge’ CommonKADS Principle ‘First concentrate on the conceptual structure, then on the programming details’ Main goal of the analysis phase. First set up the planning decisions (the structure) and the business rules. Then move to solutions design

© 2012 | The Logic Factory CommonKADS vs. Our Project Methodology (2) CommonKADS Theory ‘KBS construction entails the construction of a number of models that together constitute part of the product delivered by the project’ CommonKADS Theory‘The number and level of elaboration of models depends on the specific project context’ CommonKADS element ‘Organisational model’ -> supports analysis of an organisation. CommonKADS element ‘Task model’ -> tasks performed in the organisational model CommonKADS element ‘Agent model’ -> describes the agents (capabilities, preferences, etc.) CommonKADS element ‘Knowledge model’ -> implementation independent description of the knowledge involved in a task CommonKADS element ‘Communication model’ -> describes the transaction between agents CommonKADS element ‘Design model’ -> describes the design of the system to be constructed Application = software + model description(s) + additional documentation Although one methodology per project one should always pragmaticaly decide what to use or not. Our deliverables are: QBA, QID, QAD, QDD Quintiq Business Analysis (QBA) – Context, Business Goals, KPI Matrix ( Organisation Model ) – Overview Planning decisions ( Task Model ) – Details Planning decisions Business rules ( Knowledge Model ) Use Cases ( Agent Model ) UI ( Communication Model ) Quintig Interface Document (QID) – Interaction between all related applications ( Communication Model ) Quintiq Design Document (QDD) and the model (.qproject) ( Design Model )

© 2012 | The Logic Factory R 247 / G 150 / B 72 R 38 / G 157 / B 192 R 35 / G 41 / B 66 A day in the life…

© 2012 | The Logic Factory Travel or work from home

© 2012 | The Logic Factory Work with the customer or the project team?

© 2012 | The Logic Factory Work in a (internal) project, or full time detached

© 2012 | The Logic Factory Customers and cases