Research Issues in Systems Analysis and Design, Databases and Software Development phần 8 ppsx

 Ca

Copyright © 2007, IGI Global. Copying or distributing in print or electronic forms without written permission

of IGI Global is prohibited.

by systematically reconciling various perspectives, improving the processes,

and controlling the product data and organizational structure.

Perspective Modeling

The perspective modeling mainly consists of building the concept model

and the perspective model. While the process model depicts the tangible

activities of the project, the concept model and perspective model track the

knowledge evolution and changes of social behaviors.

The first step is to generate the concept structure hierarchy. A concept model is

a hierarchical structure that represents the organization of the ontology (Huhns

& Stephens, 1999; Staab, Schnurr, Studer, & Sure, 2001) that stakeholders

propose and use in their collaboration. Figure 3 shows a concept structure

example of a product development team. Stakeholders may use both top￾down and bottom-up construction methods (Vet & Mars, 1999) to build the

Figure 2. The sociotechnical analysis methodology for knowledge manage￾ment

Perspectve

Model

Dstance

Matrx

Concept

Model

(Ontology)

Conflct

Intensty

Clusterng

Tree

Conflct

Classfcaton

Process

Model

Incdence

Matrx

Task

Assgnment

Matrx

Task

Percepton

Matrx

Task

Agreement

Index

Product

Data

CM

Analyss

Perspectve Control

Ontology

Control

Data

Control

Process

Control

Organzaton Control

Conflict

Detection

Point

Conflict

Control

Modelng and Analyzng Perspectves to Support Knowledge Management 

Copyright © 2007, IGI Global. Copying or distributing in print or electronic forms without written permission

of IGI Global is prohibited.

concept structure. It is possible to apply some templates (e.g., product function

template, organizational template, conflict types template, etc.) to clarify the

concepts. These templates act as the contend-based skeletons for organizing

the external information that stakeholders may share with others.

When stakeholders propose new concepts, the concept structure is updated

and is used to systematically organize these concepts and their relationships.

Since a stakeholder should first consider whether there are same or similar

concepts in the structure, only the novel concepts can be specified and added.

The concepts involved within the collaboration are classified into two types.

Shared concepts are those that have been well defined from previous projects.

They have widely accepted meaning shared among the stakeholders (e.g.,

in Figure 3, Function Requirements, Product, and Organization are shared

concepts). Private concepts are perceived only by some particular stakehold￾ers. Their names or meanings are not expressed around the group. If a group

of people have a shared purpose toward a concept, everyone will be asked

Figure 3. A concept structure built by stakeholders in a collaborative design

project

Product

Functon Structure

Functon lst Mechanical

Behavor

Energy Consumpton

Impact to envronment

Nose rato

S3

Techncal Decson

Desgn Methodology Desgn Process

Domans

Functon Requrements

Desgn Parameter

Process Varable

Events

Tasks

Dependency

Resource

S2 S4

Customer Needs

Axioms

Independent Axom

Informaton Axom

FR

FR

S1

Looking Organzaton

Norm Structure

Company Regulaton Employee

ISO9000

Relatonshp specfed by ndvdual

Relatonshp defned by group

Freezing

system

Shared concept

Prvate concept