scholarly journals SISTEM INFORMASI MANAJEMEN BERBASIS UML (STUDI KASUS PEMELIHARAAN TOILET PADA KAMPUS FAKULTAS TEKNIK UNIVERSITAS LAMBUNG MANGKURAT)

2016 ◽  
Vol 1 (2) ◽  
pp. 59-59
Author(s):  
Yuslena Sari ◽  
Irfan Prasetia
Keyword(s):  
Unified Modeling Language ◽  
Computer Software ◽  
Object Oriented ◽  
Software Systems ◽  
Modeling Language ◽  
Unified Modeling ◽  
Analysis And Design ◽  
Systems Requirements ◽  
Computer Software System ◽  
Object Oriented Systems

This paper presents concept of a database system on a computer software systems. Requirements in analysis and design are a serious problem in developing a manual system into a computer software system that is fully automated. To link the two systems (manual and automatic), a modeling language Unified Modeling Language (UML) is now accepted as the de facto standard for the design and specification of object-oriented systems. In this study, ULM modeling language used to design a management information system (MIS) of Toilet Maintenance on the Faculty of Engineering, Lambung Mangkurat University using Access 2013. From this system, dean as admin of the system, can immediately know the damage or the need of maintenance in real time every day. Such information would greatly assist the management on making decision related to monitoring, maintenance and repair of toilet in the Faculty of Engineering, Lambung Mangkurat University. The final results is to keep the cleanliness and reliability of toilet in the Faculty of Engineering, Lambung Mangkurat University.

Reengineering Structured Legacy System Documentation to UML Object-Oriented Artifacts

2012 ◽  
pp. 30-53
Author(s):  
Terrence P. Fries
Keyword(s):  
Unified Modeling Language ◽  
Object Oriented ◽  
Software Systems ◽  
Legacy Systems ◽  
Unified Modeling ◽  
Analysis And Design ◽  
Structured Analysis ◽  
Structured System ◽  
Object Oriented Systems ◽  
Computer Aided Software Engineering

The need for reengineering of software systems has dramatically increased as legacy systems are migrated to new platforms and rewritten in modern object-oriented languages. Although the de facto standard for describing object-oriented systems is the Unified Modeling Language (UML), many legacy systems have been documented using non-object-oriented structured analysis and design methods. Problems arise in the migration because non-object-oriented documentation is inherently not conducive to the development of object-oriented systems. This chapter presents a set of rules to automate the conversion of systems which were originally modeled using structured techniques to UML. The newly created UML documentation can then be used in developing an object-oriented equivalent system. The UML model may also be used by computer aided software engineering tools to implement a new system. The reengineering rules are tested on an example structured system to demonstrate their viability.

Reengineering Structured Legacy System Documentation to UML Object-Oriented Artifacts

2014 ◽  
pp. 749-771
Author(s):  
Terrence P. Fries
Keyword(s):  
Unified Modeling Language ◽  
Object Oriented ◽  
Software Systems ◽  
Legacy Systems ◽  
Unified Modeling ◽  
Analysis And Design ◽  
Structured Analysis ◽  
Structured System ◽  
Object Oriented Systems ◽  
Computer Aided Software Engineering

The need for reengineering of software systems has dramatically increased as legacy systems are migrated to new platforms and rewritten in modern object-oriented languages. Although the de facto standard for describing object-oriented systems is the Unified Modeling Language (UML), many legacy systems have been documented using non-object-oriented structured analysis and design methods. Problems arise in the migration because non-object-oriented documentation is inherently not conducive to the development of object-oriented systems. This chapter presents a set of rules to automate the conversion of systems which were originally modeled using structured techniques to UML. The newly created UML documentation can then be used in developing an object-oriented equivalent system. The UML model may also be used by computer aided software engineering tools to implement a new system. The reengineering rules are tested on an example structured system to demonstrate their viability.

scholarly journals Sistem Informasi Pembelian, Persediaan, dan Penjualan untuk Apotek

2013 ◽  
Vol 4 (1) ◽  
pp. 430
Author(s):  
Lusiana Citra Dewi
Keyword(s):  
Information System ◽  
Unified Modeling Language ◽  
Object Oriented ◽  
Field Studies ◽  
Modeling Language ◽  
Information System Design ◽  
Or Management ◽  
Unified Modeling ◽  
Analysis And Design ◽  
Operational Activities

This study aims to create a system that can simplify common operational activities of pharmacy such as purchasing, inventory, and sales. The system is expected to improve manual processes of purchasing, inventory, and sales into a computerized ones. In addition, this system also provides convenience, accuracy, and speed for owner or management to access reports of purchase, inventory, and sales in real-time. The research methods used are literature studies, field studies, and the methods of analysis and design of object-oriented information system design language UML (Unified Modeling Language). Tthe result of this research is an information system of purchasing, inventory, and sales of medicines that may help pharmacies to get information quickly and accurately, and to help pharmacy operations to run more effectively and efficiently.

Unified Modeling Language

2005 ◽  
pp. 2921-2928 ◽  
Author(s):  
Peter Fettke
Keyword(s):  
Systems Engineering ◽  
Subject Matter ◽  
Unified Modeling Language ◽  
Object Oriented ◽  
General Purpose ◽  
Modeling Language ◽  
Unified Modeling ◽  
Object Oriented Systems

Mature engineering disciplines are generally characterized by accepted methodical standards for describing all relevant artifacts of their subject matter. Such standards not only enable practitioners to collaborate, but they also contribute to the development of the whole discipline. In 1994, Grady Booch, Jim Rumbaugh, and Ivar Jacobson joined together to unify the plethora of existing object-oriented systems engineering approaches at semantic and notation level (Booch, 2002; Fowler, 2004; Rumbaugh, Jacobson, & Booch, 1998). Their effort led to the Unified Modeling Language (UML), a well-known, general-purpose, tool-supported, process-independent, and industry-standardized modeling language for visualizing, describing, specifying, and documenting systems artifacts. Table 1 depicts the origin and descent of UML.

Modeling an Object-Oriented Accounting System with Computer-Aided Software Engineering

2008 ◽  
Vol 22 (2) ◽  
pp. 123-139 ◽  
Author(s):  
Alan S. Levitan ◽  
Jian Guan ◽  
Andrew T. Cobb
Keyword(s):  
Software Engineering ◽  
Unified Modeling Language ◽  
Object Oriented ◽  
Modeling Language ◽  
Accounting System ◽  
Sequence Diagrams ◽  
Unified Modeling ◽  
Computer Aided ◽  
Object Oriented Systems ◽  
Computer Aided Software Engineering

ABSTRACT: The purpose of this case is, first, to provide students with an experience in systems modeling, using facts gathered through interviews with employees who may not be skilled in presenting their responsibilities in a systematic, logical, sequential manner. Second, students will gain actual hands-on experience learning and using a leading modeling language, the Unified Modeling Language (UML), through a popular Computer-Aided Software Engineering (C.A.S.E.) tool. Finally, the students will be using those interview facts to model an object-oriented system for processing cash receipts. In that effort, they will learn and apply the unique documentation techniques used in analyzing and designing object-oriented systems with design features such as use cases, class diagrams with inheritance, and sequence diagrams.

Analysis and Design Based on the Educational Management System Adopting the Object-Oriented Modeling Technique

2013 ◽  
Vol 411-414 ◽  
pp. 444-447
Author(s):  
Yu Yang Lu ◽  
Zhi Hao Yin ◽  
Yong Yang ◽  
Ben Cheng Yu
Keyword(s):  
Design Process ◽  
Management System ◽  
Unified Modeling Language ◽  
Object Oriented ◽  
Modeling Language ◽  
Administrative System ◽  
Educational Management ◽  
Modeling Tool ◽  
Unified Modeling ◽  
Analysis And Design

This text has introduced a kind of design process on the basis of teaching administrative system facing target's modeling. During the design, we have used unified modeling language UML and modeling tool Rational Rose2002 Enterprise Edition analysis to conduct overall analysis and design. Meanwhile, we used Rose Delphi Link to produce the frame code of Delphies at the same time, so as to greatly improve the expansibility of the administrative system and the reusability of module .

scholarly journals RANCANG BANGUN SISTEM INFORMASI PERMINTAAN KEBUTUHAN LOGISTIK DI KANTOR WILAYAH II PT PEGADAIAN KOTA PEKANBARU BERBASIS WEB

2019 ◽  
Vol 5 (2) ◽  
pp. 136
Author(s):  
Zarnelly Zarnelly ◽  
Muhammad Hidayat
Keyword(s):  
Test Object ◽  
Unified Modeling Language ◽  
Object Oriented ◽  
User Acceptance ◽  
Black Box ◽  
Modeling Language ◽  
Acceptance Test ◽  
Unified Modeling ◽  
Analysis And Design ◽  
Object Oriented Analysis

Kantor wilayah II PT Pegadaian Kota Pekanbaru mempunyai unit bidang yang melayani permintaan kebutuhan kantor cabang dan unit pelayanan cabang yaitu bidang logistik. Permasalahan yang dihadapi dalam proses permintaan kebutuhan logistik antara lain masih menggunakan pembukuan apabila ada surat permohonan permintaan logistik yang masuk, menyebabkan sulit dalam pencarian data ketika dibutuhkan karena harus mencari data pada pembukuan satu persatu dan pada proses persetujuan  harus menunggu pimpinan ketika berada di kantor, apabila pimpinan berada diluar kota proses persetujuan harus tertunda dan menyebabkan penumpukan surat permohonan di kantor sehingga terjadi  keluhan dari  kantor cabang yang mengajukan permohonan karena permintaan yang diajukan tidak ada pemberitahuan dari bidang logistik. Dengan permasalahan yang terjadi dibutuhkan sistem informasi baru yang terhubung dengan kantor cabang  untuk dapat membantu mempermudah pekerjaan para pengguna dalam pengelolaan permintaan kebutuhan di bidang logistik yang menjadi solusi dari permasalahan yang terjadi. Sistem informasi permintaan kebutuhan logistik berbasis web ini menggunakan metode analisa dan perancangan Object Oriented Analysis and Design (OOAD) dan Waterfall pada pengembangan sistem dan tools unified modeling language (UML). Hasil uji Black Box yang dilakukan terhadap fitur yang terdapat pada sistem yang dibuat berjalan 100%. Hasil pengujian menggunakan User Acceptance Test (UAT) yang telah dihitung didapatkan persentase hasil akhir kelayakan sistem yang dibangun sebesar 82.29%.Kata kunci: Black Box, Sistem Informasi Permintaan kebutuhan logistik, User Acceptance Test, Object Oriented Analysis and Design, Waterfall.

Unified Modeling Language 2.0

2011 ◽  
pp. 3871-3879
Author(s):  
Peter Fettke
Keyword(s):  
Systems Engineering ◽  
Subject Matter ◽  
Unified Modeling Language ◽  
Object Oriented ◽  
General Purpose ◽  
Modeling Language ◽  
Unified Modeling ◽  
Object Oriented Systems

Mature engineering disciplines are generally characterized by accepted methodical standards for describing all relevant artifacts of their subject matter. Such standards not only enable practitioners to collaborate, but they also contribute to the development of the whole discipline. In 1994, Grady Booch, Jim Rumbaugh, and Ivar Jacobson joined together to unify the plethora of existing object-oriented systems engineering approaches at semantic and notation level (Booch, 2002; Fowler, 2004; Rumbaugh, Jacobson & Booch, 1998). Their effort leads to the unified modeling language (UML), a well-known, general-purpose, tool-supported, processindependent, and industry-standardized modeling language for visualizing, describing, specifying, and documenting systems artifacts.

How Complex is the Unified Modeling Language?

2002 ◽  
pp. 294-306 ◽  
Author(s):  
Keng Siau ◽  
Qing Cao
Keyword(s):  
Unified Modeling Language ◽  
Object Oriented ◽  
Quantitative Measure ◽  
Software Systems ◽  
Modeling Language ◽  
Unified Modeling ◽  
Complexity Metrics ◽  
Modeling Methods

Unified Modeling Language (UML) has emerged as the software industry’s dominant modeling language. It is the de facto modeling language standard for specifying, visualizing, constructing, and documenting the components of software systems. Despite its prominence and status as the standard modeling language, UML has its critics. Opponents argue that it is complex and difficult to learn. Some question the rationale of having nine diagramming techniques in UML and the raison d’être of those nine techniques in UML. Others point out that UML lacks a comprehensive methodology to guide its users, which makes the language even more convoluted. A few studies on UML can be found in the literature. However, no study exists to provide a quantitative measure of UML complexity or to compare UML with other object-oriented techniques. In this research, we evaluate the complexity of UML using complexity metrics. The objective is to provide a reliable and accurate quantitative measure of UML complexity. A comparison of the complexity metrical values of UML with other object-oriented techniques was also carried out. Our findings suggest that each diagram in UML is not distinctly more complex than techniques in other modeling methods. But as a whole, UML is very complex–2-11 times more complex than other modeling methods.

scholarly journals A Heuristic for Developing Object Interaction Diagrams

10.28945/2355 ◽  
2001 ◽  
Author(s):  
Il-Yeol Song
Keyword(s):  
Unified Modeling Language ◽  
Heuristic Method ◽  
Object Oriented ◽  
Modeling Language ◽  
Interaction Diagram ◽  
Unified Modeling ◽  
Analysis And Design ◽  
Object Interaction ◽  
Collaboration Diagram

The UML (Unified Modeling Language) has been widely accepted as a standard language for object-oriented analysis and design. Among the UML diagrams, one of the most difficult and time-consuming diagrams to develop is the object interaction diagram (OID), which is rendered as either a sequence diagram or a collaboration diagram. Our experience shows that developers have significant trouble in understanding and developing OIDs. In this paper, we present an effective heuristic for developing interaction diagrams and illustrate the technique with a case study. We found that students effectively developed OIDs using this heuristic method.

Sign in / Sign up

Export Citation Format

Share Document