Your browser does not support JavaScript!
http://iet.metastore.ingenta.com
1887

Identifying tacit knowledge-based requirements

Identifying tacit knowledge-based requirements

For access to this article, please select a purchase option:

Buy article PDF
£12.50
(plus tax if applicable)
Buy Knowledge Pack
10 articles for £75.00
(plus taxes if applicable)

IET members benefit from discounts to all IET publications and free access to E&T Magazine. If you are an IET member, log in to your account and the discounts will automatically be applied.

Learn more about IET membership 

Recommend Title Publication to library

You must fill out fields marked with: *

Librarian details
Name:*
Email:*
Your details
Name:*
Email:*
Department:*
Why are you recommending this title?
Select reason:
 
 
 
 
 
IEE Proceedings - Software — Recommend this title to your library

Thank you

Your recommendation has been sent to your librarian.

Requirements may be derived from a number of sources. Determining the source of a given requirement is known as pre-requirements tracing. Typically, some requirements appear that have no clear source, yet stakeholders will attest to the necessity of these requirements. However, such requirements are likely to be based on tacit or tacit-like knowledge embedded in the problem domain. A tool called Prospect that retrospectively identifies pre-requirement traces is presented. This tracing is achieved by working backwards from requirements to the documented records of the elicitation process, such as interview transcripts or ethnographic reports. A vector-space technique, latent semantic analysis, is shown to be useful to perform pre-requirements tracing. The identification of badly sourced requirements naturally leads to the inference that further investigation of these requirements is necessary, whether or not the requirements turn out to be based on tacit knowledge.

References

    1. 1)
      • M. Polanyi . (1983) The tacit dimension.
    2. 2)
      • Takeuchi, H.: ‘Beyond knowledge management: lessons from Japan’ http://www.sveiby.com/articles/LessonsJapan.htm,June 1998, last accessed August 2005.
    3. 3)
      • C.D. Manning , H. Schütze . (1999) Foundations of statistical natural language processing.
    4. 4)
      • S. Deerwester , S.T. Dumais , G.W. Furnas , T.K. Landauer , R. Harshman . Indexing by latent semantic analysis. J. Am. Soc. Inf. Sci. , 6 , 391 - 407
    5. 5)
      • Maarek, Y.S., Berry, D.M.: `The use of lexical affinities in requirements extraction', ‘Proceedings of the 5th International Workshop on Software Specification and Design’, May 1989, Pittsburgh, PA, p. 196–202, (IEEE Computer Society Press).
    6. 6)
    7. 7)
      • Ryan, K.: `The role of natural language in requirements engineering', Proc. IEEE Int. Symposium RE, 1993, p. 80–82.
    8. 8)
    9. 9)
      • Lormans, M., van Deursen, A.: `Reconstructing requirements coverage views from design and test using traceability recovery via lsi', ‘TEFSE'05: Proceedings of the 3rd International Workshop on Traceability in emerging forms of software engineering, 2005, New York, NY, USA, p. 37–42, ACM Press.
    10. 10)
      • S.T. Dumais . Improving the retrieval of information from external sources. Behav. Res. Methods, Instrum. Comput. , 229 - 236
    11. 11)
      • Lecoeuche, R.: `Finding comparatively important concepts between texts', Proc. 15th IEEE Int. Conf. Automated Software Eng. (ASE'00), 2000, p. 55–63.
    12. 12)
      • G. Ryle . (1984) The concept of mind.
    13. 13)
      • Oxford University Computing: ‘British National Corpus’, http://www.natcorp.ox.ac.uk, accessed February 2005.
    14. 14)
      • I. Nonaka , H. Takeuchi . (1995) The knowledge-creating company.
    15. 15)
      • Nuseibeh, B., Easterbrook, S.: `Requirements engineering: a roadmap', Proc. 23rd Int. Conf. Software Engineering (ICSE 2000), 2000, p. 35–46.
    16. 16)
      • Parnas D.: ‘Preparing requirements documents using the four variable model’. A presentation to the British Computer Society's Requirements Engineering Specialist Group, http://www.resg.org.uk/parnastutorial.pdf,accessed June 2006.
    17. 17)
      • Marcus, A., Maletic, J.I.: `Recovering documentation- to-source-code traceability links using latent semantic indexing’', ‘International conference on software engineering’, 2003, IEEE Computer Society Press, p. 125–134.
    18. 18)
      • Bentley, R.: `Supporting multi-user interface development for cooperative systems', 1994, PhD, , Lancaster University.
    19. 19)
      • Finkelstein, A.: Unsolved Problems in Requirements Engineering. A presentation to the British Computer Society's Requirements Engineering Specialist Group, http://www.resg.org.uk/unsolved.pdf, accessed January 2005.
    20. 20)
    21. 21)
      • Gotel, O.C.Z., Finkelstein, A.C.W.: `An analysis of the requirements traceability problem', ‘First International Conference on Requirements Engineering (ICRE)’, 1994, p. 94–101, IEEE Computer Society Press.
    22. 22)
      • V. Gervasi , B. Nuseibeh . Lightweight validation of natural language requirements. Softw. Pract. Exp. , 2 , 113 - 133
    23. 23)
      • H.M. Collins . (2001) What is tacit knowledge.
    24. 24)
    25. 25)
      • Bentley, R., Hughes, J.A., Randall, D., Rodden, T., Sawyer, P., Shapiro, D., Sommerville, I.: `Ethnographically-informed systems design for air traffic control', Proc. ACM CSCW'92 Conf. Computer-Supported Cooperative Work, Ethnographically-Informed Design, 1992, p. 123–129.
    26. 26)
http://iet.metastore.ingenta.com/content/journals/10.1049/ip-sen_20060034
Loading

Related content

content/journals/10.1049/ip-sen_20060034
pub_keyword,iet_inspecKeyword,pub_concept
6
6
Loading
This is a required field
Please enter a valid email address