Journal of Computer Science 6 (3): 253-260, 2010 ISSN 1549-3636 © 2010 Science Publications Corresponding Author: Rafa E. Al-Qutaish, Department of Software Engineering, Alzaytoonah University of Jordan, Airport Street, Amman 11733 253 UML Diagrams Generator: A New CASE Tool to Construct the Use-Case and Class Diagrams from an Event Table Mohammad I. Muhairat, Rafa E. Al-Qutaish and Akram A. Abdelqader Department of Software Engineering, Alzaytoonah University of Jordan, Airport Street, Amman 11733, Jordan Abstract: Problem statement: Building UML diagrams is a very important and time consuming task for both requirements and design phases. However, some of these diagrams, such as use-case and class diagrams can be considered as a transition between the two phases. Approach: Through this study, the event table will be used to derive the use-case and class diagrams. Results: A new CASE tool to automate the proposed approach will be introduced, that is, the UML diagrams generator (UMLdg). Conclusion: It is clearly noted that the proposed CASE tool (UMLdg) gives an ideal and reasonable methodology to construct the intended use-case and class diagrams from any comprehensive event table. Furthermore, this tool will save the time for the building process of such diagrams. Key words: Requirements specification, software design, CASE tool, UML, use-case diagram, class diagram INTRODUCTION Nowadays, there are many different techniques (approaches) to identify the use-cases, for examples: • Listing of all users and define their needs (Bennett et al., 2005; Larman, 2004; Liang, 2003; Reed, 2001; Schach, 2003) • Defining all system functions and adding new functions that user may be need (Bennett et al., 2005; Larman, 2004; Reed, 2001; Satzinger et al., 2004; Schach, 2003) • List all Graphical User Interfaces that may be used by users (Cockburn, 2000; Larman, 2004) • Defining of all users’ goals in using the system (Chung and Supakkul, 2004; Larman, 2004; Lee and Xue, 1999; Liang, 2003; Satzinger et al., 2004) Many analysts used the fourth approach to get an initial list of use-cases. However, the most used approach for defining a use-case model is event decomposition technique (Larman, 2004; Reed, 2001; Satzinger et al., 2004). This technique focusing on events a system must respond to and looking at how a system responds. An event is an occurrence at specific time and place, can be described and should be remembered by the system (Larman, 2004; Reed, 2001; Satzinger et al., 2004). Building the use-case and class diagrams is a very important task since it represents a transition between the requirements and design phases. However, building such diagrams is a time consuming process and needs a complete understanding of the requirements. In this paper, we introduce an approach to derive the use-case and class diagrams from an event table. In addition, a new CASE tool for automating the new approach will be discussed. The new approach with the new CASE tool will facilitate and speed the generation process of these diagrams. Taking into account that this approach will completely depend on the availability of a comprehensive event table which to be built from the available requirements. MATERIALS AND METHODS Event table: Since 1980s, the event analysis technique (McMenamin and Palmer, 1984; Yourdon, 1988; Page- Jones, 1999) has been the preferred one of event analysis during the requirements engineering. The results of event analysis are documented in an event table. In the structured approach, event analysis recognizes a basic set of processes. While in the object- oriented approach, each event discourses an essential use-case (Stumpf and Teague, 2005). Furthermore, an event table can be created from the external events to support the use-case diagrams (Purhonen, 2002). In addition, the event table has been used by Gargantini