Model-Based Development of Embedded Systems

Schätz, Bernhard; Pretschner, Alexander; Huber, Franz; Philipps, Jan

doi:10.1007/3-540-46105-1_34

Cited by 62 publications

(34 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…While the use of intuitive interface (Barfield, 2004) and graphical tools is helpful for acceptance, (Schatz et al, 2002) highlights that it is not essential for the concept. Also, to perform model checking, the state machines eventually need to be converted into model checking input models.…”

Section: Translation Of Hip-hops Failure Annotations To a Refined Stamentioning

confidence: 99%

Integrated Application of Compositional and Behavioural Safety Analysis

Sharvia

Papadopoulos

2011

Advances in Intelligent and Soft Computing

View full text Add to dashboard Cite

Section: Translation Of Hip-hops Failure Annotations To a Refined Stamentioning

confidence: 99%

Integrated Application of Compositional and Behavioural Safety Analysis

Sharvia

Papadopoulos

2011

Advances in Intelligent and Soft Computing

View full text Add to dashboard Cite

“…Model-Based Development (MBD) [1] is an approach that aspires to tackle the challenge by taking RTES development into a higher level of abstraction, by using models at the center of the development process. MBD permits automatic treatments of these models with dedicated tools like for instance synthesis of system's application by automatic code generation.…”

Section: To Cite This Versionmentioning

confidence: 99%

Toward optimized code generation through model-based optimization

Charfi

Mraidha

Gerard

et al. 2010

2010 Design, Automation &Amp; Test in Europe Conference &Amp; Exhibition (DATE 2010)

View full text Add to dashboard Cite

Abstract-Model-Based Development (MBD) provides an additional level of abstraction, the model, which lets engineers focus on the business aspect of the developed system. MBD permits automatic treatments of these models with dedicated tools like synthesis of system's application by automatic code generation. Real-Time and Embedded Systems (RTES) are often constrained by their environment and/or the resources they own in terms of memory, energy consumption with respect to performance requirements. Hence, an important problem to deal with in RTES development is linked to the optimization of their software part. Although automatic code generation and the use of optimizing compilers bring some answers to application optimization issue, we will show in this paper that optimization results may be enhanced by adding a new level of optimizations in the modeling process. Our arguments are illustrated with examples of the Unified Modeling Language (UML) state machines diagrams which are widely used for control aspect modeling of RTES. The well-known Gnu Compiler Collection (GCC) is used for this study. The paper concludes on a proposal of two step optimization approach that allows reusing as they are, existing compiler optimizations.

show abstract

“…These levels of abstraction support refinement of goals and obstacles and establishment of the obstruction and contribution link among them. The refinement is fulfilled through vertical abstraction so that goals are traced by the control action for their satisfaction [SPHP02]. The more goals and risks are refined, the better it can support the risk management at early stage.…”

Section: Levels Of Abstractionmentioning

confidence: 99%

“…Artifacts are the deliverables that are produced, modified and used by a sequence of tasks as a part of the risk specification. It includes content that reflects according to the concept of a specific domain, precisely defining the used elements and their relation for specific description techniques [SPHP02,Sch]. The concept defines the elements as attribute of a specific artifact and their dependencies with other elements from another concept.…”

Section: Generic Process Modelmentioning

confidence: 99%

Software development risk management model

Islam

2009

Proceedings of the Doctoral Symposium for ESEC/FSE on Doctoral Symposium

View full text Add to dashboard Cite

Every software project by its inherent nature is unique and contains significant numbers of uncertainties from various perspectives such as time-to-market, budget and schedule estimation, product deployment or maintenance. If failing to control these uncertainties, it imposes potential risks not only during the development phases but also throughout the life cycle of the product. Software risk management is an effective tool to control these risks and contributes to increase the likelihood of project success. Risk management needs to be integrated as early as possible from a holistic perspective into the development. However a comprehensive risk management practice is not always possible due to resource problems, more emphasize on budget and schedule constraints and difficulties to concretely estimate the benefit of risk management.This thesis proposes a Goal-driven Software Development Risk Management Model (GSRM) that explicitly integrates into the requirements engineering phase. The integration provides an early warning of potential problems so that both preventive and corrective actions can be undertaken to avoid the causes of project failure. The framework is comprised of four layers, i.e., goal, obstacle, assessment and treatment, that support the identification, assessment, treatment and documentation of risks in relation to project-specific goals. GSRM is implemented in active on-going software development projects to empirically evaluate its usefulness, particular advantages and limitations in an industrial context. The results show that goaldriven approach is suitable for risk management and risk management is well integrated into requirements engineering phase. It is not always necessary to rank budget and schedule related goals and risk factors at the highest priority for risk management. At the early stage of the project risk factors related to estimation, project management, project scope, requirements, change management and human (i.e. customer/user and practitioner) and at the later stage risk factors related to user satisfaction and product usage are more frequent and severely affect meeting the project goals. If project risk factors are beyond the control of a project manager and project development environment, it is difficult to control the risks. The results conclude that early risk management practice is necessary and GSRM contributes to this direction for a successful project outcome. ZusammenfassungJedes Software-Entwicklungsprojekt ist einzigartig und geprägt von schwer planbaren Einflussfaktoren, wie time-to-market oder Budget, aber auch von Einflüssen resultierend aus der Integration und der Wartung. Die Beherrschung dieser Einflussgrößen ist unabdingbar für die Minimierung der Risiken während der Entwicklung als auch während des gesamtem Software-Lebenszyklus.

show abstract

Model-Based Development of Embedded Systems

Cited by 62 publications

References 5 publications

Integrated Application of Compositional and Behavioural Safety Analysis

Integrated Application of Compositional and Behavioural Safety Analysis

Toward optimized code generation through model-based optimization

Software development risk management model

Contact Info

Product

Resources

About