Preferencje help
Widoczny [Schowaj] Abstrakt
Liczba wyników

Znaleziono wyników: 3

Liczba wyników na stronie
first rewind previous Strona / 1 next fast forward last
Wyniki wyszukiwania
Wyszukiwano:
w słowach kluczowych:  activity diagram
help Sortuj według:

help Ogranicz wyniki do:
first rewind previous Strona / 1 next fast forward last
EN
Modelling of all aspects of logic controller in design phase is very important. The paper presents handling of possible exceptions with usage of two specification techniques – UML activity diagrams and control interpreted Petri nets. Sample control process of transportation of friable goods is a base for further discussion about complexity of exception handling in each technique. Furthermore, the target is to model exceptions with usage of standard syntax of each technique.
PL
Szczególnie ważnym etapem procesu projektowania sterownika logicznego jest modelowanie poszczególnych jego perspektyw. Artykuł przedstawia możliwość reprezentacji obsługi wyjątków z wykorzystaniem dwóch technik modelowania – diagramów aktywności języka UML oraz interpretowanych sieci Petriego sterowania. Aspekty modelowania obsługi wyjątków dla obu wymienionych technik zostały zaprezentowane na przykładzie specyfikacji procesu sterowania transportem materiałów sypkich. Dodatkowo, celem jest zrealizowanie obsługi sytuacji wyjątkowych z wykorzystaniem tylko i wyłącznie standardowych elementów obu technik modelowania.
2
EN
The paper concerns models with time dependencies that can be used in modelling dynamic reliability and complex maintenance processes. Emphasis is put on models that have been elaborated with authors participation. The following models are presented: fault trees with time dependencies, probabilistic fault trees with time dependencies, reliability enhanced activity diagrams. The above models are illustrated by examples. Both types of fault trees are used in modelling the time coordination of distance protections in high voltage transmission line. Then reliability enhanced activity diagrams that express the maintenance process of computer system with redundant components. Components are submitted to failures and repairs.
3
Content available remote Formalization of functional requirements in software development process
EN
In this paper, we propose to establish traceability of functional requirements expressed in a SRS document in analysis and design phase that goes down to the coding phase. UML has become a de-facto standard for modeling object-oriented systems. To ensure traceability of requirements in different phases of software lifecycle, it is also mandatory to ensure consistency between different UML diagrams used in those different phases. Here, after specifying some rules to trace requirements and verify consistency, we formally represent functional requirement UML Use case diagram, and some other UML diagrams that are widely used for analyzing and designing object-oriented systems, using Z notation. At the end we represent the formalized functional requirement and the UML diagrams along with their relationship visually using Entity-Relationship (ER) diagram. Implementation of our approach would bridge the gap between a formal language, which is mathematical and difficult to understand and UML that is visual and easy to comprehend. Development of a tool based on this approach would generate a visual representation of formalized functional requirements and their traceability among different UML diagrams, from which automated traceability of requirement in different phases of software development and consistency verification between different UML diagrams can be achieved.
first rewind previous Strona / 1 next fast forward last
JavaScript jest wyłączony w Twojej przeglądarce internetowej. Włącz go, a następnie odśwież stronę, aby móc w pełni z niej korzystać.