A Relational Model for Formal Object-Oriented Requirement Analysis in UML

The Unified Software Development Process (USDP) and Unified Modeling Language (UML) have been now generally accepted as the standard methodology and modeling language for developing object-oriented systems. Although agent-based systems introduce new issues, we consider that USDP and UML can be used in an extended manner for modeling agent-based systems. We present a methodology for designing agent-based systems and the specific models expressed in the UML-based notation corresponding to each phase of the software development process. UML was extended using the provided mechanism: stereotypes. Therefore, this approach can be managed with any CASE tool supporting UML. A case study, the development of a specific agent-based student assessment system (SAS), is presented.

The software development process (SDP) contains many variables depending on the methodology chosen. Software development methodologies such as Agile or Waterfall can specify how and in what sequence software is developed. However, the SDP remains a hot topic among practitioners and academics, who seek to clarify the key aspects that influence the successful implementation of the SDP. As the SDP is a dynamic and knowledge-intensive business process (BP), one of its most impact components is the human factor (HF). It is difficult to predict how the HF impacts the sequence and results of SDP implementation. This paper proposes a new approach to investigate the impact of the HF on the SDP through the perspectives of different software development methodologies. The advantages and novelties of this approach include modelling HF uncertainties through their fuzzification in SDP activities, modelling different SDP methodologies using a case-handling approach, and simulating a dynamic, case-based SDP with real HF-related data collected from several IT organizations. The results show that the impact of the HF on SDP performance differs across the Waterfall and Agile methodologies. The results also allow researchers and practitioners working on software development projects to familiarize themselves with the impact of the HF on different SDPs, and to assess the degree of development risk associated with the SDP depending on the methodology chosen.

Unified Modeling Language (UML) plays an important role in the modern software development process by offering standardized methods for visual modeling, analysis, and design of complex systems. This paper discusses the main aspects of storing, editing, and integrating UML documents with integrated development environments (IDEs). The main focus is on comparing the two main formats for storing UML models – XML Metadata Interchange (XMI) and JavaScript Object Notation (JSON). XMI, being an official standard developed by Object Management Group, provides a high degree of detail and compatibility with various UML tools, making it preferable for large and complex projects that require support for the full UML specification. At the same time, JSON is simple and flexible, which makes it suitable for projects where speed of development and ease of integration are important, although it is inferior to XMI in describing complex aspects of UML models. The paper analyzes in detail the methods of editing UML documents, including manual editing and automated approaches, using APIs and scripts. Manual editing is useful when you need to make small changes to the structure of a UML document, but it can be time-consuming and error-prone when working with large projects. Automation, on the other hand, provides effective tools for mass editing and generating UML elements, which significantly speeds up development and minimizes the likelihood of errors, especially since modern tools such as StarUML offer the necessary tools for programmatically modifying UML documents by integrating them into development processes. Combining of UML documents with integrated development environments also plays a key role in increasing development efficiency, as this allows automating code generation based on UML models, maintaining synchronization between code and diagrams, and facilitating visualization and documentation of architectural solutions. Despite the significant advantages, there are challenges associated with limited support for all UML features and potential conflicts between models and code. This only emphasizes the need for further research in this area. Prospects for further research include the development of new methods and tools for working with UML documents, improving their integration with development environments, and using artificial intelligence to automate the analysis and design of UML models. Attention should also be paid to the using of UML with continuous integration processes, which can significantly increase the flexibility and adaptability of software development. Thus, the study of the structure of storing, editing, and integrating UML documents is an important area for optimizing the design and development of modern software systems.

In this paper a system static structure modeling formalization and formalization of static models based on topological functioning model (TFM) is proposed. TFM uses mathematical foundations that holistically represent complete functionality of the problem and application domains. By using TFM within software development process it is possible to do formal analysis of a business system and in a formal way to model the static structure of the system. After construction of the TFM of a system’s functioning a problem domain object model is defined by performing transformation of defined TFM. By making further transformations of TFM and by using TFM within software development it is possible to introduce more formalism in the Unified Modeling Language (UML) diagrams and in their construction. In this paper we have introduced topology into the UML class diagrams.

In recent years, the number and scope of events in the Asia and Middle East / North Africa region has increased significantly. Events are one of the things that attracts the attention of foreign tourists to come to visit a country as a tourist destination. Refers toMinister of Tourism Regulation Number 2 Year 2017on Guidelines for Venues for Meetings, Incentive Trips, Conventions and Exhibitions, explains that criteria and indicators are needed to increase the competitiveness of venues for meetings, incentive trips, conventions and exhibitions at the regional and global levels. This is done to increase the number of visits, length of stay, and expenditures for domestic and foreign tourists. Therefore, visual indicators or data are needed that can present the location of the event and a list of events in DKI Jakarta. From these problems, this study aims to produce a web-based spatial information system for the distribution of tourism industry events to map event locations in DKI Jakarta. The methodology used in collecting this data is the method of observation, interviews, and literature studies. While the system development methodology uses PHP and MySQL with the Rapid Application Development (RAD) approach and uses the Unified Modeling Language (UML) which is a tool for system description and design, as well as the Google Maps API for digital maps. The results of this study are in the form of a spatial information system that can display a map of the distribution of event locations in DKI Jakarta based on event data and event categories at the DKI Jakarta Tourism and Creative Economy Department. While the system development methodology uses PHP and MySQL with the Rapid Application Development (RAD) approach and uses the Unified Modeling Language (UML) which is a tool for describing and designing systems, as well as the Google Maps API for digital maps. The results of this study are in the form of a spatial information system that can display a map of the distribution of event locations in DKI Jakarta based on event data and event categories at the DKI Jakarta Tourism and Creative Economy Department. While the system development methodology uses PHP and MySQL with the Rapid Application Development (RAD) approach and uses the Unified Modeling Language (UML) which is a tool for describing and designing systems, as well as the Google Maps API for digital maps. The results of this study are in the form of a spatial information system that can display a map of the distribution of event locations in DKI Jakarta based on event data and event categories in the DKI Jakarta Tourism and Creative Economy Department.

Leveraging a service-oriented paradigm would significantly affect the way people build software systems. However, to achieve this ambitious vision a solid software development methodology should be in place, comprising specific, service-context patterns as well as appropriate supporting tools which altogether integrate methods and best practices into a stable development environment. This paper presents a structured approach to analyzing software development methodologies in light of the specific features of service-oriented applications. The proposed approach is based on a critical assessment of existing software development methodologies along three methodological dimensions, namely managing change in software development, specifying the software development process and targeting the stakeholder goals. For each of this dimension we first identify suitable software methodologies capable to meet the specific challenges and then discuss their contribution towards the definition of a service-oriented development methodology.

The Unified Modelling Language (UML) is a language for specifying, visualising, constructing and documenting software systems. The UML proved to be extremely successful and it has achieved tremendous popularity making it the de facto industry standard for object oriented system development. As such, many researchers presented empirical studies on the practical usage of UML but as well criticisms for UML complexity, difficulty to be learnt, etc. Even though a large number of articles and books are devoted to various aspects of UML language, there is little evidence on how UML is used. This study attempts to identify the profile of persons using UML, to pinpoint UML diagrams that are being used and their effectiveness, to discover whether CASE tools are being used and to record the perceived usefulness of UML language. For conducting the study a survey was developed and it was distributed to mailing lists of Greek IT professionals and to university students. The findings indicate that UML is used successfully in the majority of software development projects and that most users perceive UML positively since it supports faster system building, development of higher quality software systems, and for specific cases, it leads to software development cost‐decrease.

Unless the business model that governs software production adjusts to new technology, it is unlikely that an investment in the technology will result in real productivity benefits. Commercial development always takes place in the context of a business model, and in that context an understanding of how business constraints influence commercial software development is imperative. As software markets become more competitive and business pressures shorten software development cycles, improved software development productivity continues to be a major concern in the software industry. Many believe that new software technology, such as object-oriented development, provides a breakthrough solution to this problem. Unfortunately, there is little quantitative evidence for this belief. In this paper we explore the relationship between the business model and the productivity that a software development methodology can achieve in a commercial environment under that model. We first examine empirical data from several commercial products developed using object-oriented methods. The results indicate that object-oriented development may not perform any better than "procedural" development in environments that lack incentives for early completion of intermediate project tasks. We then model and simulate the impact of the software task-completion incentives and deadlines on the productivity that might be expected from a technology with high-performance potential. We show how and why some common business practices might lower project productivity and project completion probability. We also discuss to what extent poor software process control and (im)maturity of the technology compounds the problem.

In the process of software development, software testing is a huge project, and most of the software functionality testing is complex and repetitive, should to spend a lot of cost and manpower. Therefore, you can save a lot of manpower and costs, avoid human error and improve software quality if we can achieve automated testing. In the software development process, the application of model-driven developments has grown wider recently. The main concept is to fetch all of the significant properties referring to system design, and use formal or semi-formal model to describe system in different levels of abstraction. In this paper, we apply a tool based on high level Petri Net model of automated testing -- MISTA [1](Model based Integration and System Testing Automation) to automated generate test code for system. In this paper, through capture the information of the state machine diagram describes the behavior of the system in the Unified Modeling Language. Through the eXtensible Markup Language automation converted to High Level Petri Net test model, and then using automated test code generating software MISTA generation test cases and test code of system to achieve automated testing, and save the software required for testing a large number of human costs, and the software development process from design architecture to the software testing for a bridging.

Software development methodologies offer a methodical way to working on projects in accordance with client expectations. In the software development process, the customer is seen as the main entity. In order to build valuable software quickly and within a given budget, firms are now seeking to implement customer-centric techniques. Customer satisfaction plays a crucial part in the development and deployment of software products. One software development process that helps to best fulfil changing customer requirements is agile software development. In the following part, a table of comparisons between the various agile modelling methodologies with regard to requirements and the role of the customer follows a discussion of agile methodology. The Scrum & Extreme Programming framework is presented, along with how different firms use the approach for projects of various sizes.

Behavior Driven Development (BDD) is a widely adopted agile methodology for software development that emphasizes the behavior of an application as a series of test cases, using the keywords, which include "Given," "When," and "Then." It involves writing requirements in a structured and testable format that can be evaluated to ensure compliance with the expected behavior. Although a significant amount of research has been conducted to examine the impact of using BDD on software development process yet rare work is observed to synthesize these studies and identify areas for future exploration. This study presents a review of the state-of-the-art BDD by synthesizing the recent advancements in its uses and applications. It aims to systematically investigate the impact of BDD on software development process as well as on product quality by aiding to bridge the communication gap between the stakeholders. The results reveal that BDD is an effective technique to clarify requirements during the software development process as it helps minimizing the intrinsic ambiguities. This work proposes a taxonomy based on the role and applications of BDD in various contexts. It suggests a framework for applying BDD in software development and defines a workflow for its application in software development. Finally, this work highlights some pertinent future directions for the use of BDD in software development.

Unified Modeling Language (UML) has been widely accepted in the software engineering area, because it provides most of the concepts and notations that are essential for documenting object-oriented models. However, UML does not have an explicit format to describe and interchange its model information intentionally. This paper addresses the UML model interchange and presents our efforts to make UML highly interoperable. We developed an interchange format called UXF (UML eXchange Format) based on XML (Extensible Markup Language). UXF is a simple and well-structured format to encode UML models. It leverages the tool interoperability, team development and reuse of design models by interchanging the model information with the the XML standard. Also, we propose an open distribution platform for UML models, which provides multiple levels of interoperability of UML models. Our work shows an important step in the evolution for the interoperable UML.

The Unified Modeling Language (UML) has been widely accepted as the standard object-oriented (OO) modeling language for modeling various aspects of software and information systems. The UML is an extensible language, in the sense that it provides mechanisms to introduce new elements for specific domains if necessary, such as web applications, database applications, business modeling, software development processes, data warehouses and so on. Furthermore, the latest work of the Object Management Group (OMG) on UML [1] resulted in a larger and more complicated specification, with even more diagrams for some good reasons. Although providing different diagrams for modeling specific parts of a software system, not all of them need to be applied in most cases. Therefore, heuristics, design guidelines, and lessons learned from experiences are extremely important for the effective use of UML and to avoid unnecessary complication.

In the past, research on agent-oriented software engineering had been widely lacking touch with the world of industrial software development. Recently, a cooperation has been established between the Foundation of Intelligent Physical Agents (FIPA) and the Object Management Group (OMG) aiming to increase acceptance of agent technology in industry by relating to de facto standards (object-oriented software development) and supporting the development environment throughout the full system lifecycle. As a first result of this cooperation, we proposed AGENT UML [1; 20], an extension of the Unified Modeling language (UML), a de facto standard for object-oriented analysis and design. In this paper, we describe the heart of AGENT UML, i.e., mechanisms to model protocols for multiagent interaction. Particular UML extensions described in this paper include protocol diagrams, agent roles, multithreaded lifelines, extended UML message semantics, nested and interleaved protocols, and protocol templates.

ARCADE is a project aimed to develop an integrated software platform for authoring and delivery of Internet-based distance courses covering the university needs. Unified Modeling Language (UML) and Unified Software Development Process were applied as a basis for the project development. The Assessments and Assignments package provides computer supported instructional feedback (tests, projects, essays, problems). The IMS Question and Test Interoperabitity specification (QTI) defines the basic structures (Assessment, Section, Item - ASI) for the Assessments module development. This module includes three main subsystems - ASI Structures Management, Tests Management, and Test Performance.