Product lines embody a strategic reuse of both intellectual effort and existing artefacts, such as software architectures and components. Third-party components are increasingly being used in product line based softwa...
详细信息
Product lines embody a strategic reuse of both intellectual effort and existing artefacts, such as software architectures and components. Third-party components are increasingly being used in product line based software engineering, in which case the integration is controlled by the product line architecture. However, the software integrators have difficulties in finding out the capabilities of components, because components are not documented in a standard way. documentation is often the only way of assessing the applicability, credibility and quality of a third-party component. Our contribution is a standard documentation pattern for software components. The pattern provides guidelines and structure for component documentation and ensures the quality of documentation. The pattern has been validated by applying and analysing it in practice. (C) 2004 Elsevier B.V. All rights reserved.
component integration is widely recognized as a process which plays a central role in overall component Based System (CBS) development. A system integrator focuses on assembling existing components, developed by diffe...
详细信息
component integration is widely recognized as a process which plays a central role in overall component Based System (CBS) development. A system integrator focuses on assembling existing components, developed by different parties, to build a software system. The integration process usually involves adapting existing component interfaces and writing new functions to handle the mismatches between stakeholder needs and available component features. The lack of detailed component documentation has been a key area of concern in CBS development due to its profound impact on the integration phase of a CBS development life cycle. In this paper, we report results of an industrial survey conducted among system integrators to understand role of component documentation in the CBS integration phase. The survey investigates whether the presence of component documentation helps a system integrator and its correlations with typical CBS integration success factors. The result reinforces current perceptions of the significance of component documentation in CBS integration. However, the lack of comprehensive component documentation presents a potential risk for a system integrator during integration effort estimation and testing processes. (C) 2011 Elsevier B.V. All rights reserved.
When designing a component, the developer holds certain usage scenarios in mind. But this is not enough. If customers do not understand the component's purpose and how its developer expected it to be used, they wi...
详细信息
When designing a component, the developer holds certain usage scenarios in mind. But this is not enough. If customers do not understand the component's purpose and how its developer expected it to be used, they will misuse it. Good documentation is the primary means of communication between a software component's creator and its users, providing insight into design intent, use cases, and potential problems. The author provides four examples that show how patterns can provide guidance on documentation content, structure, and presentation.
The use of third-party components in software system development is rapidly increasing. The product lines have also adopted this new tendency, as the COTS and OCM components are increasingly being used in product-line...
详细信息
The use of third-party components in software system development is rapidly increasing. The product lines have also adopted this new tendency, as the COTS and OCM components are increasingly being used in product-line-based software engineering. component documentation has become a key issue in component trading because it often is the only way of assessing the applicability, credibility and quality of a third-party component, especially for product lines in which the common architecture determines the decisive requirements and restrictions for components. However, at the present time there is no standard model for component documentation, and, therefore, the component documents are often inconsistent, insufficient and of various quality. The lack of a standard documentation model is thus one of the bottlenecks in component trading. The purpose of this thesis is to define the documentation requirements of software components and form a standard documentation pattern from these requirements. The documentation requirements are examined from the viewpoint of the software product lines, where the common product line architecture may define several specific requirements for a component. The standard pattern is a skeleton of documentation, defining the content and structure for component documentation. The pattern ensures the documentation that assists the integrator in successful component selection, validation, integration and use within product lines. The development of the documentation is defined by identifying the roles responsible for the documentation and associating them with the pattern. Definition of the documentation pattern is not sufficient for the adoption of a new documentation practice. An environment that supports the development of documentation is also required. This thesis also introduces the developed documentation system, which defines how the component documentation could be implemented. The system provides guidelines concerning how to document a s
暂无评论