Citation Context

...d in product lines testing. Literatures Table 5.7: Hints from literature search. No Investigated book(s) Selected Book 1 Software Product Lines: Practices and Patterns 1 1 2 Lerma [76] 1 1 3 Cockburn =-=[44]-=- 1 1 Total 3 3 Use cases can be use to develop test case by going through the steps below. Capture requirements for systems. Define requirements model for software systems including software product l...

Citation Context

... and cost. 25sCHAPTER 3 26s3 PRODUCT LINES TESTING PROCESS 3.1 INTRODUCTION Software product line goal is to increase reuse of software, increase quality and decrease maintenance and development cost =-=[3]-=-. It improves the quality of product that is developed from product lines to ensure that customers are satisfied with products in terms of reliability and correctness of products. To make sure these g...

Citation Context

...le process, where new systems within a given domain are built from existing parts constructed to be reuse [110]. Software product line consists of family of products software that has common features =-=[111]-=-. Product line basic concept is that similar products share a common set of components and functionality called core assets, though, individual products have some functionality specific to it, called ...

Citation Context

...1 3 1 2 4 2 3 4 1 4 6 2 5 3 1 Total 20 7 Articles selected from IEEE database search. Poston et al. 1992 [28] Chaver at el. 1998 [58] Agresti et al. 1987 [61] Basili et al 1990 [67] Boehm et al. 1988 =-=[68]-=- Mayrhauser et al. 1994 [70] Mayrhauser et al. 1994 [71] 57sThe general concept shared by selected articles is that; create test cases as part of reusable software artefacts in domain engineering and ...

Citation Context

...f journals, proceedings, projects, and Internet resources related to the research. Kitchenham systematic review procedure is adopted in conducting our research. The steps in the process are as follow =-=[20]-=-: Introduction Work Background Research Method � Identification of research � Selection of studies � Quality assessment of primary studies � Data extraction procedures � Data analysis Each of these st...

Citation Context

...t lines testing process that is domain engineering and application engineering. The activities include: requirements analysis, design, components testing, integration and system testing. Weyuker 1998 =-=[119]-=-, listed all product lines artefacts that can be tested. They include requirements, architecture, components and test documents. These artefacts were described as the activities in software product li...

Citation Context

...ct lines therefore depends on product lines core assets developed in domain engineering. Product lines framework has two key engineering processes: domain engineering and application engineering [50] =-=[104]-=-. The framework is defined based on experiences and the results of European SPLE research projects ESAPS, CAFA. [104]. The framework show the process and the general domain engineering activities and ...

Citation Context

...nformation for selecting COTS product [100]. They developed criteria for certifying components to develop product lines. In addition to the techniques to verify and certify components for reuse, Voas =-=[101]-=- presents black box testing methodology to determining the quality of off the shelf (OTS) components. According to [101], the methodology provides developers with information useful for choosing compo...

Citation Context

... [52][61]. Software reuse can help reduce maintenance costs due to that fact that, when reusing quality software the time and effort required to maintain the software will be reduced drastically [29] =-=[67]-=-. Software component reuse in development is classified into two directions and types [64]. The first one is development for reuse and the second type is development with reuse [63] [66]. Development ...

Citation Context

...Test cases 55sThe reuse of software artefacts across multiple projects and product is a good strategy to improve software development efficiency towards increasing the quality of software development =-=[56]-=- [58] [59]. The major motivation for reuse of software artefacts is that it decreases the development cost for software and reduce the human effort and time required to build improved software by reus...

Citation Context

...n a product line organization encompasses activities from the validation of the initial requirements model to verification activities carried out by customers to complete the acceptance of a product.”=-=[4]-=-. Testing is one quality assurance techniques for software products [5]. 1.4 NOTATIONS IN SOFTWARE TESTING This section presents the different notations use in software testing context. 1.4.1 SOFTWARE...

Citation Context

... for a specific product. Product lines testing process is split into product line infrastructure, core assets, and test processes for the various products in software product lines [15]. According to =-=[14]-=-, product lines testing can be performed like traditional testing; using the V-Model. But software product lines testing process has to be integrated with higher level product lines business process. ...

Citation Context

...cation, design, codes, and other artefacts [4]. One major purpose of software inspections is to increase the quality of software artefacts use in constructing product line by detection of faults [95] =-=[97]-=-. Secondly, it provides useful information to decision makers in software organizations, in order for them to take well informed decision concerning the product line [95] [96]. Further more, other tec...

Citation Context

...t lines and other systems, and help to uncover hidden requirements, to verify and validate and to integrate analysis of functional and non-functional requirements for product lines. Amyot et al. 1999 =-=[79]-=- Gomaa et al. 2002 [81] Gomaa et al. 2006 [122] ACM Digital Library Table 5.2: Hints from ACM digital library database search. No Investigated Articles Selected Articles 1 7 0 2 4 0 3 3 1 4 4 0 5 3 0 ...

Citation Context

...roduct line development, core assets and product assets input. The core software assets can include requirements, architecture and design, source code, test cases, product documentation, and so forth =-=[78]-=-. The product assets are derived from domain engineering core assets [105]. For that, much effort goes into domain engineering compared to product development [105]. According to [106], “Software prod...

Citation Context

...f products belonging to software product lines is a key issue for test case in software product lines. Majority of the variation points are introduced into product lines during the requirements phase =-=[118]-=-. The major challenge and urging question in this process is how to handle and represent variability in software product lines. The delivery of quality software product lines and its specific products...

Citation Context

... Software Engineering Institute Site Search Table 2.4: Hints from SEI site search. No Investigated Articles Selected Articles 1 6 3 Total 6 3 McGregor 2001 [4] Clements 2002 [113] Chastek el al. 2001 =-=[114]-=- The major relationship between software product lines and product is that test cases created in domain engineering for product lines are extended to specific product level. The selected articles from...

Citation Context

...hniques to verify the reliability of software components before reusing components for software product lines development. John Morris et al. 2002 [91] Chillarege et al. 1992 [92] Geppert et al. 2005 =-=[94]-=- Thelin et al. 2004 [95] Voas et al. 1998 [101] Yacoub proposed Scenario based analysis approach to verify components reliability. Yacoub et al. 2004 [98] ACM Database Search Table 7.2: Hints from ACM...

Citation Context

...using quality software the time and effort required to maintain the software will be reduced drastically [29] [67]. Software component reuse in development is classified into two directions and types =-=[64]-=-. The first one is development for reuse and the second type is development with reuse [63] [66]. Development for reuse and development with reuse can both be applied in software product lines. Softwa...

Citation Context

...51]. The major reason for reusing software artefacts in product lines development is to reduce development costs and time by reducing the cost and human effort required to build the software products =-=[53]-=- [54]. Therefore, software reuse in product lines is a welcome development. The reuse of software artefacts across multiple projects is important strategy for improving software development efficiency...

Citation Context

...rket depends on how reliable are the reusable artefacts of domain engineering. Product lines should be able to compromise between customer requirements, existing requirements architecture constraints =-=[75]-=-. The key to successful product lines development is managing variability in numerous products developed. This can be archive by constructing product lines models of requirements and features. This ma...

Citation Context

...ms, and help to uncover hidden requirements, to verify and validate and to integrate analysis of functional and non-functional requirements for product lines. Amyot et al. 1999 [79] Gomaa et al. 2002 =-=[81]-=- Gomaa et al. 2006 [122] ACM Digital Library Table 5.2: Hints from ACM digital library database search. No Investigated Articles Selected Articles 1 7 0 2 4 0 3 3 1 4 4 0 5 3 0 Total 21 1 Bertolino et...

Citation Context

...are organizations, in order for them to take well informed decision concerning the product line [95] [96]. Further more, other techniques propose to analyse the reliability of software components are =-=[98]-=-: • System level reliability estimation. Reliability estimation is based on the entire system. • Component based reliability estimation. Reliability estimation of the application is based on the relia...

Citation Context

...roduct. PLUTO METHOD PLUTO (Product Lines Use case Test Optimization), is a methodology for early derivation of test cases from product lines requirements described as product lines use cases (PLUCs) =-=[21]-=-[43]. The methodology is inspired by Category Partition method, but it is expanded with the ability to handle variability in software product lines and to instantiate test cases for software product l...

Citation Context

...ing is divided into levels for example, unit testing, integration testing and system testing. In each level of testing, the purpose of testing is different. It has specific objectives and limitations =-=[9]-=-. Black box and white-box testing methods are suitable for different testing levels and has different strategies to run testing [9]. Software testing basically involves the operation of a system under...

Citation Context

... reuse. Table 6.1: Hints from IEEE database search. No Investigated Articles Selected Articles 1 3 1 2 4 2 3 4 1 4 6 2 5 3 1 Total 20 7 Articles selected from IEEE database search. Poston et al. 1992 =-=[28]-=- Chaver at el. 1998 [58] Agresti et al. 1987 [61] Basili et al 1990 [67] Boehm et al. 1988 [68] Mayrhauser et al. 1994 [70] Mayrhauser et al. 1994 [71] 57sThe general concept shared by selected articl...

Citation Context

...n for reuse of software artefacts is that it decreases the development cost for software and reduce the human effort and time required to build improved software by reusing quality software artefacts =-=[52]-=-[61]. Software reuse can help reduce maintenance costs due to that fact that, when reusing quality software the time and effort required to maintain the software will be reduced drastically [29] [67]....

Citation Context

...on method based on two concepts from software reuse, domain analysis and domain modeling. Because DBT it is based on ideas from software reuse, DBT also provides a good structure for test case reuse” =-=[70]-=- [71]. 56sDuring domain engineering product lines core assets consisting of sets of reusable assets from which product lines specific products can be derived during application engineering [72]. It im...

Citation Context

...detection of faults [95] [97]. Secondly, it provides useful information to decision makers in software organizations, in order for them to take well informed decision concerning the product line [95] =-=[96]-=-. Further more, other techniques propose to analyse the reliability of software components are [98]: • System level reliability estimation. Reliability estimation is based on the entire system. • Comp...

Citation Context

...ed to produce quality software that satisfies customers’ needs. It is expensive and time consuming to design and develop software for a single system that satisfies the need of just a single customer =-=[1]-=-. As a result of constraints of time and cost involved in designing and developing software for a single system and specific customer, this lead to the concept of product family development which sati...

Citation Context

...tion engineering) [50]. The variability at the different levels in product lines design, which includes: Variability in product line level, the architecture level, the component level, and code level =-=[22]-=-. Developers of software product lines have to deal with two development processes and the variability in software product lines in order to achieve the goals of developing quality software at reduced...

Citation Context

...capture and derive requirements with uses cases, and derive test cases that are extended by model to express variability in the captured requirements. Bertolino et al. 2004 [21] Fantechil et al. 2004 =-=[82]-=- Bertolino et al. 2007 [83] Fantechil et al. 2004 [84] Science Direct Electronic Database Table 5.4: Hints from science direct electronic database search. No Investigated Articles Selected Articles 1 ...

Citation Context

...emerging product lines software development approach and affects the maintainability, understandability and usability and reusability characteristics of systems or basically family of similar systems =-=[107]-=-. Domain engineering methodology is actually based on the concept of family of products, in order to achieve systematic reuse within product lines. For software product lines organizations that constr...

Citation Context

...ces are not devoted, then anticipated high level of test assets and software reuse will not be realised. When this happens, the quality of the software products lines and specific product is affected =-=[42]-=-. Product line testers and developers sometimes find it difficult constructing product line software as a result of variability complexity associated with product line test cases. Capturing the variat...

Citation Context

...cases 55sThe reuse of software artefacts across multiple projects and product is a good strategy to improve software development efficiency towards increasing the quality of software development [56] =-=[58]-=- [59]. The major motivation for reuse of software artefacts is that it decreases the development cost for software and reduce the human effort and time required to build improved software by reusing q...

Citation Context

...ended by mechanism. The approach describes how to capture and derive requirements with uses cases, and derive test cases that are extended by model to express variability in the captured requirements =-=[83]-=-[84]. In addition to dynamic view of collaborating objects, a systematic view of class definition is usually shown with design class diagram. This illustrates the attributes and the methods of the cla...

Citation Context

...The major reason for reusing software artefacts in product lines development is to reduce development costs and time by reducing the cost and human effort required to build the software products [53] =-=[54]-=-. Therefore, software reuse in product lines is a welcome development. The reuse of software artefacts across multiple projects is important strategy for improving software development efficiency and ...

Citation Context

...thod based on two concepts from software reuse, domain analysis and domain modeling. Because DBT it is based on ideas from software reuse, DBT also provides a good structure for test case reuse” [70] =-=[71]-=-. 56sDuring domain engineering product lines core assets consisting of sets of reusable assets from which product lines specific products can be derived during application engineering [72]. It implies...

Citation Context

...more in software organizations [2]. The goals of software product lines is aimed at producing high quality software products and at the same time significantly reduce development and maintenance cost =-=[72]-=-. In this chapter, the relationship between product lines and product is investigated. 2.1 RESEARH METHOD This section presents the method use in conducting our research. How we identified articles re...

Citation Context

...Articles Selected Articles 1 0 0 2 8 2 3 6 1 4 4 1 Total 18 4 From the 18 articles investigated, 4 provided direct evidence relating to research question. Tevanlinna et al. 2004 [24] Kolb et al. 2006 =-=[120]-=- Core assets that can be tested in product line are reusable software product lines artefacts, such as components, architecture, requirements and test cases. Both articles state clearly the artefacts ...

Citation Context

...in software product line is referred to as defining variability [10]. These variations in products represent the customisation of the specific products with respect to other members of a product line =-=[45]-=-. The first phase of software project is requirement analysis and specification for the system under construction. Software product lines developers are always bothered and thinking on how to handle t...

Citation Context

...ecification, design, codes, and other artefacts [4]. One major purpose of software inspections is to increase the quality of software artefacts use in constructing product line by detection of faults =-=[95]-=- [97]. Secondly, it provides useful information to decision makers in software organizations, in order for them to take well informed decision concerning the product line [95] [96]. Further more, othe...

Citation Context

...e developed from product line, all product instances of product line share configurable, customizable components in order to save development cost, when creating similar products for different market =-=[108]-=-. Software product line is a set of software products that share a set of common features, that satisfies the needs of a particular market and are developed from a set of common assets [109]. Product ...

Citation Context

...lity analysis models is for systems whose design is based on independent executions of scenarios. Yacoub [98] introduces the reliability analysis model, Component Dependency Graph (CDG). And Gokha 65s=-=[99]-=- discuss the flexibility offered by discrete event simulation to analyse component based applications. Testing and certification techniques are considered by [100], to be essentially required to asses...

Citation Context

... Dependency Graph (CDG). And Gokha 65s[99] discuss the flexibility offered by discrete event simulation to analyse component based applications. Testing and certification techniques are considered by =-=[100]-=-, to be essentially required to assess the suitability of COTS components for integration in product line architecture. Though testing and certification is considered suitable, there is need to develo...

Citation Context

...tant part of software development project. The testing phase in software project is time consuming and takes up to 50% of the total project effort, though it contributes significantly to product cost =-=[27]-=-. Software is prone to changes and changes can influence the result of test. Based on this, testing has to be performed regularly [26] [27]. Software testing is a very challenging activity, time consu...

Citation Context

...ool support for software product lines testing is as a result of lack of test planning. If proper attention is paid to test planning and preparation, the tools required for testing will be identified =-=[41]-=-. Software product lines development is very complex and expensive. To achieve high quality in software product lines and its specific product, enough resources should be devoted to testing process. I...

Citation Context

...oped manually, which is time consuming task. Thus, it is desirable to create both test case scenarios and specifications in domain engineering and to reuse them during application engineering [2] [4] =-=[74]-=-. Product lines organizations can afford to invest in the following core assets that can be reused in product development: Requirements, software architecture, test plans and test cases [2]. 6.3.2 STU...

Citation Context

...ponents are reliable. Therefore, the reliability of software product lines and its specific products depends on the quality of product line reusable components from which the products are constructed =-=[91]-=-. Component based software engineering is a new technology for software development that has been accepted by software organisations for software product line development that aims to construct applic...

Citation Context

...mers need to useful product. (Requirements phase, design phase execution phase, implementation, testing phase and maintenance)[2] [25]. Requirement tool for software product lines are DOORS and REMAP =-=[121]-=-. They help to manage requirements in product lines. Selecting tools for product lines testing, from the few tools available to support the business goals and technical needs of developers is very cha...

Citation Context

...o development processes, domain engineering and application engineering. In domain engineering, product lines core assets are developed and extended to application engineering for product development =-=[12]-=-. Core assets created in domain engineering for product lines are reused in application engineering for products development. Further more; product line development is the differentiation of two devel...

Citation Context

...domain artefacts and application artefacts. Therefore, testing in software product lines encompasses testing domain engineering artefacts and application engineering artefacts [11]. According to John =-=[16]-=-, testing core assets in domain testing and detect remaining defects in application testing which are mainly caused by unexpected interactions. John supports testing core assets in domain engineering ...

Citation Context

...rocess. Product lines AND testing activities. Survey AND product family AND testing process. Testing in software product lines is performed in domain engineering and application engineering [11] [15] =-=[17]-=- [18]. Domain engineering process is aimed at developing the general concept of product lines together with all the assets that are common to product lines, while application engineering process is ai...

Citation Context

...Café Projects on software product lines framework in supporting their arguments most especially in defining methodologies to manage and control variability in software product line. According to [14] =-=[23]-=-, product line testing can be performed using traditional V-Model. The view of some studies is that V-Model for single product testing can be used to perform testing in software product lines. Also, t...

Citation Context

... Search Table 2.2: Hints from ACM database search. No Investigated Articles Selected Articles 1 15 6 Total 15 6 Articles selected from ACM database search Pohl et al. 2006 [11] Tevanlinna et al. 2004 =-=[24]-=- Cohen et al. 1979 [46] Verlage et al .2005 [108] Ereno et al. 2005 [109] Hamilton et al. 2005 [110] 15 articles were investigated from ACM database search, from which 6 primary studies were selected....

Citation Context

...olves two processes, domain engineering and application engineering process. Product lines testing involve automatically generating test cases from software product line requirements. 28sAccording to =-=[29]-=- PLSE consists of two major processes: asset development and product development. Asset developer analyses product line domain and develops architecture and reusable components in assets development p...

Citation Context

...handle the problems of capturing test cases common to all members of the product lines on one side, at the other side, how to specialise the general product lines test cases into 43sspecific products =-=[43]-=-. To handle this problem, use case approach was introduced in software product lines. Use cases from requirement analysis phase of product lines development are often use to create system test cases. ...

Citation Context

...s from ACM database search. No Investigated Articles Selected Articles 1 15 6 Total 15 6 Articles selected from ACM database search Pohl et al. 2006 [11] Tevanlinna et al. 2004 [24] Cohen et al. 1979 =-=[46]-=- Verlage et al .2005 [108] Ereno et al. 2005 [109] Hamilton et al. 2005 [110] 15 articles were investigated from ACM database search, from which 6 primary studies were selected. The six selected artic...

Citation Context

...The procedure should define the people that should be involved in software product lines testing, and skills of each team members. For more information on challenges of software product lines see [7] =-=[47]-=- [48] [49]. 8.5 DISCUSSION The challenges facing testing in software product lines context are both technical and non technical. And if proper attention is not given to these issues they will definite...

Citation Context

...be applied in software product lines. Software development for reuse creates reusable core assets for product lines and software development with reuse creates reusable core assets to create products =-=[69]-=-. TEST CASES Testing software application requires unique test cases. Test cases are sequence of steps to test the correct behavior of a functionality/feature of an application. For testers to perform...

Citation Context

...zations and customers. As represented in SPLIT Model, there are two parts in model based testing, the test model built from requirements, using state charts or activity diagram to represent the model =-=[76]-=-. The second part is test cases created using coverage criteria. 38sTest models in domain engineering contain variability which must be considered in domain engineering. Considering the fact that ther...

Citation Context

...d by mechanism. The approach describes how to capture and derive requirements with uses cases, and derive test cases that are extended by model to express variability in the captured requirements [83]=-=[84]-=-. In addition to dynamic view of collaborating objects, a systematic view of class definition is usually shown with design class diagram. This illustrates the attributes and the methods of the class [...

Citation Context

...studies as it relates to the research question are as follow: There are three approaches that support the concept of extending reuse to software product lines testing. McGregor [4] and Geppert et al. =-=[87]-=- approach support creating reusable test cases from use cases during domain engineering. Product lines test cases created during domain engineering are derived from natural language requirements and g...

Citation Context

...from natural language requirements and generalize from existing test cases [4]. Test cases derived from use cases during domain engineering should be extended to application engineering. According to =-=[88]-=- test cases derived in domain engineering for software product lines can be extended to application engineering for reuse. Scenarios fragments are considered in domain engineering and are assembled to...

Citation Context

... to specify dependencies between use cases. Though test cases are only derived from use cases for specific applications only when variability is already bounded. Activity diagram was used by Hartmann =-=[89]-=-, as test model, which contains variability, but test cases are only derived in application engineering. It is a model based testing approach for deriving test cases from use cases only in application...

Citation Context

...product lines development. The concept is that use cases can be modeled to define the variability in software components before reusing the components for product lines development. Blake el al. 2005 =-=[103]-=- Springer Link Electronic Database Search. Table 7.3: Hints from Springer link electronic database search. No Investigated Articles Selected Articles 1 0 0 2 0 0 3 0 0 4 0 0 5 0 0 6 0 0 Literatures Ta...

Citation Context

...oftware assets can include requirements, architecture and design, source code, test cases, product documentation, and so forth [78]. The product assets are derived from domain engineering core assets =-=[105]-=-. For that, much effort goes into domain engineering compared to product development [105]. According to [106], “Software product line engineering (SPL) involves developing the requirements, architect...

Citation Context

...nt market [108]. Software product line is a set of software products that share a set of common features, that satisfies the needs of a particular market and are developed from a set of common assets =-=[109]-=-. Product lines is a well defined repeatable process, where new systems within a given domain are built from existing parts constructed to be reuse [110]. Software product line consists of family of p...

Citation Context

... and are developed from a set of common assets [109]. Product lines is a well defined repeatable process, where new systems within a given domain are built from existing parts constructed to be reuse =-=[110]-=-. Software product line consists of family of products software that has common features [111]. Product line basic concept is that similar products share a common set of components and functionality c...

Citation Context

...ic concept is that similar products share a common set of components and functionality called core assets, though, individual products have some functionality specific to it, called the variable part =-=[112]-=-. 2.1.2 IDENTIFICATION OF RESEARCH On page 13 a summary of method used in identification of research can be found. List of combination of search term used for all databases search: Software AND produc...