Application domain competence in software requirements: deconstructing a unified approach

ABSTRACT

In this paper, we present a research-in-progress study that examines the issue of how application domain competence is addressed in systems development literature. The underlying questions are: how does the area of systems development approach the concept of application domain? What steps do we take to ensure sufficient application domain competence when developing systems? We address this question by analyzing a recent practical book on software requirements in the unified approach series, to get a picture of how this important area for IT professional is presented and prescribed.

REFERENCES

• 1: Beath, C.M., and Orlikowski, W.J. The Contradictory Structure of Systems Development Methodologies: Deconstructing the IS-User Relationship in Information Engineering. Information Systems Research, 5,4, (1994) 350--377.
• 2: Blyth, A. Using stakeholders, domain knowledge, and responsibilities to specify information systems' requirements. Journal of Organizational Computing and Electronic Commerce, 9,4, (1999) 287--296.
• 3: Chatzoglou, P.D, and Soteriou, A.C. A DEA framework to assess the efficiency of the software requirements capture and analysis process. Decision Sciences, 30,2, (1999) 503--531.
• 4: Alistair Cockburn, Surviving object-oriented projects: a manager's guide, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1998
• 5: Robert L. Glass , Iris Vessey, Contemporary Application-Domain Taxonomies, IEEE Software, v.12 n.4, p.63-76, July 1995 [doi>10.1109/52.391837]
• 6: Jeffrey A. Hoffer , Joseph S. Valacich , Joey F. George, Modern Systems Analysis and Design, Prentice Hall PTR, Upper Saddle River, NJ, 2001
• 7: Philippe Kruchten, The Rational Unified Process: An Introduction, Second Edition, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 2000
• 8: Denis M. S. Lee , Eileen M. Trauth , Douglas Farwell, Critical skills and knowledge requirements of IS professionals: a joint academic/industry investigation, MIS Quarterly, v.19 n.3, p.313-340, Sept. 1995 [doi>10.2307/249598]
• 9: Dean Leffingwell , Don Widrig, Managing software requirements: a unified approach, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1999
• 10: Nordheim, S. Interdisciplinary IS Competence at an Individual Level - A case study. In Proceedings of ISD '01 (London, Sept. 2001).
• 11: Olsson, E. and Gulliksen, J. A corporate style guide that includes domain knowledge. International Journal Of Human-Computer Interaction, 11,4, (1999) 317--338.
• 12: Shaft, T.M. and Vessey, I. The Relevance of Application Domain Knowledge: Characterizing The Computer Program Comprehension Process. Journal of Management Information Systems, 15,1, (1998) 51--79.
• 13: Silverman, D. Harvey Sacks: Social Science and Conversation Analysis. Cambridge: Polity Press, 1998.
• 14: Sykes, J.B. (Ed.). The Concise Oxford Dictionary of Current English, 7th ed., Oxford: Clarendon Press, 1982.
• 15: Douglas Troy , Robert McQueen, An approach for developing domain specific CASE tools and its application to manufacturing process control, Journal of Systems and Software, v.38 n.2, p.165-192, Aug. 1997 [doi>10.1016/S0164-1212(96)00120-3]
• 16: Karl Eugene Wiegers, Software Requirements, Microsoft Press, Redmond, WA, 1999

INDEX TERMS

Keywords:
IT skills, IT workforce, personnel, requirements/specifications - elicitation methods