China
Africa
Explore chapters and articles related to this topic
Identification and Construction of Reusable Components from Object-Oriented Legacy Systems Using Various Software Artifacts
Published in Ankita Bansal, Abha Jain, Sarika Jain, Vishal Jain, Ankur Choudhary, Computational Intelligence Techniques and Their Applications to Software Engineering Problems, 2020
Amit Rathee, Jitender Kumar Chhabra
Component modeling and transformation is another research field and is only targeted by few researchers. Lau et al. (2005) presented a taxonomy related to different software component models. Song et al. (2002) proposed a code analysis approach that converts identified components from the underlying Java Servlet source code to Enterprise JavaBeans components. Washizaki and Fukazawa (2005) proposed a refactoring technique for converting a Java software to its equivalent JavaBean system using the class relations-based dependency graph and Façade interfaces. Allier et al. (2011) reported a transformation technique for converting Java application to the OSGi component model standard using software design patterns, namely, Adapter and Façade.
Introduction to the CD++ Toolkit
Published in Gabriel A. Wainer, Discrete-Event Modeling and Simulation, 2017
SimBeams [16] is a component-based software architecture based on Java and JavaBeans. The idea is to provide a set of layered components that can be used in model creation, result output analysis, and visualization using DEVS.
Service-oriented invisible numerical control application: architecture, implementation, and test
Published in International Journal of Production Research, 2022
Lisi Liu, Yingxue Yao, Jianguang Li
The platform-dependency of component and the heterogeneity of component model. Component depends on a client platform (or a middleware or a framework) because it interacts with the client by direct language-level method call (Erl et al. 2017). Moreover, component depends on a component model to define standards for component implementation, documentation, and development (Crnkovic et al. 2010). Microsoft Component Object Model (COM) (Ma et al. 2007; Michaloski et al. 2000), .NET assembly (Sun et al. 2017), Java-based component models (e.g. JavaBeans, J2EE, etc.), CORBA Component Model (CCM) (Zhang, Guo, and Lan 2006), and IEC61499 function block (FB) (Li et al. 2010; Minhat et al. 2009) are widely used to build CNC components. In addition to these off-the-shelf component models, some CNC-specific component models have been designed to build CNC components (Du et al. 2009; Du and Yu 2009; Li, Zhou, and Tang 2004). But it is impossible for components developed using different component models to work together (Sommerville 2016). For instance, a .NET assembly and a JavaBeans fail to interact within a process boundary. In this sense, componentized CNC modules are not good at portability and interoperability. And, the secondary development of component-based open CNC applications is often constrained by a specific component model (or platform/framework). For instance, custom CNC components coupled to TwinCAT3 should conform to TcCOM, a component model designed by Beckhoff in light of COM (BECKHOFF 2019). Moreover, component models like CCM and COM have too large specifications to completely implement, and they are kind of outdated (Henning 2006; Sommerville 2016).