Requirement Model for Storing and Retrieving ISO Document : Teaching and Learning Process

Requirements play an important role in system development project. It is because requirement form the backbone of any successful project and provides the measure of success of failure of a certain project Mis-interpreted of requirements will make the system development does not meet the customer�...

Full description

Saved in:
Bibliographic Details
Main Author: Badriyah, Johari
Format: Thesis
Language:eng
eng
Published: 2004
Subjects:
Online Access:https://etd.uum.edu.my/1133/1/BADRIYAH_JOHARI.pdf
https://etd.uum.edu.my/1133/2/1.BADRIYAH_JOHARI.pdf
Tags: Add Tag
No Tags, Be the first to tag this record!
id my-uum-etd.1133
record_format uketd_dc
institution Universiti Utara Malaysia
collection UUM ETD
language eng
eng
topic TS 156.6 Quality Control
spellingShingle TS 156.6 Quality Control
Badriyah, Johari
Requirement Model for Storing and Retrieving ISO Document : Teaching and Learning Process
description Requirements play an important role in system development project. It is because requirement form the backbone of any successful project and provides the measure of success of failure of a certain project Mis-interpreted of requirements will make the system development does not meet the customer's expectation and increasing cost. Therefore, it is necessary to present the requirement in an understandable and meaningful way. Requirement model is one of the techniques used to model out the requirements. This model will give a complete view of certain system and represent idea without having to build an actual system. This study aims to create a requirement model for storing and retrieving ISO document : teaching and learning process at Universiti Utara Malaysia (UUM). UML notation was used to model out the requirements. To validate requirements, system modeling and prototyping were used to complete this task. Meanwhile, HOORA Analysis Tool (HAT) was used to validate requirement model produced in this study. UML diagrams and a set of requirement list will be produced in this study. Problems and limitations, which encountered during this project several recomendations for future research, will be discussed at the end of this study.
format Thesis
qualification_name masters
qualification_level Master's degree
author Badriyah, Johari
author_facet Badriyah, Johari
author_sort Badriyah, Johari
title Requirement Model for Storing and Retrieving ISO Document : Teaching and Learning Process
title_short Requirement Model for Storing and Retrieving ISO Document : Teaching and Learning Process
title_full Requirement Model for Storing and Retrieving ISO Document : Teaching and Learning Process
title_fullStr Requirement Model for Storing and Retrieving ISO Document : Teaching and Learning Process
title_full_unstemmed Requirement Model for Storing and Retrieving ISO Document : Teaching and Learning Process
title_sort requirement model for storing and retrieving iso document : teaching and learning process
granting_institution Universiti Utara Malaysia
granting_department Faculty of Information Technology
publishDate 2004
url https://etd.uum.edu.my/1133/1/BADRIYAH_JOHARI.pdf
https://etd.uum.edu.my/1133/2/1.BADRIYAH_JOHARI.pdf
_version_ 1747827078554714112
spelling my-uum-etd.11332013-07-24T12:10:33Z Requirement Model for Storing and Retrieving ISO Document : Teaching and Learning Process 2004 Badriyah, Johari Faculty of Information Technology Faculty of Information Technology TS 156.6 Quality Control Requirements play an important role in system development project. It is because requirement form the backbone of any successful project and provides the measure of success of failure of a certain project Mis-interpreted of requirements will make the system development does not meet the customer's expectation and increasing cost. Therefore, it is necessary to present the requirement in an understandable and meaningful way. Requirement model is one of the techniques used to model out the requirements. This model will give a complete view of certain system and represent idea without having to build an actual system. This study aims to create a requirement model for storing and retrieving ISO document : teaching and learning process at Universiti Utara Malaysia (UUM). UML notation was used to model out the requirements. To validate requirements, system modeling and prototyping were used to complete this task. Meanwhile, HOORA Analysis Tool (HAT) was used to validate requirement model produced in this study. UML diagrams and a set of requirement list will be produced in this study. Problems and limitations, which encountered during this project several recomendations for future research, will be discussed at the end of this study. 2004 Thesis https://etd.uum.edu.my/1133/ https://etd.uum.edu.my/1133/1/BADRIYAH_JOHARI.pdf application/pdf eng validuser https://etd.uum.edu.my/1133/2/1.BADRIYAH_JOHARI.pdf application/pdf eng public masters masters Universiti Utara Malaysia REFERENCES Bernett, S., McRobb,S. & Farmer, R. (2002). Object oriented system analysis and design using UML (2nd ed). Backshire: McGraw-Hill Education. Bielawski,L & Boyle, J. (1997). Electronic document management system: a user centered approuch for creating, distributing and managing online publications New Jersey: Prentice hall PTR. Booch. G., Rumbaugh, J. & Jacobson, I. (1999). The unified modeling language user guide. Boston: Addison-Wesley. Borbinha, J. & Freire, N. (2002). Model requirement analysis document-1: analysis and evaluation of input data.. Retrieved April 15, 2004 from http://www.google. com Cain, P.(2003). MoReq: the standard of the future? Information Management Journal,37 (2),54. Cleveland, G. (1995). Overview of document management technology. Retrieved April 10:2004, from http://www.ifla. org/vI/5/op/udtop2/udt-op2. pdf cradle (no date). Requirements audits. Retrieved April 10,2004, from http://ww.threesl.com/pages/reference/requirements/audits.php Davis, A.M. (1993). Software requirements objects, function and states. New Jersey:PTR Prentice Hall. Fortune Informatics Limited. (no date). Document management system: the case of papyrus. Retrieved April 10,2004, from http://www.fortuneit.com/Papyrus/whitepaper.pdf. Fresko, M. &: Waldron, M.(2001). Model requirements for the management of electronic records (MoReq). Cornwell Affiliates plc. Health Level Seven.Inc.(2002). HL7 EHR system functional model: a major developent towards consenus on electronic health record system functionality. A white paper. Retrieved April 15,2004 from http://www.h17.org/library/committees/her/contents.pdf Jackson, M.(1995). Software requirements and specifications.Great Britain: Addison Wesley Publishing Company. Jenner. M.G (1995). Software quality management and IS0 9001: how to make them work-for you. Canada: John Wiley & Sons, Inc. Jin, Z., Bell, D.A., Wilkie, F.G. & Leahy, D.G. (2003). Automated requirements elicitation: combining a model-driven approach with concept reuse. International Journal of Sofware Engineering and Knowledge Engineering, 13(1),53-82. Kohn, D.(2002). Electronic document management systems: an overview. Topics in Health Information Management, 23(1),1 Lethbridge, T & Laganiere, R. (2001). Object oriented software engineering: practical software evelopment using UML and Java. England: Mc-Graw Hill Education. Loucopoulos, P. & Karakostas, V. (1995). System requirement engineering. Berkshire: McGraw-Hill Book Company Europe. Model Requirements for the Management of Electronic Record (MoReq). Retrieved April 1 5,2004 from http://www.cornwell.co.uk/moreq.pdf Public Record Office. (2002). Requirements for electronic records management systems. Retrieved April 15,2004 from http://www.prog.gov.uk/recordsmanagement/erecords/2002reqs/2002referencefinal.pdf. Raynes, M. (2002). Document management system: is the time now right? Work Study,51(6), 303-308. Ruottinen, P. & Wittborn, C. (1999). MEMO system reference model. Retrieved May 15,2004, from http://impact-internal. lboro.ac.uk/memo/specs/srd1.pdf Sawyer, D. & Reich, L. (1999). Reference model for an Open Archival Information System(OAIS). Retrieved April 15, 2004 from http://www.personal.leeds.ac.uk/ccldh/ccsds-650.0-w-5.pdf Sommerville:, I. (2001). Software engineering (6th ed.). Harlow, England: Addison-Wesley. Standish Group. (1995). Chuos: application project failure and success.Retrieved April 20, 2004 from Http://www.standishgroup.com/chaos.html. Whittaker, B (1999). What went wrong? unsuccessful information technology projects. Informution Management and Computer Security, 7 (I), 23-29. Whitten, J.L., Bentley, L.D. & Dittman, K.C. (2001). System analysis and design methods(5th ed.) Boston: Mc-Graw-Hill. www.hoora.org.com