Software Engineering : Design Rules For All Components

935 Words4 Pages
In software engineering, requirements from user met with available components, then following activities needs to be performed
1) Component Qualification: System requirements and architecture define the components that will be required. Reusable components (whether COTS or in house) are normally identified by the characteristics of their interfaces. That is, “the services that are provided, and the means by which consumers access these services” are described as part of the component interface. But the interface does not provide a complete picture of the degree to which the component will fit the architecture and requirements. The software engineer must use a process of discovery and analysis to qualify each component’s fit. 2) Component Adaptation: we noted that software architecture represents design patterns that are composed of components (units of functionality), connections, and coordination. In essence the architecture defines the design rules for all components, identifying modes of connection and coordination. In some cases, existing reusable components may be mismatched to the architecture’s design rules. These components must be adapted to meet the needs of the architecture or discarded and replaced by other, more suitable components.

3) Component Composition: Architectural style again plays a key role in the way in which software components are integrated to form a working system. By identifying connection and coordination mechanisms (e.g., run-time properties
Get Access