DOC PREVIEW
LEHIGH CSE 335 - Experience Maintenance

This preview shows page 1-2-15-16-31-32 out of 32 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 32 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 32 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 32 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 32 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 32 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 32 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 32 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

Experience MaintenanceWhy Experience Maintenance?What is Experience MaintenanceSlide 4What is the role of knowledge in IS, and IS development?Types of ExperienceData to KnowledgeExperience Maintenance CycleSlide 9Main Areas of Experience MaintenanceWhat does an Experience Management System ShareINRECAINRECASlide 14INRECA MethodologyINRECA Process ModelINRECA Experience BaseSlide 18INRECA ProcessesSlide 20Slide 21INRECA DescriptionsSlide 23INRECA Process Description SheetINRECA ReuseINRECA ReuseSlide 27Maintaining INRECASlide 29Open issues in experience maintenanceSome Companies Using Experience Maintenance SystemsSummaryExperience MaintenanceWhy Experience Maintenance?Consider the cases - when a highly skilled employee leaves, he “takes his experience” with him - when new employees are inducted, they have to be trained manually - when the current project at hand is very similar to one that has been done before – do we need to do it all over again?Solution : Experience Maintenance!What is Experience Maintenance Formally, it is defined as …‘the acquisition, sharing and use of knowledge within organizations, including learning processes and management information systems’What is Experience MaintenanceIn other words It is an information system that aids knowledge workers to create, integrate and reuse knowledge in an organization.What is the role of knowledge in IS, and IS development?SystemsSystemsDesignDesignRequirementsRequirementsAnalysisAnalysisBillCustomerUpdateMarketingInventoryAuthorizeCreditOrderEntryScheduleDeliveryCustomerOrderScheduledDeliveryProductSalespersonSystem System ImplementationImplementationSpecSpecTablesTablesVC++ CodeVC++ CodeArchitectureArchitectureVB CodeVB CodeERDERDCustomerOrderScheduledDeliveryProductSalespersonFormsFormsRefer Experience BaseKnowledgeabout worldReuse applicable experienceUpdate Experience BaseTypes of ExperienceExplicitYou can communicateEasy to formalizeSavable on different mediadisembodied Implicithard to communicateHard to formalizeSaved in brainembodiedExperience Maintenance System converts implicit knowledge into explicitData to Knowledge Very Valuable!Experience Maintenance CycleIdentifyClassifyCollectOrganize/StoreShare/DisseminateAccessUse/Exp lo itCreateWhy Experience Maintenance?Product lifecycle becomes shorter Streamline operations and reduce costs by eliminating redundant or unnecessary processes Reduce training time Foster innovation by encouraging the free flow of ideas Improve customer service by streamlining response time Boost revenues by getting products and services to market faster Enhance employee retention rates by recognizing the value of employees' knowledge and rewarding them for itMain Areas of Experience MaintenanceCapturing knowledge Storing knowledge Creating knowledge Distributing knowledge Sharing knowledge Using knowledgeTransfer knowledge from the individual to the collective realmWhat does an Experience Management System ShareSkills  Experiences Reflections  Lessons Memoirs  Technical advice Experts intuition  Case studies Best practices  MethodologiesINRECA INRECA supports the development of experience management applications by an experience management approach itself. Targeted at industrial experience management applications developmentBased on software engineering techniques and using these techniques to build/maintain experience management applicationsApplies Case-Based Reasoning to experience management application developmentINRECAINRECACompany 1 Company 4Company 3Company 2 Company N…EMA 1 EMA 2 EMA 3 EMA 4 EMA N…INRECACompany 1EMA 1Product 1Product 2Product 3Product N...INRECA MethodologyThe INRECA Methodology (contd.)- Has an experience base containing specific experience on how to build experience management applications- This experience base is represented in the form of linked HTML documents. -The structure of these documents and the linking structure is derived from software process modeling Using this form (textual based) of representation results in: Increased flexibility Decreased accuracyINRECA Process ModelThe INRECA Process Model has 3 main components:1. Process – Describes what should be done2. Method – Describes how to do it3. Product – Describes what is output of the processInput ProductOutput ProductProcessComplexMethodSimpleMethodINRECA Experience BaseINRECA Experience Base is organized on 3 levels of abstraction:1. Common Generic Level The processes, products and methods in this level are common across a wide spectrum of different experience management applications.2. Cookbook Level The processes, products and methods in this level are tailored for a particular class of applications (e.g. help desk, technical maintenance, product catalog).3. Specific Project Level This level describes experience in the context of a single, particular project that has been carried out.INRECA Experience BaseBuilding blocks & general purpose approachRecipe 2Recipe 1 Recipe N…App. 1 App. 2 App. 3 App. N…Common Generic LevelCookbook levelSpecific Project LevelINRECA ProcessesThe INRECA methodology adapts techniques used in software engineering. As a result of this, the INRECA process modeling is very much similar to software process modeling.Like in software process modeling, the processes in INRECA are divided into 3 types:Technical processesOrganizational processesManagerial processesINRECA ProcessesTechnical processes These describe the development of the system and the required documentation. e.g. requirement analysis, testing, system design. Organizational processes These address those parts of the organization’s business process in which the newly developed system will be embedded. e.g. in building a help-desk system, organizational processes could be training help-desk personnel, updating help-desk systemINRECA ProcessesManagerial processes The primary goal of these is to provide services for enacting the technical and the organizational processes. e.g. project planning, quality assurance and monitoringINRECA DescriptionsThe INRECA methodology contains descriptions of each of the processes, methods and products.There are 2 kinds of descriptionsGeneric Descriptions These describe the products, methods and


View Full Document

LEHIGH CSE 335 - Experience Maintenance

Download Experience Maintenance
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Experience Maintenance and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Experience Maintenance 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?