Software Component Technology: Concepts, Design, and Management Method

Software Component Technology: Concepts, Design, and Management Method

Fadoua Rehioui (University Soultan Moulay Slimane, Morocco)
Copyright: © 2021 |Pages: 17
DOI: 10.4018/978-1-7998-3479-3.ch039

Abstract

The data gives the key to make the decisions and the complexity of the information from the leads to the bad decisions. There it needed a method for improvement as a result of the amount of this data. This chapter discusses the developing of information systems, by their data, information, and the knowledge resulted by proposing a component identification approach and the management component for data management. The advantage of using component is to manage the information system by dividing it to several parts with less complexity.
Chapter Preview
Top

Introduction

Data and Knowledge are at the level of all organizations. Due to the amount of data generated, companies require different analyzes, supporting data-driven decision making (Nimmy et al., 2017). Well-organized management of data and knowledge are the key to the success science related data and then the almost of any enterprise.

The issue of data and knowledge management (Ermine and al., 1996) has been defined as the implementation of a management system that allows all components of the company (Brunet et al., 1994) to use and enrich knowledge and to consider this heritage of knowledge as the same subject of the information system of the company (Ermine, 2000). As a result, the technological revolution has brought about a change in the way information/data is collected (Kamal et al., 2017) and treated and so the implication of the Components.

Any conventional design of complex software systems always starts with the identification of the system in parts (subsystems, blocks, class, etc.) where the idea and the concept of the components come from, i.e. the decomposition of the system is to bring out the parts which are interested. It is no coincidence that the notion of component gives a great interest in the development of complex systems.

Certainly, the importance and usefulness of components in scientific research are not new topics, especially in the reuse of components. Formerly, this work focuses on the complete definition of component-based information systems approach design.

The idea of component-based development is introduced by defining the concept and providing its management. The approach primarily seeks to explain and analyze and manage the variety of data and information exchanged in a company. This method is useful for a global vision of the company's system, using phases and steps designed tailored to the needs. This represents a lot of “Components” not yet developed in implementation.

The difficulty is to design the components and the services most relevant to the goals. Design requires a method for modeling that involves creating a virtual representation in such a way as to bring out the goals interested in and build upon.

In fact, there is no standard for modeling a component-based system, so it is necessary to try to propose a component identification approach, and an approach to illustrate the management of a software system.

The objectives of this chapter the contribution of a new solution of the method based on software components, and a communication management approach between these identified software components mediators between the components and the information system. Hence, the idea that software systems can be developed by components intended to provide specific services such as combining, managing, connecting and communicating between system units.

This paper is organized in separate paragraphs and sections, distributed as follows:

  • Section 2: Provides definitions incorporating general discussions on Data Management and Component Development, presents the state of the art (literature review).

  • Section 3: formalizes the model of the proposed approaches.

  • Section 4: presents the different elements of the technology served in this area.

  • Conclusion: The paper ends with a conclusion.

Top

Background (Section 2)

Commonly, a system processes the data with a set of actions from a huge store of information and then invoking the input / output functions. A computer system has the function, in a very general way, of processing information. One of the first difficulties is to define the notion of information and in particular to delimit it in relation to related notions such as data and knowledge. Knowledge is used all the time and on many occasions, it refers to information. The difficulty of defining knowledge comes from its relationship to two concepts, data and information. Data are not organized in any way and provide no further information. As a result, data, information and knowledge are defined as follows:

The first concept to meet is the data which is a raw element not yet explained or guessed. The contextualization in an interpreted data, by creating one or more added values, generates information (Davenport & Prusak 2000).

Key Terms in this Chapter

Component: It is a data concept informally corresponding to a list of activities, providing the business functionality of the system.

Base Component: It is the first common component that includes the features and common functionalities between the different components, accessible by every user, also called default component because it is the unique component that is activated when no component of the system is enabled.

Management Component: Mediator component to manage all operations and to react and interact with other components. Its role is the management of all associations and links existing between a base component and the other subordinate system components, the management of the ability to communicate units.

Knowledge: Knowledge is contextual information that provides an environment and framework for evaluating and making decision and information. In organizations, it often becomes implanted in documents, practices.

Subordinate Component: Is performed by a structure consisting of the interfaces offering or requesting some data from the base component of the application.

Modelization: The process of modeling, constructing on the base of the function should give the functional modelization of the system, based on the conceptual function.

EJB Component: It’s this type of component that is particularly interested in business requirements through remote objects. These EJBs serve as an intermediary between windowed applications, or web applications, and the database.

Data: Facts and numbers which relay something specific, but which are not organized in any way and which provide no further information.

Information: when data become contextualized, calculated, its called information.

Complete Chapter List

Search this Book:
Reset