SoMeT 2004 Interplay of Tacit and Explicit Knowledge in Requirements Engineering Marite Kirikova...
-
Upload
leslie-newton -
Category
Documents
-
view
219 -
download
0
Transcript of SoMeT 2004 Interplay of Tacit and Explicit Knowledge in Requirements Engineering Marite Kirikova...
SoMeT 2004
Interplay of Tacit and Explicit Knowledge in Requirements Engineering
Marite Kirikova
Riga Technical University
LATVIA
SoMeT 2004
What is knowledge Lock (1632-1704):“Knowledge then seems to me to be nothing but perception of the connexion of an agreement, or disagreement and repugnancy of any of our ideas”
H. Davenport and L. Prusak [5]:“Knowledge is a fluid mix of framed experience, values, contextual
information, expert insight and grounded intuition that provides an environment and framework for evaluating and incorporating new experiences and information. It originates and is applied in the minds of knowers. In organization it often becomes embedded not only in documents or repositories but also in organizational routines, processes, practices, and norms.”
Sidmae: “Knowledge consists of dynamic functional structures. It comprises the unity of three following aspects: first, understanding of the reality, second, attitude to the reality, and, third, corresponding reaction.”
SoMeT 2004
Main emphasis on the following aspects:
• Systemic nature of knowledge
• Dynamic development of knowledge
• Ownership of knowledge
SoMeT 2004
Knowledge in requirements engineering
Paper based knowledge
Knowledge recorded on mechanical
devices
Knowledge in files Knowledge in data bases
Knowledge in CASE tools
Tacit knowledge(Natural knowledgeMental knowledge)
Explicit knowledge(Artificial knowledgeCodified knowledge)
Digitally documented knowledge
Knowledge Dimension in Requirements Engineering
SoMeT 2004
Addressing tacit knowledge in ISD methodologies by Fiona M. Murphy & Dr. Larry Stapleton, presented at ISD’04, reprinted by permission
SoMeT 2004
Motivation
• Shall we consider potential availability of different types of knowledge and possibilities of its growth when choosing SE approaches?
The hottest point – requirements!
• How interplay of tacit and explicit knowledge influences capability of the methodology?
SoMeT 2004
Approaches Under the Analysis
• Use Cases based approach
• Enterprise Model based approach
• Agile approach
SoMeT 2004
Object Model
Knowledge
integration
Interviews
Use cases
Use Cases based approach(simplified)
SoMeT 2004
Interviews or group work
Business Process Model
Object Model
Businessrules
Actors ...
Enterprise Model based approach(simplified)
SoMeT 2004
Interviews or group work
Agile approach
(simplified)
SoMeT 2004
Knowledge domains
• Knowledge about the enterprise
• Knowledge about the the application
• Knowledge about the design
Knowledge possesors
• Use Cases based approach– User– Analyst – Designer
• EM based approach– Planner – Owner– Designer
• Agile approach– Stakeholder– Designer
SoMeT 2004
Knowledge types
• Tacit • Explicit
• Shallow • Deep
• Pieces • Models• System
Knowledge features
• Consistency– Individual– Shared– Formal
• Completeness– Intuitive– Formal
SoMeT 2004
AnalysisTransfer of tacit knowledgeTransformation of tacit knowledge
DesignTransfer of explicit knowledgeTransformation of explicit knowledge
SocialisationTransfer of tacit knowledgeTransformation of tacit knowledge
ExternalisationTransfer of tacit knowledgeTransformation of explicit knowledge
CombinationTransfer of explicit knowledgeTransformation of explicit knowledge
InternalisationTransfer of explicit knowledgeTransformation of tacit knowledge
ImplementationTransfer of explicit knowledgeTransformation of explicit knowledge
Knowledge elicitation
Knowledge acquisition
Learning
Knowledge interpretation
Knowledge analysis
Tacit knowledge pieces
Explicit knowledge models
Explicit knowledge system
Knowledge Processes and Related Concepts
SoMeT 2004
SocialisationUser and Analyst
ExternalisationUser and Analyst
InternalisationDesigner
Use Cases
CombinationDesigner
Design model
Information about the enterprise
Enterprise and application knowledge pieces
Application knowledge models
Application knowledge models
Enterprise knowledge models
Design knowledge system
Enterprise and applicatoin knowledge+ designers design knowledge
Enterprise knowledge models
Use Cases Based Approach
SoMeT 2004
Use Cases Based ApproachKnowledge Enterprise
Knowledge
transfer (Enterprise – Application)
Application Knowledge transfer (Application -
Design)
Design
TACIT
Shallow Pieces U A d U U A d D D
Models U A d U U A d D D
System (U) (A) (d) (D) (D) D
Detailed Pieces U A U U A d (D) D
Models U A U U A d D D
System (U) (D) D D
EXPLICIT
Shallow Pieces N/a N/a
Models
System
Detailed Pieces
Models
System
Consistency check Individual + + +
Shared Partly Partly -
Formal - - Possible
Completeness Intuitive Intuitive and use cases based IntuitiveFormal
SoMeT 2004
InternalisationPlanner AND Owner
ExternalisationPlanner AND Owner
SocialisationPlanner AND Owner AND Facilitator
InternalisationDesignerEnterprise model
Application model
ExternalisationPlanner AND Owner AND Designer
Design model
CombinationPlanner AND Owner AND Facilitator
SocialisationPlanner AND Owner AND Designer AND Facilitator
ProjectionCASE tool
Enterprise knowledge pieces
A
Design knowledge
B
New enterprise knowledge
To be enterprise and software knowledge
Constituents of the enterprise model
Organised constituents of the enterprise model
Enterprise knowledge system
Enterprise model
Enterprise and design knowledge system
Application knowledge system
Application knowledge systemApplication details
Design details
Design knowledge system
To be enterprise models
New enterprise knowledge
C
EM Based Approach
SoMeT 2004
EM Based ApproachKnowledge Enterprise
Knowledge
transfer (Enterprise – Application)
Application Knowledge transfer (Application -
Design)
Design
TACIT
Shallow Pieces P O d P O D P O D
Models P O d P O D D
System P O (d) P O D D
Detailed Pieces P O P O D D
Models P O P O D D
System (P) (O) (D) (D)
EXPLICIT
Shallow Pieces
Models
System
Detailed Pieces
Models
System
Consistency check Individual + + +
Shared + + +
Formal + + +
Relative completeness IntuitiveFormal
IntuitiveFormal
IntuitiveFormal
SoMeT 2004
SocalisationStakeholder AND Developer
ExternalisationStakeholder and Developer
InternalisationStakeholder AND Developer
SocalisationStakeholder AND Developer
ExternalisationStakeholder and Developer
CombinationDeveloper
Shallow enterprise and application
models
Shallow enterprise and application
models
CombinationDeveloper
Shallow design model
InternalisationStakeholder AND DeveloperImplementation
Developer
Shallow or detailed design model
Knowledge pieces on broad range of issues
Knowledge pieces on broad range of issues
Initial design model
Application knowledge
Detailed design model
Real software product
More detailed application knowledge
Detailed requirements model
Initial requirements model
Agile Approach
SoMeT 2004
Agile ApproachKnowledge Enterprise
Knowledge transfer
(Enterprise – Application)
Application Knowledge transfer (Application -
Design)
Design
TACIT
Shallow Pieces S D S D S D D D
Models S D S D S D D D
System S D S D S D D D
Detailed Pieces S D S D S D D D
Models S D S D S D D D
System (S) (D) (S) (D) (S) (D) (D) (D)
EXPLICIT
Shallow Pieces
Models
System
Detailed Pieces
Models
System
Consistency check Individual + + +
Shared + + +
Formal - - -
Relative completeness Supported by S involvement Supported by S involvement IntuitiveFormal
SoMeT 2004
How does the approaches look from the point of view of
knowledge?
How capable are they?
Let us look at potential knowledge growth patterns...
SoMeT 2004
Agile
Use-case based
Enterprise model based
Diversity of views
Size of project knowledge system(tacit+explicit)
Depth of knowledge
SoMeT 2004
Conclusions: Capability of approaches
• Traditional use-cases based approach is most suitable for middle sized, projects where as-is rather than to-be enterprise system is to be supported by new software applications
• Enterprise model based approach is suitable for large size systems with a potential explicit knowledge reuse. It can be used for as-is enterprises as well as for to-be enterprises, and can handle frequent changes in requirements
• Agile approach is suitable for small and middle-sized projects, it can handle frequent changes, and is useful for both as-is enterprise applications and to-be enterprise applications
SoMeT 2004
Answers to the stated questions
• Shall we consider potential availability of different types of knowledge and possibilities of its growth when choosing SE approaches? YES
• How interplay of tacit and explicit knowledge influences capability of the methodology? – Natural flow of knowledge creation– Both tacit and explicit systems knowledge– Transfer of both tacit and explicit knowledge – Appropriate depth of both tacit and explicit
knowledge
SoMeT 2004
Future work
• Analysis of knowledge processes and respectively potential capabilities of other approaches such as:
• Components based development• Patterns based development• Natural language based development• Adoption of ERP systems • Etc.