Home > Research > Publications & Outputs > Unknown knowns: Tacit knowledge in requirements...

Research

Associated organisational unit

Links

Text available via DOI:

View graph of relations

Unknown knowns: Tacit knowledge in requirements engineering

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Conference contribution/Paper › peer-review

Published

Standard

Unknown knowns: Tacit knowledge in requirements engineering. / Sawyer, Peter; Gervasi, Vincenzo; Nuseibeh, Bashar.
RE '11: Proceedings of the 2011 IEEE 19th International Requirements Engineering Conference. Washington, DC, USA: IEEE Computer Society, 2011. p. 329.

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Conference contribution/Paper › peer-review

Harvard

Sawyer, P, Gervasi, V & Nuseibeh, B 2011, Unknown knowns: Tacit knowledge in requirements engineering. in RE '11: Proceedings of the 2011 IEEE 19th International Requirements Engineering Conference. IEEE Computer Society, Washington, DC, USA, pp. 329. https://doi.org/10.1109/RE.2011.6051683

APA

Sawyer, P., Gervasi, V., & Nuseibeh, B. (2011). Unknown knowns: Tacit knowledge in requirements engineering. In RE '11: Proceedings of the 2011 IEEE 19th International Requirements Engineering Conference (pp. 329). IEEE Computer Society. https://doi.org/10.1109/RE.2011.6051683

Vancouver

Sawyer P, Gervasi V, Nuseibeh B. Unknown knowns: Tacit knowledge in requirements engineering. In RE '11: Proceedings of the 2011 IEEE 19th International Requirements Engineering Conference. Washington, DC, USA: IEEE Computer Society. 2011. p. 329 doi: 10.1109/RE.2011.6051683

Author

Sawyer, Peter ; Gervasi, Vincenzo ; Nuseibeh, Bashar. / Unknown knowns: Tacit knowledge in requirements engineering. RE '11: Proceedings of the 2011 IEEE 19th International Requirements Engineering Conference. Washington, DC, USA : IEEE Computer Society, 2011. pp. 329

Bibtex

@inproceedings{9720b4a2e5e24bbc9d7f6f8f1627a192,
title = "Unknown knowns: Tacit knowledge in requirements engineering",
abstract = "Donald Rumsfeld famously identified three classes of knowledge: known knowns, known unknowns and unknown unknowns. The three knowledge classes map surprisingly well onto requirements knowledge but are all outside the scope of this panel. Our focus is on what Rumsfeld missed: unknown knowns. In RE terms, an unknown known is knowledge that a person (say, a customer) holds, but which they withhold (say, from a requirements analyst). They may withhold the knowledge deliberately for some perceived personal advantage. They may withhold it accidentally, perhaps not realizing the value of their knowledge. They may strive to share the knowledge but end up withholding it because they are unable to articulate it. Or it may be knowledge they don't even realize they hold. In each case, the unknown known fits at least one of several definitions that exist of tacit knowledge (TK).",
author = "Peter Sawyer and Vincenzo Gervasi and Bashar Nuseibeh",
year = "2011",
doi = "10.1109/RE.2011.6051683",
language = "English",
isbn = "978-1-4577-0921-0",
pages = "329",
booktitle = "RE '11: Proceedings of the 2011 IEEE 19th International Requirements Engineering Conference",
publisher = "IEEE Computer Society",

}

RIS

TY - GEN

T1 - Unknown knowns: Tacit knowledge in requirements engineering

AU - Sawyer, Peter

AU - Gervasi, Vincenzo

AU - Nuseibeh, Bashar

PY - 2011

Y1 - 2011

N2 - Donald Rumsfeld famously identified three classes of knowledge: known knowns, known unknowns and unknown unknowns. The three knowledge classes map surprisingly well onto requirements knowledge but are all outside the scope of this panel. Our focus is on what Rumsfeld missed: unknown knowns. In RE terms, an unknown known is knowledge that a person (say, a customer) holds, but which they withhold (say, from a requirements analyst). They may withhold the knowledge deliberately for some perceived personal advantage. They may withhold it accidentally, perhaps not realizing the value of their knowledge. They may strive to share the knowledge but end up withholding it because they are unable to articulate it. Or it may be knowledge they don't even realize they hold. In each case, the unknown known fits at least one of several definitions that exist of tacit knowledge (TK).

AB - Donald Rumsfeld famously identified three classes of knowledge: known knowns, known unknowns and unknown unknowns. The three knowledge classes map surprisingly well onto requirements knowledge but are all outside the scope of this panel. Our focus is on what Rumsfeld missed: unknown knowns. In RE terms, an unknown known is knowledge that a person (say, a customer) holds, but which they withhold (say, from a requirements analyst). They may withhold the knowledge deliberately for some perceived personal advantage. They may withhold it accidentally, perhaps not realizing the value of their knowledge. They may strive to share the knowledge but end up withholding it because they are unable to articulate it. Or it may be knowledge they don't even realize they hold. In each case, the unknown known fits at least one of several definitions that exist of tacit knowledge (TK).

U2 - 10.1109/RE.2011.6051683

DO - 10.1109/RE.2011.6051683

M3 - Conference contribution/Paper

SN - 978-1-4577-0921-0

SP - 329

BT - RE '11: Proceedings of the 2011 IEEE 19th International Requirements Engineering Conference

PB - IEEE Computer Society

CY - Washington, DC, USA

ER -