Employees Training Management System In KUIN: A Requirement Model.

Employees Training Management System In KUIN: A Requirement Model.

The main purpose of software requirements is to describe the functionality of the software. The requirements often serve as a basis for contracts as well as for communication between customers and developers. Prior researches also have shown that requirements' errors have impact on software dev...

Full description

Saved in:
Bibliographic Details
Main Author: Norzaila, Mohamad Nor
Format: Thesis
Language:eng
Published: 2007
Subjects:
QA76 Computer software
Online Access:https://etd.uum.edu.my/112/1/norzaila.pdf
Tags: Add Tag
No Tags, Be the first to tag this record!
id my-uum-etd.112
record_format uketd_dc
institution Universiti Utara Malaysia
collection UUM ETD
language eng
topic QA76 Computer software
spellingShingle QA76 Computer software
Norzaila, Mohamad Nor
Employees Training Management System In KUIN: A Requirement Model.
description The main purpose of software requirements is to describe the functionality of the software. The requirements often serve as a basis for contracts as well as for communication between customers and developers. Prior researches also have shown that requirements' errors have impact on software development and they are more expensive to fix during later stages than early stages in software development. Hence, the requirements model is normally developed during the analysis phase. The model presents a complete view of the systems' requirement prior to the development of the actual system. The goal of this study is to create a requirements model for employee training management system (ETMS) which involves the usage of the Web Application Extension-Unified Modeling Language (WAE-UML).This proposed requirements model provides a guideline for other employee training management system developers.
format Thesis
qualification_name masters
qualification_level Master's degree
author Norzaila, Mohamad Nor
author_facet Norzaila, Mohamad Nor
author_sort Norzaila, Mohamad Nor
title Employees Training Management System In KUIN: A Requirement Model.
title_short Employees Training Management System In KUIN: A Requirement Model.
title_full Employees Training Management System In KUIN: A Requirement Model.
title_fullStr Employees Training Management System In KUIN: A Requirement Model.
title_full_unstemmed Employees Training Management System In KUIN: A Requirement Model.
title_sort employees training management system in kuin: a requirement model.
granting_institution Universiti Utara Malaysia
granting_department College of Arts and Sciences (CAS)
publishDate 2007
url https://etd.uum.edu.my/112/1/norzaila.pdf
_version_ 1747826822347751424
spelling my-uum-etd.1122013-07-24T12:05:38Z Employees Training Management System In KUIN: A Requirement Model. 2007-11 Norzaila, Mohamad Nor College of Arts and Sciences (CAS) Faculty of Information Technology QA76 Computer software The main purpose of software requirements is to describe the functionality of the software. The requirements often serve as a basis for contracts as well as for communication between customers and developers. Prior researches also have shown that requirements' errors have impact on software development and they are more expensive to fix during later stages than early stages in software development. Hence, the requirements model is normally developed during the analysis phase. The model presents a complete view of the systems' requirement prior to the development of the actual system. The goal of this study is to create a requirements model for employee training management system (ETMS) which involves the usage of the Web Application Extension-Unified Modeling Language (WAE-UML).This proposed requirements model provides a guideline for other employee training management system developers. 2007-11 Thesis https://etd.uum.edu.my/112/ https://etd.uum.edu.my/112/1/norzaila.pdf application/pdf eng validuser masters masters Universiti Utara Malaysia Andersson, H., & Gustavsson, M. (2005). A comparison of UML and WAE-UML for the Design of Web applications [Electronic version]. Retrieved August 16,2007 from http://www.bth.se/fou/cuppsats.nsf/6753b78eb2944eOac 1256608004f0535/3177707f45450b29c1257012003dc2a0?0penDocument. Andreas, A., Frank, B., & Michael, R. (2006). A Rational Unified Process (RUP) Plug-in To Support Requirements Quality Assurance [Electronic version]. Retrieved October 2,2007 from http://www. micsymposium.org/mics_2006/papers/AltmannsbergerBuhlerRowe.pdf. Arthur, J.D., Nance, R.E., & Henry, S.M. (1986). A Procedural Approach to Evaluating Software Development Methodologies: The Foundation [Electronic version]. Retrieved June 10, 2007 from http://eprints.cs.vt.edu/archive/0000003l/Ol/TR-86-24.pdf. Barker, D. (2004). Requirements Modeling Technology: A Vision for Better, Faster and Cheaper Systems. Retrieved May 9,2007, from IEEE Database, pp. 3-6. Baresi, L., Garzotto, F., & Paolini, P. (2001). Extending UML for Modeling Web Applications. Proceedings of the 34th Hawaii International Conference on System Sciences,pp.1-10. Benneth, S., McRobb,S., & Farmer,R.(2006). Object-Oriented Systems Analysis And Design, Third Edition, McGraw-Hill Education, Berkshire. Bruegge, B., & Dutoit A.H.(2000). Object-Oriented Software Engineering: Conquering Complex and Changing Systems. Prentice-Hall Ltd. Booch, G. (1999). UML in Action. Communications of the ACM, Vol. 42, No.10, pp. 26-28. Booch, G., Jacobson, I., & Rumbaugh, J.(2001). The Unified Modeling Language User Guide. Addison-Wesley: Boston. Booch, G., Jacobson, I., & Rumbaugh, J.(1998). The Unified Modeling Language User Guide. Addison-Wesley. Ceri, S., Fraternelli,P., & Bongio, A.(2000). Web Modeling Language (WebML): A Modeling Language for Designing Web Sites. Retrieved August 10, 2007 from Computer Networks, Vol. 33, No. 1, pp. 137-157. Collaborative Quality Systems. (2003). Training Management System [Electronic version]. Retrieved October 2, 2007 from http://www.coqusys.com/TMS.htm. Conallen, J. (1998). Modeling Web Application Design with UML [Electronic version]. Retrieved September 2,2007 from http://www/itmweb.com/essay546.htm. Conallen, J.(1999). Modeling Web Application Architectures with UML. Communication of the ACM, Vol.42, No.10,pp.63-70. Conallen, J. (2004). Building Web Applications with UML, 2nd Edition, Addison-Wesley, Boston. Davis, A. M. (1990). Software Requirements: Analysis and Specification. Englewood Cliffs, NJ: Prentice Hall. Davis, A. M. (1993). Software requirements: objects, functions and states. Prentice-Hall: New Jersey. Davis, F.D.(1989). Perceived usefulness, Perceived ease of use, and User Acceptance of information technology. MIS Quarterly, 319-340 [Electronic version]. Retrieved October 20, 2007 from http://oldwww.acm.org/perlman/question.cgi?form=PUEU. Diev, S. (2007). Requirements Development as a Modeling Activity. ACM SIGSOFT Software Engineering Notes, Vol.32, No.2, pp. 1-3. Diev, S. (2007). Structuring Complex Requirements. ACM SIGSOFT Software Engineering Notes, Vo1.32, No.2, pp. 1-5. EcoLogic Systems. (2005). SMART Training Management Software System [Electronic version]. Retrieved October 30, 2007 from http:// www.ecologicsystems.com/training-management system.html. Gutierrez,0.(1989).Experimental Techniques for Information Requirements Analysis. Information & Management, Vol. 16, pp. 31-43. Holbrook, H. (1990). A Scenario-Based Methodology for Conducting Requirements Elicitation. ACM SIGSOFT Software Engineering Notes, Voi. 15, No. 1, pp. 95-104. Hoe, K.L.(2004). Requirement Model for Learning Management System in Dell. Project Paper, Universiti Utara Malaysia. iEmployee. (2005, April 26). - The Hot list of Top HRMS Provider [Electronic version]. Retrieved October 20, 2007 from ttp://www.iemployee.com/mkt/TopHRMS_providers.htm. IISME Consortium. (2000). CRM System Reference Model for Small and Medium Enterprises [Electronic version]. Retrieved on Jun 20, 2007 from http://www/vis.iao.fhg.de/en/projects/iisme/Rmodel.stm. Jain, H., Vitharana, P., & Zahedi, F.M. (2003). An Assessment Model for Requirements Identification in Component-Based Software Development. The DATA BASE for Advances in Information Systems, Vol. 34, No. 48-63. Javed, T., Maqsood, M., & Durrani, Q.S. (2004). A Study to Investigate the Impact of Requirements Instability. ACM Software Engineering Notes, Vo1.29, No.4, pp. 1-7. Kotonya, G., & Sommerville, I. (2002). Requirements Engineering, Processes and Techniques. John Wiley & Sons. Lamsweerde, A. (2000). Requirements Engineering in the Year 00: A Research Perspective. Retrieved May 3,2007 from ACM Press, pp.5-19. Lauesen, S. (2002). Software Requirements: Styles and Techniques. Addison-Wesley. Lemoine, M., & Foisseau, J. (2000). Modeling Long Lifetime Systems: Building a Referential with UML. TIC'2000, Nimes. Retrieved May 1,2007. Loucopolous, P.,& Karakostas,V.(1995). System Requirements Engineering. London. The McGraw Hill. May, L.J. (1998). Major Causes of Software Project Failure [Electronic version]. Retrieved May 10, 2007 from http://www.stsc.hill.af.mil/crosstalk/l998/07/causes.asp. Moody, J., Blanton, J.E., & Cheney, P. H. (1998). A Theoretically Grounded Approach to Assist Memory Recall during Information Requirements Analysis. Retrieved October 6,2007 from Journal of MIS. Moreira, A., Araujo, J., & Brito, B. (2002). Crosscutting Quality Attributes for Requirements Engineering. Retrieved May 23, 2007 from ACM, pp. 167-174. National Governors Association (NGA). (2006). Information Technology Systems (2006) [Electronic version]. Retrieved May 15,2007, from http://www.nga.org/Files/pdf/06GOVGUIDITS.PDF. Nuseibeh, B., & Easterbrook, S. (2000). Requirements Engineering: A Roadmap. Proceedings of the Conference on the Future of Software Engineering (ICSE 'OO),pp.35-46. OMG, Object Management Group. (2001). OMG Unified Modeling Language Specification [Electronic version]. Retrieved September 18, 2007 from http://www.omg.org/technology/documents/formaI/uml.htm. Oskarsson, A., Norberg, T., & Kling, M. (2002). Web Application Development: A Study on UML Web Application Extension. Bachelor Thesis. Retrieved August 7, 2007 from http://www.bth.se/fou/cuppsats.nsf. Oxford Advanced Learner Dictionary. (2007). Requirement [Electronic version]. Retrieved May 13, 2007 from http://www.oup.com/elt/catalogue/teachersites/oald7/?cc=my. Pareto, L.(2005). Extended Abstract: Requirements Modeling within Iterative, Incremental Processes. Retrieved August 20,2007 from IEEE. Proctor, R.W., & Vu, K. P. L. (2005). Handbook of Human Factors in Web Design. CRC Press. Ricca, F., Penta, M.D., Torchiano, M., Tonella, P., & Ceccato, M.(2006). An Empirical Study on the Usefulness of Conallen's stereotypes in Web Application Comprehension. Eighth IEEE International Symposium on Web Site Evolution (WSE'06), pp. 1-8. Soltis, J., Patel, P., & Whitworth, B. (2005). Designing a New Employee Orientation (NEO) System. Retrieved May 6,2007 from ACM, pp.349-351.. Sommerville, I. (2004). Software Engineering. Addison-Wesley Pub Co. Sommerville, I. (2001). Software Engineering (6'h Ed.). Harlow, England: Addison-Wesley. Sommerville, I., & Sawyer, P. (1997). Requirements Engineering. A Good Practice. John Wiley and Sons. Sparling, M. (2000). Lessons Learned through Six Years of Component-based Development. Communications of the ACM, Vol. 43, No.10, pp. 47-53. Whitten,J.L., Bentley,L.D., & Dittman, K.C.(2001). Systems Analysis and Design Methods (5th Ed.). Boston: McGraw-Hill. Wikepedia. (2006). Requirement [Electronic version]. Retrieved May 27, 2007 from http://en.wikipedia.org/wiki/requirement. Zave, P. (1997). Classification of Research Efforts in Requirements Engineering. ACM Computing Surveys, Vol. 29, No. 4, pp. 315-321.

Similar Items