Abstract
Component-based software engineering (CBSE) / Component-Based Development (CBD) lays emphasis on decomposition of the engineered systems into functional or logical components with well-defined interfaces used for communication across the components. Component-based software development approach is based on the idea to develop software systems by selecting appropriate off-the-shelf components and then to assemble them with a well-defined software architecture. Because the new software development paradigm is much different from the traditional approach, quality assurance for component-based software development is a new topic in the software engineering research community. Because component-based software systems are developed on an underlying process different from that of the traditional software, their quality assurance model should address both the process of components and the process of the overall system. Quality assurance for component-based software systems during the life cycle is used to analyze the components for achievement of high quality component-based software systems. Although some Quality assurance techniques and component based approach to software engineering have been studied, there is still no clear and well-defined standard or guidelines for component-based software systems. Therefore, identification of the quality assurance characteristics, quality assurance models, quality assurance tools and quality assurance metrics, are under urgent need. As a major contribution in this paper, I have proposed QAM: Quality Assurance Model for component-based software development, which covers component requirement analysis, component development, component certification, component architecture design, integration, testing, and maintenance.
Highlights
Component-based software systems (CBSS) are developed by selecting and assembling various components together rather than programming overall system from scratch: this is the differentiation between the life cycle of component-based software systems and life cycle of traditional software systems
Because component-based software systems are developed on an underlying process different from that of the traditional software, their quality assurance (QA) model should address the process of components and the process of the overall system
We conclude that COSD is a promising discipline to be considered as one of the alternatives to promote software evolution and to improve the software development process of currently complex systems with the help of our proposed QAM: Proposed Model for Quality Assurance in CBSS
Summary
Component-based software development (CBSD) has become one of the preferred streams for developing large and complex systems by integrating prefabricated software components that facilitates the process of software development but is changing the ways for software professionals to develop software applications [1]. Component Requirement Analysis Phase is the first stage in the software development process. Component development consists of four procedures: Implementation: In this phase, input is the component requirement document on the basis of which the draft structure of component is devised and submitted to procedure of function testing. The input to this phase should be component development document, and the output should be testing documentation for system maintenance. After the analysis of the component requirement document, component certification document is created that is integrated with component architecture to create a testable component specification document This phase consists of: Requirement gathering: The input to requirement gathering stage is the format/structure of requirement document template. As the output of this phase, a new version can be produced for system testing phase for a new life cycle
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: Advances in Science and Technology Research Journal
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
