Published on Open University Malaysia Digital Library Portal (https://library.oum.edu.my/oumlib)

Home > CBRE3103

CBRE3103

Last updated on 21 April 2014
REQUIREMENTS ENGINEERING
  1. AddBytes.com. (2004). Check Text Readability. Retrieved February 10, 2009 from http://www.addedbytes.com/readability/ [1].
  2. Ambler, S. W.(2009). UML 2 Class Diagrams. Retrieved April 1, 2009, from http://www.agilemodeling.com/artifaccts/classDiagram.htm [2].
  3. Bahill, A. T., and Henderson, S. J.(2005). Requirements Development, Verification, and Validation Exhibited in Famous Failures. System Engineering, 8(1), 1 – 14.
  4. Beloff, N. (2009). Program Design: Object Interaction, Part 2. Retrieved April 4, 2009, from http://www.sussex.ac.uk/informatics/documents/lecture8_ [3] nb.pdf.
  5. Bennett, S., McRobb, S. and Farmer, R. (2002). Object-oriented Systems Analysis and Design using UML (2nd ed.). London: McGraw-Hill Education.
  6. Boehm, B. W.(1981). Software engineering economics. Englewood Cliffs NJ: Prentice Hall.
  7. Bohner, S.A., and Arnold, R.S.(1996). Software Change Impact Analysis. Los Alamitos, CA: IEEE Computer Society Press.
  8. Brooks, F. P. Jr. (1987). No Silver Bullet: Essence and Accidents of Software Engineering. Computer. 20(4), 10-19.
  9. Chrissis, et al. (2007). CMMI: Guidelines for Process Intgertaion and product Impeovement [4]. 2ndEds. Upper Sadle, NJ: Addison-Wesley. (TSDAS Digital Library : QA76.758 Chr)
  10. Coley Consulting (2007). MoSCoW Prioritisation. Retrieved, January 2, 2009, from http://www.coleyconsulting.co.uk/moscow.htm [5]
  11. Davidson, E.J.(1999). Joint application design (JAD) in practice. Journal of Systems & Software, 45(3),215-223.
  12. Davis, A. M., and Zowghi, D. (2004). Good Requirements Practices are Neither Necessary Nor Sufficient. Requirements engineering. Springer-Verlag London Limited, 11, 1-3. 
  13. El Emam, K., and Madhavji, N.H.(1995). A Field Study of Requirements Engineering Practices in Information Systems Development. Proceeding 2nd IEEE International symposium of requirements engineering, IEEE Press, 68-80.
  14. Fellows, L. (2003). 10 Steps to Better Requirements. Proceedings of the International Conference on Practical Software Quality Techniques (PSQT)and Practical Software Testing Techniques (PSTT) 2003. 10 Sept. North, Minneapolis, MN.
  15. Hofmann, H. F.(2000). Requirements engineering: A situated discovery process. Wiesbaden, Germany: Gabler.
  16. Hofmann, H.F., and Lehner, F. (2001). Requirements engineering as a success factor in software projects. IEEE Software, 58-66.
  17. IBM (2010). Rational DOORS Web access. Retrieved January 2, 2009 from http://www-o1.ibm.com/software/awdtools/doors/webaccess [6].
  18. IEEE (1990). IEEE Std 610.12-1990. IEEE standard glossary of software engineering terminology. New York: The Institute of Electrical and Electronics Engineers, Inc.
  19. IEEE (1998a). IEEE Std 1233-1998. IEEE Guide for developing system requirements specifications. New York: The Institute of Electrical and Electronics Engineers, Inc.
  20. IEEE (1998b). IEEE Std 1362-1998.  IEEE guide for information technology - system definition – concept of operations (ConOps) document. New York: The Institute of Electrical and Electronics Engineers, Inc.
  21. IEEE (1998c). IEEE Std 830-1998. IEEE recommended practice for software requirements specifications. New York: The Institute of Electrical and Electronics Engineers, Inc.IEEE, 1998a
Source URL (retrieved on 19/05/2024 - 15:41): https://library.oum.edu.my/oumlib/content/reading-list/cbre3103

Links:
[1] http://www.addedbytes.com/readability/
[2] http://www.agilemodeling.com/artifaccts/classDiagram.htm
[3] http://www.sussex.ac.uk/informatics/documents/lecture8_
[4] http://iportal.oum.edu.my/cgi-bin/catalog/chameleon?&function=INITREQ&search=KEYWORD&u1=12101&t1=026320
[5] http://www.coleyconsulting.co.uk/moscow.htm
[6] http://www-o1.ibm.com/software/awdtools/doors/webaccess