Class Diagram

Agent technology is a software paradigm that permits to implement large and complex distributed applications [1]. In order to assist analyzing, conception and development or implementation phases of multi-agent systems, we've tried to present a practical application of a generic and scalable method of a MAS with a component-oriented architecture and agentbased approach that allows MDA to generate source code from a given model. We've designed on AUML the class diagrams as a class meta-model of different agents of a MAS. Then we generated the source code of the models developed using an open source tool called AndroMDA. This agent-based and evolutive approach enhances the modularity and genericity developments and promotes their reusability in future developments. This property distinguishes our design methodology of existing methodologies in that it is constrained by any particular agentbased model while providing a library of generic models [2].

L'ingénierie des lignes de produits est une approche récente du génie logiciel. Elle regroupe les activités de développement d'un ensemble de logiciels appartenant à un domaine particulier. L'objectif principal de cette approche est d'augmenter la productivité et diminuer le temps de réalisation. L'une des difficultés est de représenter dans un modèle la variabilité, c'est à dire les parties communes ou distinctes dans différents produits. Cet article propose une approche pour modéliser les lignes de produits en UML, en intégrant à la fois les aspects fonctionnels, statiques et dynamiques. Dans un premier temps, nous proposons une extension des cas d'utilisations, des diagrammes de classes, et des diagrammes de séquences pour tenir compte de la notion de variabilité. La cohérence des modèles est ensuite assurée par des contraintes écrites en OCL (Object Constraint Language).

The Unified Modeling Language (UML) is the effective standard language of an object-oriented based system analysis and design. The using of objectoriented approach based on UML specification can offer an understandable model, which can reduce the system's complexity. The use-case diagram, class diagram and sequence diagram are important models of the system development during early stages. The object mapping approach between UML class diagram in the analysis phase and source code in the implementation phase is a significant process in the software development life cycle. In order to ensure the consistency of system requirements from analysis to implementation. This paper presents the student registration system by using object mapping based on UML. The UML specification and the generation of Java source code influenced by specific features of class in object-oriented such as inheritance and the association between the classes.

Most of legacy systems use nowadays were modeled and documented using structured approach. Expansion of these systems in terms of functionality and maintainability requires shift towards object-oriented documentation and design, which has been widely accepted by the industry. In this paper, we present a survey of the existing Data Flow Diagram (DFD) to Unified Modeling language (UML) transformation techniques. We analyze transformation techniques using a set of parameters, identified in the survey. Based on identified parameters, we present an analysis matrix, which describes the strengths and weaknesses of transformation techniques. It is observed that most of the transformation approaches are rule based, which are incomplete and defined at abstract level that does not cover in depth transformation and automation issues. Transformation approaches are data centric, which focuses on data-store for class diagram generation. Very few of the transformation techniques have been applied o...

System testing is concerned with testing an entire system based on its specifications. In the context of object-oriented, UML development, this means that system test requirements are derived from UML analysis artifacts such as use cases, their corresponding sequence and collaboration diagrams, class diagrams, and possibly the use of the Object Constraint Language across all these artifacts. Our goal is to support the derivation of test requirements, which will be transformed into test cases, test oracles, and test drivers once we have detailed design information. Another important issue we address is the one of testability. Testability requirements (or rules) need to be imposed on UML artifacts so as to be able to support system testing efficiently. Those testability requirements result from a trade-off between analysis and design overhead and improved testability. The potential for automation is also an overriding concern all across our work as the ultimate goal is to fully support testing activities with high-capability tools.

Model-based selective regression testing promises reduction in cost and labour by selecting a subset of the test suite corresponding to the modifications after system evolution. However, identification of modifications in the systems and selection of corresponding test cases is challenging due to interdependencies among models. State-based testing is an important approach to test the system behaviour. Unfortunately the existing state-based regression testing approaches do not care for dependencies of the state machine with other system models. This paper presents the tool support and evaluation of our statebased selective regression testing methodology for evolving state-based systems. START is an Eclipsebased tool for state-based regression testing compliant with UML 2.1 semantics. START deals with dependencies of state machines with class diagrams to cater for the change propagation. We applied the START on a case study and our results show significant reduction in the test cases ...

Software reusability has considerable effect on software quality. Software quality increases as reuse of software components increases. But software quality cannot be improved unless it can be measured. In this paper we have derived a new approach to measure the software reusability of OO class diagram, an attribute of software quality. We have also empirically studied the approach in OO programming language C++.

Recently, it has been pointed out that the majority of the requirements engineering methods do not take into account non-functional requirements (NFRs) [10][11]. Consequently, we have been experiencing serious problems during the development of software systems, such as cost and schedule overruns. In order to diminish this negligence of NFRs and its consequences, this work proposes a strategy (OONFR) that brings NFRs to object-oriented modeling. The OONFR strategy uses as input a Language Extended Lexicon of the Universe of Discourse (LEL of UofD) and outputs a class diagram with indications of what classes, attributes, operations and relationships are responsible for satisficing 1 NFRs. This strategy consists of the following activities: build the Language Extended Lexicon of Universe of Discourse-NFR (LEL of UofD-NFR), build the scenarios and build the class diagram.

In recent years, the significance of automated generation of object-oriented code from UML diagrams has increased due to its benefits, such as, cost reduction and accuracy. Consistency Checking between UML diagrams, and ensuring accuracy, maintainability, efficiency, and completeness of the generated code are the main concerns in this area. This paper extends our work on a tool called UJECTOR for automatic generation of executable Java code from UML diagrams. A set of three UML diagrams, ie, class diagram, sequence ...

Practitioners spend significant amounts of time creating high-level design from requirements. Though there exist methodologies to describe and manage requirements and design artifacts, there is not yet an automated way to faithfully translate a requirement into a high-level design. While it is extremely difficult to generate design elements from free-form natural language due to its inherent ambiguity, it is possible to significantly improve the accuracy of the design from relatively structured and constrained natural language. In this paper we propose a technique to generate high-level class diagrams from a set of requirements, using a set of requirement-specific heuristics. In this approach, we leverage work we had previously done to first process a requirement statement to classify it into a requirement type, and then break it into various constituents. Depending on the requirement type and its constituents, our heuristics then discover a functional design comprising of coarse-grained modules, their relationships and responsibilities. We express the design as a UML class diagram in IBM rational software architect (RSA) format. Our preliminary investigation shows that the resulting class diagram is rich, and can be used by practitioners as a basis for further design.

The department of Social Services (DSS) is one of the leading Government Department of People’s Republic of Bangladesh under the ministry of social welfare. The mandate of the Department of social services is to provide services to the vulnerable groups of Society, the poorest of the poor, the marginalized and the disadvantaged groups.
DSS is working to ensure Social protection and Social Safety nets for the poor vulnerable people of the country as well as social-economic development, community empowerment and other development activates for the vulnerable aged persons, the person with disabilities (PWDs), orphans, children at risk, destitute, poor and hopeless persons.
DSS is responsible for a range of social protection allowance programs that provide support to vulnerable members of the population through office and staff at the district, Upazila and Union levels. DSS is already developed and implemented the Management Information System for its major 3 allowance Program:
 Old age allowance Program
 Disability allowance Program
 Widow’s allowance Program
The system is an integrated and web based management information system solution which helps DSS and District/ Upazila level office to manage different allowance related works and activities. This MIS Solution provides an easy and hassle free solution for everyday task to its employees and stakeholders or users. The MIS system create a technology enabled environment; where individuals, system & communities will able to interact with each other for better services and other administration process.

In recent years, the significance of automated generation of object-oriented code from UML diagrams has increased due to its benefits, such as, cost reduction and accuracy. Consistency Checking between UML diagrams, and ensuring accuracy, maintainability, efficiency, and completeness of the generated code are the main concerns in this area. This paper extends our work on a tool called UJECTOR for automatic generation of executable Java code from UML diagrams. A set of three UML diagrams, ie, class diagram, sequence ...

Enterprise information systems can be developed following a modeldriven paradigm. This way, models that represent the organisational work practice are used to produce models that represent the information system. Current software development methods are starting to provide guidelines for the construction of conceptual models, taking as input requirements models. This paper proposes the integration of two methods: Communication Analysis (a communication-oriented requirements engineering method [1]) and the OO-Method (a model-driven object-oriented software development method ). For this purpose, a systematic technique for deriving class diagrams from business process models is proposed. The business process specifications (which include message structures) are processed in order to obtain class diagram views, which are integrated to create the class diagram incrementally. Then, using the OLIVANOVA framework, software source code can be generated automatically. The paper also discusses the advantages and current limitations of the technique. Results show that, although there is room for improvement, the technique is feasible and it does facilitate the creation of the class diagram.

The automation of class generation from natural language requirements is highly challenging. This paper proposes a method and a tool to facilitate requirements analysis process and class diagram extraction from textual requirements supporting natural language processing NLP and Domain Ontology techniques. Requirements engineers analyze requirements manually to come out with analysis artifacts such as class diagram. The time spent on the analysis and the low quality of human analysis proved the need of automated support. A "Requirements Analysis and Class Diagram Extraction (RACE)" is a desktop instrument to assist requirements analysts and SE students in analyzing textual requirements, finding core concepts and its relationships, and step by step extraction of the class diagram. The evaluation of RACE system is in the process and will be conducted using two forms of evaluation, experimental and expert evaluation.

In the present Scenario, the competitive environment in banking sector, paradigm is changing rapidly. Various new things can be seen in banking sector, because it is adopting new concepts and technology to improve their business & to win the satisfaction of their customers. The present paper discusses the role of Unified Modeling Language (UML) in the Object Oriented Database Management System (OODBMS) in banking sector. The Object Oriented Database technology is considered as the fifth generation database technology. OODBMS can be considered as a combination of two technologies, Database Management System and Object Oriented System. A case study of Online Banking System has been taken to explain how various accounts and transactions can be classified. Object oriented Data Modeling technique has been used to store the data and it is represented with the help of UML Use-Case diagram, Class Diagram, Sequence diagram and State diagram.

Graph Theory, which studies the properties of graphs, has been widely accepted as a core subject in the knowledge of computer science. Object-Oriented (OO) software engineering, which deals with the analysis, design and implementation of systems employing classes as modules. Since the main mode of representation, namely the class diagram, is essentially a directed graph. The study of graph properties can be valuable in many ways for understanding the characteristics of the underlying software systems. The usefulness of graph theory on OO systems to develop metric suite is presented in this paper. Metrics developed in previous research, while contributing to the field's understanding of s/w development process, have generally been subject to serious criticism, including the lack of a theoretical base. It provides steps to perform measurements of key structural attributes including coupling and cohesion .In this paper Six design metrics are developed, & then analytically evaluated. The need for such metric is particularly acute when an organization is adopting a new technology for which established practices have yet to be developed. This research addresses S/W product attribute needs through the development & implementation of a new suite of metric for OO design.

UML has been used widely as a design and analysis tool for objectoriented software projects. Despite of having a good number of diagram categories, UML is still lacking of a dedicated set of diagrams for representing design patterns. While numerous works have been published on attempts to describe design patterns in terms of UML features, there is hardly any work has been done on attempts to un-clutter class diagrams at the initial development stage so that the design patterns in used can be seen clearly. With the aim to tidy-up huge networks of interconnecting class diagrams, this paper proposes a new higher level set of diagrams and layout schemes to better highlight the design patterns used in a software architecture. This proposal can go further as a proposal for a new set of diagram in UML standard.

We compare EER and OO data models from the point of view of design quality. Quality is measured in terms of (a) correctness of the conceptual schemas being designed, (b) time to complete the design task, and (c) designers' preferences of the models. Result of an experimental comparison of the two models reveal that the EER model surpasses the OO model for designing unary and ternary relationships, it takes less time to design EER schemas, and the EER model is preferred by designers. We conclude that even if the objective is to implement an OO database schema, the recommended procedure is to: (1) create an EER conceptual scheme, (2) map it to an OO schema, and augment the target schema with behavioral constructs that are unique to the OO approach.

LATAR BELAKANG

Salah satu tujuan dari  perusahaan Pabrik Roti  adalah  mencari  laba  atau  profit yang semaksimal mungkin, untuk dapat mencapai tujuan tersebut perusahaan harus dapat  mengikuti  perkembangan  dunia  perindustrian  baik  dalam  bidang  teknologi informasi maupun dalam bidang manajemen. Dalam hal ini, Pabrik Roti membutuhkan sebuah sistem enterprise resource planning (ERP) untuk mengakomodir semua rangkaian kegiatan perusahaan.
Seiring dengan perkembangan ilmu dan  teknologi, pemanfaatan ERP  di segala bidang sudah merupakan  suatu keharusan. Enterprise Resource Planning (ERP) adalah Sistem Pendukung  Keputusan untuk menggambarkan semua rangkaian-rangkaian kegiatan dari mulai penyiapan SDM, purchasing, warehousing, finance, serta pembuatan laporan keuangan untuk para manajemen dan para aktor dalam sebuah organisasi atau perusahaan sehingga dengan penerapan sistem ERP dapat memberikan alternatif solusi bagi pembuat keputusan agar lebih mudah dalam pencatatan laporan pengadaan barang, laporan produksi, laporan keuangan hingga laporan penjualan yang transparan dan akuntabel
Permasalahan yang dihadapi oleh perusahaan pabrik roti ini adalah  perusahaan  sulit menentukan laporan laporan proses transaksi serta sulitnya mengklasifikasikan jobdesk sesuai dengan tugas masing-masing para user sebuah organisasi. Selain  itu  manajemen produksi  yang  dilakukan  secara  manual  oleh  pemilik  perusahaan  yang  kemudian mengakibatkan  tidak  terkontrolnya  biaya  produksi  dan  kesalahan  perencanaan analisis pasar. Oleh karena itu perlu dibuat sebuah Sistem Enterprise resource planning (ERP) yang membantu perusahaan untuk menentukan SDM dan proses produksi roti yang tersistem secara akurat
Untuk menganalisa perencanaan produksi,pelayanan transaksi konsumen perusahaan dapat menggunakan metode Unified Modeling Language (UML) dalam sebuah ERP. Apabila metode  UML  ini  diterapkan  dalam  bagian  proses perencanaan produksi sampai proses transaksi maka pihak perusahaan akan lebih terbantu dalam penentuan produksi, karena metode ini dapat memberikan  output  terbaik  sehingga  diharapkan  resiko  kesalahan  yang disebabkan oleh kesalahan perencanaan dapat ditekan seminimal mungkin. Dengan latar belakang tersebut maka yang menjadi pembahasan utama dari tugas ini adalah bagaimana membangun Sistem Pendukung Keputusan terhadap  Penentuan  Produksi  Roti dengan  metode UML.

Historians occasionally use timelines, but many seem to regard such signs merely as ways of visually summarizing results that are presumably better expressed in prose. Challenging this language-centered view, I suggest that timelines might assist the generation of novel historical insights. To show this, I begin by looking at studies confirming the cognitive benefits of diagrams like timelines. I then try to survey the remarkable diversity of timelines by analyzing actual examples. Finally, having conveyed this (mostly untapped) potential, I argue that neglecting timelines might mean neglecting significant aspects of reality that are revealed only by those signs. My overall message is that, once we accept that relations are as important for the mind as what they relate, we have to pay closer attention to any semiotic device that enables or facilitates the discernment of new relations.

In the analysis phase of the information system development, the user requirements are studied, and analysis models are created. In most UML-based methodologies, the analysis activities include mainly modeling the problem domain using a class diagram, and modeling the user/functional requirements using use cases. Different development methodologies prescribe different orders of carrying out these activities, but there is no commonly agreed order for performing them. In order to find out whether the order of analysis activities makes any difference, and which order leads to better results, a comparative controlled experiment was carried out in a laboratory environment. The subjects were asked to create two analysis models of a given system while working in two opposite orders. The main results of the experiment are that the class diagrams are of better quality when created as the first modeling task, and that analysts prefer starting the analysis by creating class diagrams first.

Entity Relationship schemas include weak entity types, whose entities are identified by their inter-relationships to other entities. During the translation of the EER schema into a logical database schema, the weak entity types are either translated into logical units of the database (a relation or a class), or are embedded as attributes of other logical units. Formal studies of EER schemas either ignore the presence of weak entity types, or simplify their dependency structure. The presence of weak entity types in an EER schema may be problematic: A weak entity may not be easy to identify because it may be related to other weak entities in various ways, thus causing problems in schema comprehension, as well as in mapping it to a logical database schema.
We claim that the presence of weak entity types in an EER schema belongs to an intermediate design stage, but the final EER schema must not include such entity types. We introduce an algorithm for resolving the status of weak entity types, following user directions. If the directions are legal, the algorithm yields an EER schema without weak entity types. The advantage of our approach is twofold: First, the translation of an EER schema into a logical database schema can be fully automated. This is essential for upgrading the EER model to support full database management. Second, it enables a fully formal study of the EER model.

In recent years, the significance of automated generation of object-oriented code from UML diagrams has increased due to its benefits, such as, cost reduction and accuracy. Consistency Checking between UML diagrams, and ensuring accuracy, maintainability, efficiency, and completeness of the generated code are the main concerns in this area. This paper extends our work on a tool called UJECTOR for automatic generation of executable Java code from UML diagrams. A set of three UML diagrams, ie, class diagram, sequence ...

Perkembangan teknologi komputer dan kebutuhan yang muncul pada instansi atau perusahaan, maupun perguruan tinggi kini semakin meningkat demi memperoleh dan berbaginya informasi. Terdapat banyak fasilitas teknologi komputer yang memberikan kemudahan, secara langsung berdampak lebih baik kepada kegiatan instansi atau perusahaan. Lembaga Penelitian dan Pengabdian Masyarakat UIN Sultan Syarif Kasim Riau atau yang disingkat LPPM UIN Suska Riau merupakan lembaga yang memfasilitasi dosen dan mahasiswa di UIN Suska Riau dalam melakukan penelitian serta pengabdian kepada masyarakat. Dalam melakukan tugas penelitian dan pengabdian kepada masyarakat, dosen pasti mengeluarkan dana untuk melakukan tugas perjalanan dinas tersebut. Pegawai keuangan di LPPM sebelumnya hanya menggunakan aplikasi Microsoft Excel untuk memantau aliran dana di LPPM untuk tugas perjalanan dinas ini seperti, pembuatan kuitansi dan realisasi anggaran.  Pegawai keuangan sering melakukan kesalahan seperti ketidakcocokan data pada kuitansi yang dibuat dengan data yang sebenarnya. Dan juga pegawai keuangan membutuhkan waktu untuk melihat realisasi anggaran pada bulan tertentu. Karena ketidakcocokan data tersebut, realisasi anggarannya tentu juga tidak sesuai dengan apa yang terjadi di lapangan dan juga membutuhkan waktu untuk melihat realisasi anggarannya. Berdasarkan permasalahan yang dialami, solusi yang bisa diterapkan adalah membuat rancang bangun sistem informasi. Rancang bangun sistem informasi tersebut mencakup pengelolaan realisasi anggaran berbasis komputer. Tujuan dari pembuatan sistem informasi ini, adalah untuk membantu dan memudahkan dalam memenuhi proses monitoring anggaran untuk pegawai keuangan.

The Unified Modeling Language (UML) is the effective standard language of an object-oriented based system analysis and design. The using of object-oriented approach based on UML specification can offer an understandable model, which can reduce the system's complexity. The use-case diagram, class diagram and sequence diagram are important models of the system development during early stages. The object mapping approach between UML class diagram in the analysis phase and source code in the implementation phase is a significant process in the software development life cycle. In order to ensure the consistency of system requirements from analysis to implementation. This paper presents the student registration system by using object mapping based on UML. The UML specification and the generation of Java source code influenced by specific features of class in object-oriented such as inheritance and the association between the classes.

Dynamic object roles constitute a promising conceptual modeling notion, which can express in a straightforward manner some real situations when an entity during its life can acquire and lose various roles without changing its identity. The paper focuses on the problem of introducing dynamic object roles into the UML (Unified Modeling Language) class diagram, which is used to present object-

We describe an algorithmic method for transforming a Binary-Relationship (BR) conceptual schema to an Object-Ooriented (OO) database schema. The BR schema is a semantically rich diagram that represents the reality being modeled in terms of objects, relationships and constraints. It is easy to understand and serves as a communication tool between users and designers. Therefore it can be created in the early stages of system development, and later on be transformed into a specific OO database schema.
The transformation method employs a multi-stage algorithm, which first identifies the essential objects in the BR schema, together with their relationships and constraints. These are then mapped to object classes, attributes, and constraints, maintaining the semantics and all types of constraints present in the conceptual schema.

Information processing to date between various participants and phases of construction is still often carried out verbally and through written communication on paper. The information exchange and processing through paper-based communication consumes substantial time. Due to increasing complexity of construction projects and the project management team setup, information processing and communication using information technology had become critical and essential for efficient project management and control. The inherent complexity of information flows in construction project has always posed the challenge for implementing standard information systems to cater to all the needs. It appears practically not feasible to develop and implement such systems for construction industry. In the present study, critical information flow common to all construction projects are evaluated and selected through a case study. An object-oriented information system model is developed for these selected processes using unified modeling language. The benefit of computerized information system is discussed and the model development by unified modeling language is compared with traditional structured modeling.

Taxonomies play a central role in conceptual domain modeling having a direct impact in areas such as knowledge representation, ontology engineering, software engineering, as well as in knowledge organization in information sciences. Despite their key role, there is in the literature little guidance on how to build high-quality taxonomies, with notable exceptions such as the OntoClean methodology, and the ontology-driven conceptual modeling language OntoUML. These techniques take into account the ontological meta-properties of types to establish well-founded rules for forming taxonomic structures. In this paper, we show how to leverage on the formal rules underlying these techniques to build taxonomies which are correct by construction. We define a set of correctness-preserving operations to systematically introduce types and subtyping relations into taxonomic structures. To validate our proposal, we formalize these operations as a graph grammar. Moreover, to demonstrate our claim of correctness by construction , we use automatic verification techniques over the grammar language to show that: (i) all taxonomies produced by the grammar rules are correct; and (ii) the rules can generate all correct taxonomies.

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.

Database system is important to ensure the data can be stored, updated and retrieved for future use. Data modelling using the Entity Relationship Model has been introduced more than thirty years. However, designing a good database system is still an attractive issue particularly in system analysis and design because of very hard to do consistency checking between system design and database design. In this paper, a proposal for designing a relational database system based on Object Oriented Analysis and Design is presented. The database system is created by the schema table that extract from class diagram. The rules applying in this paper is following the object oriented concept. It is based on the relationships among the classes, multiplicity, attributes name, class name, data type and the behaviours of the classes. Beside that the user is required to insert record to accomplish a good designing the schema tables to avoid redundancy data. Finally, an automatic editor called CDGeST is proposed in order to automate the process.

This paper addresses not only the question of testability measurement of OO designs but also focuses on its practicability. While detecting testability weaknesses (called testability anti-patterns) of an OO design is a crucial task, one cannot expect from a non-specialist to make the right improvements, without guidance or automation. To overcome this limitation, this paper investigates solutions integrated to the 00 process. We focus on the design patterns as coherent subsets in the architecture, and we explain how their use can provide a way for limiting the severity of testability weaknesses, and of confining their effects to the classes involved in the pattern. Indeed, design patterns appear both as a usual refinement instrument, and a cause of complex interactions into a class diagram -and more specifically of testability anti-patterns. To reach our objective of integrating the testability improvement to the design process, we propose first a testability grid to make the relation between each pattern and the severity of the testability anti-patterns, and we present our solution, based on a definition of patterns at metalevel, to automate the instantiation of patterns constrained by testability criteria.

The demand for increased software quality has resulted in quality being more of differentiator between products than it ever has been before. For this reason, software developers need objective and valid measures for use in the evaluation and improvement of product quality from the initial stages of development. Class diagrams are a key artifact in the development of object-oriented (OO) software because they lay the foundation for all later design and implementation work. It follows that emphasizing class diagram quality may significantly contribute to higher quality OO software systems. The primary aim of this work, therefore, is to present a survey, as complete as possible, of the existing relevant works regarding class diagram metrics. Thus, from works previously published, researchers and practitioners alike may gain broad and ready access to insights for measuring these quality characteristics. Another aim of this work is to help reveal areas of research either lacking completion or yet to undertaken. A SURVEY OF METRICS FOR UML CLASS DIAGRAMS 60 J OURNAL OF OBJECT TECHNOLOGY V OL. 4, NO. 9

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.

In recent years, the significance of automated generation of object-oriented code from UML diagrams has increased due to its benefits, such as, cost reduction and accuracy. Consistency Checking between UML diagrams, and ensuring accuracy, maintainability, efficiency, and completeness of the generated code are the main concerns in this area. This paper extends our work on a tool called UJECTOR for automatic generation of executable Java code from UML diagrams. A set of three UML diagrams, i.e., class diagram, sequence diagrams and activity diagrams are input to the tool to generate completely executable Java code automatically. The object-oriented code structure is built from class diagram, methods' flow of control is created through sequence diagrams, and object manipulations are included by activity diagrams from the implemented approach in UJECTOR. The extension includes a more detailed overview of the code generation tool regarding its architecture and code generation process. Two detailed case studies are presented to validate the generated code from the code generation tool. We also compare UJECTOR with the existing research-based, commercial and open-source tools. The evaluation results show that the generated code from UJECTOR is fully functional and understandable.