25 research outputs found
A Model Driven Approach to the Analysis of Timeliness Properties
Abstract. The need for a design language that is rigorous but accessible and intuitive is often at odds with the formal and mathematical nature of languages used for analysis. UML and Petri Nets are a good example of this dichotomy. UML is a widely accepted modelling language capable of modelling the structural and behavioural aspects of a system. However UML lacks the mathematical foundation that is required for rigorous analysis. Petri Nets on the other hand have a strong mathematical base that is well suited for analysis of a system but lacks the appeal and ease-of-use of UML. Design in UML languages such as Sequence Diagrams and analysis in Petri Nets require on one hand some expertise in potentially two incompatible systems and their tools, and on the other a seamless transition from one system to the other. One way of addressing this impediment is to focus the software development mainly on the design language system and to facilitate the transition to the formal analysis by means of a combination of automation and tool support. The aim of this paper is to present a transformation system, which takes UML Sequence Diagrams augmented with time constraints and generates semantically equivalent Petri Nets that preserve the timing requirements. A case study on a small network is used in order to illustrate the proposed approach and in particular the design, the transformation and the analysis processes.
Black-Box System Testing of Real-Time Embedded Systems Using Random and Search-Based Testing
Embedded System Construction -- Evaluation of Model- Driven and Component-Based Development Approaches
Model-driven development has become an important engineering paradigm. It is said to have many advantages, such as reuse or quality improvement, over traditional approaches, even for embedded systems. Along a similar line of argumentation, component-based software engineering is advocated. In order to investigate these claims, the MARMOT method was applied to develop several variants of a small micro-controller-based automotive subsystem. Several key figures, like model size and development effort were measured and compared with two main-stream methods: the Unified Process and Agile Development. The analysis reveals that model-driven, component-oriented development performs well and leads to maintainable systems and a higher-than-normal reuse rate
Effective security requirements analysis: HAZOP and use cases
Abstract. Use cases are widely used for functional requirements elicitation. However, security non-functional requirements are often neglected in this requirements analysis process. As systems become increasingly complex current means of analysis will probably prove ineffective. In the safety domain a variety of effective analysis techniques have emerged over many years. Since the safety and security domains share many similarities, various authors have suggested that safety techniques might usefully find application in security. This paper takes one such technique, HAZOP, and applies it to one widely used functional requirement elicitation component, UML use cases, in order to provide systematic analysis of potential security issues at the start of system development
The Object-Oriented Protocol for Data Exchange and Control in Computational-Diverse Embedded Systems
OMAKOTITALON KUNTOARVIO JA KORJAUSSUUNNITELMA
Opinnäytetyön tavoitteena oli suorittaa kuntoarvio ja laatia sen pohjalta korjaussuunnitelma Rovaniemen Saarenkylässä sijaitsevaan omakotitaloon. Talo on rakennettu vuonna 1966. Kuntoarvioinnin tavoitteena oli selvittää koko raken-nuksen rakenteiden kunto ja suurimmat korjaustarpeet.
Kuntoarvion suorittaminen edellytti perehtymistä Korjaus RYL- ja Asuinrakennuksen kuntotarkastusopaskirjoihin, joita soveltaen kuntoarvio saatiin suoritettua. Kohdekiinteistöstä tarkastettiin rakenteet, asuintilat ja talotekniikka. Kunto-arviossa käytettiin apuvälineenä Vaisalan pinta- ja ilmankosteusmittaria. Kunto-arvio tehtiin laitteista huolimatta pääasiassa aistienvaraisesti.
Kuntoarvion tuloksena havaittiin rakennuksen olevan huonossa kunnossa sekä sisältävän useita riskirakenteita. Riskirakenteita lukuun ottamatta korjaustarpeet ovat pintapuolisia ja pelkästään ulkonäköön vaikuttavia tekijöitä. Korjaussuunnitelmassa on esitetty korjausehdotukset kaikille kunnostusta vaativille kohteille