Article Preview
Top1. Introduction
During the development of a software project, it must be defined a method of analysis, design and development of software modules. The 'software component', by analogy with the components used in the electronics industry, by use and interconnection is old but its feasibility on a large scale is recent.
The researches are still needed to provide reliable and effective software components. In fact, there is no standard for modeling a component-based system. It is therefore necessary to try to propose an approach based on use cases that illustrate the functional behavior of a software system and for the identification of its components (Rehioui, 2018).
Modeling components from use cases envisages the precision of development and specific identification of the components. Use cases are models that ensure the coherence of the components development process and the connection to the system architecture.
A component is characterized by a set of provided interfaces that include all the services offered by a component to other components. As for the required interfaces, they contain the services they need to operate. Generally, a component interface is a set of functional and non-functional properties that are outside of the component.
This paper aims to present the process of software components development based on use cases and identifying the interfaces of these components. The proposed method is limited to the level of design and modeling.
The following section presents the related work of engineering methods based on software components. Section 3 is devoted to the presentation of the proposed approach and its different phases. Section 4 formalizes the model of the proposed approach and its implementation on a library management case study.
Finally, conclusion and perspectives.