8:30 – 9:00 Registration
9:00 – 10:30 Welcome and Keynote speaker (Dr. Pete Sawyer)
Pete Sawyer is a professor at Lancaster University, UK. His main interests are in requirements engineering, and currently on tacit knowledge in requirements understanding. Pete has published many articles.
Talk: Tacit Knowledge in Requirements
Description: [...] In requirements engineering, we know that we cannot make everything explicit. Much must remain implicit; we need to assume that sufficient shared understanding exists between the stakeholder and the analyst to obviate the need for complete, explicit description of all the requirements and their context. However, problems occur when this shared understanding is poor and particularly when one or both of the parties fails to understand the extent of their imperfect shared understanding. In his talk Pete will briefly review the problem of tacit knowledge in RE and suggest some techniques that may contribute to exposing its presence. [more...]
10:30 – 11:00 Coffee Break
11:00 – 12:30 Session 1: Early Requirements (Chair:)
12:30 – 14:00 Lunch
14:00 – 15:30 Session 2: Late Requirements and Architecture (Chair:)
15:30 – 16:00 Coffee break
16:00 – 17:30 Session 3: Requirements Elicitation and Management (Chair:)
10:00 – 11:30 Session 4: Traceability and Product Lines(Chair:)
11:30 – 12:00 Coffee break
12:00 – 13:10 Session 5 Requirements Specification and Management (Chair:)
13:10 – 14:45 Lunch
14:45 – 16:15 Panel
16:15 – 16:30 Closing session
Dr. Pete Sawyer, Lancaster University, UK
The importance of tacit knowledge in requirements elicitation and understanding is widely accepted but poorly understood. There is no clear definition of tacit knowledge, with definitions spanning knowledge that cannot be articulated to knowledge that is merely unarticulated. The situation is further confused by the fact that the most widely cited author on tacit knowledge (Michael Polanyi) actually wrote about tacit knowing. As a phenomenon, tacit knowledge is regarded both as a problem and an advantage. It’s a problem because if knowledge remains tacit, then it cannot be effectively communicated and codified, making the explicit knowledge that we hold incomplete. It’s an advantage because if it is valuable to our company, our competitors cannot easily gain access to it.
In requirements engineering, we know that we cannot make everything explicit. Much must remain implicit; we need to assume that sufficient shared understanding exists between the stakeholder and the analyst to obviate the need for complete, explicit description of all the requirements and their context. However, problems occur when this shared understanding is poor and particularly when one or both of the parties fails to understand the extent of their imperfect shared understanding.
A skilled analyst will recognize the presence of tacit knowledge and use a range of techniques to expose it, or as much of it as is feasible to extract. Important information evades even skilled analysts, however, and many analysts lack the skill and experience to recognize its absence or its significance. My interest is in deepening our understanding of tacit knowledge in RE and in seeking to develop tools and techniques to mitigate its harmful effects. I and my colleagues are investigating the use of techniques from computational linguistics to define baseline knowledge and to infer the presence of tacit knowledge. The general problem is so nuanced that no complete solution is possible. However, it may be possible to draw the analyst’s attention to missing or incomplete knowledge that may be rooted in stakeholders’ inability, difficulty or inhibition with articulating their knowledge and from which the analyst can formulate appropriate requirements.
In my talk I will briefly review the problem of tacit knowledge in RE and suggest some techniques that may contribute to exposing its presence.
Paper Submission: April 1th, 2009
Paper Submission extended to April 15th, 2009
Acceptance Notification: May 18th, 2009
Camera Ready Due: June 11th, 2009
Early Registration until: June 25th, 2009
> Late Registration until: July 16th, 2009
Workshop: July 16-17, 2009
