China
Africa
Explore chapters and articles related to this topic
Introduction to Software Engineering and Component-Based Software Engineering
Published in Umesh Kumar Tiwari, Santosh Kumar, Component-Based Software Engineering, 2020
Umesh Kumar Tiwari, Santosh Kumar
Component-based software engineering (CBSE) is an elite form of software engineering that offers the feature of reusability. Reuse of software artifacts and the process of reusability make CBSE a specialized software development paradigm. Its philosophy is “buy, don’t build.” CBSE reuses pre-constructed and available software constructs rather than developing them from the beginning (see Figure 1.10). The basic idea is to develop a component (including classes, functions, methods and operations) only once and reuse it in various applications rather than re-constructing it every time. Reusing pre-developed and pre-tested components make the development life cycle shorter, helps to increase the reliability of the overall application and reduces time to market.
Robot Programming
Published in Marina Indri, Roberto Oboe, Mechatronics and Robotics, 2020
Christian Schlegel, Dennis Stampfer, Alex Lotz, Matthias Lutz
Component-based software engineering (CBSE) [15] is an approach that has arisen in the software engineering community in the last decade. It shifts the emphasis in system-building from traditional requirements analysis, system design, and implementation to composing software systems from a mixture of reusable off-the-shelf and custom-built components. Software components explicitly consider reusable pieces of software, including notions of independence and late composition [44]. Composition can take place during different stages of the life-cycle of components; that is, during the design phase (design and implementation), the deployment phase (system integration), and even the run-time phase (dynamic wiring of data flow according to situation and context). CBSE is based on the explication of all relevant information of a component to make it usable by other software elements without the need to get in contact with the component provider. The key properties of encapsulation and composability result in the following seven criteria that make a good component: (i) may be used by other software elements (clients), (ii) may be used by clients without the intervention of the component’s developers, (iii) includes a specification of all dependencies (hardware and software platform, versions, other components), (iv) includes a precise specification of the functionalities it offers, (v) is usable on the sole basis of that specification, (vi) is composable with other components, and (vii) can be integrated into a system quickly and smoothly [22]. An overview on CBSE in robotics is given in Brugali and Scandurra [5] and Brugali and Shakhimardanov [6].
An Introduction to Component-Based Software Systems
Published in Kirti Seth, Ashish Seth, Aprna Tripathi, Component-Based Systems, 2020
Kirti Seth, Ashish Seth, Aprna Tripathi
The development of systems based on components starts with a range of pre-existing parts. The components are embedded with some restrictive code in the frame that holds them together. This code is called the “glue code”. Object orientation (OT) has a similar methodology; objects are interchangeable components that can be combined into programs. OT is not appropriate for component-based software engineering (CBSE). OT does not pass on the use’s relationship, which is important for CBSE. OT express “has an” and “is a” association. Components pass on the condition in which they will work by demonstrating what framework assets the segment needs to work appropriately. OT for the most part does not back up this kind of idea. A component need not be a thing; it might just be a capacity or an executable program which is not treated as an object. In any case, regardless of whether items (or classes) cannot be seen as a feature of the plan, they are reusable segments and OT inventiveness can be utilized successfully to upgrade parts. Object-oriented design (OOD) structures are increasingly favored for upgrading programming contrasted with publications. Structures are software components containing objects related with, and in a described setting by, shared relationships. A Framework portrays a utility that is at a more significant level of abstraction. The motivation behind why Frameworks are favored over articles is that objects can, as a rule, have more than one occupation in more than one condition; OOD systems can do that, and OOD structures can get this; however, existing OOD techniques cannot. The last use classes or items as the essential unit of structure or reuse, and depends on the customary perspective on an article, as appears in Figure 1.1 which views an article as a closed substance with one fixed job.
A hybrid re-composition based on components and web services
Published in International Journal of Computers and Applications, 2020
Khadidja Bentlemsan, Djamal Bennouar, Dalila Tamzalit, Khaled Walid Hidouci
Component-based software engineering (CBSE) is meant to develop software systems so that the final applications can be created by using existing reusable software entities called components [1]. CBSE provides the facility of reusability, ensures controllability of the application, reduces the effort for effective management of complexity, and raises competition in the market to enhance the quality of components. But, it is still being rigid with very complicated reconfiguration.