Enterprise modeling with the Joint Use of User Requirements Notation and UML

2011 ◽  
pp. 45-66
Author(s):  
Anna Medve
Keyword(s):  
Process Modeling ◽  
Unified Modeling Language ◽  
Enterprise Modeling ◽  
User Requirements ◽  
Urn Model ◽  
Fully Integrated ◽  
Unified Modeling ◽  
User Requirements Notation ◽  
Design Documentation ◽  
Enterprise Models

This chapter introduces the User Requirements Notation (URN) standardized formal methods and its joint use with Unified Modeling Language (UML) in enterprise modeling. It argues that the joint use of URN and UML can enhance enterprise models and co-evolve with enterprise engineering processes. URN combines goals and scenarios to help reasoning and to capture user requirements prior to detailed design. Furthermore, URN can be integrated partially or entirely into an existing business process modeling approach, without replace current ways of creating and analyzing models in order to be useful. Modelled in the UML, a URN model may be incorporated into the rest of a system’s UML design documentation, seamlessly linking the documentation for the requirements elicitation part of a project to the whole and an be fully integrated with the rest of the design documentation for a software system.

An Object-Oriented Abstraction Mechanism for Generic Enterprise Modeling

2011 ◽  
pp. 1646-1656
Author(s):  
Islam Choudhury ◽  
Sergio de Cesare ◽  
Emily Di Florido
Keyword(s):  
Information Systems ◽  
Object Oriented ◽  
Enterprise Modeling ◽  
Dynamic Object ◽  
Fully Integrated ◽  
Partially Ordered ◽  
Modeling Process ◽  
Enterprise Models ◽  
Business Changes ◽  
Integrated Information

A generic object-oriented enterprise modeling process (GOOEMP) is a set of partially ordered steps intended to reach the objective of building a fully integrated, dynamic, object-oriented model of the enterprise. An abstraction mechanism is proposed to enable this process. The process is generic because it applies to most types of enterprises. Enterprise models are the products developed from the process and these can be used by various stakeholders in an organization to: a) give them an understanding of the enterprise; b) design integrated information systems; c) respond to business changes by evolving their enterprise models and information systems in a coordinated and coherent manner; and d) enable the enterprise models built within a particular industry to be reused and applied to many other industries.

Collaborative Web Based System (CWBS)

2010 ◽  
pp. 151-173
Author(s):  
Bhuvan Unhelkar ◽  
Abbass Ghanbary ◽  
Houman Younessi
Keyword(s):  
Software Architecture ◽  
Process Modeling ◽  
Business Processes ◽  
Unified Modeling Language ◽  
Process Models ◽  
Modeling Language ◽  
Web Based ◽  
Unified Modeling ◽  
Business Process Modeling Notation ◽  
Web Based System

This chapter describes the modeling of the Collaborative Web Based System (CWBS). This CWBS is the means by which the CBPE model, discussed earlier in this book, is practically implemented. The focus of this chapter, however, is on the models of collaborative business processes that can be implemented in CWBS. The software architecture aspect of the CWBS is based on the detailed discussions of technologies in previous chapters 2, 4 and 5. The models in this chapter are based on the Business Process Modeling Notation (BPMN) and the use cases are based on the specifications of the Unified Modeling Language (UML). These notations and the ensuing process models are important when organizations try to collaborate with each other. These process models show, visually, how the interactions amongst multiple organizations will take place from a business viewpoint.

Generic Object Oriented Enterprise Modeling Approach Utilizing a Strategic Abstraction Mechanism

2010 ◽  
pp. 322-335
Keyword(s):  
Information Systems ◽  
Object Oriented ◽  
Enterprise Modeling ◽  
Dynamic Object ◽  
Fully Integrated ◽  
Partially Ordered ◽  
Modeling Approach ◽  
Modeling Process ◽  
Enterprise Models ◽  
Business Changes

A Generic Object-Oriented Enterprise Modeling Process (GOOEMP) is a set of partially ordered steps intended to reach the objective of building a fully integrated, dynamic, object-oriented model of the enterprise. An abstraction mechanism is proposed to enable this process. The process is generic because it applies to most types of enterprises. Enterprise models are the products developed from the process and these can be used by various stakeholders in an organization to: a) give them an understanding of the enterprise; b) design integrated information systems; c) respond to business changes by evolving their enterprise models and information systems in a coordinated and coherent manner; and d) enable the enterprise models built within a particular industry to be reused and applied to many other industries.

Consistency Checking of Specification in UML

2014 ◽  
pp. 300-316
Author(s):  
P. G. Sapna ◽  
Hrushikesha Mohanty ◽  
Arunkumar Balakrishnan
Keyword(s):  
Software Development ◽  
Software Testing ◽  
Human Life ◽  
Unified Modeling Language ◽  
Software Systems ◽  
User Requirements ◽  
Consistency Checking ◽  
Unified Modeling ◽  
Development Cycle ◽  
Development Life Cycle

The increasing use of software is giving rise to the development of highly complex software systems. Further, software systems are required to be of high quality as a defect can have catastrophic effect on business as well as human life. Testing is defined as the process of executing a program with the intention of finding errors. Software testing is an expensive process of the software development life cycle consuming nearly 50% of development cost. Software testing aims not only to guarantee consistency in software specification but also to validate its implementation meeting user requirements. On the whole, it is observed that in general, errors in software systems set in at the early stages of the software development cycle (i.e. while gathering user requirements and deciding on specification of intended software). Even though formal specification in B and Z assures a provable system, its use has become less popular due to mathematical rigor. The Unified Modeling Language (UML), a semi-formal language with graphical notations consisting of various diagrams has caught software developers’ imaginations and, it has become popular in industry. UML, with its several diagrams, helps to develop a model of intended software, and the model behaviour is simulated and tested to the satisfaction of both developer as well as users. As a UML model includes specifications of different aspects of a software system through several diagrams, it is essential to maintain consistency among diagrams so that quality of the model is maintained, and through inconsistency checking and removal, the model moves toward completeness. The works reported in literature on this topic are reviewed here.

scholarly journals Designing a Reliable UAV Architecture Operating in a Real Environment

2021 ◽  
Vol 12 (1) ◽  
pp. 294
Author(s):  
Krzysztof Andrzej Gromada ◽  
Wojciech Marcin Stecz
Keyword(s):  
Hazard Analysis ◽  
Unified Modeling Language ◽  
Modeling Language ◽  
Test Cases ◽  
User Requirements ◽  
Unified Modeling ◽  
Flight Simulators ◽  
Medium Range ◽  
Aerial Vehicle ◽  
Aerial Platform

The article presents a method of designing a selected unmanned aerial platform flight scenario based on the principles of designing a reliable (Unmanned Aerial Vehicle) UAV architecture operating in an environment in which other platforms operate. The models and results presented relate to the medium-range aerial platform, subject to certification under the principles set out in aviation regulations. These platforms are subject to the certification process requirements, but their restrictions are not as restrictive as in the case of manned platforms. Issues related to modeling scenarios implemented by the platform in flight are discussed. The article describes the importance of Functional Hazard Analysis (FHA) and Fault Trees Analysis (FTA) of elements included in the hardware and software architecture of the system. The models in Unified Modeling Language (UML) used by the authors in the project are described, supporting the design of a reliable architecture of flying platforms. Examples of the transformations from user requirements modeled in the form of Use Cases to platform operation models based on State Machines and then to the final UAV operation algorithms are shown. Principles of designing system test plans and designing individual test cases to verify the system’s operation in emergencies in flight are discussed. Methods of integrating flight simulators with elements of the air platform in the form of Software-in-the-Loop (SIL) models based on selected algorithms for avoiding dangerous situations have been described. The presented results are based on a practical example of an algorithm for detecting an air collision situation of two platforms.

Modeling of Component Arrays via Scenario Driven Approach

2013 ◽  
Vol 380-384 ◽  
pp. 2745-2748
Author(s):  
Hui Xu ◽  
Hong Zou ◽  
Li Hao Wei ◽  
Tian Wang
Keyword(s):  
Unified Modeling Language ◽  
State Machine ◽  
Modeling Language ◽  
User Requirements ◽  
Complex Time ◽  
Unified Modeling ◽  
Environment Changes ◽  
And Coping

The component array is a group of components that implement the same functions but provide different qualities. These component implementations can be switched at runtime for satisfying different user requirements and coping with environment changes. However, the design of component arrays is completely performed by hands of developers, which is complex, time-consuming, error-prone, and is poor at keeping up with the actual runtime conditions. This paper presents a scenario-driven state-based approach to modeling component arrays for satisfying requirements of predictable qualities. The automation of four vital steps of this approach is dependent on the interaction based modeling and state-machine based modeling. The approach is illustrated with UML (Unified Modeling Language) and the demonstration and experimentation are implemented on JEE (Java 2 Platform Enterprise Edition).

Business Process Modeling with the User Requirements Notation

2011 ◽  
pp. 165-197
Author(s):  
Michael Weiss ◽  
Daniel Amyot
Keyword(s):  
Business Process ◽  
Process Modeling ◽  
Business Processes ◽  
Service Oriented Architecture ◽  
Reactive Systems ◽  
Business Process Modeling ◽  
User Requirements ◽  
User Requirements Notation ◽  
Service Oriented ◽  
Management Case Study

This chapter demonstrates how the user requirements notation (URN) can be used to model business processes. URN combines goals and scenarios in order to help capture and reason user requirements prior to detailed design. In terms of application areas, this emerging standard targets reactive systems in general, with a particular focus on telecommunications systems and services. This chapter argues that the URN can also be applied to business process modeling. To this end, it illustrates the notation, its use, and its benefits with a supply chain management case study. It then briefly compares this approach to related modeling approaches, namely, use case-driven design, service-oriented architecture analysis, and conceptual value modeling. The authors believe that a URN-based approach will provide usable and useful tools to assist researchers and practitioners with the modeling, analysis, integration, and evolution of existing and emerging business processes.

Consistency Checking of Specification in UML

2017 ◽  
pp. 993-1010
Author(s):  
P. G. Sapna ◽  
Hrushikesha Mohanty ◽  
Arunkumar Balakrishnan
Keyword(s):  
Software Development ◽  
Software Testing ◽  
Human Life ◽  
Unified Modeling Language ◽  
Software Systems ◽  
User Requirements ◽  
Consistency Checking ◽  
Unified Modeling ◽  
Development Cycle ◽  
Development Life Cycle

The increasing use of software is giving rise to the development of highly complex software systems. Further, software systems are required to be of high quality as a defect can have catastrophic effect on business as well as human life. Testing is defined as the process of executing a program with the intention of finding errors. Software testing is an expensive process of the software development life cycle consuming nearly 50% of development cost. Software testing aims not only to guarantee consistency in software specification but also to validate its implementation meeting user requirements. On the whole, it is observed that in general, errors in software systems set in at the early stages of the software development cycle (i.e. while gathering user requirements and deciding on specification of intended software). Even though formal specification in B and Z assures a provable system, its use has become less popular due to mathematical rigor. The Unified Modeling Language (UML), a semi-formal language with graphical notations consisting of various diagrams has caught software developers' imaginations and, it has become popular in industry. UML, with its several diagrams, helps to develop a model of intended software, and the model behaviour is simulated and tested to the satisfaction of both developer as well as users. As a UML model includes specifications of different aspects of a software system through several diagrams, it is essential to maintain consistency among diagrams so that quality of the model is maintained, and through inconsistency checking and removal, the model moves toward completeness. The works reported in literature on this topic are reviewed here.

scholarly journals Pengukuran Fungsionalitas Perangkat Lunak Menggunakan Metode Function Point Berdasarkan Dokumentasi Desain

2013 ◽  
Vol 7 (2) ◽  
pp. 111
Author(s):  
Anie Rose Irawati ◽  
Khabib Mustofa
Keyword(s):  
Software Design ◽  
Unified Modeling Language ◽  
Modeling Language ◽  
Use Case ◽  
Size Measurement ◽  
End User ◽  
Unified Modeling ◽  
Functional Size Measurement ◽  
Function Point ◽  
Design Documentation

AbstrakPerkiraan nilai perangkat lunak yang disepakati oleh end user dan tim pengembang harus dinyatakan dalam besaran tertentu, salah satunya adalah dalam u ku ran fungsionalitas (functional size measurement/FSM).Metode Function Point (FP) merupakan salah satu metode yang digunakan untuk mendapatkan ukuran fungsionalitas, pertama kali dikenalkan oleh Allan Albrecht dan kemudian terus dikembangkan sampai saat ini oleh International Function Point User Goup (IFPUG). Tujuan dari pengukuran menggunakan FP adalah untuk mendapatkan ukuran biaya, durasi, dan jumlah sumber daya yang diperlukan oleh sebuah proyek perangkat lunak dan dapat dilakukan pada setiap tahap pengembangan perangkat lunak. Pengukuran FP memerlukan keahlian dalam hal analisis perangkat lunak dan hasil perhitungannya dinyatakan valid jika dilakukan oleh seseorang yang mempunyai sertifikasi FP (certified FP) dari IFPUG.Penelitian ini bertujuan untuk membangun sebuah sistem yang dapat memberikan kemudahan bagi pelaku pengukuran perangkat lunak dalam menganalisis perangkat lunak dengan metode Function Point berdasarkan pada IFPUG CPM 4.3.1.Penelitian ini menghasilkan sistem yang membantu pengguna untuk melakukan analisis FP dengan cepat dan dengan validitas yang tinggi. Sistem yang dibuat mampu menghitung FP sesuai dengan dokumentasi yang dimiliki software dan menggunakan input berupa dokumen XMI yang di-eksport dari Use Case Diagram, Class Diagram dan perpaduan antara Use Case dan Class. Selain itu, penelitian ini menunjukkan pola bahwa semakin lengkap dokumen UML (Unified Modeling Language) yang dimiliki oleh sebuah perangkat lunak maka semakin akurat hasil perhitungan FP yang didapatkan. Kata kunci— Pengukuran perangkat lunak, UML, Function Point, dokumentasi desain perangkat lunak.  AbstractEstimated value of software as agreed by the end user and the developer team should be expressed in a certain magnitude, one of which is the measure of functionality (functional size measurement / FSM).Function Point (FP) Method is one of the methods used to obtain the size of the functionality, first introduced by Allan Albrecht and then further developed by the International Function Point User Goup (IFPUG). FP is a method to get a measure of the cost, duration, and amount of resources required by a software project and can be done at any stage of software development. However, Function Point measurement requires expertise in software analysis and the results of the calculation are valid if done by someone with IFPUG certification.This study realizes a system that is convenient for actors in analyzing software using Function Point method based on IFPUG CPM 4.3.1.The system helps users to perform FP analysis in a faster way and confers accurate results. The system is able to count FP based on software design documentation and uses XMI document exported from use case diagrams, class diagrams, and diagrams illustrating the use cases and classes relationship as an input. The study also indicates that the more complete software UML (Unified Modeling Language) documents, the more accurate the FP calculation results obtained. Keywords— Software measurement, UML, Function Point, software design documentation.

Perancangan dan Pembuatan Aplikasi Pendeteksi Kesalahan Penempelan Barcode pada Kemasan Produk Menggunakan Sistem Arduino Uno dan Sistem Komputasi (Studi Kasus PT. Duta Nichirindo Pratama)

2020 ◽  
Vol 5 (1) ◽  
pp. 78
Author(s):  
Ade Sumaedi ◽  
Makhsun Makhsun ◽  
Achmad Hindasyah
Keyword(s):  
Unified Modeling Language ◽  
Database Design ◽  
Black Box ◽  
Design System ◽  
Modeling Language ◽  
Unified Modeling ◽  
Uml Diagrams ◽  
Arduino Uno ◽  
Menu Design ◽  
A Company

PT. Duta Nichirindo Pratama is a company engaged in the field of Autoparts Manufacture. Barcode is the identity of an item / product on the package. Barcode technology has been used as the identity of goods in a production. Barcodes are used to facilitate the identification of goods produced. Paste the barcode on the packaging of packaging results at PT. Duta Nichirindo Pratama is done manually, but there are often errors attached to the barcode on a similar packaging. This research will design and create a system based on Visual Basic.Net and Arduino to select barcode attachment errors that have the potential to be sent to consumers. The system is designed using Unified Modeling Language (UML) diagrams, database design and interface menu design. The system created will then be tested to detect the black box test. With a computing-based design system that functions to detect barcodes on the packaging automatically, the problem of sticking barcodes on the packaging can be detected.

Sign in / Sign up

Export Citation Format

Share Document