Enhanced UML Methodology with New Hybrid Diagrams: An ATM Application

Object oriented proved to be the most important software engineering tools. The main reason behind the importance is that, Object Oriented covers the most powerful programming languages such as Java and C++. UML is a modeling language which is a part of object oriented and it was created to provide the software development industry with analysis and design techniques based on some diagrams. The most common UML diagrams in use are Class and Activity diagram. To implement any system using object oriented UML, the programmer needs at least two or three diagrams beside the Use Case diagram in order to understand a full picture of the system. There is no diagram which can show the full picture of the system. In this research, new methodology called “Touch and Go†has been generated by the researchers to implement the system. In this methodology, analysis and design are merged in one stage called Touch. Implementation and testing stage are merged in one stage called Go. The Class and Activity diagram are merged to introduce new integrated diagram called Enhanced Class Activity (ECA) diagram and the normal Activity diagram will be modified and improved as Activity Remarked Class (ARC) diagram. Analytical analysis of the new methodology is implemented in ATM machine system which can be later implemented using Java language or any other Object Oriented language. A powerful system like ATM is chosen to apply the new technique and it has been shown clearly how the methodology is working perfectly with such system. This study helps to reduce the number of diagrams that are being used to implement the system, reducing total time of implementation and making the coding stage easier by using only few numbers of diagrams

Sistem Informasi Anggaran Pendapatan dan Belanja Desa Berorientasi Objek

This Object-Oriented Urban Revenue Information System is developed by analyzing the needs of the Village Office of Belitang Satu Kabupaten Sekadau West Kalimantan. The preparation of Revenue and Expenditure Budget still use Microsoft Excel application. To process the data, especially financial data required the use of certain calculation formulas. And the capacity of data in Microsoft Excel is also limited to a certain amount. With the help of Unified Modeling Language (UML), the information system design of Revenue and Expenditure Budget is made. The UML types used are Use Case Diagrams, Activity Diagrams, Sequence Diagrams and Deployment Diagrams. The design of this application can be a reference in making the information system in the future so that it can improve the effectiveness and efficiency of the performance of the apparatus

Transformation of UML models for service-oriented software architectures

Comunicação apresentada ao IEEE International Conference and Workshop on the Engineering of Computer Based Systems (ECBS 2005), 12, Washington, 2005.The main aim of this paper is to present how to transform user requirements models into a software architecture for mobile applications. The technique (called "4SRS") is essentially based on the mapping of UML use case diagrams into UML object diagrams. UML sequence, activity, and state diagrams and other artifacts can also be considered within the transformation decisions. The applicability of this technique is illustrated by presenting some results from an e-government mobile application. The development of mobile applications typically follow a service-oriented approach. A service is a software entity running on one or more machines and providing a particular type of function to a priori unknown clients. These services must communicate with each other, whose combination makes up a service-oriented architecture. The communication can involve either simple data passing or it could involve two or more services coordinating some activity. Some means of connecting services to each other is needed, so workflow is a critical part of making services effective. When those services react to changes on user context, application are context-aware. For mobile applications, the definition of the underlying service-oriented software architecture must consider the services themselves as user requirements, as well as the mobile operators entry-points and the final clients interfaces, and use them to characterize the platform.USE-ME.GOV - IST-2002-002294 ; Fundação para a Ciência e a Tecnologia - METHODES (POSI/CHS/37334/2001), STACOS (POSI/CHS/48875/2002)

Object-oriented modelling with unified modelling language 2.0 for simple software application based on agile methodology

Unified modelling language (UML) 2.0 introduced in 2002 has been developing and influencing object-oriented software engineering and has become a standard and reference for information system analysis and design modelling. There are many concepts and theories to model the information system or software application with UML 2.0, which can make ambiguities and inconsistencies for a novice to learn to how to model the system with UML especially with UML 2.0. This article will discuss how to model the simple software application by using some of the diagrams of UML 2.0 and not by using the whole diagrams as suggested by agile methodology. Agile methodology is considered as convenient for novices because it can deliver the information technology environment to the end-user quickly and adaptively with minimal documentation. It also has the ability to deliver best performance software application according to the customer's needs. Agile methodology will make simple model with simple documentation, simple team and simple tools.Comment: 15 pages, 30 figure

Literate modelling: capturing business knowledge with the UML

At British Airways, we have found during several large OO projects documented using the UML that non-technical end-users, managers and business domain experts find it difficult to understand UML visual models. This leads to problems in requirement capture and review. To solve this problem, we have developed the technique of Literate Modelling. Literate Models are UML diagrams that are embedded in texts explaining the models. In that way end-users, managers and domain experts gain useful understanding of the models, whilst object-oriented analysts see exactly and precisely how the models define business requirements and imperatives. We discuss some early experiences with Literate Modelling at British Airways where it was used extensively in their Enterprise Object Modelling initiative.We explain why Literate Modelling is viewed as one of the critical success factors for this significant project. Finally, we propose that Literate Modelling may be a valuable extension to many other object-oriented and non object-oriented visual modelling languages

Three Dimensional Software Modelling

Traditionally, diagrams used in software systems modelling have been two dimensional (2D). This is probably because graphical notations, such as those used in object-oriented and structured systems modelling, draw upon the topological graph metaphor, which, at its basic form, receives little benefit from three dimensional (3D) rendering. This paper presents a series of 3D graphical notations demonstrating effective use of the third dimension in modelling. This is done by e.g., connecting several graphs together, or in using the Z co-ordinate to show special kinds of edges. Each notation combines several familiar 2D diagrams, which can be reproduced from 2D projections of the 3D model. 3D models are useful even in the absence of a powerful graphical workstation: even 2D stereoscopic projections can expose more information than a plain planar diagram