No abstract

this paper presents principles for model based testing of embedded systems with use of critical knowledge about system and their environment. For critical knowledge representation UML models can be used. These properties have different priority, impact, dependency, which creates different situations for testing. Critical properties mentioned in this article can serve as input for generating test cases. V-model, as a well known model, provides another approach for representing critical properties of software architecture and testing embedded systems. This model is often used in medical projects, e.g. radiotherapy. Some principles are taken from radiotherapy software project in Siemens Healthcare. Tracing of critical properties in V-model is also part of this article. Keywords-critical knowledge, model based testing, embedded systems, UMLI. MOTIVATION The progress in technological solutions allows designing, implementing and using systems in various spheres of everyday life. Except of information and control systems are becoming popular various embedded systems working in specialized hardware architectures, with specialized operating systems and using specialized peripherals developed for a specific application domain. As an example of these systems used for medical purposes can be radiotherapy.These kind of embedded medical systems are developed by top-down method. V-model is a frequently used model for these cases. Figure 1. V-model The main parts of this model (Figure 1. ) are creating requirements of developed system, analysis, detailed design, implementation and multiple types of testing. Each type of testing on the right side of V-model is binded with a specific phase of software life cycle on the left side of a model (e.g. unit tests are created based on design specification and integration tests are created based on requirement specification).First step of this implementation type is the analysis of requirements with the goal to identify critical properties of final system. Those are the properties, which have high impact on the success of a system. These are especially outer properties such as safety, reliability, userfriendliness (in case of interactive systems) and adapting communication protocols of embedded systems with communication protocols of peripherals or technological devices, where communication is required.Critical properties are regarding to architecture of final system, ways of accessing required processes, data and control flows. All these identified critical properties represented with convenient models together with acquired relevant experiences of managers, analytics, designers, programmers and testers are creating critical knowledge, which usage in software life cycle is crucial. One area of using this knowledge is testing of systems.To identify critical requirements of embedded system in whole model, special keys are introduced. These keys accomplish one basic property -traceability. It is assured that the requirement is fully implemented and tested from the beginning to the end of V-m...

No abstract

Nowadays, knowledge about design and implementation models of current version of software system and also knowledge about application domain of software system are important for software engineering processes related to design, management, maintenance and modification of software system. Utilization of proper knowledge can streamline and speed up each phase of software system life cycle and increase quality of outcome software and length of its operation. This paper briefly analyzes types of knowledge which could be utilized in software development and maintenance process and the ways how they can be acquired and stored. Proposed modeldriven maintenance is based on utilization of knowledge acquired from abstract models of software system, which could be used as easy readable and understandable source of essential knowledge for maintenance process. The paper also analyzes the need of representing the knowledge about application domain in form of ontologies and the possibilities of using OMG specification of Ontology Definition Metamodel as a basis for development of these ontologies.

Software maintenance presents nowadays one of the most critical phases of software system life cycle. Constant changes of system's requirements or changes related to occurrences of system defects caused that thorough system understanding in order of efficient realization of system's modifications becomes now an inevitable part of maintenance process.In this paper, we emphasize the importance of system's comprehension in the context of an early detection of system's defects by offering the description of its life cycle and classification, but mainly by introducing the principles of architectural knowledge concept. We also propose a new approach of dealing with one of the currently most serious obstacles inhibiting this concept from its further use -the problem of architectural knowledge automatic acquisition.Index Terms-Knowledge, software defect life cycle, software maintenance, architectural knowledge, architectural knowledge acquisition process.