Requirement Model for Instructor Management System

The purpose of this project is to create a requirement model for Instructor Management System (IMS) based in Universiti Utara Malaysia (UUM), Kedah Darul Aman. Requirement model provide a more structured and integrated guide for the development of systems. Its serves as a good starting point or...

Full description

Saved in:

Bibliographic Details
Main Author:	Lee, Ai Leng
Format:	Thesis
Language:	eng eng
Published:	2004
Subjects:	QA76 Computer software
Online Access:	https://etd.uum.edu.my/1290/1/LEE_AI_LENG.pdf https://etd.uum.edu.my/1290/2/1.LEE_AI_LENG.pdf
Tags:	Add Tag No Tags, Be the first to tag this record!

id	my-uum-etd.1290
record_format	uketd_dc
institution	Universiti Utara Malaysia
collection	UUM ETD
language	eng eng
topic	QA76 Computer software
spellingShingle	QA76 Computer software Lee, Ai Leng Requirement Model for Instructor Management System
description	The purpose of this project is to create a requirement model for Instructor Management System (IMS) based in Universiti Utara Malaysia (UUM), Kedah Darul Aman. Requirement model provide a more structured and integrated guide for the development of systems. Its serves as a good starting point or reference for system developers to understand the user's requirement which save cost, time and resources, thus helps to decrease effort in the system development process and increased quality of the developed system. The methodology for requirement mode of the IMS is derived from requirements, analyze requirements and validate requirement model. System modeling and prototyping approach were used for requirement validation, while HOORA Analysis Tool (HAT was used to validate the requirement model. Unified Modeling Language (UML) notation was adopted for the development of the requirement model. The requirement model consists of use case diagram, use case specification, class diagram, sequence diagram, collaboration diagram, activity diagram and supporting textual information. This requirement model provides a guideline in developing IMS by specifies a solution that is right for the user's needs. This project concludes by discussing problems and limitations that were encountered in completing this project, and offers a few recommendations for future development in this subject.
format	Thesis
qualification_name	masters
qualification_level	Master's degree
author	Lee, Ai Leng
author_facet	Lee, Ai Leng
author_sort	Lee, Ai Leng
title	Requirement Model for Instructor Management System
title_short	Requirement Model for Instructor Management System
title_full	Requirement Model for Instructor Management System
title_fullStr	Requirement Model for Instructor Management System
title_full_unstemmed	Requirement Model for Instructor Management System
title_sort	requirement model for instructor management system
granting_institution	Universiti Utara Malaysia
granting_department	Faculty of Information Technology
publishDate	2004
url	https://etd.uum.edu.my/1290/1/LEE_AI_LENG.pdf https://etd.uum.edu.my/1290/2/1.LEE_AI_LENG.pdf
_version_	1747827113788964864
spelling	my-uum-etd.12902013-07-24T12:11:18Z Requirement Model for Instructor Management System 2004 Lee, Ai Leng Faculty of Information Technology Faculty of Information Technology QA76 Computer software The purpose of this project is to create a requirement model for Instructor Management System (IMS) based in Universiti Utara Malaysia (UUM), Kedah Darul Aman. Requirement model provide a more structured and integrated guide for the development of systems. Its serves as a good starting point or reference for system developers to understand the user's requirement which save cost, time and resources, thus helps to decrease effort in the system development process and increased quality of the developed system. The methodology for requirement mode of the IMS is derived from requirements, analyze requirements and validate requirement model. System modeling and prototyping approach were used for requirement validation, while HOORA Analysis Tool (HAT was used to validate the requirement model. Unified Modeling Language (UML) notation was adopted for the development of the requirement model. The requirement model consists of use case diagram, use case specification, class diagram, sequence diagram, collaboration diagram, activity diagram and supporting textual information. This requirement model provides a guideline in developing IMS by specifies a solution that is right for the user's needs. This project concludes by discussing problems and limitations that were encountered in completing this project, and offers a few recommendations for future development in this subject. 2004 Thesis https://etd.uum.edu.my/1290/ https://etd.uum.edu.my/1290/1/LEE_AI_LENG.pdf application/pdf eng validuser https://etd.uum.edu.my/1290/2/1.LEE_AI_LENG.pdf application/pdf eng public masters masters Universiti Utara Malaysia Albus, J. S. (1993). A Reference Model Architecture for Intelligent System Design [Electronic version]. Retrieved December 18, 2003, from http://www.isd.mel.nist.gov/documents/albus/Ref_Model_Arch345.pdf. Bennett, S., McRobb, S. & Farmer, R. (2002). Object-Oriented Systems Analysis and Design (2nd ed.). London: McGraw-Hill. Booch, G., Rumbaugh, J. & Jacobson, I. (1999). The Unified Modeling Language User Guide. Boston: Addison-Wesley. Davis, A. (1993). Software Requirements: Objects,Functions, States. Englewood Cliffs, New Jersey: Prentice-Hall. Dorfman, M. (1990). System and Software Requirements Engineering. In M.Dorfman and Thayer. R.H.(Eds.), System and Software Requirements Engineering. Washington: IEEE Computer Society. Gibbs, W. W. (1994). Software's Chronic Crisis. Scientific American, 271(3),72-81. Hawry Szkiewycz, I.(2001 ). Introduction to Systems Analysis & Design (5th ed.).Malaysia: Prentice Hall. Introduction to Cimosa. (1999). [Electronic version]. Retrieved February 14, 2003 from http://www.rgcp.com/cimosa.htm. Kromker, M., Weber, F., Steinlechner, V. & Wanke, P.(1998). A Reference Model and Software Support for Bid Preparation in Supply Chains in the Construction Industry [Electronic version]. International Workshop on Business Process Reengineering and Supporting Technologies for Electronic Commerce.Retrieved January 15, 2003 from http://www.biba. unibremen.de/users/web/download/Kroemker_etal_1998_DEXA_Reference_Model_for_Bid_Preparation.pdf Leisch, E. (1998). Contents and Use of a Healthcare Domain Reference Data Model [Electronic version]. Retrieved January 15, 2004, from http://www.ercim.org/publication/Ercim_News/en35/leisch.html. Lethbridge, T. C. & Laganiere, R. (2001). Object-Oriented Software Engineering. London: McGraw-Hill. Loucopoulos, P. & Karakostas, V. (1995).System requirements Engineering. London: The McGraw-Hill. Misic, V.B. & Zhao, J.L. (1999). Reference Models for Electronic Commerce [Electronic version]. The 9th Hong Kong Computer Society Database Conference: Database and Electronic Commerce. Retrieved December 18, 2003 from http://www.ops2.moc.go.th/PDF/HKDC-MisicZhao-pdf. Molina, A. & Bell, R.(2002). Reference Models for the Computer Aided Support of Simultaneous Engineering, International Journal of Computer Integrated Manufacturing, 15(3), 193-213. Naumenko, A. (2001). Reference Model for Open Distributed Processing [Electronic version]. Retrieved January 15, 2004 from http://lamswww.epfl.ch/reference/rm-odp. Ng, P. Y. (2003). Recent Methodologies in Requirements Analysis. Journal of Information Technology, 5(1), 105-116. RM-ODP Overview. (2003). [Electronic version]. Retrieved February 14, 2004 From http://jmx4odp.sourceforge.net/rm_odp_in_a_nutshell. html Ruiz, D.D.A. & Bastos, R. M. (2002). C-Wf: a Model to Represent Workflow Business Processes in Production System [Electronic version]. Journal of Applied System Studies, 3(1). Retrieved January 18, 2004, from http://chord.nce.ufrj.br/docs/JASS-2002.pdf. Schulz, Y., Fisher, D. & Curtis, T.(1999). PPDM Manages Oil & gas Data Better,Faster. (2001). [Electronic version]. Retrieved December 28, 2003, from http://www. corvelle.com/articles/pesa_ppdm_article.pdf Sommerville, I. (2001). Software Engineering (6th ed.). Harlow, England: Addison-Wesley. Whitten, J. L., BentleX , L. D. & Dittman, K. C. (2001). Systems Analysis and Design Methods (5th ed.). Boston: McGraw-Hill. Why PPDM? (2001). [Electronic version]. Retrieved December 31, 2003 from http://www.ppdm.org/whyppdm/index.html Yeh, R. T. & Ng, P. A. (1990). Software Requirements-A Management Perspective. In R. H. Thayer & M. Dorfman (Eds.), System and Software Requirements Engineering. Washington: IEEE Computer Society Press.

Requirement Model for Instructor Management System

Similar Items