You are on page 1of 117

REQUIREMENT MODEL FOR ONLINE CHEMICAL INVENTORY MANAGEMENT SYSTEM OF CHEMICAL LAB AT SCHOOL OF MATERIAL ENGINEERING, UNIMAP

A project submitted to Dean of Research and Postgraduate Studies Office in partial Fulfillment of the requirement for the degree Master of Science (Information Technology) Universiti Utara Malaysia

By Mohd Fitri bin Edros

PERMISSION TO USE

In presenting this project in partial fulfillment of the requirements for a postgraduate degree from Universiti Utara Malaysia, I agree that the University Library may make it freely available for inspection. I further agree that permission for copying of this project in any manner, in whole or in part, for scholarly purpose may be granted by my supervisor(s) or, in their absence by the Dean of Postgraduate and Research. It is understood that any copying or publication or use of this project or parts thereof for financial gain shall not be allowed without my written permission. It is also understood that due recognition shall be given to me and to Universiti Utara Malaysia for any scholarly use which may be made of any material from my project. Requests for permission to copy or to make other use of materials in this project, in whole or in part, should be addressed to

Dean of Research and Postgraduate Studies College of Arts and Sciences Universiti Utara Malaysia 06010 UUM Sintok Kedah Darul Aman Malaysia

i

ABSTRAK (BAHASA MALAYSIA)

Matlamat kajian ini ialah untuk menghasilkan Model Keperluan untuk Online Chemical Inventory Management System (OCIMS) bagi Makmal Bahan di Pusat Pengajian Kejuruteraan Bahan, UniMAP. Kajian Model Keperluan ini amat penting untuk memperbaiki beberapa kelemahan yang terdapat pada sistem sedia ada. Metodologi yang digunakan dalam kajian ini ialah Unified Software Development Software (USDP). Terdapat empat fasa yang terlibat dalam kajian ini iaitu inception, elaboration, construction dan transition. Unified Modeling Language (UML) akan digunakan di dalam kajian ini untuk merekabentuk Model Keperluan. Prototaip untuk kajian ini telah dibangunkan menggunakan Bahasa Pemprograman Java Server Pages (JSP), Apache Tomcat akan bertindak sebagai pelayan aplikasi dan Oracle Express Edition (XE) akan digunakan sebagai Pangkalan Data. Kaedah Expert Review telah digunakan untuk mengesahkan model keperluan yang dibangunkan. Model Keperluan ini akan menjadi panduan kepada pembangunan Sistem Pengurusan Stok Bahan Kimia dan boleh digunakan juga untuk pembangunan sistem yang berkaitan pengurusan stok bahan kimia yang lain. Kajian ini diakhiri dengan membincangkan penemuan dan kekangan yang ditemui sepanjang pembangunan model keperluan ini. Terdapat juga perbincangan berkaitan cadangan kajian pada masa hadapan untuk topik ini.

ii

construction and transition. inception. the study on requirement model is essential. The prototype of the system has been used developed using Java Server Pages (JSP). and can be extended for use in development of other chemical inventory management system in meeting the needs of system users. elaboration. The Unified Modeling Language (UML) has been used in this study to design the requirement model. Due to the limitation of existing system in term of functionality. Apache Tomcat and Oracle Express Edition (XE). There are four main phases involves in this study. The Expert Review has been used to validate the requirement model. This study was concluded by discussing the findings and constraints as well as limitations arising during the course of producing the model. which are. in addition to recommended future study in this domain. as to rectify the weaknesses of the existing system.ABSTRACT (ENGLISH) The aim of the study is to produce a requirement model for Online Chemical Inventory Management System (OCIMS) for Chemical Lab at School of Material Engineering UniMAP. The requirement model provides a referencing point for the development of a chemical inventory management system. iii . The formation of a requirement model for OCIM was approached using a Unified Software Development Software (USDP).

My appreciation also goes to all my fellow colleagues and friends who had provided guidance and ideas as well as encouragement that have definitely encouraged me to complete this study.ACKNOWLEDGEMENT By the Name of Allah. Lastly. My deepest thanks go to my beloved family (Najdawati Mohd Fadzil. support and understanding. Muhammad Faheem and Naufa) for their love. I would like to extend my sincere thanks to my supervisors. iv . Dr Haslina Mohd for the guidance and supervision in the course of my study. a special thanks to all those who had lent a helping hand in allowing me to materialized thin study. the Most Gracious and the Most Merciful First of all.

8 Requirements Requirements Model Online System Unified Modeling Language Java Server Pages Database Current Process of Chemical Inventory Management System Previous Related Works 6 7 8 8 11 12 14 15 v .3 1.1 1.7 2.2 2.4 2.5 2.1 2.2 1.6 Introduction Problem Statement Objective Scope Significant Organization of the Thesis 1 3 4 4 5 5 i ii iii iv v viii ix CHAPTER II: LITERATURE REVIEW 2.4 1.6 2.3 2.TABLE OF CONTENTS Page PERMISSION TO USE ABSTRAK (BAHASA MALAYSIA) ABSTRACT (ENGLISH) ACKNOWLEDGMENTS TABLE OF CONTENT LIST OF TABLE LIST OF FIGURES CHAPTER I : INTRODUCTION 1.5 1.

5 Inception Elaboration Construction Transition Summary 22 23 23 24 24 CHAPTER IV: FINDING AND RESULT 4.4 4.7 4.2 4.2 3.2.3 4.6 4.1 4.4 3.9 Requirements for OCIMS Use Case Diagram Use Case Specification Class Diagram Sequence Diagram Collaboration Diagram Activity Diagram Validate Requirement 25 26 30 31 31 31 32 32 32 Summary CHAPTER V: CONCLUSION AND RECOMMENDATION 5.3 5.5 4.3 3.1 5.4 Project’s Summary Constraints and Limitations Recommendation for Future Research Summary 33 34 35 35 36 REFERENCES vi .2 5.9 Summary 20 CHAPTER III: METHODOLOGY 3.8 4.1 3.

APPENDICES Appendix A Appendix B Appendix C Appendix D Appendix E Appendix F Appendix G USE CASE SPECIFICATION CLASS DIAGRAM SEQUENCE DIAGRAM COLLABORATION DIAGRAM ACTIVITY DIAGRAM EXPERT REVIEW RESULT USER INTERFACE OF THE PROTOTYPE 38 64 68 76 83 95 100 vii .

LIST OF TABLES No 2.1 2.2 Title Brief Description on UML Page 9 19 List of Functionalities by Organization Existing Chemical Inventory Management System 4.1 List of use cases 27 viii .

LIST OF FIGURES No 2.2 2.1 4.1 2.1 JSP Architecture Oracle Database Architecture The current process of Chemical Inventory Management USDP Phases Use Case Diagram Title Page 11 12 14 22 29 ix .3 3.

or as requested by the Chemical Hygiene Officer. storage. 2003). 2005). A physical chemical inventory should be performed at least annually. Defining system requirements is the most important step in developing or acquiring any information system. A successful chemical management program includes standard operating procedures to ensure the safe handling. and transport of chemicals and the proper disposal of chemical waste. The amounts of hazardous materials should be carefully monitored in the laboratory. A thorough inventory will ultimately facilitate the elimination of unneeded or outdated chemicals and provide more efficient use of laboratory storage space (Foster. If the requirements are not correctly defined. Page 1 of 107 . 2005). from their procurement to their proper disposal as chemical waste. is a critical element of a departmental laboratory safety program. By using effective chemical inventory management. the system will not meet the needs of its users (Association of Public Health Laboratories. The chemical inventory process is a critical element of chemical management in academia. Hazard Minimization.CHAPTER I INTRODUCTION 1. A wellmanaged inventory system can address Hazard Identification.1 Introduction The prudent management of hazardous materials. Storage Incompatibility. and Flammable Liquid concerns before they become issues (Cournoyer. many of these requirements are met.

This labs are meant to support the practical approach implies for the students of UniMAP. Page 2 of 107 . the students has to apply for chemical from the technician that in charge in the particular lab. The statement of problem that exists in the scenario is described in the next section. this school has 59 of academic staff. Currently. There are 8 engineering schools in UniMAP.Therefore this study serves to present a requirement model for Online Chemical Inventory Management System (OCIMS) that can be used as a referencing point for such system development initiatives. University Malaysia Perlis (UniMAP) is one of the local public universities in Malaysia that focus in engineering and technology field. School of Materials Engineering is established in UniMAP in 1st March 2003. For the time being. To done their experiment. Beside that this school has to manage 30 of labs scattered around Perlis. One of it is School Of Material Engineering. they are not able to apply via online. 16 of non-academic staff and 656 of students.

Accordingly. As to rectify the weaknesses of the existing system. the following objectives are formulated. acknowledgement mechanism for application status and viewing report via web. the study on requirement model is essential. in order to develop real system. Therefore. Based on the described problem. Page 3 of 107 . three research questions are addressed: i) ii) iii) What are the user requirements for OCIMS? How to model the user requirement for OCIMS? How to validate the user requirement? To resolve the problem and to answer the research questions. it will help the software developer to develop the system that can fulfill the needs of the user. user requirement need to be clearly analyzed and documented.1.2 Problem Statement The existing system functionalities are limited where it does not include online chemical application.

to model the user requirements for OCIMS. get application status and search for chemical information) and chemical application approval (display list of application and process the application). They are as follow: i) ii) iii) to identify the user requirements for OCIMS.4 Scope This study focus on providing a requirement model and a set of requirement list based on functional requirement of OCIMS. This study assumed only student of UniMAP will play a role as an applicant.3 Objective The main objective is to produce a requirement model for Online Chemical Inventory Management System (OCIMS). and to develop the prototype and validate the requirement by Expert Review.1. chemical information management and inventory management). This study covered on chemical inventory administration (user management. chemical applications (apply for chemical. use case specification. The requirements are captured from Chemical Lab at School of Material Engineering UniMAP. collaboration diagrams and activity diagrams. sequence diagrams. To achieve the main aim. Page 4 of 107 . 1. This requirement model consists of use case diagram. this study formulates three subobjectives. class diagrams.

Finally.6 Organization of the Thesis Five chapters involve in this report including this chapter. Appendix section presents the Use Case Specification. Expert Review Result and User Interface Of The Prototype Page 5 of 107 . Activity Diagram. Requirements Model. Chapter I serves a summary of the whole report that contains problem statements. Class Diagram. Constraints and Limitations. there is no requirement model has been form for OCIMS at the moment. To date. the process of software development could be accelerated. Chapter IV presents the model produce in this study in detailed. Online System. Chapter II covers the concept of Requirements. scope and significant of this study. The methodology used in this study was explained in detail in this chapter. This model can be a reference model for other chemical lab in higher education institution in Malaysia. Collaboration Diagram. Sequence Diagram. Chapter V presents the Project’s Summary. 1. With this requirement model. which deal with previous work done on Chemical Inventory Management System. objective. Recommendation for Future Research and Summary. Java Server Pages and Database.5 Significance This study would produce a specific guideline to design OCIMS for Chemical Lab at UniMAP. This chapter will review the literature.1. Unified Modeling Language. Chapter III focuses on how the study conducted.

which are functional requirement and nonfunctional requirement. statement of system behavior.CHAPTER II LITERATURE REVIEW 2. Sommervile (1998) stated that Functional Requirement is a system service. requirements invariably contain mixture of problem information. It also defined as something essential to the existence or occurrence of something else. or specifications of a system property or attribute. properties. design and constraints. application domain information.1 Requirements Requirements are defined during the early stages of a system development as a specification of what should be implemented. The functional requirement will present the Page 6 of 107 . Requirements are divided into two categories. which is expected by the user of the system. Merriam Webster defined requirement as something wanted or needed. They are descriptions of how the system should behave. constraints on the system’s operation. Therefore.

A more general meaning of the term “model” is used here -. It will significantly reduce the cost of systems development and will reduce the probability and severity of cost and schedule growth (overruns) by enabling the description of human readable and “computer friendly”. does not imply a simulation model. security. communicate. A requirement modeling is not a completely new or foreign concept. validate. track. Non-functional requirements include safety. Note that the term “model”.an accurate representation of a system. usability. Page 7 of 107 . reliability. view. 2.functions or features that must included in certain system in order to satisfy the business needs and be acceptable to the user. and they specify external constraints that the product must meet. 2003). Designers have used various forms of requirements modeling for years and these have improved the design process (Air Force Research Laboratory. A large part of a requirements model is not simulatable. and manage the hundreds of hierarchical and interrelated engineering requirements necessary for large and/or complex systems. and performance requirements. analyze. specifications of a system’s engineering requirements.2 Requirements Model A requirement modeling is an information technology for making it easier to capture. They place restrictions on the product being developed and the development process. with respect to requirements modeling. Sommervile (1998) defined non-functional requirement as requirement which are not specifically concerned with the functionally of a system. verify.

2010). and relationship such as association. its contents are described in diagrams that are graphs with model elements. entertainment. shopping. and dependency.4 Unified Modeling Language (UML) UML organizes a model in a number of views that present different aspects of a system. components.2. The term videotex was formerly applied to electronic interactive systems of this type (Encyclopedia Britannica. (Eriksson. Some also provide message services and graphic and audio information. nodes. business. education. 1998) Page 8 of 107 . Such a service provides information. usually in text form. generalization. 2. A diagram contains model elements such as classes. a meaning and graphical symbols to represent them. and more. A diagram typically shows only a part of the contents in a view. A view is not a graph.3 Online System Online System refers to any electronic interactive system that delivers information to users via telephone lines to personal computers (PCs) or via cables to terminals. about news. objects. Only by combining all the views can a complete picture of a system be achieved. The elements have semantics. and a view is defined with many diagrams.

1: Brief Description on UML Diagram name Use Case Diagram What diagram shows What diagram is used to do the functionality A number of external actors and Define their connection to the use cases requirements of the system that the system provides Class Diagram The static structure of classes in Describes the static view of a the system system in term of classes and relationships among the classes Object Diagram A variant of a class diagram and Used to exemplify a complex uses almost identical notation class diagram by showing what the actual instances and the relationships could look like. State Diagram Shows all the possible states that Capture the life cycles of the objects of the class can have. subsystems. and system. Sequence Diagram Shows a dynamic collaboration To describe how the objects Page 9 of 107 . which events cause the state to It specifies the behavior and how change it differs depending on the current state. and objects.The UML diagrams that are used to model the system are as follow: Table 2.

Component Diagram The physical structure of the code Used in practical programming in term of code components. Collaboration Diagram The exchange of messages (called To describe how the objects the interaction). Deployment Diagram work to give a coherent The physical architecture of the Used hardware and software in the description of the system as a system whole Page 10 of 107 . the diagram also interact and communicate with shows the objects and their each other in term of space. relationships (sometimes referred to as a context) Activity Diagram A sequential flow of activities To describe in the an activities operation. It also shows an interaction between objects. something that will happen at one specific point in the execution of the system. such as a use case or an interaction. the object. performed through it can also be used to describe other activity flows.between a numbers of objects in interact and communicate with term of messages send between each other in term of time.

On large Page 11 of 107 . static HTML with dynamically generated content.2. Figure 2. JSP technology is a web-based programming language that enable user to mix regular. ii) Can utilize the common Web Development Tools – the programmer can edit the JSP code using familiar Web Development Tools. iii) Can easily divide work to development team – the Java Programmers can work on the dynamic code. The JSP code only has to enclose with a special tags.5 Java Server Pages (JSP) According to Hall (2004). JSP pages are translated into servlets. For example. The Web Developers can concentrate on the user interface. Most of which start with <% and end with %>. Macromedia Dreamweaver and Microsoft FrontPage. Even other HTML editor tools can also be used to code the JSP page.1: JSP Architecture JSP provides the following benefits: i) Easy to write and maintain the code – the programmer simply can write the JSP code in the regular HTML page in normal manner.

Structurally. corresponding sales orders. advertising executives can study and forecast product sales and warehouse personnel can efficiently manage product inventories. the system development works can easily be divided and can also enforce a weaker or stronger separation between the static HTML and the dynamic content. A database is a tool that can be used to safely store information and properly organize it for fast retrieval. Figure 2.2: Oracle Database Architecture Page 12 of 107 . log files. (Bobrowski. it nothing more than an orderly collection of related information. and employee lists. a business can use a database to store tables of customer records. Database. data files. 2006) An Oracle Database is a collection of related operating system files that Oracle uses to store and manage a set of related information. For example. products parts. Depending on the size of the team and the complexity of the project. salespeople can quickly enter or look up sales orders. an Oracle database has three primary types of files. Various workers can then use the database to efficiently perform their jobs.6 Database Computer typically store and organize large amount of information within a database. 2. For example.project this division is very vital. and control files. whether or not computer manages it.

The latest stable version of Oracle database is Oracle Database 10g. Oracle Database 10g is available in several different license formats. It can be installed on various platforms. and large multiprocessor system. It can be use to design. but mostly on Windows or Linux. vi) Oracle Database 10g Express Edition – A free version of Oracle that supports most popular Oracle database features. including features for high-end database processing. Also called and henceforth referred as Oracle XE. deploy. v) Oracle Database 10g Lite – An Oracle compatible database designed for use in mobile computing environments. build. data warehouse. iii) Oracle Database 10g Enterprise Edition – The complete version of Oracle that provides multiuser access to all features. except this version supports four-processor system. and support Oracle-based applications that run on one-processor systems with databases of 4 gigabytes (GB) or less. ii) Oracle Database 10g Standard Edition – Same to Standard Edition One. There are as follows: i) Oracle Database 10g Standard Edition One – An entry-level version of Oracle that includes the most commonly used option and features available with Oracle and supports two-processor system. Page 13 of 107 . Oracle XE is very easy to install and automatically include powerful application development tools. iv) Oracle Database 10g Personal Edition – A single-user development database license that provides access to most of the Oracle Database 10g Enterprise Edition features.

7 Current Process of Chemical Inventory Management System The existing system of Chemical Inventory Management System was developed using standalone technology. Page 14 of 107 .3: Adminstrator will stored chemical in the system User will applyed for chemical Approver will approved the application Administrator will prepared the chemical User will received the chemical Administrator will updated the chemical stock Figure 2. The current process of Chemical Inventory Management can be summarized in the Figure 2.2.3: The current process of Chemical Inventory Management Reports including Processing Time and Consumption Rate will be generated and printed on monthly basis.

University of California University of California used CiBR-Trac to manage their chemicals inventory. CiBR-Trac allows authorized users to view. and local regulations for reporting.8.. Main modules and their functionalities are stated as follow: a) Material Inventory Management: View/update hazardous materials inventories: i) Chemicals ii) Radioactive materials and Radiation producing equipment iii) Biological Agents b) Radiation Use Authorizations (RUA): RUA Application. CiBR-Trac is a repository of information relating to hazardous chemicals. This online system supports UC Irvine's efforts to maintain compliance with federal. 2.8 Previous Related Works In this part. biological and radioactive materials tracking system. biological and radioactive materials at UC Irvine locations (e. track and update their chemical or radioactive inventory and submit biological use authorizations on a regular basis or when a new chemical. state. Submission and Documentation Page 15 of 107 . biological or radioactive material is used in a laboratory.1 The UC Irvine online hazardous chemicals.2. campus and affiliated research centers). the reviews of existing or related system that produce by others are discussed.g.

research personnel are able to actively maintain their chemical inventories while accessing information about the hazards of each of their chemicals. b) Add or Edit information for any of the chemicals in your inventory. including Page 16 of 107 . NFPA flammability rating. Maintaining active inventories will provides reasonable account of what chemicals are actually in the laboratories at any given time. NFPA and other miscellaneous ratings. NFPA health rating.8.2 Chemical Inventory Management System at the University of Colorado The University of Colorado Chemical Inventory Management System is a compilation of chemical inventories from the research laboratories and maintenance shops on the CU Boulder campus. Utilizing a user-friendly format and direct links for chemical safety information provided in the system. Utilize the system to search the contents of your inventory by chemical name. building. CAS number. There are a number of optional fields that you may use to add information about your chemical. chemical formula. Capabilities of the CU Chemical Inventory Management System: a) Search your chemical inventory.c) Laboratory Administration: i) Contact Information ii) Laboratory Location Information iii) Laboratory Personnel Information 2. It also provides safety information and direct links to MSDS. This system becomes a valuable tool in emergency response situations. room number. NFPA reactivity rating.

physical state. Some data entered in chims must be compared against a list of known valid values either provided by chims or entered into the chims database. This process is called validation. 2. Northwestern University. purchase information. Data which must undergo validation includes Chemical Owner. Data entered which does not validate is not allowed. and unit of measure. building.8. The available information includes NFPA ratings. a web based application developed by Stanford University. OSU. c) Have immediate access to safety information about your chemicals. room.3 Chemical Inventory Management System at the Pennsylvania State University PSU utilizes ChemTracker. department. direct links to Material Safety Data Sheets (MSDS) as well as a direct link to the CU Chemical Hazards Information Database for additional information about the chemical. LSU. and CMU. The ChemTracker server is located at Stanford University and all communication to or from the server is securely encrypted.mixture components and concentrations. and general usage or experiment information. storage location descriptions. including Stanford. It is currently in use at several other major Universities. List of functionalities of chims are as follow: a) Adding Inventory Items i) Adding New items ii) Data Validation iii) Saving Default Values Page 17 of 107 .

b) Editing and Deleting Inventory Items i) Editing Items ii) Editing Items with data validation iii) Deleting Items c) Searching for Inventory i) Creating a search query ii) Saving searches iii) Sorting searches iv) Sorting via amount note d) Generating a reports Table 2.2 below summarizes all the functionalities developed by each system: Page 18 of 107 .

Table 2.2: List of Functionalities by Organization Existing Chemical Inventory Management System FUNCTIONALITY Administration Module ORGANIZATION Manage User Account University California University Colorado Pennsylvania State University University Malaysia Perlis √ √ √ √ √ √ √ √ √ √ of √ √ √ √ √ of √ Manage Chemical Info √ Manage Chemical Stock √ Applicant Module Search for Chemical Apply for Get Chemical Application Status Approver Module Display list Process the Generate of Application √ Application a Report Page 19 of 107 .

None of the Organization’s Chemical Inventory Management System has bellow functionality: a) Apply for Chemical. b) Manage Chemical Info. and e) Generate a Report. it can help the readers to understand the topic deeply and know what are being done in this domain. online system and chemical inventory management system.9 Summary This chapter discussed several topics. c) Display List of Applications. The study on requirement model is highlighted in order to give surface explanation about this term.2.Based on Table 2. and d) Process the Applications. c) Manage Chemical Stock. requirement model. 2. With this study. there are list of common functionality or criteria for Chemical Inventory Management System which are: a) Manage User Account. Page 20 of 107 . It has focused on concept of requirement. d) Search for Chemical. b) Get Application Status. which are related to the study.

According to Booch (2003).CHAPTER III METHODOLOGY There are numerous options of methodologies in the system development area. Among them are Agile Software Development. Unified Software Development Process (USDP) and etc. This methodology was choosing because it contains logical phases that can support all the three sub-objectives that have been formulated earlier. Joint Application Development (JAD). It is described in a variety of whitepapers and books. Rapid Application Development (RAD). Extreme Programming (XP). This study adopted the Unified Software Development Process (USDP). architecture-centric. USDP is a software development approach that is iterative. and use-case driven. Page 21 of 107 .

Chemical Information Form. These phases are as follow: a) Inception b) Elaboration c) Construction d) Transition Within each iteration. Requirements.According to Jacobson (1999). USDP has determined a project lifecycle consisting of four phases. Deployment) Figure 3. Supporting document such as Chemical Application Form.1 Inception Phase The first phase has presents the functional user requirements towards the OCIMS. current work flow of chemical inventory management also was study. Furthermore. Test. The process starts by getting information from existing Chemical Inventory Management System to capture common functionalities that the system should have. and Consumption Rate Report are also been gather. Beside Page 22 of 107 . Analysis and Design. Implementation.1: USDP Phases 3. the tasks are categorized into nine disciplines: six “engineering disciplines” (Business Modeling.

the user requirement has been analyzed and modeled using a tool. UML notations were used to model the user requirement because UML is standardized. easy to use and easy to understand. This architecture has 3 layer with is Client tier. Use Case Specification.3 Construction Phase In this phase. 3. Then. the UML diagrams and Use Case Specification document has been used as a guideline to develop the prototype of the system. For each tier there is specific software has been used in order to build a prototype. The outputs of this phase are the Use Case Diagram. 3.2 Elaboration Phase In this phase. Collaboration Diagram and Activity Diagram. Class Diagram. Use case diagram is used to show the functionality of the system and the related actor that interact with the functionality. Sequence Diagram. namely Unified Modeling Language (UML). The following software was used to develop the prototype: Page 23 of 107 .that a series of interview has been conducted with Lab Coordinator and Technician of the Chemical Lab to identify the user requirement clearly. sequence diagram. Middle tier and Data tier. The study has continued by designing the class diagram. The Microsoft Office Visio 2003 is proprietary software used to design exact software models which is based on UML standard. The Microsoft Office Visio 2003 software is used to construct the UML Diagrams. The output for this phase is a list of Functional User Requirement. this study has continued by providing the Use Case Specification to elaborate each of the use case define in Use Case Diagram. collaboration diagram and activity diagram. It was designed followed the Web-Based System 3-tier Architecture.

b) Java Server Pages (JSP) – It was utilized as a programming language for the OCIMS prototype. They has been be given list of test cases. the prototype of the system has been developed and tested by the expert reviewer. the prototype has been tested by the expert reviewer from ICT Center of UniMAP. Firstly.3 Transition Phase In this phase.0 – It was used as an application server for the OCIMS prototype d) Oracle Express Edition (XE) – It was used as a Database in order to store the testing data of OCIMS prototype. Page 24 of 107 . There are 4 expert reviewer involve in the testing.4 Summary This chapter has described the methodology which is a step-by-step process which being followed to accomplish this study. In order to validate the model. an access to system prototype and also test data set. The Expert Review has been used to validate the requirement model. c) Apache Tomcat 5. 3. This study has used Unified Software Development Process (USDP) as a methodology. Then. the requirement model is design based on requirement list using Unified Modeling Language (UML). 3. the requirement list of the system has been gathered and listed. All of them have an experience in Software Development more than 5 years.a) Macromedia Dreamweaver MX – It was used to design the User Interface for the OCIMS prototype and also as a tool to code the server-side-script.

collaboration diagrams and activity diagrams. Student and Lab Coordinator have to login the system Lab technician can manage user account Lab technician can manage chemical information Page 25 of 107 . 3. class diagram. sequence diagrams. No. List of Requirements Lab technician. use case specifications. 1 2. 4.CHAPTER IV FINDING AND RESULT This chapter focuses on the details of OCIMS requirement model where has been documented using UML notation. The findings and results of the study were presented that discussed the elements in the model that consist of use case diagrams.1 Requirements for OCIMS Listed below are the functional requirements of the system that has been gathered.

The actors identified during requirement capturing and analysis process are as follows: a) Lab Technician b) Student c) Lab Coordinator Page 26 of 107 . 6. 9. 12. 7.2 Use Case Diagram This diagram shows a number of external actors and their connection to the use cases that the system provides. 11. 8. 5.4. It was used to define the functionality requirements of the system. 10. Lab technician can add chemical stock Student can search for the chemical information Student can apply for chemical Student can get their application’s status Lab coordinator can view list of application for chemical as well as its status Lab coordinator can manage the application for chemical Lab coordinator can view report on chemical stock Lab coordinator can view report on processing time Lab coordinator can view report on consumption rate 4. eleven (11) main use cases and three (3) extended use cases were identified. With all the requirements collected and analysis. a total of three (3) actors.

1: List of use cases No 1 2 3 4 5 6 7 8 9 10 Use Case Login Create User Account Create Chemical Information Add New Stock Search for Chemical Apply for Chemical Get Application Status View List of Application Manage the Application View Report Extend use case : View Current Chemical Stock Report Extend use case : View Processing Time Report Extend use case : View Consumption Rate Report 11 Logout Page 27 of 107 .Table 4.1 illustrates the use cases that have been identified. Table 4.

Figure 4.1 shows the use case diagram for OCIMS Figure 4.1: Use Case Diagram Page 28 of 107 .

1998). It concentrates on the external behavior of the system and ignores how things are actually performed inside the system (Eriksson.3 Use Case Specification This is a simple and consistent specification about how the actors and the use cases interact. There are thirteen (13) use case specifications elaborating the use cases (refer Appendix A).4. The use case specifications are as follows: a) Use case specification for Login b) Use case specification for Create User Account c) Use case specification for Create Chemical Profile d) Use case specification for Add New Stock e) Use case specification for Search for Chemical f) Use case specification for Apply for Chemical g) Use case specification for Get Application Status h) Use case specification for View List of Application i) Use case specification for Manage the Application j) Use case specification for View Current Chemical Stock Report k) Use case specification for View Processing Time Report l) Use case specification for View Consumption Rate Report m) Use case specification for Logout Page 29 of 107 .

5 Sequence Diagram This diagram shows a dynamic collaboration between a numbers of objects in term of messages send between the object. It was used to describe the static view of a system in term of classes and relationships among the classes. It was used to describe how the objects interact and communicate with each other in term of time. For details diagrammatic representation of this diagram please refer Appendix D.6 Collaboration Diagram This diagram shows the exchange of messages (called the interaction).4. 31 attributes and 14 operations (refer Appendix B). It was used to describe how the objects interact and communicate with each other in term of space. something that will happen at one specific point in the execution of the system.4 Class Diagram This diagram shows the static structure of classes in the system. 4. the diagram also shows the objects and their relationships (sometimes referred to as a context). The class diagrams consist of 5 classes. There are 11 collaboration diagrams was constructed. There are 11 sequence diagrams was constructed. Page 30 of 107 . For details diagrammatic representation of this diagram please refer Appendix C. It also shows an interaction between objects. 4.

There are 4 expertise involved in the testing activity. collaboration diagram and activity diagram. They are Software Developer at ICT Center of UniMAP.7 Activity Diagram This diagram shows the sequential flow of activities. Based on this analysis. 4. (Refer the Appendix F the see the Expert Review Result and refer the Appendix G to see the User Interface of the Prototype) 4. the key terms. It was used to describe the activities performed in an operation. through it can also be used to describe other activity flows. the requirement model for OCIMS is provided.4. such as a use case or an interaction.9 Summary The requirement model for OCIMS is discussed in detail in this chapter. class diagram. There are 16 test cases was designed. The full model is constructed using use case diagram. is explained.8 Validate Requirement This study used prototype and Expert Review in order to validate the requirement model. Page 31 of 107 . which is used in this model. Expert Review Result and User Interface on Prototype were also presented in this chapter. sequence diagram. There are 11 activity diagrams was constructed. For details diagrammatic representation of this diagram please refer Appendix E. use case specification. In order to give better understanding to this model.

1 Project’s Summary The objective of the study is to develop. and the prototype fulfils the entire requirement needed. The requirement model provided guidance Page 32 of 107 . Furthermore. constraints and limitations relating to this study are also elaborated and recommendations were offered for further study in the area. This study followed the USDP methodology that consists of four (4) phases including the inception (requirement gathering). The Expert Review was used to validate the requirement model. construction (prototyping) and transition (requirement validating). elaboration requirement modeling).CHAPTER V CONCLUSION AND RECOMMENDATION This chapter concludes the construction and discussion of the requirement model for OCIMS. test and validate the requirement model for OCIMS that includes diagrammatic and textual descriptions utilizing UML that tailor to requirements of owners and users of the Chemical Inventory Management System. 5.

platform and reliability). Page 33 of 107 . 4) This study only conducting interviews and prototype testing with the expertise from UniMAP. Among the constraints and limitation in the construction of the requirement model are: 1) There are some of the requirements that are not included in this study due to time constraint. some constraint and limitation still happen. the requirements are model based on local experience and tailor with the UniMAP environment. Due to that. usability. Although the objective of developing requirement model for OCIMS is achieved. the study manages to finish basic functionality of the prototype.2 Constraints and Limitations There are several difficulties encountered during constructing this requirement model. 5. However.for development of OCIMS full function system. It also can be a referencing point for other similar system as OCIMS in other universities or institution. 2) The prototype of the system was not fully functional system also due to the time constraints in developing the prototype. This is due to the scope of the study was only emphasize on the functional requirements. 3) This study does not include the non-functional requirements such as performance. security.

is the development of the fully function prototype. The non-functional requirements may consist of performance. the future study should include users from other universities or institutions. Page 34 of 107 . usability. As with any studies in the area of IT. 3) Due to its focus to provide generalized functions for international and local chemical inventory management. recommendations for the future studied are forwarded to gain the full advantages of future studies regarding this topic. security and platform issues.3 Recommendation for Future Research The below recommendations are suggested to accommodate some of the constraints and limitations stated above in future study. This was suggested to be done at least in 6 month duration.5. this study was subjected to constraints and limitations. from within or other country to gather and validate the requirements of OCIMS.4 Summary Overall. 5. this study achieved the objectives of producing a validated requirement model for OCIMS that includes diagrammatic and textual description using UML. Finally. reliability. 1) It is recommended that a complete requirement model for OCIMS including the nonfunctional requirements will be produced by the future researcher. This is significant to make the requirement model more accurate and can be a referencing point locally and globally. 2) Next.

(2006). New York: McGraw-Hill. (2003). Hand-On Oracle Database10g Express Edition for Linux.References Air Force Research Laboratory. Chichester:John Wiley & Sons Ltd.microsoft. J.edu/chims/faq. Inc. Journal of Chemical Health and Safety. M. 12(5). 2010. B.html Cournoyer.). from http://office. Association of Public Health Laboratories. Hall. L. Journal of Chemical Health and Safety.: Author. & Penker. L. 2010. UML 2 and The Unified Process Practical-Oriented Analysis and Design (2nd ed. DC. M. Chims FAQ (2006). Bobrowski. (2005). Faster. Arlow. Chemical inventory management: The key to controlling hazardous materials. S. NJ: Pearson Education. Requirements Modeling Technology A Vision For Better. And Cheaper Systems. Retrieved September 15.ehs. Retrieved April 3. Washington. Chemical Inventory Management System. E. P. R.. & Spink. 21-25.. (2005).psu.com/en-us/visio-help/create-a-uml-use-case-diagramHP081550218. (1998). H. Ohio : Wright-Patterson Air Force Base. (2004). & Neustadt. from http://www. The Chemical Inventory Management System in academia. (2003). (2005). Foster. Porterfield. M.aspx Erikson. Create a UML use case diagram (2003). M. D. M. & Brown. 15-20.). UML Toolkit. I. Requirements for Public Health Laboratory Information Management Systems. Maestas. California: Prentice Hall. 12(5).Core Servlets and Java Server Pager (2nd ed. Page 35 of 107 .

C.org/tcuid/index. (2010).net/ University of Colorado Chemical Inventory Management System (2007). The Unified Software Development Process. 2010.). (2004). Inc. Lam. & Rumbaugh. & Judith. Booch. In Encyclopedia Britannica Online. Kroll. The Rational Unified Process Made Easy a Practitioner’s Guide to the RUP. (1994). The UC Irvine online hazardous chemicals.J... In Merriam-Webster’s online dictionary. I. biological and radioactive materials tracking system (2008). Internet Computing (2nd ed. G. Task-Centered User Interface Design. P.ecompliance.com/EBchecked/topic/429262/online-system Requirement. I. & Rieman. NJ: Pearson Education. 2010. 2010.colorado.edu/helpindex.Jacobson. from http://www. from http://hcibib.com/dictionary/requirement Sommerville.merriam-webster. C. 2010. Lewis. Singapore: Prentice Hall. Jalloul. P. B. Retrieved March 27.html Online system. (2003). & Kotanya. from http://www. from http://ucbchemicalinventory. Retrieved July 24. Retrieved March 27.htm Page 36 of 107 . NJ: Pearson Education. J. C. Keck. (1999). 2010. G. (1998). Cambridge: Cambridge University Press. (2010). Retrieved March 27. Inc. Chichester:John Wiley & Sons Ltd. Requirements Engineering Process and Techniques.britannica. Retrieved March 27. (2003). G. UML by Example. from http://ucirvine. & Kruchten.

APPENDIX A USE CASE SPECIFICATION Page 37 of 107 .

0 LOGIN (OCIMS_01) 1.Alternative Flow • Not Applicable. display main page of the system.1. process the chemical application or view a monthly basis report.1. FLOW OF EVENTS 1.3. 1. 1. • The user will click Log-in button. 1. • The system shall validate the User Account (E-1: User Account Not Valid). BRIEF DESCRIPTION This use case will enable the user (Lab technician. Please try again”. Page 38 of 107 .1.Exceptional Flow • E-1: User Account Not Valid. CHARACTERISTIC OF ACTIVATION Event Driven (on user’s demand) 1.4.3. 1.4.2.4. The system shall wait until the user enters valid Username and Password.4. The system shall display the message “Username or Password Not Valid. PRE-CONDITIONS The user must be registered in to the system.2.Basic Flow • This use case begins after the user enters their Username and Password. apply for chemical. Lab coordinator and Student) to log into the system in order to manage chemical items.

POST-CONDITIONS The user manages to log into the system 1.6. CONSTRAINT(S) Not applicable. RULE(S) Not applicable.1. Page 39 of 107 . 1.5.7.

2.3.1. FLOW OF EVENTS 2. CHARACTERISTIC OF ACTIVATION Event Driven (on lab technician’s demand) 2. The lab technician will navigate to the Administration menu New User. Not Valid The system shall display the message “IC Not Valid. Please key-in a valid IC no”.0 CREATE USER ACCOUNT (OCIMS_02) 2. • The lab technician will key-in IC No.1.2. The system shall check for IC No validity (E-1: IC No. Create 2. Page 40 of 107 .4. Exceptional Flow • E-1: IC No. 2.4. BRIEF DESCRIPTION This use case will enable the lab technician to create.3. Not Valid).4. 2. Alternative Flow • Not Applicable. Basic Flow (OCIMS_02_01) • • This use case begins after the lab technician logged in to the system. PRE-CONDITIONS The lab technician must be logged in to the system. select the user’s role and create the user account. 2. update or delete user account for OCIMS. of the user.2.4. The system shall wait until the lab technician enters the valid IC No.

CONSTRAINT(S) The user account will only created for internal user (staff and student of UniMAP).2.6. Page 41 of 107 .7. POST-CONDITIONS The user account was successfully created. 2. RULE(S) Not applicable.5. 2. The users outside UniMAP are not applicable to use the system.

3. 3. The system shall wait until the lab technician inserts valid Chemical ID. BRIEF DESCRIPTION This use case will enable the lab technician to add. The lab technician will navigate to the Administration menu New Chemical. The system shall display the message “Chemical ID already used”. 3. Add 3.3. Basic Flow (OCIMS_03_01) • • This use case begins after the lab technician logged in to the system.4.2.2.1. FLOW OF EVENTS 3. CHARACTERISTIC OF ACTIVATION Event Driven (on lab technician’s demand) 3. 3.4. The system shall check for uniqueness of Chemical ID (E-1: Chemical ID already used) and process the request.4. PRE-CONDITIONS The lab technician must be logged in to the system. update or delete the chemical profile.4. Exceptional Flow • E-1: Chemical ID already used. Page 42 of 107 .3. • The lab technician will fill in the entire field with appropriate value. Alternative Flow • Not Applicable.1.0 CREATE CHEMICAL PROFILE (OCIMS_03) 3.

3. Page 43 of 107 .3. RULE(S) Not applicable.7.5. CONSTRAINT(S) Not applicable. POST-CONDITIONS The chemical item was successfully created.6. 3.

4.0 ADD NEW STOCK (OCIMS_04) 4. The system shall calculate the new value of particular chemical stock.1. 4.3. • The lab technician will select the desired chemical and key-in the value of new stock to be added.1. POST-CONDITIONS 4. 4.5. Add 4. Alternative Flow Not Applicable.4.4.5. Basic Flow (OCIMS_04_01) • This use case begins after the lab technician logged in to the system. 4.1. BRIEF DESCRIPTION This use case will enable the lab technician to add stock to chemical stock.2. • The lab technician will navigate to the Administration menu New Stock.4. calculate latest stock value and display it to lab technician.2.3. Page 44 of 107 . PRE-CONDITIONS The lab technician must be logged in to the system and the particular chemical information must be inserted first. Exceptional Flow Not Applicable.4. FLOW OF EVENTS 4. • The system shall display list of available chemical. The lab technician manages to add new stock to current chemical stock. CHARACTERISTIC OF ACTIVATION Event Driven (on lab technician’s demand) 4.4.

2.6. Page 45 of 107 . CONSTRAINT(S) Not applicable.5.4. The system will calculate new value for particular chemical stock. RULE(S) Not applicable. 4.7. 4.

4. • The system shall display list of Chemical Name • The student will select the Chemical Name. 5. • The student will navigate to the Application menu Chemical.4. PRE-CONDITIONS The student must be logged in to the system. (E-1: The chemical are not in the database) and shall display the chemical info based on Chemical Name provided. BRIEF DESCRIPTION This use case will enable the student to search for chemical information. 5. CHARACTERISTIC OF ACTIVATION Event Driven (on student’s demand) 5. FLOW OF EVENTS 5. Alternative Flow Not Applicable.3.4.1. Page 46 of 107 Search for . 5. The system shall check whether the chemical exist or not.4. Basic Flow (OCIMS_05_01) • This use case begins after the student logged in to the system.3.0 SEARCH FOR CHEMICAL PROFILE (OCIMS_05) 5. Exceptional Flow E-1: The chemical are not in the database The system shall display the message “The chemical are not in the database”.2.2.1.5. 5.

5. CONSTRAINT(S) Not applicable. 5. 5.5.7. RULE(S) Not applicable.6. POST-CONDITIONS The student manages to search for chemical and get the detail about chemical. Page 47 of 107 .

0 APPLY FOR CHEMICAL (OCIMS_06) 6. Basic Flow (OCIMS_06_01) • This use case begins after the student logged in to the system.2. 6. • The student will enter Chemical ID and number of chemical to be applied. • The system shall check for value of request compared with value of current stock. 6. 6.1.4. • The student will navigate to the Application menu Chemical. PRE-CONDITIONS The student must be logged in to the system. BRIEF DESCRIPTION This use case will enable the student to apply for chemical. Alternative Flow Not Applicable. FLOW OF EVENTS 6. 6. (E-1: The Requested value is exceeding the value of current stock) and shall submit the application. • The system shall display the chemical profile and current stock information.6.2.3. Exceptional Flow E-1: The Requested value are exceed the value of current stock Apply for Page 48 of 107 .4. CHARACTERISTIC OF ACTIVATION Event Driven (on student’s demand) 6.1.4.3.4.

Page 49 of 107 . CONSTRAINT(S) Not applicable. 6.5.The system shall display the message “The Requested value are exceed the value of current stock”.6. 6. POST-CONDITIONS The student manages to apply for chemical and the application was submitted for processing. 6. RULE(S) Not applicable.7. The system shall wait until the student inserts valid requested value.

7.7. CONSTRAINT(S) Not applicable. RULE(S) Not applicable. The system shall display list of chemical application and their status. PRE-CONDITIONS The student must be logged in to the system and has applied the chemical 7.1.3. 7. Alternative Flow Not Applicable.4.2. 7. 7. 7.2. FLOW OF EVENTS 7.3. BRIEF DESCRIPTION This use case will enable the student to get the acknowledgement on their application status 7. CHARACTERISTIC OF ACTIVATION Event Driven (on student’s demand) 7. Page 50 of 107 .4.4.5. Exceptional Flow Not Applicable.6.4.1. POST-CONDITIONS The customer manages to get their application status 7.0 GET APPLICATION STATUS (OCIMS_07) 7. Basic Flow (OCIMS_07_01) • • This use case begins when the student log into the system.

8.1.3.2. Basic Flow (OCIMS_08_01) • This use case begins after the Lab coordinator logged in to the system • The system shall display Reporting Menu. 8.4. POST-CONDITIONS The manager manages to get list of application for chemical as well as its status.3. FLOW OF EVENTS 8.4.2. RULE(S) Not applicable.1.5.8. CHARACTERISTIC OF ACTIVATION Event Driven (on Lab coordinator’s demand) 8.0 VIEW LIST OF APPLICATION (OCIMS_08) 8. PRE-CONDITIONS The Lab coordinator must be logged in to the system. Alternative Flow Not Applicable. BRIEF DESCRIPTION This use case will enable the Lab coordinator to view list of application for chemical as well as its status 8. 8. 8. • The Lab coordinator will select to view list of application for chemical as well as its status • The system shall generate and display the selected report. Page 51 of 107 .4.4. 8. Exceptional Flow Not Applicable.6.

7. Page 52 of 107 .8. CONSTRAINT(S) Not applicable.

4. • The system display list of unprocessed application. PRE-CONDITIONS The Lab coordinator must be logged in to the system. 9.4.9.2. Page 53 of 107 .0 MANAGE THE APPLICATION (OCIMS_09) 9.1. 9. CHARACTERISTIC OF ACTIVATION Event Driven (on Lab coordinator‘s demand) 9.3.1. Alternative Flow Not Applicable. FLOW OF EVENTS 9.4. • The Lab coordinator will select the desired unprocessed application Input the value to release. BRIEF DESCRIPTION This use case will enable the Lab coordinator to process the chemical application from student. Basic Flow (OCIMS_09_01) • This use case begins after the Lab coordinator logged in to the system. 9. (E-1: The Released value is exceeding the value of current stock) and shall deduct the value from current chemical stock. The system shall check for value of release compared with value of current stock.2.

Page 54 of 107 . CONSTRAINT(S) Not applicable.4. 9. Exceptional Flow E-1: The Released value is exceeding the value of current stock The system shall display the message “The Released value is exceeding the value of current stock”.9.6.3. 9. RULE(S) Not applicable. POST-CONDITIONS The Lab coordinator manages to process the chemical application from the student.7.5. 9.

10. • The Lab coordinator will select to view report on chemical stock. 10.3.1. Alternative Flow Not Applicable. Page 55 of 107 .4.4. 10. CHARACTERISTIC OF ACTIVATION Event Driven (on Lab coordinator’s demand) 10.3.4.2.4. PRE-CONDITIONS The Lab coordinator must be logged in to the system. FLOW OF EVENTS 10. The system shall generate and display the selected report.1.0 VIEW REPORT ON CHEMICAL STOCK (OCIMS_10) 10.2. Basic Flow (OCIMS_10_01) • This use case begins after the Lab coordinator logged in to the system • The system shall display Reporting Menu. Exceptional Flow Not Applicable.10. BRIEF DESCRIPTION This use case will enable the Lab coordinator to view report on chemical stock 10.

POST-CONDITIONS The manager manages to get report on chemical stock.7. 10. RULE(S) Not applicable. Page 56 of 107 .5. 10.6.10. CONSTRAINT(S) Not applicable.

1.0 VIEW REPORT ON PROCESSING TIME (OCIMS_11) 11. 11.4. Page 57 of 107 . The system shall generate and display the selected report. Basic Flow (OCIMS_11_01) • This use case begins after the Lab coordinator logged in to the system • The system shall display Reporting Menu. Exceptional Flow Not Applicable.1.2.4.11.4. CHARACTERISTIC OF ACTIVATION Event Driven (on Lab coordinator’s demand) 11. BRIEF DESCRIPTION This use case will enable the Lab coordinator to view report on processing time 11. 11. • The Lab coordinator will select to view report on processing time.2. 11. PRE-CONDITIONS The Lab coordinator must be logged in to the system. Alternative Flow Not Applicable.3.4.3. FLOW OF EVENTS 11.

11. RULE(S) Not applicable.6. CONSTRAINT(S) Not applicable. Page 58 of 107 .7. POST-CONDITIONS The manager manages to get report on processing time 11.11.5.

2. CHARACTERISTIC OF ACTIVATION Event Driven (on Lab coordinator’s demand) 12.4.1. FLOW OF EVENTS 12. Alternative Flow Not Applicable. 12. Basic Flow (OCIMS_12_01) • This use case begins after the Lab coordinator logged in to the system • The system shall display Reporting Menu. • The Lab coordinator will select to view report on consumption rate. PRE-CONDITIONS The Lab coordinator must be logged in to the system. The system shall generate and display the selected report.0 VIEW REPORT ON CONSUMPTION RATE (OCIMS_12) 12.4. 12.2.1.3. Page 59 of 107 .4.12. BRIEF DESCRIPTION This use case will enable the Lab coordinator to view report on consumption rate 12.

RULE(S) Not applicable.12. 12. 12.7. Page 60 of 107 . Exceptional Flow Not Applicable.6.3.5.4. POST-CONDITIONS The manager manages to get view report on consumption rate. 12. CONSTRAINT(S) Not applicable.

13.2. 13. 13.4. • The system will redirect to OCIMS Login Page 13.1.0 LOGOUT (OCIMS_13) 13.4. POST-CONDITIONS The user manages to log out from the system Page 61 of 107 .4. FLOW OF EVENTS 13.2. 13. PRE-CONDITIONS The user must be logged in to the system. Alternative Flow Not Applicable. • The system shall logout the user successfully. Exceptional Flow Not Applicable.5.3. Basic Flow (OCIMS_13_01) • This use case begins when the user click to logout button.1.3.4. BRIEF DESCRIPTION This use case will enable the user to logout from the system 13. CHARACTERISTIC OF ACTIVATION Event Driven (on user’s demand) 13.

13. RULE(S) Not applicable.6. Page 62 of 107 . CONSTRAINT(S) Not applicable.7.13.

APPENDIX B CLASS DIAGRAM Page 63 of 107 .

Page 64 of 107 .

Page 65 of 107 .

Page 66 of 107 .

APPENDIX C SEQUENCE DIAGRAM Page 67 of 107 .

Page 68 of 107 .

Page 69 of 107 .

Page 70 of 107 .

Page 71 of 107 .

Page 72 of 107 .

Page 73 of 107 .

Page 74 of 107

APPENDIX D

COLLABRATION DIAGRAM

Page 75 of 107

Page 76 of 107

Page 77 of 107 .

Page 78 of 107 .

Page 79 of 107 .

Page 80 of 107 .

Page 81 of 107 .

APPENDIX E ACTIVITY DIAGRAM Page 82 of 107 .

Page 83 of 107 .

Page 84 of 107 .

Page 85 of 107 .

Page 86 of 107 .

Page 87 of 107 .

Page 88 of 107 .

Page 89 of 107 .

Page 90 of 107 .

Page 91 of 107 .

Page 92 of 107 .

Page 93 of 107 .

APPENDIX F EXPERT REVIEW RESULT Page 94 of 107 .

b) Click Login button. c) Click Search button d) Select the user’s role e) Click Submit button 4 a) Navigate to the User The system shall display the message Create “Matric No. Please key-in a Y Y Y Y Management menu Page 95 of 107 . “Username or Password Not Valid. b) Key-in correct Matric No. Create Y Y Y Y 3 MANAGE USER ACCOUNT (OCIMS_02) a) Navigate to Y Y Y Y Management menu New User. Not Valid. Expert Reviewer #1 #2 #3 #4 Y Y Y Y 2 a) Enter wrong Username and The system shall display the message Password.EXPERT REVIEW RESULT No 1 Use Cases LOGIN (OCIMS_01) Test Steps Expected Results a) Enter correct Username and Main page of the system will be displayed. Password. Please try again”. of the user. the User The user account will be created and listed in the list of users. b) Click Login button.

menu Add New Chemical. Y Y Y Y chemical stock. Y Y Y Y b) Fill in the entire field with appropriate value. c) Click Submit button 5 MANAGE CHEMICAL INFO (OCIMS_03) valid Matric No. b) Key-in wrong Matric No. c) The system shall calculate the new value of particular New stock will be added to current chemical stock. c) Click Submit button 6 ADD NEW STOCK (OCIMS_04) a) Navigate to the Stock menu. Y Y Y Y Page 96 of 107 .” a) Navigate to the Chemical Info The chemical info will be created. 7 SEARCH FOR CHEMICAL PROFILE (OCIMS_05) a) Navigate to the Chemical Info The system shall display the chemical info menu Search for Material. d) Fill in the Invoice No and PO No. based on Chemical Name selected. b) Key-in the chemical ID and value of new stock to be added.New User. of the user.

b) Select the application status c) Click Process button d) Navigate to the Manage Page 97 of 107 . 8 APPLY FOR CHEMICAL (OCIMS_06) a) Navigate to the Request Form The menu. Status menu. 9 GET APPLICATION STATUS (OCIMS_07) VIEW LIST OF APPLICATION (OCIMS_08) MANAGE THE APPLICATION (OCIMS_09) a) Navigate to the Application The system shall display list of chemical application and their status. a) Navigate to the List 11 Y Y Y Y Application menu. c) Select the Chemical Name.b) The system shall display list of Chemical Name and ID. Y Y Y Y 10 Y Y Y N Application menu. a) Navigate to the List of The system shall display list of chemical application and their status of The application will be processed. d) Click Submit application was submitted for Y Y Y Y processing. b) Select the Approver Name and Purpose c) Enter Chemical ID and number of chemical to be applied.

Y Y Y Y 14 a) Navigate to the Report menu The system shall generate and display the Processing Time. f) Input correct value to release. The system will redirect to OCIMS Login Page Y Y Y Y 16 Y Y Y Y Page 98 of 107 . e) The system shall display list of approved application. k) Click Update 13 VIEW REPORT ON CHEMICAL STOCK (OCIMS_10) VIEW REPORT ON PROCESSING TIME (OCIMS_11) VIEW REPORT ON CONSUMPTION RATE (OCIMS_12) LOGOUT (OCIMS_13) l) Navigate to the Report menu The system shall generate and display the Chemical Stock. selected report. g) Click Update 12 h) Navigate to the Manage The system shall display the message : “The Released value is exceeding the Y Y Y Y Application menu. Y Y Y Y 15 a) Navigate to the Report menu The system shall generate and display the Consumption Rate. selected report. a) Click to logout. i) The system shall display list of value of current stock)” approved application. selected report.Application menu. j) Input wrong value to release.

APPENDIX G USER INTERFACE OF THE PROTOTYPE Page 99 of 107 .

Login Page The login page will be displayed upon accessing the prototype URL. To log into the system. users will enter their valid username and password. Page 100 of 107 .

After entering the valid matric no. Then select the user group and click Submit button. Lab Technician: Create New User This page enables the Lab Technician to create new user for the system. Page 101 of 107 . The functionalities consist of the functionalities to create new user.Lab Technician: Main Page This page contains the functionalities for the Lab Technician. add new chemical and add new stock. the system will display the information about the user. view list of user.

After filling the entire field with appropriate value and click Add button. After filling the entire field with appropriate value and click submit button. Lab Technician: Add New Stock This page enables the Lab Technician to add new stock to chemical stock. the new stock will be added to current chemical stock.Lab Technician: Add New Chemical Information This page enables the Lab Technician to add new chemical information. Page 102 of 107 . the chemical information will be created and stored in database.

Click Search button and the Chemical Information will be shown to the student. Student: Search for Chemical Information This page enables the Student to search for chemical information. Page 103 of 107 . apply for chemical and get application status. The functionalities consist of the functionalities to search for chemical information.Student: Main Page This page contains the functionalities for the Students. List of chemicals will be displayed by the system and the student will have to select the appropriate chemical name.

Student: Apply for Chemical

This page enables the Student to make application for chemical. Student has to fill in the appropriate field and click Add button. The application will be submitted for processing. Optionally, they can also print their application by clicking print button.

Student: Get Application Status

This page enables the Student to know the application status. The status will be shown at Current Status column. Student can also view back the application forms that are currently being process.

Page 104 of 107

Lab Coordinator: Main Page

This page contains the functionalities for the Lab Coordinator. The functionalities consist of the functionalities to view list of application, manage the application and view related report.

Lab Coordinator: View List of Application

This page enables the Lab Coordinator to view list of application and approve or disapprove them. The application can be approve by selecting the approved status and click Process button. The status will be change to approve in Current Status column.

Page 105 of 107

Lab Coordinator: Manage the Application

This page enables the Lab Coordinator to process the approved application. This page will only display application with the approved status. To process the application, just click Process button, fill in the release value and click Update button.

Lab Coordinator: View Report on Chemical Stock

This page enables the Lab Coordinator to view Report on Chemical Stock. From this report, there are information consist of total number of stock that comes in, total number of stock that goes out and total current stock balance.

Page 106 of 107

there are an information consist of approval cycle time and processing cycle time Lab Coordinator: View Report on Consumption Rate This page enables the Lab Coordinator to view Report on Consumption Rate. From this report. From this report. there are an information consist of no of chemical that had been used per semester Page 107 of 107 .Lab Coordinator: View Report on Processing Time This page enables the Lab Coordinator to view Report on Processing Time.