What is KBE? The KBE systems defined as: The use of advanced software techniques to capture and re-use product and process knowledge in and integrated.

Slides:



Advertisements
Similar presentations
Defining Decision Support System
Advertisements

DIGIDOC A web based tool to Manage Documents. System Overview DigiDoc is a web-based customizable, integrated solution for Business Process Management.
Components of GIS.
Systems Development Environment
SWEN 5130 Requirements EngineeringSlide 1 Software Prototyping u Animating and demonstrating system requirements.
1 Software Processes A Software process is a set of activities and associated results which lead to the production of a software product. Activities Common.
CHAPTER 1 SOFTWARE DEVELOPMENT. 2 Goals of software development Aspects of software quality Development life cycle models Basic concepts of algorithm.
Key-word Driven Automation Framework Shiva Kumar Soumya Dalvi May 25, 2007.
Alternate Software Development Methodologies
IS 4420 Database Fundamentals Leon Chen. 2 Agenda About yourself About yourself  Name  Major About the instructor About the instructor Syllabus Syllabus.
Software Engineering 6/e, Chapter 8
SESSION 10 MANAGING KNOWLEDGE FOR THE DIGITAL FIRM.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 1 Software Prototyping l Rapid software development.
© 2005 Prentice Hall12-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Lecture 13 Revision IMS Systems Analysis and Design.
F29IF2 : Databases & Information Systems Lachlan M. MacKinnon The Domain of Information Systems Databases & Information Systems Lachlan M. MacKinnon.
Decision Support Systems
The Traditional Approach to Requirements: Using Dataflow Diagrams Spring
Course Instructor: Aisha Azeem
CSC230 Software Design (Engineering)
Chapter 11 Management Decision Making
Problems with reuse – Increased maintenance costs; lack of tool support; not-invented- here syndrome; creating, maintaining, and using a component library.
Services Product design Concept design
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 1 The Systems.
Write today’s date and title in the front of your book. Underline it.
Chapter 1- Introduction Lecture 1 Ready, fire, aim (the fast approach to software development). Ready, aim, aim, aim, aim... (the slow approach to software.
Organizing Information Technology Resources
SOFTWARE.
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
Chapter 3 – Agile Software Development 1Chapter 3 Agile software development.
Chapter 10 Organizing Information Systems and Services.
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
Legacy systems overview DT Legacy System definition “Legacy system is deficiency in a system in terms of its suitability to the business, its Platform.
©Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapter 8 Slide 1 Software Prototyping l Animating and.
1 SYS366 Lecture 1: Introduction to Systems. 2 What is Software Development? Software Development implies developing some software – but it does not involve.
OHTO -99 SOFTWARE ENGINEERING “SOFTWARE PRODUCT QUALITY” Today: - Software quality - Quality Components - ”Good” software properties.
Chapter 11: Software Prototyping Omar Meqdadi SE 273 Lecture 11 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 1 Software Prototyping l Rapid software development to validate requirements.
OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.
SE: CHAPTER 7 Writing The Program
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Architectural Design Identifying system components and their interfaces.
The Systems Development Life Cycle
Software Product Line Material based on slides and chapter by Linda M. Northrop, SEI.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Software Prototyping Rapid software development to validate requirements.
Definitions of GIS Works with geographic information Performs data input, management, manipulation/analysis, and output functions Composed of hardware,
IS444: Modern tools for applications development Dr. Azeddine Chikh.
Requirements Engineering Requirements Validation and Management Lecture-24.
©Ian Sommerville 2000, Tom Dietterich 2001 Slide 1 System prototyping l Prototyping is the rapid development of a system l In the past, the developed system.
1 SYS366 Week 1 - Lecture 1 Introduction to Systems.
ASSESS Workgroups Aligning Commercial, Government and Research Joe Walsh, IntrinSIM Joe Walsh, intrinSIM Potential Game Changers Andreas Vlahinos, Advanced.
UNIT – II BUSINESS PROCESS MANAGEMENT
Rekayasa Perangkat Lunak Part-6
Chapter 1- Introduction
Software Prototyping.
Software Specification and Configuration Management
TECHNOLOGY PLUG-IN T12 BUSINESS PROCESS.
Chapter 1- Introduction
Modern Systems Analysis and Design Third Edition
Usability engineering
Software Maintenance
Information Systems Development
Knowledge Management Landscape (in US)
Model Based Testing Venkata Ramana Bandari, Expert Software Engineer
Chapter 3 – Agile Software Development
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Decision Support Systems
Technology 6 Operating Systems.
Presentation transcript:

What is KBE? The KBE systems defined as: The use of advanced software techniques to capture and re-use product and process knowledge in and integrated way. Knowledge-based engineering (KBE) is an engineering product development technology wherein the knowledge of the engineered product and its design process is captured and embedded into software system(known as KBE systems) and the use of this system in the design And development of similar new products. The main objective of KBE is to reduce lead time by capturing product and process knowledge. The core of the system is the product model where product and process knowledge is stored. External databases are used for labeled data. Input to the KBE system is usually customer’s specifications, which in turn gives several kinds of output when being processed. The system software is object-oriented and can therefore perform demand-driven calculations.

Existing Knowledge Structure has following drawbacks:-  Disorganized Existing designs, database if not maintained in order make reusability difficult.  Volatile Knowledge that is not documented, like knowledge in the human mind, can be lost when people leave an organization.  Insecure Databases which are not centrally maintained are susceptible to change by users and become unreliable.  User unfriendly Often, captured knowledge has not been documented well, with result that it becomes difficult to understand.  Excessive While capturing knowledge is essential, too much knowledge would lead to confusion and in turn affect re- usability.

Advantages 1.Reduces time to market and lead time 2.Reduce production costs 3.Automates repetitive tasks 4.More innovative 5.Product Optimization Optimizing the design is easy - trial and error goes fast 6.Allows for the reuse of critical knowledge and designs 7.Suitable for analysis and simulation processes 8.Reduces overhead costs 9.Skilled staff turnover is not a big problem 10.Costs and time use can be reduced by 90%

In the above figure, KBE system starts with customer requirements and end with customer satisfaction. (C2C process) In this C2C loop process have more four steps like KBE application design, design the 3D or 2D models, Graphical User Interface (GUI) development & integration of GUI and CAD data.