A Case Study on Variability Management in Software Product Line
|
|
- Joan Phillips
- 8 years ago
- Views:
Transcription
1 A Case Study on Variability in Software Product Line Sabir Hussain (1), Muhammad Asif (2), Muhammad Shahid (3) 1) Department Of Computer Science, National Textile University Faisalabad Pakistan 2) Assistant Professor, Department of Computer Science, National Textile University Faisalabad Pakistan 3) Lecturer, Department of Computer Science, National Textile University Faisalabad Pakistan Abstract A product line is a collection of products that together address a specific business sector section or satisfy a specific mission. While software product line satisfies a market or segment by using its common set of features that are developed as a core assets for different products of a family. SPLE (Software product line engineering) is composed of two major parts one is Domain Engineering and other one is Application engineering. One common and major issue that is to be faced in SPL is to manage variability at different phases of SPL. Despite of this there are many other models like FODA, PuLse, Cobra etc. that are purposed to manage VM in SPL but have many back draws and implications during different phases of implementation. In this paper we will explore first some welldefined processes and methods to manage VM in better way as compared to existing models as described in Cobra, PuLse, FOAD etc. and then apply a case study of LMS(Logistic System) to identify variability in SPL. We have also discovered that how the defined processes and models manage variability at different phases of SPL and also highlight advantages and disadvantages of this model. Keywords: Variability, Software Product Line, Logistic System Introduction In recent years SPLE(Software product line engineering) has dramatically gained substantial attention because it has been argued that SPLE delivers a promising technique to improve the development of a huge variety of improved, better, cheaper and faster [1] software concentrated systems. By using SPLE it has been stated that in some case s the quantity increased with low cost, enhanced time to market and also quality improved much better as compared to existing old traditional reusing techniques to develop a product[2]. The development of the software products by using SPL (Software Product Line) can be developed easily and rapidly by taking the advantage of reusing core assets like frameworks, patterns, designs, components and documentation. There are a variety of products that are supported by SPLE diverges individually to support entirely dissimilar market segments or specific customers. As a result here comes the concept of variability, which is an important theory in SPLE. Variability has the capability for an artifact to be personalized, organized, changed or extended for the use of particular or in an unambiguous context[3]. Various artifacts that are used in variability to develop different products in SPL must be exploited, signified, defined, executed and developed during the whole lifecycle of that SPL[4]. This is the nutshell when practitioners and researchers refer to variability management (VM) in SPLE and it is also when we use the term variability in this research. Domain Engineering and application engineering are two main parts of the SPLE.
2 The core asset of the product line that is called product-line architecture belongs to domain engineering. The main objective of product line engineering is to build products by understanding and monitoring the commonality between a set of similar software system or controlling common functionality that exists between a product family that is shared between products, system can be customized or changed to specific needs by using the concept of variability. Therefore a key point between the product families is to understand and manage the concept of variability that is significant for the success of software product line. Software growth can be determined by managing variability in SPL. There are some issues that are discussed in different research papers such as: Development of Variability[5] Managing unvarying variability over the all phases of SPLs[6] Documentation and modeling of variability[7, 8] Mapping of family assets with variability[9] The SPLs contains multiple-view Meta-Modeling[10] The identification of variability and commonality [11] To manage VM tasks is an extremely complex and challenging, therefore it is essential that different techniques, approaches and tools should support VM[7, 11]. There are some outstanding methods and techniques that have been presented or described in different research papers to manage variability in SPL like FODA, PuLse, Cobra, and many more with some back draws. While FODA (feature oriented domain analysis) method is the first input to manage variability in 1990[9]. However many problems still need to be resolved [12]. There is no generally well known technique or notation that is used to accomplish variability of all stages of SPL because variability ascends in each stage of SPL and needs to establish traceability of identifying product variability from the initial stage to product design, implementation and testing. Therefore in this paper [13] it has been claimed that variability is managed uniformly throughout life cycle of SPL, at each phase specifically artifacts, process are purposed. Furthermore a detailed case study is implemented on purposed methodology to verify and check how these methods help to manage variability uniformly at every stage of SPL. Background There are several techniques and methods that are introduced to manage variability in SPL. Each model has purposed some different methodology to cater the problem of VM like PuLSE (Product Line Software Engineering), KobrA, FAST (Family-Oriented Abstraction, Specification, and Translation), FORM (Feature-oriented reuse method), and PoLITe. One model named with PuLSE[14] is purposed to overcome the problems that occurred in most of the other research in SPL which lacks of customizability, and lost their focus, which only covers domains as opposed to products. PuLSE methodology enables the notation and deployment of SPL for a large number of products with enterprise background. This methodology was achieved by having focus on products in all the phases of PuLSE and also giving customizability of its different phases and components also includes incremental introduction capability, a well-structured deployment and a few main product development situations. In a particularly domain applications can be designed more significantly by reusing their
3 similarities. By developing core assets for reusability for a domain allows multi applications to build efficiently from existing core assets. According to PuLSE methodology domain engineering methods are not as efficient as expected this is due to following three reasons: Wrong and misguided application scope Laps of operation guidance More focus on organizational issues KobrA[15] is component based product line approach and emphasizes on significantly increase of reusability in industrial maintenance and software development. Rather than going into old techniques organizations follow a product line approach after gathering the parts of Old systems in a temporary manner, which gives good results by increasing efficiency, high quality consolidation of software assets, software core is reused and also focuses on the resources which can accommodate changes from customer by using this core. There is a wrong perception about the usage of product-line development that is unsuited with usual development of single system a lot of developers has thought that product line development approach not comfortable for them to develop single system according to some developers its forcefully adaption technique. The component based software engineering differs from object oriented paradigm because it gives interoperation of binary code modules. Organization creates component based systems and expected that many similarities will be shared and particularly uses the same components. There are some critical components which handles the variability s in a family of systems. FAST[16] process applies product-line principles to software engineering process. However a family of products can be defined from a common platform. This platform is composed from similarities between several products close to each other. In this paper it is also described that how same family has common basis and variability for products[17]. It also describes about core assets development and acquisition for productline[18]. The variability s within the product family members can be managed and implemented by using various variation techniques like conditional compilation. A detailed elaboration about variability in product-line architectures can be found in [18] as an example. The core objective of FAST is to decrease production costs by reducing duplicate, multiple works and with quick delivery in market. FAST process can be implemented by a consistent, smooth and disciplined way. It is called PASTA model where PASTA is (Process and artifact state transition abstraction). FAST process can be followed by using PASTA model. PASTA process provides a way during the execution of FAST process and also determines a set of steps that how get success during the current step. The role of PASTA in software engineering process is to provide an iteration and reusability of future processes. Below is a centralized model that summarizes the information mined from the core assets particularly the dependency information. On basis of this model product line organization can anticipate what is needed or involved to build a specific product.
4 Figure 1 Contributors to the Core Asset Base[19] Literature Review This section describes methodology of [13] with its defined processes and methods. Common characteristic and variation (C&V) must be achieved and managed at each stage of SPL or phases of abstraction[20]. As described in the below diagram each stage of product development is labeled with the way to figure architecture with respect to product line in SPLE and also at each level of C&V artifacts are defined with each process. First the overall description of how to SPL can be used to build software development is displayed in below pictorial diagram Figure 2.
5 Figure 2 Suggested process and artifacts for VM [13] As it is depicted in Figure 2 the purposed methodology is made out of two primary parts domain engineering (DE) and second is application engineering (AE). We will concentrate of domain engineering (DE) rather than going into the detail of application engineering (AE). So let s start from step 1. Step 1: Scoping In this step particular prerequisites of every product are recognized which should be part of product line (PL). Scoping is introduced to conclude the boundaries of SPL. The boundaries of conceptual groups are also recognized. Artifacts that are involved in this stage are feature list, refined feature diagram and enhanced product map. The term features [21] in SPL define a projecting and unique concept or a characteristic that varies according to various specific requirements needed by various stockholders [22]. Furthermore there are different types of feature like External features [23], mandatory features, optional feature and variant features [23]. The stakeholders such as product experts, maintainers, users, and developers identify characteristics of the product by analyzing it and also help to collect product related materials and this all procedure helps to make
6 feature list. The enhanced product map helps to identify individual products feature and which features are required to compose each product. Features are grouped by property and listed with the help of (EPM) enhanced product map. Figure 3 Features and Product are displayed using enhanced product map (EPM) [13] A feature can be variable or common among the different products. In Product A all features are involved of the product line while a feature can be implemented in set of the product-lines or in a single member [24]. Gray shaded lines are representing variability among the product families. There exists a value relationship between product families in (EPM) enhanced product map as shown in figure 3. Step2: C & V Modeling Depended or Involved in N a feature is depended if some other feature N is involved and so on. Excluded from N or Omitted from N a feature will be omitted or excluded if a feature is N is nominated. In this step, a way is provided how to identify the variation in product family and by analyzing commonality and variability it is identified that what is common across the domain of SPL. Here are the artifacts that are purposed: i-a refined use-case model (RUM) ii-a business service scenario (BSS) iii-a BSCV (business service commonality and variability) decision model Functional requirements of system can be determined by utilizing use case model. A UCM (Use case model) delivers a technique for describing and understanding the FR (functional requirement). It is also used to determine C &V (variation and commonality) by using stereotype<<optional>> and <<mandatory>>. The terminology of stereotype is naturally used to model
7 variability because it is the usual way to be presented by UML Figure 4 Refined use-case model [13] In fig 4 stereotype <<uses>> means that feature 5 is also included the behavior of feature 4. A (BSS) business service scenario and (UCS) use case scenario could be utilized to determine the comprehensive functional and non-functional attributes. Below figure 5 is representing business service scenario and fig 6 is representing proposed in [9] paper. Figure 5 Business service scenario [13] In the product line BSCV decision model defines the variable and optional necessities of products. To determine variability and commonality of the business service BSCV decision model is used as described in below figure 6.
8 Figure 6 A decision model BSCV for business service (BSS) Figure 7 Use-case model represented by BSCV decision model Step 3: Architecture modelling Building design or architecture is an important component toward the achievement of any product venture, not simply SPLE. A SPLA portrays the shared characteristics among the dissimilar products and likewise unmistakably depicts the variability which is permitted among the products. As being what is indicated a SPLA is foremost to typically attain the characteristics of the different items in a SPL [25]. SPLA purpose three core artifacts that are: i-architecture View ii-quality Goal Specification (QGS) iii- Decision Model for the Architecture of Commonality and Variability (ACV). Keeping in mind the end goal to delineate the shared characteristic and variability of the product offering construction modeling, a few view types as architectural features are utilized, including view type, allocation view and others as shown in figure 9. Each one view type comprises of a few sub views, as is shown in Fig1. Several views are used to present the variability and commonality of SPLA including module view type, allocation view type and component and connector(c &C) view type. Now each architecture view is sub divided into more sub views, as described in below figure.
9 A Case Study Figure 8 Architecture view type [13] In the following segment, a real time case study is implemented that shows the provision of the suggested model, artifacts and processes into particular areas keeping in mind the end goal to delineate the inspirations for our research. The model of [13] is implemented to the (LMS), a web-based solution for logistic management. For the case study, it is supposed that LMS is supporting a family of products that are composed of East Course Trucking Company, Total A&G Trucking Company and Al-Nahif Trucking Company. In phase 1, features are mined, examined, and grouped, as indicated in table-1. In this table features with gray background are representing variability among the family of products with respect to features. For examples Total A&G Trucking Company is composed of twelve features. Relationship column is used to identify the dependency of features on each other. Table 1 Enhanced product map for LMS Feature LMS Order LMS Financial Product East Course Trucking Company Total A&G Trucking Company Al-Nahif Trucking Company Relationship 1 Add order record Involved in 2 2 Order record inquiry 3 Driver payroll 4 Chassis split 5 Auto charges 6 Auto payments 7 Add document record 8 Document record inquiry 9 Manifest Billing Involved in 8 10 Invoicing Build 11 Payments record Involved in 13
10 LMS Fleet 12 Payment record Inquiry 13 Invoice Posting Involved in Invoice Posting Inquiry 15 Weekly Payment 16 Vehicle 17 Insurance 18 Maintenance 19 Tracking 20 Fleet Security & Controller 21 Remote Disabling Vehicle System 22 Fleet Scheduling 23 Fleet Allocation Involved in 21 Refined features diagram is used to present the dependency between the features and also feature group variation. In order to identify the FR (functional requirement) of LMS, a refined use-case model is used on the basis of refined feature diagram of LMS. In figure 10 a business service has been described which has 3 actors and 6 use cases for Fleet management System. Product LMS Order LMS Fleet LMS Financial Add Order Record Vehicle Manifest Building Driver Payroll Insurance Invoice Build Auto Charges Maintenance Payments Record Auto Payments Tracking Payment Record Inquiry Included
11 Add Document Fleet Security & Controller Invoice Posting Can be Excluded Optional Order Record Inquiry Chassis Split Document Inquiry RDVS Fleet Scheduling Fleet Allocation Invoice Posting Inquiry Weekly Payment Figure 9 Refined feature Diagram
12 Figure 10 A more refined use-case models In order to clearly represent the non-functional and functional requirements a business service is used as in below Table 2. It depicts the functional and non-functional requirements with a brief detail. The business service scenario is designed by using refined feature diagram and refined use-case model diagram. To determine the effects of business service and features BSCV decision model for the BS (Business Service) and UCM (use-case model) constructed on this refined UCM and BSS (Business service scenario) are used. As depicted in Table 3 and Table 4.
13 Table 2 Business Service Scenario <<mandatory>> To manage fleets with respect to consignments 2. LMS Fleet 2.1 Vehicle : to add and manipulate vehicle records 2.2 Insurance: do insurance of different vehicles 2.3 Maintenance: to keep records of the maintenance of vehicles 2.4 Tracking: to view the live position of vehicle and also manage history of vehicle position, speed and running time 2.5 Fleet Security & Controller: to control the security of vehicle or fleet 2.6 Remote Disabling Vehicle System: to attach a hardware device to fleet and have control to disable fleet at remote position 2.7 Fleet Scheduling: To manage and schedule fleets according to consignment 2.8 Fleet Allocation: Allocate a fleet to specific driver to fulfill consignment pickup and delivery Non-functional Requirements Execution Environment UI Environment Efficiency Security Other Contents and text based environment Make UI user friendly and put some advance filtering criteria to easily find available fleets and drivers etc. Response time should be more efficient during live tracking and inquiring fleet Authorization and Authentication is required to perform any operation Data storage should be consistent By using Table 2 and business scenario G2 in Table 3 is extracted. And showed in Fig.10 variations points can be selected or not selected by using BSCV model for UCM. The important element in software development is SPLA which is also used as core asset as we have described in previous section that SPLA has three main view types e.g. (C&C, module) can be used in this case study. Table 3 BSCV decision model for business service of LMS ID G2 Variation Point LMS Fleet Type Condition Solution Effect Optional Does a Fleet Manager or QA Inspector need LMS Fleet management? Yes No Eliminate stereotype <<optional>> Eliminate LMS Fleet management business service The runtime presence of elements and interaction between the elements is defined by C&C view. While in C&C view components are units of the system s which interact with
14 each other using various different ways like complex communication protocols and RPC etc. Table 4 Decision model BSCV for use case model of LMS ID Variation Point G2.2 Insurance Optional G2.3 Maintenance Optional G2.5 G2.6 G2.7 G2.8 Fleet Security & Controller Remote Disabling Vehicle System Fleet Scheduling Fleet Allocation Type Condition Solution Effect Optional Optional Optional Optional Is Insurance to a fleet management is necessary? Is maintenance feature for fleet management is necessary? Is Fleet security & Controller feature is essential? Is RDVS is needed? Is Fleet Scheduling necessary? Is Fleet Allocation is needed? Yes No Yes No Yes No Yes No Yes No Yes Remove stereotype <<optional>> Eliminate the insurance feature Remove stereotype <<optional>> Eliminate the maintenance feature Remove stereotype <<optional>> Eliminate fleet security & Controller feature Remove stereotype <<optional>> Eliminate the RDVS feature Remove stereotype <<optional>> Eliminate the Fleet scheduling feature Remove stereotype <<optional>> Conclusion The purposed[13] study on managing variability in SPL gives good artifacts and processes to manage variability at different phases of software product development. Software products can be developed so easily and rapidly if we have an architecture that can accommodate future changes easily. The problem that we face during SPL development is variability that is the core issue in the development of SPL. There are many models that are purposed to cater this issue but failed to give some standard solution. For somehow
15 comparatively the purposed processes and artifacts gives better solution including entertaining some problems of existing models like Cobra, PuLse etc. Now in this paper we have focused on implementing a real case study on purposed models, process and artifacts to see how to manage and identify variability throughout the life cycle of SPL. Many issues are resolved that are purposed in upper section of this paper in step 1 introduction. However we face some implications during the implementation of our case study. By using this purposed processes and artifacts domain model becomes too mess that causes some serious issues at application level. We have divided issues into two categories that occurs during the implementation of our case study LMS first category is general issues and second is specific to domain engineering References 1. Bosch, J. Architecture-centric software engineering. in Proceedings of the 24th International Conference on Software Engineering ACM. 2. Clements, P. and L. Northrop, Software product lines: practices and patterns Pohl, K. and G. Böckle, van~ der Linden, FJ, Software Product Line Engineering: Foundations, Principles and Techniques. 2005, Springer- Verlag New York, Inc., Secaucus, NJ, USA. 4. Linden, F., van der, SCHMIDT, K. and ROMMES, E.,(2007): Software Product Lines in Action: The Best Industrial Practice in Product Line Engineering, Springer-Verlag New York, Inc. Secaucus. 5. Loesch, F. and E. Ploedereder. Optimization of variability in software product lines. in Software Product Line Conference, SPLC th International IEEE. issues. In general issues purposed model gives us first class representation of variant points and also describes the dependences between the architectural elements however this models does not define a standard solution to some specific issues of domain engineering like over generalization and over trivialization in which during the analysis of a new domain there are two main issues that are raised very frequently. First, the analyst does know about the exact requirement of variability during product line so this leads towards over generalizing. Second is the complexity of understanding domain detail and the particularly to domain variability is not sufficiently understood this is called overtrivialized. Similarly other issues like over simplification, mechanism impact and resource impact etc. are some issue relevant to domain engineering that needs to be addressed by standard way. 6. Kim, Y.-G., et al. Managing variability for software product-line. in Software Engineering Research, and Applications, Fourth International Conference on IEEE. 7. Razavian, M. and R. Khosravi. Modeling variability in the component and connector view of architecture using UML. in Computer Systems and Applications, AICCSA IEEE/ACS International Conference on IEEE. 8. Bachmann, F., et al., A meta-model for representing variability in product family development, in Software Product-Family Engineering2004, Springer. p Becker, M. Mapping variabilities onto product family assets. in Proceedings of the International Colloquium of the Sonderforschungsbereich Sinnema, M., et al., Covamof: A framework for modeling variability in software product families, in Software
16 Product Lines2004, Springer. p Gawley, R. Automating the identification of variability realisation techniques from feature models. in Proceedings of the twenty-second IEEE/ACM international conference on Automated software engineering ACM. 12. Sinnema, M. and S. Deelstra, Classifying variability modeling techniques. Information and Software Technology, (7): p Kim, Y.-G., S.K. Lee, and S.-B. Jang, VARIABILITY MANAGEMENT FOR SOFTWARE PRODUCT-LINE ARCHITECTURE DEVELOPMENT. International Journal of Software Engineering and Knowledge Engineering, (07): p Bayer, J., et al. PuLSE: a methodology to develop software product lines. in Proceedings of the 1999 symposium on Software reusability ACM. 15. Atkinson, C., J. Bayer, and D. Muthig, Component-based product line development: the KobrA approach, in Software Product Lines2000, Springer. p Harsu, M., FAST product-line architecture process2002: Tampere University of Technology. 17. Ardis, M., et al., Software product lines: a case study. Software-Practice and Experience, (7): p Bergey, J., et al., Basic concepts of product line practice for the DoD, 2000, DTIC Document. 19. Bachmann, F. and P.C. Clements, Variability in software product lines, 2005, DTIC Document. 20. Berg, K., J. Bishop, and D. Muthig. Tracing software product line variability: from problem to solution space. in Proceedings of the 2005 annual research conference of the South African institute of computer scientists and information technologists on IT research in developing countries South African Institute for Computer Scientists and Information Technologists. 21. Bosch, J. Software variability management. in Proceedings of the 26th international Conference on Software Engineering IEEE Computer Society. 22. Lee, K., K.C. Kang, and J. Lee, Concepts and guidelines of feature modeling for product line software engineering, in Software Reuse: Methods, Techniques, and Tools2002, Springer. p Roubtsov, S. and E. Roubtsova. Modeling evolution and variability of software product lines using interface suites. in Workshop on Software Variability. Editors Jilles van Gurp and Jan Bosch. Groningen, The Netherlands. cs. rug. nl/research/se/svm/proceedingssvm 2003Groningen. pdf Thiel, S. and A. Hein, Systematic integration of variability into product line architecture design, in Software Product Lines2002, Springer. p Belategi, L., G. Sagardui, and L. Etxeberria. Variability management in embedded product line analysis. in Advances in System Testing and Validation Lifecycle (VALID), 2010 Second International Conference on IEEE.
An Aspect-Oriented Product Line Framework to Support the Development of Software Product Lines of Web Applications
An Aspect-Oriented Product Line Framework to Support the Development of Software Product Lines of Web Applications Germán Harvey Alférez Salinas Department of Computer Information Systems, Mission College,
More informationKeywords: - Software Product Lines (SPLs), Product Line Engineering (PLE), Core Assets, Software Product Line Development.
Volume 4, Issue 1, January 2014 ISSN: 2277 128X International Journal of Advanced Research in Computer Science and Software Engineering Research Paper Available online at: www.ijarcsse.com Systematic Review
More informationTool Support for Software Variability Management and Product Derivation in Software Product Lines
Tool Support for Software Variability Management and Product Derivation in Software s Hassan Gomaa 1, Michael E. Shin 2 1 Dept. of Information and Software Engineering, George Mason University, Fairfax,
More informationProduct Derivation Process and Agile Approaches: Exploring the Integration Potential
Product Derivation Process and Agile Approaches: Exploring the Integration Potential Padraig O Leary, Muhammad Ali Babar, Steffen Thiel, Ita Richardson Lero, the Irish Software Engineering Research Centre,
More informationVariability Integration at Requirements and Architecture Level in Software Product Line Engineering
Variability Integration at Requirements and Architecture Level in Software Product Line Engineering Shahliza Abd Halim Software Engineering Department Faculty of Computer Science and Information System
More information15 Jahre Software-Produktlinien: Einführung und aktueller Stand
Software Systems Engineering 15 Jahre Software-Produktlinien: Einführung und aktueller Stand Mini-Tutorial Dr. Andreas Birk (Software.Process.Management), Prof. Dr. Klaus Schmid (Universität Hildesheim)
More informationA Variability Viewpoint for Enterprise Software Systems
2012 Joint Working Conference on Software Architecture & 6th European Conference on Software Architecture A Variability Viewpoint for Enterprise Software Systems Matthias Galster University of Groningen,
More informationArchitecture Centric Development in Software Product Lines
Architecture Centric Development in Software Product Lines Aurangzeb Khan DCE, College of E & ME National University of Science and Technology (NUST), Pakistan Farooque Azam DCE, College of E & ME National
More informationSOPLE-DE: An Approach to Design Service-Oriented Product Line Architectures
SOPLE-DE: An Approach to Design -Oriented Product Line Architectures Flávio M. Medeiros, Eduardo S. de Almeida 2, and Silvio R.L. Meira Federal University of Pernambuco (UFPE) 2 Federal University of Bahia
More informationThe UML «extend» Relationship as Support for Software Variability
The UML «extend» Relationship as Support for Software Variability Sofia Azevedo 1, Ricardo J. Machado 1, Alexandre Bragança 2, and Hugo Ribeiro 3 1 Universidade do Minho, Portugal {sofia.azevedo,rmac}@dsi.uminho.pt
More informationCREDENTIALS & CERTIFICATIONS 2015
THE COMMUNITY FOR TECHNOLOGY LEADERS www.computer.org CREDENTIALS & CERTIFICATIONS 2015 KEYS TO PROFESSIONAL SUCCESS CONTENTS SWEBOK KNOWLEDGE AREA CERTIFICATES Software Requirements 3 Software Design
More informationA Framework for Software Product Line Engineering
Günter Böckle Klaus Pohl Frank van der Linden 2 A Framework for Software Product Line Engineering In this chapter you will learn: o The principles of software product line subsumed by our software product
More informationUmbrella: A New Component-Based Software Development Model
2009 International Conference on Computer Engineering and Applications IPCSIT vol.2 (2011) (2011) IACSIT Press, Singapore Umbrella: A New Component-Based Software Development Model Anurag Dixit and P.C.
More informationBusiness Process Modeling with Structured Scenarios
Business Process Modeling with Structured Scenarios Doug Rosenberg ICONIX Software Engineering, Inc. In 2008, based on our experience with a number of business process engineering projects over the last
More informationRun-time Variability Issues in Software Product Lines
Run-time Variability Issues in Software Product Lines Alexandre Bragança 1 and Ricardo J. Machado 2 1 Dep. I&D, I2S Informática Sistemas e Serviços SA, Porto, Portugal, alexandre.braganca@i2s.pt 2 Dep.
More informationTowards Collaborative Requirements Engineering Tool for ERP product customization
Towards Collaborative Requirements Engineering Tool for ERP product customization Boban Celebic, Ruth Breu, Michael Felderer, Florian Häser Institute of Computer Science, University of Innsbruck 6020 Innsbruck,
More informationBasic Unified Process: A Process for Small and Agile Projects
Basic Unified Process: A Process for Small and Agile Projects Ricardo Balduino - Rational Unified Process Content Developer, IBM Introduction Small projects have different process needs than larger projects.
More informationImproving Decision Making in Software Product Lines Product Plan Management
Improving Decision Making in Software Product Lines Product Plan Management Pablo Trinidad, David Benavides, and Antonio Ruiz-Cortés Dpto. de Lenguajes y Sistemas Informáticos University of Seville Av.
More informationManaging Variability in ALPR Software
Managing Variability in ALPR Software Dr. Marco Sinnema Product Manager Video and ALPR, Q-Free ASA P.O. Box 180, 9410 AD Beilen, The Netherlands tel. +31 593 542055, fax. +31 593 542098 marco.sinnema@q-free.com
More informationHow To Develop Software
Software Engineering Prof. N.L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture-4 Overview of Phases (Part - II) We studied the problem definition phase, with which
More informationVariability in Service-Oriented Systems: An Analysis of Existing Approaches
Variability in -Oriented Systems: An Analysis of Existing Approaches Holger Eichelberger and Christian Kröher and Klaus Schmid 1 Software Systems Engineering, Institute of Computer Science, University
More informationVARIABILITY MODELING FOR CUSTOMIZABLE SAAS APPLICATIONS
VARIABILITY MODELING FOR CUSTOMIZABLE SAAS APPLICATIONS Ashraf A. Shahin 1, 2 1 College of Computer and Information Sciences, Al Imam Mohammad Ibn Saud Islamic University (IMSIU) Riyadh, Kingdom of Saudi
More informationTo introduce software process models To describe three generic process models and when they may be used
Software Processes Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
More informationElite: A New Component-Based Software Development Model
Elite: A New Component-Based Software Development Model Lata Nautiyal Umesh Kumar Tiwari Sushil Chandra Dimri Shivani Bahuguna Assistant Professor- Assistant Professor- Professor- Assistant Professor-
More informationBuilding Service-oriented User Agents using a Software Product Line Approach. Ingrid Oliveira de Nunes ionunes@inf.puc-rio.br
Building Service-oriented User Agents using a Software Product Line Approach Ingrid Oliveira de Nunes ionunes@inf.puc-rio.br 2 Summary Introduction Objectives Integration of SOA, MAS and SPL Related Work
More informationSPLConfig: Product Configuration in Software Product Line
SPLConfig: Product Configuration in Software Product Line Lucas Machado, Juliana Pereira, Lucas Garcia, Eduardo Figueiredo Department of Computer Science, Federal University of Minas Gerais (UFMG), Brazil
More informationQuestions? Assignment. Techniques for Gathering Requirements. Gathering and Analysing Requirements
Questions? Assignment Why is proper project management important? What is goal of domain analysis? What is the difference between functional and non- functional requirements? Why is it important for requirements
More informationSeparating Concerns in Software Logistics
Separating Concerns in Software Logistics Danny Greefhorst Software Engineering Research Centre PO Box 424, 3500 AK The Netherlands greefhor@serc.nl Software logistics deals with the storage, administration,
More informationUsing Requirements Traceability Links At Runtime A Position Paper
Using Requirements Traceability Links At Runtime A Position Paper Alexander Delater, Barbara Paech University of Heidelberg, Institute of omputer Science Im Neuenheimer Feld 326, 69120 Heidelberg, Germany
More information11 Tips to make the requirements definition process more effective and results more usable
1 11 Tips to make the s definition process more effective and results more usable This article discusses what I believe are the key techniques for making s definition process repeatable from project to
More informationSoftware Rapid Approach to Agency Design and Development
1 Introduction Over the past decades, agents have become a powerful software abstraction to support the development of complex and distributed systems (Jennings 2001). They are a natural metaphor to understand
More informationCS 389 Software Engineering. Lecture 2 Chapter 2 Software Processes. Adapted from: Chap 1. Sommerville 9 th ed. Chap 1. Pressman 6 th ed.
CS 389 Software Engineering Lecture 2 Chapter 2 Software Processes Adapted from: Chap 1. Sommerville 9 th ed. Chap 1. Pressman 6 th ed. Topics covered Software process models Process activities Coping
More informationUniversity of East London Institutional Repository: http://roar.uel.ac.uk
University of East London Institutional Repository: http://roar.uel.ac.uk This paper is made available online in accordance with publisher policies. Please scroll down to view the document itself. Please
More informationComponent-based Development Process and Component Lifecycle Ivica Crnkovic 1, Stig Larsson 2, Michel Chaudron 3
Component-based Development Process and Component Lifecycle Ivica Crnkovic 1, Stig Larsson 2, Michel Chaudron 3 1 Mälardalen University, Västerås, Sweden, ivica.crnkovic@mdh.se 2 ABB Corporate Research,
More informationSoftware Engineering Reference Framework
Software Engineering Reference Framework Michel Chaudron, Jan Friso Groote, Kees van Hee, Kees Hemerik, Lou Somers, Tom Verhoeff. Department of Mathematics and Computer Science Eindhoven University of
More informationVAIL-Plant Asset Integrity Management System. Software Development Process
VAIL-Plant Asset Integrity Management System Software Development Process Document Number: VAIL/SDP/2008/008 Engineering For a Safer World P u b l i c Approved by : Ijaz Ul Karim Rao Revision: 0 Page:2-of-15
More informationSoftware Product Line Engineering to Develop Variant-rich Web Services
Software Product Line Engineering to Develop Variant-rich Web Services Bardia Mohabbati, Mohsen Asadi, Dragan Gašević, and Jaejoon Lee Abstract Service-Oriented Architecture (SOA) enables enterprise for
More informationUser experience storyboards: Building better UIs with RUP, UML, and use cases
Copyright Rational Software 2003 http://www.therationaledge.com/content/nov_03/f_usability_jh.jsp User experience storyboards: Building better UIs with RUP, UML, and use cases by Jim Heumann Requirements
More information1.1 The Nature of Software... Object-Oriented Software Engineering Practical Software Development using UML and Java. The Nature of Software...
1.1 The Nature of Software... Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering Software is intangible Hard to understand
More informationBusiness Family Engineering: Does it make sense?
Business Family Engineering: Does it make sense? Ildefonso Montero, Joaquín Peña, Antonio Ruiz-Cortés Departamento de Lenguajes y Sistemas Informáticos Av. Reina Mercedes s/n, 41012 Seville (Spain) University
More informationLinking BPMN, ArchiMate, and BWW: Perfect Match for Complete and Lawful Business Process Models?
Linking BPMN, ArchiMate, and BWW: Perfect Match for Complete and Lawful Business Process Models? Ludmila Penicina Institute of Applied Computer Systems, Riga Technical University, 1 Kalku, Riga, LV-1658,
More informationA Comparison of SOA Methodologies Analysis & Design Phases
202 A Comparison of SOA Methodologies Analysis & Design Phases Sandra SVANIDZAITĖ Institute of Mathematics and Informatics, Vilnius University Abstract. Service oriented computing is a new software engineering
More informationSoftware Requirements Specification of A University Class Scheduler
Software Requirements Specification of A University Class Scheduler Deanna M. Needell Jeff A. Stuart Tamara C. Thiel Sergiu M. Dascalu Frederick C. Harris, Jr. Department of Computer Science University
More informationA software product line approach for the development of construction safety IT solutions
Creative Construction Conference 2015 A software product line approach for the development of construction safety IT solutions Annie Guerriero*, Alain Vagner Luxembourg Institute of Science and Technology
More informationA Knowledge-based Product Derivation Process and some Ideas how to Integrate Product Development
A Knowledge-based Product Derivation Process and some Ideas how to Integrate Product Development (Position paper) Lothar Hotz and Andreas Günter HITeC c/o Fachbereich Informatik Universität Hamburg Hamburg,
More informationTOWARDS AN AUTOMATED EVALUATION PROCESS FOR SOFTWARE ARCHITECTURES
TOWARDS AN AUTOMATED EVALUATION PROCESS FOR SOFTWARE ARCHITECTURES R. Bashroush, I. Spence, P. Kilpatrick, T.J. Brown Queen s University Belfast School of Computer Science 18 Malone Road, Belfast BT7 1NN,
More informationA Service Modeling Approach with Business-Level Reusability and Extensibility
A Service Modeling Approach with Business-Level Reusability and Extensibility Jianwu Wang 1,2, Jian Yu 1, Yanbo Han 1 1 Institute of Computing Technology, Chinese Academy of Sciences, 100080, Beijing,
More informationRequirement Management with the Rational Unified Process RUP practices to support Business Analyst s activities and links with BABoK
IBM Software Group Requirement Management with the Rational Unified Process RUP practices to support Business Analyst s activities and links with BABoK Jean-Louis Maréchaux Software IT Specialist IBM Rational
More informationWeb Service Implementation Methodology
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 Web Service Implementation Methodology Public Review Draft 1.0, 05 September 2005
More informationRETRATOS: Requirement Traceability Tool Support
RETRATOS: Requirement Traceability Tool Support Gilberto Cysneiros Filho 1, Maria Lencastre 2, Adriana Rodrigues 2, Carla Schuenemann 3 1 Universidade Federal Rural de Pernambuco, Recife, Brazil g.cysneiros@gmail.com
More informationA Configuration Management Model for Software Product Line
A Configuration Management Model for Software Product Line Liguo Yu 1 and Srini Ramaswamy 2 1 Computer Science and Informatics Indiana University South Bend South Bend, IN 46634, USA ligyu@iusb.edu 2 Computer
More informationSoftware Architecture
Cairo University Faculty of Computers and Information Computer Science Department Premasters Studies Software Architecture Report on Software Product Line Submitted to: Dr. Hany Ammar Submitted by: Hadeel
More informationComparison of Software Product Line Architecture Design Methods: COPA, FAST, FORM, KobrA and QADA
Comparison of Software Product Line Architecture Design Methods: COPA, FAST, FORM, KobrA and QADA Mari Matinlassi VTT Technical Research Centre of Finland, P.O Box1100, 90571-Oulu FIN Mari.Matinlassi@vtt.fi
More informationElicitation and Modeling Non-Functional Requirements A POS Case Study
Elicitation and Modeling Non-Functional Requirements A POS Case Study Md. Mijanur Rahman and Shamim Ripon, Member IACSIT Abstract Proper management of requirements is crucial to successful development
More informationJOURNAL OF OBJECT TECHNOLOGY
JOURNAL OF OBJECT TECHNOLOGY Online at http://www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2007 Vol. 6, No. 1, January-February 2007 CM Configuration Change Management John D.
More informationAn Empirical Study of COTS components Persuasion, Evaluation & Selection and Integration in software houses Faisalabad, Pakistan
www.ijcsi.org 165 An Empirical Study of COTS components Persuasion, Evaluation & Selection and Integration in software houses Faisalabad, Pakistan Zahid Javed 1, Ahsan Raza Sattar 2, Salman Afsar 3, Muhammad
More informationSoftware Engineering. Software Processes. Based on Software Engineering, 7 th Edition by Ian Sommerville
Software Engineering Software Processes Based on Software Engineering, 7 th Edition by Ian Sommerville Objectives To introduce software process models To describe three generic process models and when
More informationProcess Patterns for Component-Based Software Development
Process Patterns for -Based Software Development Ehsan Kouroshfar, Hamed Yaghoubi Shahir, and Raman Ramsin Department of Computer Engineering Sharif University of Technology kouroshfar@ce.sharif.edu, yaghoubi@ieee.org,
More informationSoftware Development in the Large!
Software Development in the Large! Peter Eeles Executive IT Architect, IBM peter.eeles@uk.ibm.com IBM Rational Software Development Conference 2007 2007 IBM Corporation Agenda IBM Rational Software Development
More informationNASCIO EA Development Tool-Kit Solution Architecture. Version 3.0
NASCIO EA Development Tool-Kit Solution Architecture Version 3.0 October 2004 TABLE OF CONTENTS SOLUTION ARCHITECTURE...1 Introduction...1 Benefits...3 Link to Implementation Planning...4 Definitions...5
More informationSoftware Development Methodologies
Software Development Methodologies Lecturer: Raman Ramsin Lecture 5 Integrated Object-Oriented Methodologies: OPM and Catalysis 1 Object Process Methodology (OPM) Introduced by Dori in 1995 Primarily intended
More informationDesign of automatic testing tool for railway signalling systems software safety assessment
Risk Analysis VI 513 Design of automatic testing tool for railway signalling systems software safety assessment J.-G. Hwang 1, H.-J. Jo 1 & H.-S. Kim 2 1 Train Control Research Team, Korea Railroad Research
More informationA Case study based Software Engineering Education using Open Source Tools
A Case study based Software Engineering Education using Open Source Tools Sowmya B J Dept. of CSE M. S. Ramaiah Institute of Technology sowmyabj@msrit.edu Srinidhi Hiriyannaiah Dept. of CSE M.S. Ramaiah
More informationConcern Driven Software Development
Concern Driven Software Development Omar Alam School of Computer Science, McGill University, Montreal, Canada Omar.Alam@mail.mcgill.ca Abstract Model Driven Engineering (MDE) has achieved success in many
More informationCDC UNIFIED PROCESS PRACTICES GUIDE
Purpose The purpose of this document is to provide guidance on the practice of Modeling and to describe the practice overview, requirements, best practices, activities, and key terms related to these requirements.
More informationSoftware development life cycle. Software Engineering - II ITNP92 - Object Oriented Software Design. Requirements. Requirements. Dr Andrea Bracciali
Software development life cycle Software life cycle: Software Engineering - II ITNP92 - Object Oriented Software Design Dr Andrea Bracciali Module Co-ordinator 4B86 abb@cs.stir.ac.uk Spring 2014 (elicitation)
More informationCarrying Ideas from Knowledge-based Configuration to Software Product Lines
Carrying Ideas from Knowledge-based Configuration to Software Product Lines Juha Tiihonen 1, Mikko Raatikainen 2, Varvana Myllärniemi 2, and Tomi Männistö 1 1 {firstname.lastname}@cs.helsinki.fi, University
More informationCREDENTIALS & CERTIFICATIONS 2016
THE COMMUNITY FOR TECHNOLOGY LEADERS www.computer.org CREDENTIALS & CERTIFICATIONS 2016 KEYS TO PROFESSIONAL SUCCESS CONTENTS SWEBOK KNOWLEDGE AREA CERTIFICATES Software Requirements 5 Software Design
More informationUML-based Conceptual Design Approach for Modeling Complex Processes in Web Application
UML-based Conceptual Design Approach for Modeling Complex Processes in Web Application Siti Azreena Mubin Faculty of Computer Science and Information Technology, Universiti Putra Malaysia, 43400 Serdang,
More informationAn Overview of Challenges of Component Based Software Engineering
An Overview of Challenges of Component Based Software Engineering Shabeeh Ahmad Siddiqui Sr Lecturer, Al-Ahgaff University, Yemen Abstract Nowadays there is trend of using components in development of
More informationTrends in Embedded Software Development in Europe. Dr. Dirk Muthig dirk.muthig@iese.fraunhofer.de
Trends in Embedded Software Development in Europe Dr. Dirk Muthig dirk.muthig@iese.fraunhofer.de Problems A software project exceeds the budget by 90% and the project time by 120% in average Project Management
More informationTowards a Product Derivation Process Reference Model for Software Product Line Organisations
University of Limerick OLLSCOIL LUIMNIGH Towards a Product Derivation Process Reference Model for Software Product Line Organisations Submitted by Pádraig O Leary For the award of Doctor of Philosophy
More informationRequirements Traceability. Mirka Palo
Requirements Traceability Mirka Palo Seminar Report Department of Computer Science University of Helsinki 30 th October 2003 Table of Contents 1 INTRODUCTION... 1 2 DEFINITION... 1 3 REASONS FOR REQUIREMENTS
More informationA Framework for Software Architecture Visualization and Evaluation
A Framework for Software Architecture Visualization and Evaluation Dr. S. Margret Anouncia Merin Cherian Anubhuti Parija Professor, M.S Software Engg M.S Software Engg School of Computing Sciences VITU,
More informationDEVELOPING REQUIREMENTS FOR DATA WAREHOUSE SYSTEMS WITH USE CASES
DEVELOPING REQUIREMENTS FOR DATA WAREHOUSE SYSTEMS WITH USE CASES Robert M. Bruckner Vienna University of Technology bruckner@ifs.tuwien.ac.at Beate List Vienna University of Technology list@ifs.tuwien.ac.at
More informationManaging Variation in Services in a Software Product Line Context
Managing Variation in Services in a Software Product Line Context Sholom Cohen Robert Krut May 2010 TECHNICAL NOTE CMU/SEI-2010-TN-007 Research, Technology, and System Solutions (RTSS) Program Unlimited
More informationTest Cases Design for Software Database Provisioning Development
Test Cases Design for Software Database Provisioning Development Sunguk Lee Research Institute of Industrial Science and Technology Pohang, Gyeongbuk, South Korea sunguk@rist.re.kr Abstract This paper
More informationUML TUTORIALS THE USE CASE MODEL
UML TUTORIALS THE USE CASE MODEL www.sparxsystems.com.au Sparx Systems 2004 Page 1/5 describes the proposed functionality of the new system. A Use Case represents a discrete unit of interaction between
More informationCo-Creation of Models and Metamodels for Enterprise. Architecture Projects.
Co-Creation of Models and Metamodels for Enterprise Architecture Projects Paola Gómez pa.gomez398@uniandes.edu.co Hector Florez ha.florez39@uniandes.edu.co ABSTRACT The linguistic conformance and the ontological
More informationFoundations of Model-Driven Software Engineering
Model-Driven Software Engineering Foundations of Model-Driven Software Engineering Dr. Jochen Küster (jku@zurich.ibm.com) Contents Introduction to Models and Modeling Concepts of Model-Driven Software
More informationSoftware Engineering/Courses Description Introduction to Software Engineering Credit Hours: 3 Prerequisite: 0306211(Computer Programming 2).
0305203 0305280 0305301 0305302 Software Engineering/Courses Description Introduction to Software Engineering Prerequisite: 0306211(Computer Programming 2). This course introduces students to the problems
More informationModellistica Medica. Maria Grazia Pia, INFN Genova. Scuola di Specializzazione in Fisica Sanitaria Genova Anno Accademico 2002-2003
Modellistica Medica Maria Grazia Pia INFN Genova Scuola di Specializzazione in Fisica Sanitaria Genova Anno Accademico 2002-2003 Lezione 18-19 The Unified Process Static dimension Glossary UP (Unified
More informationMANAGING USER DATA IN A DIGITAL WORLD
MANAGING USER DATA IN A DIGITAL WORLD AIRLINE INDUSTRY CHALLENGES AND SOLUTIONS WHITE PAPER OVERVIEW AND DRIVERS In today's digital economy, enterprises are exploring ways to differentiate themselves from
More informationSoftware Product Lines
Software Product Lines Software Product Line Engineering and Architectures Bodo Igler and Burkhardt Renz Institut für SoftwareArchitektur der Technischen Hochschule Mittelhessen Sommersemester 2015 Questions:
More informationIncreasing Development Knowledge with EPFC
The Eclipse Process Framework Composer Increasing Development Knowledge with EPFC Are all your developers on the same page? Are they all using the best practices and the same best practices for agile,
More informationDifferent Approaches used in Software Product Families
Different Approaches used in Software Product Families Rafia Inam Mälardalens University. Rafia.inam@mdh.se Abstract The use of software in consumer products is growing tremendously in current era. Further
More informationEvaluation of a Use-Case-Driven Requirements Analysis Tool Employing Web UI Prototype Generation
Evaluation of a Use-Case-Driven Requirements Analysis Tool Employing Web UI Prototype Generation SHINPEI OGATA Course of Functional Control Systems, Graduate School of Engineering Shibaura Institute of
More informationREVIEW ON THE EFFECTIVENESS OF AGILE UNIFIED PROCESS IN SOFTWARE DEVELOPMENT WITH VAGUE SYSTEM REQUIREMENTS
REVIEW ON THE EFFECTIVENESS OF AGILE UNIFIED PROCESS IN SOFTWARE DEVELOPMENT WITH VAGUE SYSTEM REQUIREMENTS Lisana Universitas Surabaya (UBAYA), Raya Kalirungkut, Surabaya, Indonesia E-Mail: lisana@ubaya.ac.id
More informationAn Investigation of Agent Oriented Software Engineering Methodologies to Provide an Extended Methodology
An Investigation of Agent Oriented Software Engineering Methodologies to Provide an Extended Methodology A.Fatemi 1, N.NematBakhsh 2,B. Tork Ladani 3 Department of Computer Science, Isfahan University,
More informationTOGAF usage in outsourcing of software development
Acta Informatica Pragensia 2(2), 2013, 68 76, DOI: 10.18267/j.aip.25 Section: Online: aip.vse.cz Peer-reviewed papers TOGAF usage in outsourcing of software development Aziz Ahmad Rais 1, Rudolf Pecinovsky
More informationDevelopment of a Feature Modeling Tool using Microsoft DSL Tools.
Development of a Feature Modeling Tool using Microsoft DSL Tools. GIRO Technical Report 2009-1.ver 1.0 (05/01/2009) Rubén Fernández, Miguel A. Laguna, Jesús Requejo, Nuria Serrano. Department of Computer
More informationEfficient Management of Tests and Defects in Variant-Rich Systems with pure::variants and IBM Rational ClearQuest
Efficient Management of Tests and Defects in Variant-Rich Systems with pure::variants and IBM Rational ClearQuest Publisher pure-systems GmbH Agnetenstrasse 14 39106 Magdeburg http://www.pure-systems.com
More informationAn Approach to Software Architecture Description Using UML
An Approach to Software Architecture Description Using UML Henrik Bærbak Christensen, Aino Corry, and Klaus Marius Hansen Department of Computer Science, University of Aarhus Aabogade 34, 8200 Århus N,
More informationFRAUNHOFER INSTITUTE FOR EXPERIMENTAL SOFTWARE ENGINEERING IESE VARIATION MANAGEMENT: USER EXPERIENCE FOR EFFICIENCY IN PROVIDING SOLUTIONS
FRAUNHOFER INSTITUTE FOR EXPERIMENTAL SOFTWARE ENGINEERING IESE VARIATION MANAGEMENT: USER EXPERIENCE FOR EFFICIENCY IN PROVIDING BUSINESS CUSTOMIZED APPLICATIONS SOLUTIONS 2 Do you need to develop variation-rich
More informationRequirements Traceability
UNIVERSITY OF WATERLOO Faculty of Mathematics School of Computer Science CS 645 - Software Requirements Specification and Analysis Requirements Traceability prepared by Michael Morckos ID : 20363329 Electrical
More informationBusiness Modeling with UML
Business Modeling with UML Hans-Erik Eriksson and Magnus Penker, Open Training Hans-Erik In order to keep up and be competitive, all companies Ericsson is and enterprises must assess the quality of their
More informationElicitation and Modeling Non-Functional Requirements A POS Case Study
Elicitation and Modeling Non-Functional Requirements A POS Case Study Md. Mijanur Rahman and Shamim Ripon, Member IACSIT Abstract Proper management of requirements is crucial to successful development
More informationFourth generation techniques (4GT)
Fourth generation techniques (4GT) The term fourth generation techniques (4GT) encompasses a broad array of software tools that have one thing in common. Each enables the software engineer to specify some
More informationRotorcraft Health Management System (RHMS)
AIAC-11 Eleventh Australian International Aerospace Congress Rotorcraft Health Management System (RHMS) Robab Safa-Bakhsh 1, Dmitry Cherkassky 2 1 The Boeing Company, Phantom Works Philadelphia Center
More informationAPPLYING CASE BASED REASONING IN AGILE SOFTWARE DEVELOPMENT
APPLYING CASE BASED REASONING IN AGILE SOFTWARE DEVELOPMENT AIMAN TURANI Associate Prof., Faculty of computer science and Engineering, TAIBAH University, Medina, KSA E-mail: aimanturani@hotmail.com ABSTRACT
More information