Software Component Models

Lau, Kung-Kiu; Wang, Zheng

doi:10.1109/tse.2007.70726

Cited by 251 publications

(64 citation statements)

References 24 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“… Models where components are objects, as in object oriented programming,  Models where components are architectural units, as in software architectures [12], [13] According to the survey conducted by Lau and Wang [14] on thirteen component models presently available, it was found that those models where components are classes, the definition language for components are same as their implementation language, but in cases where components are architectural units, the definition language is an ADL or an ADL-like language and their implementation language either do not exist like in Acme [15] or have a different implementation language like in Koala. This study also reveals that there is no specific composition language for all models, some like EJB [16], [17] do not have any composition language whereas Koala [18], [19] uses connectors.…”

Section: Proposed Work and Implemenationmentioning

confidence: 99%

A New Approach of Component Based Software Development Using Incremental Approach

Bhatia¹

2017

IJARCSSE

View full text Add to dashboard Cite

Abstract-Software development has evolved from structured programming to component based software development with in between stages of structural programming and then object oriented programming before we found component based software development. Component based software development basically involves creating individual components at the same time and then integrating them. This paper intends to study various aspects of component based software development in a systematic manner.

show abstract

Section: Proposed Work and Implemenationmentioning

confidence: 99%

A New Approach of Component Based Software Development Using Incremental Approach

Bhatia¹

2017

IJARCSSE

View full text Add to dashboard Cite

show abstract

“…The run-time environment design leverages the canonical 'pipe-and-filters' software component model [12], where POSIX processes are the atomic components, and communication objects accessible through file descriptors are the connectors [13]. Like POSIX pipes, those connectors have distinguished transmit (Tx) and receive (Rx) ports that must be opened in modes O_WRONLY and O_RDONLY respectively.…”

Section: Key Design Principlesmentioning

confidence: 99%

A Distributed Run-Time Environment for the Kalray MPPA®-256 Integrated Manycore Processor

Dinechin

Massas

Lager

et al. 2013

Procedia Computer Science

View full text Add to dashboard Cite

The Kalray MPPA R -256 is a single-chip manycore processor that integrates 256 user cores and 32 system cores in 28nm CMOS technology. These cores are distributed across 16 compute clusters of 16+1 cores, and 4 quad-core I/O subsystems. Each compute cluster and I/O subsystem owns a private address space, while communication and synchronization between them is ensured by data and control Networks-on-Chip (NoC). This processor targets embedded applications whose programming models fall within the following classes: Kahn Process Networks (KPN), as motivated by media processing; single program multiple data (SPMD), traditionally used for numerical kernels; and time-triggered control systems.We describe a run-time environment that supports these classes of programming models and their composition. This environment combines classic POSIX single-process multi-threaded execution inside the compute clusters and I/O subsystems, with a set of specific Inter-Process Communication (IPC) primitives that exploit the NoC architecture. We combine these primitives in order to provide the run-time support for the different target programming models. Interestingly enough, all these NoC-specific IPC primitives can be mapped to a subset of the classic synchronous and asynchronous POSIX file descriptor operations. This design thus extends the canonical 'pipe-and-filters' software component model, where POSIX processes are the atomic components, and IPC instances are the connectors.

show abstract

“…Following previous work on ADLs (see, e.g., [8,9] for an overview), CALM's modeling primitives are based on the four fundamental categories of entities that define every component-based system: components -loci of computation, interfaces -loci of interaction, connectors -loci of communication, and configurations in which instances of components, interfaces, and connectors are allocated and connected together to form what has been termed a component assembly or system scenario. Existing ADLs tend to organize the definition and use of these elements using two modeling tiers: in the upper tier, developers define component, interface, and connector types, and in the lower tier instances of the declared types are allocated and connected to form component assemblies.…”

Section: Principles Of Calmmentioning

confidence: 99%

“…In summary, previous work has provided significant insights and innovations that have inspired our work, and space constraints do not allow a detailed comparison to each of these (for a survey of ADLs, see [8,9]). For example, [32] emphasized notions from object-oriented (OO) type systems to describe interesting concepts of component type refinement in the C2 ADL.…”

Section: Other Frameworkmentioning

confidence: 99%

A type-centric framework for specifying heterogeneous, large-scale, component-oriented, architectures

Jung

Hatcliff

2010

Science of Computer Programming

View full text Add to dashboard Cite

Middleware Model-driven development Software architecture Type systems a b s t r a c t Maintaining integrity and consistency, and effecting conformance in architectures of largescale systems require specification and enforcement of many different forms of structural constraints. While type systems have proved effective for enforcing structural constraints in programs and data structures, most architectural modeling frameworks include only weak notions of typing or rely on first order logic constraint languages that have steep learning curves associated with them and that become unwieldy when scaling to large systems.We present the Cadena Architecture Language with Meta-modeling (CALM) -that uses multi-level type systems to specify and enforce a variety of architectural constraints relevant to the development of large-scale component-based systems. Cadena is a robust and extensible tool that has been used to specify a number of industrial strength component models and applied in multiple industrial research projects on model-driven development and software product lines.

show abstract

Software Component Models

Cited by 251 publications

References 24 publications

A New Approach of Component Based Software Development Using Incremental Approach

A New Approach of Component Based Software Development Using Incremental Approach

A Distributed Run-Time Environment for the Kalray MPPA®-256 Integrated Manycore Processor

A type-centric framework for specifying heterogeneous, large-scale, component-oriented, architectures

Contact Info

Product

Resources

About