A component-based methodology for embedded system prototyping

Tessier, Patrick; Gérard, Sébastien; Mraidha, Chokri; Terrier, François; Geib, Jean-Marc

doi:10.1109/iwrsp.2003.1207024

Cited by 14 publications

(7 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Global position system (GPS) (The GPS system is used to guide the driver to a chosen destination through a remote service provider such as a network.) which has been presented in [35] as well as in [48]. The component specification architecture of GPS system is shown in Fig.…”

Section: Incorporating the Proposed Metrics Into A Web-based Cbss Appmentioning

confidence: 99%

Multidimentional size measure for design of component-based software system

et al. 2012

View full text Add to dashboard Cite

The motivation of this study is to bridge the gap between component providers and component users, especially in the area of component evaluation, using component information flow (CIF) measurement and multidimensional approaches for measurement interpretation. By measuring the design of component-based software systems (CBSS), software designers, testers and maintainers may be able to locate weaknesses in the system design and to estimate the effort required to test as well as the cost of maintenance. This study proposes a CIF based on inter-component flow and intra-component flow. Moreover, a set of metrics based on the CIF was developed to characterise and evaluate the effect of the component design size on the quality of CBSS design. The theoretical evaluation results indicated that the proposed metrics are valid size measures. An application that demonstrates the intuitiveness of the mentioned approach is also presented. Results show that multidimensional analysis of design size appears promising as a means of capturing the quality of the CBSS design in question.

show abstract

Section: Incorporating the Proposed Metrics Into A Web-based Cbss Appmentioning

confidence: 99%

Multidimentional size measure for design of component-based software system

et al. 2012

View full text Add to dashboard Cite

show abstract

“…Then we would have to provide tools to go along our development process and help the designer by checking composition operation and refinement operation while investigating on how to enhance a UML based development methodology [16] to integrate our approach.…”

Section: Conclusion and Considerationsmentioning

confidence: 99%

Could UML and Contract tackle heterogeneity?

Lagarde

Terrier

André

2006

2006 International Symposium on Industrial Embedded Systems

View full text Add to dashboard Cite

Embedded systems integrate more and more heterogeneous subsystems. This situation leads to consider on the one hand heterogeneity owing to different formalisms and on the other hand heterogeneity created by platforms in charge of realizing the system. To deal with formalism heterogeneity some modeling frameworks handle different formalisms or project them onto a pivot. Nevertheless these solutions are often not sufficient. This paper presents ongoing works on a development process using Unified Modeling Language (UML) enhanced by a contract approach borrowed from the Interface Automata modeling. The objectives are twofold: (a) provide coherent views of a component along its refinements, (b) specify their interactions. ContextFace to ever increasing competition, industries integrate more and more heterogeneous subsystems, making products drastically more and more complex and, consequently, hard to preserve within a unified development process. The traditional main phases observed along the lifecycle process -design, implementation and validation & verification-are being ever harder to respect.The design stage depicts the system by means of formalisms as for example the so-called Model Of Computation (MoC) [1]. As a MoC is foremost a model that precisely describes how computation is done, many MoCs are available fitting to specific modeling concerns. Janstch and Sander [2] classify them according to their time expressiveness: timed models (e.g., continous-time, discretetime, synchronous) or untimed models (for instance, data flow, causal models with FSM, CSP). When it is possible, analysis and simulation tools can be executed on these models to determine system features such as a sampling rate or to early detect deadlocks.Common modeling tools (e.g., Matlab, Scilab, Modelica) can produce code from these models for target platforms. These codes can be compiled to get prototypes. In an ideal process, when the overall system can be modeled within a unique modeling framework, the difference between prototype and production can be slight. Nevertheless this process is not a common practice. A universal modeling framework able to deal with the overall system (regardless of the domain and external constraints) does not exist. Thus, implementation of these models is often realized piece by piece in an ad hoc fashion with manual implementation of interaction mechanisms. This paper investigates on introducing a contract approach to enhance continuity along software process development within a UML environment.The paper structure is as follows: Section 2 presents related work dealing with heterogeneous MoCs, Section 3 introduces our approach. Finally, we conclude with preliminary considerations and perspectives. Related works 2.1. Heterogeneous frameworkA heterogeneous framework aims to deal with different MoCs in a unified environment. The designer is free to choose the MoC fitting his/her specific modeling concern as much as possible. These frameworks are usually dedicated to hybrid system modeling. For example the Mat lab e...

show abstract

“…Component-based embedded software development [1,2] is now becoming a hot spot in software engineering. By designing and reusing software component to construct the complex software system, it enhances the efficiency of software development and improves the quality of the software.…”

Section: Introductionmentioning

confidence: 99%

A Scenario Based Modeling Method for Component-Based Embedded Software

Ibrahim¹,

Choi²,

Hashmi³

2007

2007 International Conference on Convergence Information Technology (ICCIT 2007)

View full text Add to dashboard Cite

The scenario-based specification and modeling techniques have been considered as the basic activities in modern software development .This paper considers the problem of designing component-based embedded software model based on timing scenario-based specifications. Firstly the formal model of UML sequence diagram is introduced, then the timing scenario-based specifications are specified by timed sequence diagram template(TSDT) which is a UML sequence diagram extended with a set of time interval between actions along the lifeline of the sequence diagram ,finally message passing automata is extended with time clocks, and based on timed sequence diagram template ,the design model of the componentbased embedded software is constructed by the timed message passing automata(TMPA). we have connected the TSDT with the TMPA, so it is convenient to transform from the requirement specification model to the design model .

show abstract

A component-based methodology for embedded system prototyping

Cited by 14 publications

References 16 publications

Multidimentional size measure for design of component-based software system

Multidimentional size measure for design of component-based software system

Could UML and Contract tackle heterogeneity?

A Scenario Based Modeling Method for Component-Based Embedded Software

Contact Info

Product

Resources

About