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.

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.

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.

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.

Unified Modeling Language and Object-Oriented Design Pattern Based Computer-Aided Welding Fixture Design System

2010 ◽  
Author(s):  
Hua Li ◽  
Yiming Rong
Keyword(s):  
Design Pattern ◽  
Unified Modeling Language ◽  
Object Oriented ◽  
Modeling Language ◽  
Class Diagram ◽  
Fixture Design ◽  
Software System ◽  
Unified Modeling ◽  
Object Oriented Design ◽  
Computer Aided

Most of previous computer aided fixture design (CAFD) research has mainly concentrated on machining fixtures rather than welding fixtures, and how to face the challenges such as dynamic requirements, expansion, maintenance and management in the development of complicated computer aided welding fixture design (CAWFD) software system has received much less attention. Application of Unified Modeling Language (UML) and Object-oriented Design Pattern (OODP) for developing CAWFD software system has been discussed in this paper. CAWFD system functions like design phases, workflow and design subtasks in each design phase are introduced. How to employ UML fundamental elements such as use case diagram, class diagram and component diagram to model the CAWFD system has been demonstrated. Multiple-tier architecture of CAWFD and its benefits are also presented. OODP has been certified to be an effective and efficient method especially for class diagram creation and refinement which is the key point during system analysis and design. Due to the complexity of CAWFD, the class diagram for CAWFD is classified as conceptual class diagram and detailed class diagram. How to use Model-View-Control (M-V-C) design pattern in conceptual class diagram and the benefits of M-V-C application are discussed. For detailed class diagram, the techniques of applying Command, Observer, Factory and Template patterns to realize code reuse are articulated. As a result, the extension, reusability and maintainability of CAWFD system can be obtained by applying UML and OODP.

Dimensions of UML Diagram Use

2010 ◽  
pp. 271-290 ◽  
Author(s):  
Brian Dobing ◽  
Jeffrey Parsons
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Empirical Evidence ◽  
Unified Modeling Language ◽  
Object Oriented ◽  
Modeling Language ◽  
Development Projects ◽  
Use Case ◽  
Unified Modeling ◽  
Industry Standard

The Unified Modeling Language (UML) is an industry standard for object-oriented software engineering. However, there is little empirical evidence on how the UML is used. This chapter reports results of a survey of UML practitioners. The authors found differences in several dimensions of UML diagram usage on software development projects, including frequency, the purposes for which they were used, and the roles of clients/users in their creation and approval. System developers are often ignoring the “Use Case-driven” prescription that permeates much of the UML literature, making limited or no use of either Use Case Diagrams or textual Use Case descriptions. Implications and areas requiring further investigation are discussed.

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.

APLIKASI PEMESANAN MAKANAN BERBASIS WEB

e-NARODROID ◽  
2015 ◽  
Vol 1 (2) ◽  
Author(s):  
Immah Inayati
Keyword(s):  
Unified Modeling Language ◽  
Object Oriented ◽  
Modeling Language ◽  
Unified Modeling ◽  
Model View Controller ◽  
Model View

Perkembangan dunia teknologi berjalan sangat cepat. Selaras dengan hal itu, kebutuhan manusia hususnya dibidang bisnis juga semakin berkembang. salah satunya adalah R.M. Lesehan Berkah Ilaahi. Rumah makan ini merupakan rumah makan yang memiliki banyak pelanggan. Dengan semakin bertambahnya jumlah pelanggan, maka [penumpukan antrian banyak terjadi. Di samping itu rumah makan ini memiliki potensi untuk dapat terus mengembangkan bisnisnya. Untuk itu dibutuhkan sebuah sistem yang mampu memfasilitasi proses pemesanan melalui online serta mampu membantu pemilik bisnis dalam melakukan promosi dan penawaran, terlebih kepada pelanggan yang daya belinya tinggi. Jurnal ini memaparkan proses pembangunan sistem pemesanan berbasis web dengan menekankan pada tahap analisa, desain, dan implementasi. Analisis kondisi lapangan dilakukan dengan cara observasi lapangan, studi literatur sistem lama, wawancara dan kuesioner pelanggan. Hasil analisa akan digambarkan menggunakan notasi UML (Unified Modeling Language) untuk selanjutnya diimplementasikan dalam sebuah aplikasi e-CRM menggunakan bahasa pemrograman PHP serta basis data PostgreSQL. Metode pengembangan yang digunakan adalah Object oriented dengan memanfaatkan Yii Framework yang merupakan framework PHP berbasis Model View Controller (MVC). Selain itu digunakan pula bootstrap framework dari sisi desain aplikasi untuk memberikan fleksibilitas aplikasi ketika diakses dengan device yang resolusinya lebih kecil seperti telephon genggam. Kata kunci : Observasi, Wawancara, Kuesioner, UML (Unified Modeling Language), Yii Framework, Object oriented, Model View Controller (MVC), bootstrap framework.

Sign in / Sign up

Export Citation Format

Share Document