ACKNOWLEDGING THE IMPLICATIONS OF REQUIREMENTS

Ken Boness, Rachel Harrison, Kecheng Liu

2005

Abstract

The traditional software requirements specification (SRS) used as the principal instrument for management and planning and as the foundation for design can play a pivotal role in the successful outcome of a project. However this can be compromised by uncertainty and time-to-market pressures. In this paper we recognise that the SRS must be kept in a practical and useful state. We recognise three prerequisites to this end and introduce a programme of research aimed at developing a Requirements Profile that changes the emphasis of requirements engineering from defining the requirements to defining what is known about the requirements. The former (being a subset of the latter) leaves the traditional idea of a SRS unaffected whereas the latter adds much to the avoidance of misunderstanding.

References

  1. Ambriola V, Gervassi V, 1997. “Processing Natural Language Requirements”, Proceedings of the 1997 International Conference on Automated Software Engineering (formerly: KBSE) , Page: 36.
  2. Arlow J, Emmerich W and Quinn. J, 1999. “Literate Modelling - Capturing Business Semantics with the UML”. In: J. Bezivin and P.-A. Muller (eds) The Unified Modeling Language: <<UML 7898>>: Beyond the Notation, Mulhouse, France, Lecture Notes in Computer Science. 1618, pp. 189-199. Springer Verlag.
  3. Avritzer A, Weyuker E.J, 1998. “Investigating Metrics for Architectural Assessment”, IEEE Metrics, pp 4-10.
  4. Baskerville R, Ramesh B, Levine L, 2003. Pres-Heje J, Slaughter S, “Is Internet Speed Software Development Different” , IEEE Software, November, pp70-77. Vol 20, Number 6.
  5. Berry D, 2002. “The Inevitable Pain of Software Development Including Extreme Programming, Caused by Requirements Volatility”, International Workshop on Time-Constrained Requirements Engineering , Essen, Germany, September 9.
  6. Berry D.M, Kamsties E, Krieger M, 2003. “From Contract Drafting to Software Specification: Linguistic Sources of Ambiguity - A Handbook”, Ver. 1.0, http://se.uwaterloo.ca/dberry/#Handbook,.
  7. Eberlein A and Sampaio do Prado Leite, 2002. “Agile Requirements Definition: A View from Requirements Engineering”, International Workshop on TimeConstrained Requirements Engineering, Essen, Germany, September 9.
  8. Feather M.S, Fickas S, Finkelstein A, Lamsweerde A van, 1997. “Requirements & Specification Exemplars”, Automated Software Engineering, October, vol. 4, no. 4, pp. 419-438(20), Publisher: Kluwer Academic Publishers
  9. Fenton N, Pfleeger S.L, 1996 "Software Metrics: A Rigorous & Practical Approach", 2nd edition, International Thomson Computer Press
  10. Finkelstein A, Emmerich W, 2000. “The Future of Requirements Management Tools” In G. Quirchmayr, R. Wagner and M. Wimmer (eds), Information Systems in Public Administration and Law. Oesterreichische Computer. Gesellschaft.
  11. Finkelstein A, 1993. “Requirements Engineering: an overview”, 2nd Asis-Pacific Software Engineering Conference Tokyo, Japan.
  12. Gervassi V, Nuseibeh B, 2000. “Lightweight Validation of Natural Language Requirements: a case study”, Lightweight validation of natural language requirements: a case study. Proc. of the 4th International Conference on Requirements Engineering, pages 140-148, June.
  13. Goetz R, 2002. “How Agile Process Can Help in TimeConstrained Requirements Engineering”, International Workshop on Time-Constrained Requirements Engineering (TCRE'02), Essen, Germany, Sept. 9.
  14. IEEE, 1998. “Recommended Practice for Software Requirements Specifications”, Std 830-1998, IEEE Inc 354 East 47th St. New York NY 10017, USA.
  15. Jepsen O, 2002. “Time Constrained Requirement Engineering - the Cooperative Way”, International Workshop on Time-Constrained Requirements Engineering, Essen, Germany, September 9.
  16. Keil M, Rai A, Mann J.E.C and Zhang G.P, 2003. “Why Software Projects Escalate: The Importance of Project management Constructs”, , IEEE Transactions on Engineering Management, Vol 50, No 3, August.
  17. Kitchenham B, Pickard L, Pfleeger S, 1995 "Case Studies for Method and Tool Evaluation", IEEE Software, Vol. 12, No. 4, pp. 52-62
  18. Kohler K, Paech B, 2002. “Requirement Documents that Win the Race: Not Overweight or Emaciated but Powerful and in Shape”, International Workshop on Time-Constrained Requirements Engineering, Essen, Germany, September 9.
  19. Lami G, Gnesi S, Fabbrini F, Fusani M, Trentanni G, 2000. “An Automatic Tool for the Analysis of Natural Language Requirements”, C.N.R. - Information Science and Technology Inst. ” A. Faedo”, Pisa, Italy
  20. Lamsweerde A van, 2001. “Goal-Oriented Requirements Engineering: A Guided Tour (2001)”, Axel van Lamsweerde, 2001. Proceedings 5th IEEE International Symposium on Requirements Engineering August 27 - 31.
  21. Letier E, Lamsweerde A van, 2002. “Agent-Based Tactics for Goal Oriented Requirements Elaboration” Proceedings ICSE'2002, 24th International Conference on Software Engineering, ACM Press.
  22. Leveson N.G., 2000. “Intent Specifications: An Approach to Building Human-Centered Specifications”, IEEE Transactions on Software Engineering, Vol 26, No. 1.
  23. Liu K, 2000. “Semiotics in Information Systems Engineering”, Cambridge University Press, ISBN 0- 521-59335-2.
  24. McPhee C. and Eberlein A. 2002. “Requirements Engineering for Time-to-Market Projects”, Proceedings of the 9th Annual IEEE International Conference on the Engineering of Computer Based Systems, Lund, Sweden.
  25. Mich, Luisa and Franch, Mariangela and Novi Inverardi, Pierluigi 2002. “Market research for requirements analysis using linguistic tools”, Technical Report 66, Informatica e Studi Aziendali, University of Trento.
  26. Myolopolous J, Chung L, Yu E, 1999. “From ObjectOriented to Goal-Oriented Requirements Analysis.” Communications of the ACM Vol 42 No 1 pp31-37
  27. Nuseibeh B, Easterbrook S, 2000 “Requirements Engineering: A Roadmap”, Proceedings of International Conference on Software Engineering , 4- 11 June, Limerick, Ireland.
  28. Pierce C.S, 1935. “Collected Papers 1931-35”, (6 volumes), Hartshorne C & Wiess P (eds), Cambridge, Mass. Harvard U.P.
  29. Pinheiro F.A.C, 2002. “Requirements Honesty”, International Workshop on Time-Constrained Requirements Engineering, Essen, Germany, September 9, 2002.
  30. Porter A, Votta L.G, Basili V. R, 1995. “Comparing Detection Methods for Software Requirements Inspections: A Replicated Experiment”, IEEE Transactions on Software Engineering, Volume 21 , Issue 6 Pages: 563 - 575.
  31. POST 2003. “Government IT projects”, Parliamentary Office of Science and Technology, Report 200, July 2003, http://www.parliament.uk/post
  32. Rolland C, Proix C, 1992 “A Natural Language Approach For Requirements Engineering” Proceedings of the Fourth International Conference CAiSE'92 on Advanced Information Systems Engineering.
  33. Stamper R. K, “Signs, 1993. Norms and Information Systems”, Ronal Stamper, 1993, ICL/University of Newcastle Seminar on “Information”, September 6-10.
  34. Stamper R.K, Althans K and Backhouse J, 1998. “MEASUR: Method For Eliciting, Analysing and Specifying User Requirements” Computerized Assistance During the Information Systems Life Cycle: 67-115
  35. Taylor A, 2001. “IT projects sink or swim”, BCS Review, http://www.bcs.org.uk/review .
  36. Tomayko J.E, 2002. “Engineering of Unstable Requirements Using Agile Methods”, International Workshop on Time-Constrained Requirements Engineering, Essen, Germany, September 9, 2002.
  37. Wilson W.M., Rosenberg L.H. Hyatt L.E. 1997. “Automated Analysis of Requirement Specifications” Nineteenth International Conference on Software Engineering, Boston, MA.
  38. Zowghi D, Gervassi V, 2003. “On the interplay between consistency, completeness, and correctness in requirements evolution.”, Zowghi D, Gervasi V, Information and Software Technology, 45 (14): 993- 1009, Elsevier B.V.
Download


Paper Citation


in Harvard Style

Boness K., Harrison R. and Liu K. (2005). ACKNOWLEDGING THE IMPLICATIONS OF REQUIREMENTS . In Proceedings of the Seventh International Conference on Enterprise Information Systems - Volume 3: ICEIS, ISBN 972-8865-19-8, pages 337-342. DOI: 10.5220/0002548303370342


in Bibtex Style

@conference{iceis05,
author={Ken Boness and Rachel Harrison and Kecheng Liu},
title={ACKNOWLEDGING THE IMPLICATIONS OF REQUIREMENTS},
booktitle={Proceedings of the Seventh International Conference on Enterprise Information Systems - Volume 3: ICEIS,},
year={2005},
pages={337-342},
publisher={SciTePress},
organization={INSTICC},
doi={10.5220/0002548303370342},
isbn={972-8865-19-8},
}


in EndNote Style

TY - CONF
JO - Proceedings of the Seventh International Conference on Enterprise Information Systems - Volume 3: ICEIS,
TI - ACKNOWLEDGING THE IMPLICATIONS OF REQUIREMENTS
SN - 972-8865-19-8
AU - Boness K.
AU - Harrison R.
AU - Liu K.
PY - 2005
SP - 337
EP - 342
DO - 10.5220/0002548303370342