Wyniki wyszukiwania - BazTech

1

Computer Game Scenario Representation: A Systematic Mapping Study

Paschali Maria-Eleni, Stamelos Ioannis

e-Informatica Software Engineering Journal

|

2023

|

Vol. 17, nr 1

art. no. 230103

EN

Background: Game scenario is an important factor for achieving player enjoyment; consisting a key business success factor. Additionally, the production of early design artifacts is crucial for the success of the development process. However, representing scenarios is a non-trivial task: (a) multiple aspects of the game need to be visualized; and (b) there is a plethora of representation approaches, out of which the game designer needs to select from. Aim: The goal of this work is to provide a panorama of the current scenario representation approaches, to aid game engineers in selecting the most fitting scenario representation approach and understand the existing designing options. Method: We have performed a Systematic Mapping Study, using 4 digital libraries, since the main goal can be achieved through study classification. By following an established search and filtering process, we have identified 717 articles, and analyzed in detail 95. Results: Diagrams are the most common generic approach to represent scenario; Game story is the most usual part of the scenario being represented; Characters are the most common component; and Transitions are the most usual connectors. Conclusion: Researchers may get useful information for empirically investigating several game engineering aspects; whereas game engineers can efficiently select the most fitting approach.

2

Component interface standardization in robotic systems

Hristozov Anton, Matson Eric, Dietz Eric, Rogers Marcus

Annals of Computer Science and Information Systems

|

2022

|

Vol. 32

305--312

EN

Components are heavily used in many software systems, including robotic systems. The growth in sophistication and diversity of new capabilities for robotic systems presents new challenges to their architectures. Their complexity is growing exponentially with the advent of AI, smart sensors, and the complex tasks they have to accomplish. Such complexity requires a more flexible approach for creating, using, and interoperability of software components. The issue is exacerbated because robotic systems are becoming increasingly reliant on third-party components for specific functions. In order to achieve this kind of interoperability, including dynamic component replacement, we need a way to standardize their interfaces. A formal approach is desperately needed for specifying what an interface of a robotic software component should contain. This study performs an analysis of the issue and presents a universal and generic approach to standardizing component interfaces for robotic systems. Our approach is inspired and influenced by well-established robotic architectures such as ROS, PX4, and Ardupilot. The study is also applicable to other software systems with similar characteristics to robotic systems. We consider using either JSON or Domain-Specific Languages (DSL) development with tools such as Antlr and automatic code and configuration files generation for frameworks such as ROS and PX4. A case study with ROS2 has been done as a proof of concept for the proposed methodology.

3

An integrated checklist for architecture design of critical software systems

Bierska Adela, Buhnova Barbora, Bangui Hind

Annals of Computer Science and Information Systems

|

2022

|

Vol. 31

133-140

EN

With the advancement of digitalization, critical information infrastructures, such as intelligent energy distribution, transportation, or healthcare, have opened themselves towards intelligent technological opportunities, including automation of previously manual decision making. As a side effect, the digitalization of these infrastructures gives rise to new challenges, especially linked to the complexity of architecture design of these infrastructures, to later support necessary software quality and safeguard the systems against attacks and other harm. To support software architects in the design of these critical software systems, well structure architectural knowledge would be of great help to prevent the architects from missing some of the crucial concerns that need to be reflected with built-in architectural mechanisms, early during architecture design.Given the narrow scope of existing guidelines, with the need of browsing and combining multiple sources, this paper proposes an integrated checklist to cover the breath of architectural concerns for the design of critical software systems, covering the need for built-in mechanisms to prevent, detect, stop, recover from and analyse intentional as well as unintentional threats to system dependability. Contrary to existing guidelines that typically focus on runtime incident handling, our checklist is to be used during architecture design to ensure that the system has built-in mechanisms to either handle the incidents automatically or include the right mechanisms to support the runtime incident handling.

4

Agile Architecting of Distributed Systems for Flexible Industry 4.0

Christensen Henrik Bærbak, Jepsen Sune Chung, Worm Torben

Annals of Computer Science and Information Systems

|

2021

|

Vol. 25

533--536

EN

Small and medium sized businesses within mechanical manufacturing cannot benefit from Industry 4.0 automation as small production batches are unable to pay for up-front robotic configuration and programming costs. In this paper, we report on early results from a project aiming at developing a software architecture supporting fast, easy, and flexible reconfiguration of a robotic manufacturing process, using an agile and prototyping approach.

5

Modeling of Distributed Ledger Deployment View

Górski Tomasz, Bednarski Jakub

International Journal of Electronics and Telecommunications

|

2020

|

Vol. 66, No. 4

619--625

EN

The Distributed Ledger Technology (DLT) is a peer-to-peer model of sharing data among collaborating parties in a decentralized manner. An example of DLT is a blockchain where data form blocks in an append-only chain. Software architecture description usually comprises multiple views. The paper concentrates on the Deployment view of the DLT solution within the 1+5 architectural views model. The authors have proposed Unified Modeling Language (UML) extensibility mechanisms to describe the needed additional semantic notation to model deployment details. The paper covers both the network and node levels. The proposed stereotypes and tagged values have enriched UML Deployment diagram. We have gathered those modeling elements in dedicated UML Profile for Distributed Ledger Deployment. We have applied the profile to model Deployment view of a renewable energy management system that uses R3 Corda framework. The system records information about inbound and outbound energy to/from renewable energy grid.

6

Towards Extending UML's Activity Diagram for the Architectural Modeling, Analysis, and Implementation

Kose Mehmet Alp, Ozkaya Mert

Annals of Computer Science and Information Systems

|

2020

|

Vol. 21

639--648

EN

SAWUML is a general-purpose software modeling language that extends UML by unifying component and sequence diagrams for the specifications of software architectures. While component diagram is used for modeling the system structures, sequence diagram is extended with the Design-by-Contract approach for the modeling of system behaviors. In this paper, we aim at enhancing the language usability by providing alternative modeling choices for practitioners. To this end, we extended SAWUML's notation set with UML's activity diagram for the behavior modeling. So, practitioners may now use either sequence or activity diagrams, while the system structures are still modeled with component diagrams. We also extended SAWUML's modeling editor for creating software architecture models together with component and activity diagrams and the code generators for automatically obtaining (i) formal models in SPIN's ProMeLa for formal verification and (ii) Java-based implementation. We illustrate our language extension with the gas station case-study.

7

Toward Digital Transformation of Processes in Legal Metrology for Weighing Instruments

Oppermann Alexander, Eickelberg Samuel, Exner John

Annals of Computer Science and Information Systems

|

2020

|

Vol. 21

559--562

EN

The digital transformation of sovereign processes is a driving force to streamline and innovate processes for measuring instruments under legal control. Providing trust is the essential purpose of Legal Metrology and still a challenging task in the digital domain. Taking the strict legal framework into account, a distributed software architecture is presented that offers privacy, security and resilience. At the same time, the platform approach seamlessly integrates existing public and private infrastructures. Furthermore, a service hub is created with interdependent services that support the digital transformation of paper-based processes, such as verification and software update. Exemplary, these two central use cases are introduced, and its requirements and implementation approach are described. The main goal is to provide the same level of trust and security, by developing new digital concepts, infrastructure and remote processes for a unified digital single market.

8

The Syntax of a Multi-Level Production Process Modeling Language

Vještica Marko, Dimitrieski Vladimir, Kordić Slavica, Ristić Sonja, Luković Ivan, Pisarić Milan

Annals of Computer Science and Information Systems

|

2020

|

Vol. 21

751--760

EN

The fourth industrial revolution introduces changes in traditional manufacturing systems and creates basis for a lot-size-one production. The complexity of production processes is significantly increased, alongside the need to enable efficient process simulation, execution, monitoring, real-time decision making and control. The main goal of our research is to define a methodological approach and a software solution in which the Model-Driven Software Development (MDSD) principles and Domain-Specific Modeling Languages (DSMLs) are used to create a framework for the formal description and automatic execution of production processes. In that way production process models are used as central artefacts to manage the production. In this paper, we propose a DSML which can be used to create production process models that are suitable for automatic generation of executable code. The generated code is used for automatic execution of production processes within a simulation or a shop floor.

9

Assumptions concerning a software supporting the primary intramural teaching subsidy distribution at the Wroclaw University of Science and Technology faculty

Szczurowski L., Rekuć Witold

Operations Research and Decisions

|

2019

|

Vol. 29, No. 2

89--101

EN

Assumptions concerning a software supporting the primary intramural teaching subsidy distribution at a Wroclaw University of Science and Technology faculty compatible with a distribution algorithm are described. Strategic goal, main problems, roles and operational tasks of this support are identified. Selected business processes and system use cases are analyzed. Concepts as well as introductory system architecture accommodating the necessity of the subsidy distribution algorithm updating are elaborated. Proposals important from the point of view of the dean’s financial assistant preparing analytical data concerning subsidy distribution for the faculty provisional as well as final budged version are formulated.

10

Projektowanie architektury oprogramowania systemu sterującego zrobotyzownym modułem technologicznym. Część I, Modelowanie struktury oprogramowania (statyka)

Stamirowski J.

Technologia i Automatyzacja Montażu

|

2018

|

nr 3

7--12

PL

Konsekwencją stosowania w systemach sterowania techniki komputerowej jest przeniesienie obciążenia funkcjonalnego z węzłów mechanicznych na składniki intelektualne (elektronika, komputery). Sformułowanie wymagań, modelowanie struktury i architektury oprogramowania, należą do trudnych problemów projektowania komputerowych systemów sterowania. Jest to szczególnie istotne w dobie zintegrowanego wytwarzania. Do najbardziej popularnych narzędzi modelowania struktury i zachowania systemów komputerowych należy język UML (Unified Modeling Language). W artykule przedstawiono modelowanie struktury oprogramowania sterującego zrobotyzowanym modułem technologicznym – ZMT (ang. robotic technological module – RTM) z użyciem języka UML. Jest to pierwszy etap projektowania oprogramowania systemów komputerowych do których należy system sterowania ZTM.

EN

The consequence of using computer control systems is the transfer of functional load from mechanical nodes to intellectual components (electronics, computers). Formulating requirements, modeling the structure and architecture of software are among the difficult problems of designing computer control systems. This is particularly important in the era of integrated production. UML (Unified Modeling Language) is the most popular tool for modeling the structure and behavior of computer systems. The article presents the modeling of the software structure controlling the robotic technological module (ZMT) (statics) using the UML language. This is the first stage of designing software for computer systems to which the ZTM control system belongs.

11

Selected topics in design and application of a robot for remote medical examination with the use of ultrasonography and ascultation from the perspective of the REMEDI project

Arent K., Cholewiński M., Chojnacki Ł., Domski W., Drwięga M., Jakubiak J., Janiak M., Kreczmer B., Kurnicki A., Stańczyk B., Szczęśniak-Stańczyk D.

Journal of Automation Mobile Robotics and Intelligent Systems

|

2017

|

Vol. 11, No. 2

82--94

EN

This article presents a robot for remote noninvasive medical examination. In particular, this robot allows a doctor to carry out an interview, an observation, an auscultation and an ultrasound examination, including echocardiography. The robot has been developed within the ReMeDi (Remote Medical Diagnostician) project funded by the European Union’s Research and Innovation 7th Framework Programme. At the beginning of the article, we outline selected results of the user’s evaluation of the robot idea together with the requirements regarding the robot. Then the essential system components are presented and a selection of them are discussed in detail. Subsequently we present the integrated system and discuss selected topics concerning the integration. Finally, the document is completed by a description of the users evaluation process.

12

Investigation of enterprise architecture and software architecture in relation to quality attributes in military applications

Werewka J.

Szybkobieżne Pojazdy Gąsienicowe

|

2015

|

nr 2 (37)

7--18

EN

In this paper the relations between enterprise and software architecture are investigated. These relations may be different for a company which uses the software as part of their operation as opposed to a company which develops software systems. The relations are usually very complicated, therefore only the attribute of quality was chosen for this study. This paper shows the importance of finding mappings between quality attributes on enterprise architecture and software architecture levels. Some examples from the military domain are given. An interesting example used in the military is the survivability quality attribute, which has similar meaning on enterprise, system, and network levels. This paper proposes some ways in which the relations may be investigated.

13

Searching Design Patterns Fast by Using Tree Traversals

Cicciarella S., Napoli C., Tramontana E.

International Journal of Electronics and Telecommunications

|

2015

|

Vol. 61, No. 4

321-326

EN

Large software systems need to be modified to remain useful. Changes can be more easily performed when their design has been carefully documented. This paper presents an approach to quickly find design patterns that have been implemented into a software system. The devised solution greatly reduces the performed checks by organising the search for a design pattern as tree traversals, where candidate classes are carefully positioned into trees. By automatically tagging classes with design pattern roles we make it easier for developers to reason with large software systems. Our approach can provide documentation that lets developers understand the role each class is playing, assess the quality of the code, have assistance for refactoring and enhancing the functionalities of the software system.

14

A Software Architecture Assisting Workflow Executions on Cloud Resources

Borowik G., Woźniak M., Fornaia A., Giunta R., Napoli C., Pappalardo G., Tramontana E.

International Journal of Electronics and Telecommunications

|

2015

|

Vol. 61, No. 1

17-22

EN

An enterprise providing services handled by means of workflows needs to monitor and control their execution, gather usage data, determine priorities, and properly use computing cloud-related resources. This paper proposes a software architecture that connects unaware services to components handling workflow monitoring and management concerns. Moreover, the provided components enhance dependability of services while letting developers focus only on the business logic.

15

QAM: proposed model for quality assurance in CBSS

Kharb L

Advances in Science and Technology. Research Journal

|

2015

|

Vol. 9, nr 27

50--57

EN

Component-based software engineering (CBSE) / Component-Based Development (CBD) lays emphasis on decomposition of the engineered systems into functional or logical components with well-defined interfaces used for communication across the components. Component-based software development approach is based on the idea to develop software systems by selecting appropriate off-the-shelf components and then to assemble them with a well-defined software architecture. Because the new software development paradigm is much different from the traditional approach, quality assurance for component-based software development is a new topic in the software engineering research community. Because component-based software systems are developed on an underlying process different from that of the traditional software, their quality assurance model should address both the process of components and the process of the overall system. Quality assurance for component-based software systems during the life cycle is used to analyze the components for achievement of high quality component-based software systems. Although some Quality assurance techniques and component based approach to software engineering have been studied, there is still no clear and well-defined standard or guidelines for component-based software systems. Therefore, identification of the quality assurance characteristics, quality assurance models, quality assurance tools and quality assurance metrics, are under urgent need. As a major contribution in this paper, I have proposed QAM: Quality Assurance Model for component-based software development, which covers component requirement analysis, component development, component certification, component architecture design, integration, testing, and maintenance.

16

Modelling and evaluation of software architectures

Zalewski A.

Prace Naukowe Politechniki Warszawskiej. Elektronika

|

2013

|

z. 187

3--116

EN

Software architecture is an important development artefact, with substantial influence over the quality of a software system. This monograph presents the state of the art in modelling and evaluating software architectures, which are two closely related research areas influencing each other. Three main approaches to architectural modelling have been covered, i.e. models of software structure, architectural decisions, and models of architecture description. Semi-formal models, such as block diagrams models, UML, SysML and Archimate, are mainly used for modelling software structure. Architectural decisions capture the rationale underlying a given architectural design and the logic of the architecting process. The most important models for documenting architectural decisions have been discussed and compared: textual models, a comprehensive, flagship model by Zimmerman et al. extended with decision-making support, as well as the author's Maps of Architectural Decisions model, which has been tailored to the needs of documenting the evolution of rapidly and unpredictably evolving systems. Architectural patterns and tactics, which are closely related to architectural decisions, are also covered by this survey. The System Organisation Pattern is the author's proposition for the effective representation of top-level architecture of large-scale distributed systems, combining concepts of architectural patterns and architectural decisions. The models of architectural description focus on organizing architectural information according to the stakeholders' concerns, captured by viewpoints. The monograph covers the most important developments in this area, i.e. ISO 42010:2011 standards, Kruchten's 4+1 views, Zachman's framework and recent developments regarding viewpoints. Architecture evaluation methods have evolved alongside architectural modelling. A new taxonomy of architecture evaluation methods, based on the method's applicability has been introduced, and two basic paradigms of architecture evaluation have been identified, Eighteen state-of-the-art architecture evaluation methods have been characterised according to a uniform description scheme. The Early Architecture Evaluation Methods, developed for the evaluation of large-scale system architectures at the inception stage of development, being the author's contribution to the research on architectural evaluation, was included in this survey. Such a comprehensive survey of architecture evaluation methods enabled the state of the art to be analysed, and a further research Outlook to be drawn up.

17

Store Revisited

Grzanek K.

Journal of Applied Computer Science Methods

|

2013

|

Vol. 5 No. 1

69--83

EN

Building abstraction layers is the key do the creation of reliable, scalable and maintainable software. Large number of database models and implementations together with the requirements coming from agile and TDD methodologies make it even more tangible. The paper is an attempt to present features and abstraction layers of a transactional key → value persistent storage library in which the physical storage is fully transparent for a programmer and exchangeable on the run-time.

18

One Graph to Rule Them All Software Measurement and Management

Dąbrowski R., Timoszuk G., Stencel K.

Fundamenta Informaticae

|

2013

|

Vol. 128, nr 1-2

67--63

EN

The software architecture is typically defined as the fundamental organization of the system embodied in its components, their relationships to one another and to the system's environment. It also encompases principles governing the system's design and evolution. In order to manage the architecture of a large software system the architect needs a holistic model that supports continuous integration and verification for all system artifacts. In earlier papers we proposed a unified graph-based approach to the problem of managing knowledge about the architecture of a software system. In this paper we demonstrate that this approach facilitates convenient and efficient project measurement. First, we show how existing software metrics can be translated into our model in a way that is independent of the programming language. Second, we introduce new metrics that cross the programming language boundaries and are easily implementable using our approach. We conclude by demonstrating how the new model can be implemented using existing tools. In particular, graph databases are a convenient implementation of an architectural repository. Graph query languages and graph algorithms are an effective way to define metrics and specialized graph views.

19

Funkcjonalnie czy technicznie - architektura oprogramowania billingowego

Witański M.

Przegląd Telekomunikacyjny + Wiadomości Telekomunikacyjne

|

2012

|

nr 1

24-27

PL

Oprogramowanie billingowe bywa nazywane jednym z najtrudniejszych do stworzenia Dosyć skomplikowane operacje, jakie wykonywane są na rekordach taryfikacyjnych, oraz duże wymagania użytkowników wobec funkcji, jakie spełniać ma takie oprogramowanie, stawiają duże wyzwanie przed twórcami takiego oprogramowania Starano się pokazać, na ile producent systemu taryfikacyjnego może pójść na ustępstwa, a w jakim stopniu musi spełnić surowe normy techniczne. Wykorzystano rzeczywisty przypadek rozwoju oprogramowania firmy Comfortel, a skonfrontowano to z wypowiedziami użytkowników tego typu systemów komputerowych.

EN

Billing software is sometimes considered to be one of the most difficult to develop. Cuite complex operations, which are made on call detail records, and high user demands with respect to the functionality which the software is to have pose difficult challenges for the creators of such software. This article aims at demonstrating how far the billing system manufacturer may compromise, and how far strict technical standards need to be met. A real case of development of software by the Comfortel company is used in the article and confronted with statements made by users of that type of computer systems.

20

Enhancing Usability of the Human-Computer Interfaces with Software Architecture

Kasprzyk R., Sroczyński J., Stelmach K., Szadkowski P., Wawruch K.

Biuletyn Instytutu Systemów Informatycznych

|

2011

|

nr 8

35-43

EN

The article tells about two projects, which pay a great attention to the architectural side of a non-standard human-computer interface. The first project is THEIA, which is a touchless human-computer interaction system. The main target is to give the end-user an ability to interact with a computer only by his/her sight. By looking at areas of the screen the user triggers actions in the operating system he/she is using. The second project is OLIMPUS designed for creating and integrating modern user interfaces supporting any non- standard interaction sources. The project aims at simplifying a development process of interfaces collaborating simultaneously with many different sources of interaction and their dynamical exchanging as well.

PL

W artykule przedstawiono koncepcje dwóch autorskich rozwiązań problemu komunikacji człowiek-maszyna. Obie koncepcje zostały zrealizowane w postaci prototypów o kodowych nazwach THEIA i OLIMPUS, potwierdzających słuszność założeń i ich realizowalność. Projekt THEIA (The Handy Eye-Interaction Adapter) miał na celu zbudowanie platformy pozwalającej na swobodną interakcję z komputerem, za pomocą jedynie wzroku. Poprzez analizę obrazu ze standardowej kamery internetowej, program ustalał strefę ekranu, na którą patrzy aktualnie użytkownik. Wraz z nakładkami na system operacyjny, będącymi integralną częścią projektu THEIA, umożliwia to pełną, a przy tym prostą obsługę komputera. OLIMPUS (Overall, Light, Interactive Multi Purpose User-interface System) jest platformą do tworzenia i integracji nowoczesnych interfejsów użytkownika z dowolnymi, niestandardowymi źródłami interakcji. Tym samym OLIMPUS upraszcza proces wytwarzania interfejsów symultanicznie współdziałających z wieloma źródłami interakcji i ich dynamiczną podmianę.