Wyniki wyszukiwania - BazTech

1

Nowoczesne technologie projektowania systemów automatyki

Pauluk Mariusz

Pomiary Automatyka Robotyka

|

2020

|

R. 24, nr 4

85--91

PL

W pracy omówiono stosowane obecnie techniki wytwarzania systemów automatycznej regulacji. Rozpoczęto od przybliżenia stosowanych w inżynierii oprogramowania pojęć: kryzys oprogramowania, katastrofa oprogramowania oraz cykl życia oprogramowania. To ostatnie zostało w kolejnych rozdziałach poszerzone o najbardziej popularne modele wytwarzania oprogramowania. Następnie przybliżono na bazie modelu V rolę weryfikacji i walidacji w cyklu życia oprogramowania i sterownika oraz przedstawiono techniki testowe stosowane w walidacji sterownika. Są to testy typu: oprogramowanie w pętli, procesor w pętli oraz sterownik w pętli. Ostatni rozdział opisuje technikę projektowania systemów automatyki w oparciu o zaawansowane modele matematyczne Model Based Design.

EN

The paper presents the currently used techniques for the development of the automation control systems. It begins with the introduction of the concepts used in software engineering: software crisis, software disaster, and software life cycle. The subsequent chapters extend the latter by including the most popular software development models. Then, based on the V model, the role of verification and validation in the software and controller life cycle is presented, and the test techniques used in the controller validation are given. These test types include: software in the loop, processor in the loop, and controller in the loop. The last chapter describes the technique of designing automation systems based on the advanced mathematical models Model-Based Design.

2

Pojęcie, modele i metryki jakości oprogramowania – przegląd

Horobets Y., Miłosz M.

Journal of Computer Sciences Institute

|

2017

|

Vol. 4

92--98

PL

W artykule przedstawiono analiza istniejących modeli i metryk pomiaru i oceny jakości oprogramowania. Do porównania zostały wybrane następujące modele jakości oprogramowania: McCalla, Boehma, Boeinga, FURPS, Dormey’a, ISO/IEC 9126, ISO/IEC 25000:2005 oraz metryki oprogramowania: SLOC, McCabe’a, Halsteada.

EN

The article presents analysis of existing models and metrics measurement and software quality assessment. For comparison were chosen following models of software quality: McCall, Boehm, Boeing, FURPS, Dormey, ISO / IEC 9126, ISO / IEC 25000: 2005 and software metrics: SLOC, McCabe, Halstead.

3

Models of IT project management implementation and maintenance

Plichta A., Szomiński S.

Information Systems in Management

|

2016

|

Vol. 5, No. 1

88-98

EN

The process of software development has become so dynamic that it nowadays requires more and more supporting tools. An organization which intends to have such tools implemented must take into account its possible future needs. Complex solutions usually offer greater variety of available options and functionalities but are costly to implement. This paper presents some models o IT project management together with the supporting software. Owing to applying the resource management policy at the stage of production and implementation one may assess the risk and identify potential threats. The discussed issues may shed some light on potential difficulties occurring at the particular stages of software production management whereas the conclusions may help people in charge choose the best model, including its implementation strategy. The first model are dedicated tools created from scratch and often preceded by the analysis of the existing solutions and the needs of the company and the customers. The second is to seek from the very beginning multifunction and complex tools for the big or well-developed IT systems providers. This article is to present the models regarding the IT project management (together with the related supporting tools) which are applied in the IT companies involved in providing the foreign customers with the bases of knowledge. On the basis of the experience gained while designing and developing dedicated software (by means of the above-mentioned tools) and its implementation one drew some conclusions concerning e.g., risk assessment; potential threats at every stage of the project lifecycle; improvement of the quality and production time of the software; reduction of the number of errors; improvement of the internal communication within the project team (it is the first step in the development of the design patterns). The patterns should help the managers choose the proper management model and related tools for the implementation and particular project tasks.