Software industry is moving towards a component-based development but more research is still needed for reliable and efficient software components. The objective of this work is to propose an approach to developing software components of the system from use cases. This approach consists of four stages and is based on the decomposition of use cases into elementary actions and the factorization of the past for system software components. General TermsEngineering based software components; Software Components Approach

The interest behind the use of component based software engineering is to divide an information system in subsystems with less complexity, the reduction of time, faster development, and enhancing the productivity. The software systems are developed by assembling components which are software units that offer a set of services exposed as interfaces. The indispensable role of component-based development is the component model that defines how components can be built and how they can be assembled. A component is intended to provide specific services as the management of the combination and the communication between the system units. The Manager Component is an important and complementary paradigm for the development of software systems. The functionalities that it encapsulates must be related and consistent. The model presented in this paper proposes a component called Manager Software component based on the viewpoint (vision of each system user and actor) by the assembly of Base Component and system components.

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.

The complexity of information systems leads to poor data management and therefore bad decisions. The advantage of using component-based software engineering is to divide an information system into subsystem blocks with less complexity. In fact, a component is intended to provide specific services as management of the combination and communication between the units of the system. This chapter addresses this problem by developing information systems, proposing a component identification approach and the management pattern for data management. In this work, three developed views are taken into account, which include modelization and the design to achieve the purpose of defining and building the components and how they can be assembled. A component is intended to provide specific services, as a combination and communication management between the system units, and the manager component is the important and complementary paradigm pattern and added value for the development of software systems.

The software industry is moving towards development, modeling and building software components and research is still needed to provide reliable and effective software components. All the components of a system meet the defined and common goals of the system, which requires a modeling method, to achieve these system goals. The focus of this approach is on systems development by identifying the set of system components and their interfaces from use cases. This approach consists of three phases based on the cutting process in the system into a modeling component representing a logical grouping of use cases that achieves a given work, the component modeling cutting in parts, and cutting the use case in activities to develop the component interfaces. This is where the authors proposed a new shcema, to get final system software components.