Framework for Evaluating the Version Management Capabilities of a Class of UML Modeling Tools from the Viewpoint of Multi-Site, Multi-Partner Product Line Organizations

J. Softw. Maint. Evol.: Res. Pract.

Koivulahti-Ojala

Liimatainen³

2010

Self Cite

High‐tech companies conducting product development need to collect and analyze requirements effectively, plan and implement releases, and allocate requirements to appropriate releases. Requirements and release management are complicated because development activities typically are scattered across multiple sites, involve multiple partners in different countries, leverage various development methods and tools, and are realized through various organizational arrangements such as release projects in organizations structured around products and permanent release teams in organizations responsible for the long‐term development and maintenance of strategic software and hardware assets. Flexible, scalable, and secure groupware‐based support for the activities provides substantial payoffs. Yet, the extant literature provides little theoretical guidance for designing and using requirements and release management systems (RRMS) in multi‐site, multi‐partner environments. This article develops the meta‐requirements and a meta‐design of an Information Systems Design Product Theory for the class of RRMS based on a case study in a global company and a literature review. The theory is scalable to meet the needs of global companies but simple enough so that small and medium‐sized companies can also leverage it to implement requirements and release management solutions. Copyright © 2010 John Wiley & Sons, Ltd.

Section: Description Of the Case Organization And The Research Methodsmentioning

confidence: 99%

An information systems design product theory for the class of integrated requirements and release management systems

J. Softw. Maint. Evol.: Res. Pract.

Koivulahti-Ojala

Liimatainen³

2010

Self Cite

“…Versioning enables dispersed testing teams to manage multiple versions of test artifacts in parallel, while providing an audit trail of changes throughout the life-cycle of each engagement. Version control thus helps clients and providers manage and track changes (Koivulahti-Ojala & Käkölä, 2010). The attributes of all the stored documents include name, status, version number, and author to help clients and providers to avoid parallel, conflicting changes of the shared files in a multiuser environment.…”

Section: Client Repairs Defects and Forms A New Test Versionmentioning

confidence: 99%

A dynamic life-cycle model for the provisioning of software testing services

Systems Science & Control Engineering

2014

Information and communications technology (ICT)-enabled international sourcing of software-intensive systems and services (eSourcing) is a powerful strategy for managing businesses more effectively. China is becoming a superpower for eSourcing service provisioning, but most Chinese providers are small-or medium-sized and leverage the mediated eSourcing model, delivering services to foreign ICT clients who interface with end-clients onshore. This model restricts the providers to lowvalue projects. This paper probes eSourcing of software testing services within the Chinese market because testing is one of the best ICT services small-and medium-sized providers can provide to develop domain and technological knowledge required to transcend the limitations of the mediated sourcing model. This paper draws upon a literature review and a case study to create and validate a life-cycle model for the provisioning of software testing services that helps providers to develop the capabilities for overcoming the limitations of mediated sourcing. This model helps clients and providers to dynamically manage the life-cycle, assigns specific responsibilities to the involved roles, and supports the tasks of the roles and the entire life-cycle with a class of integrated requirements, test, and defect management systems. This class is found to be the most important class of information systems for enabling the life-cycle.

“…On the other hand, high levels of abstraction improve productivity, for example, by enabling the automation of routine development tasks [23]. Industrially validated modeling methods and commercially available modeling tools are critically important to deal with the abstractions [13]. In addition to traditional system modeling, variability modeling is required in product line engineering to document explicitly how the applications within the product line can vary.…”

Section: The Need For High Levels Of Abstractionmentioning

confidence: 99%

Standards Initiatives for Software Product Line Engineering and Management within the International Organization for Standardization

2010 43rd Hawaii International Conference on System Sciences

2010

Self Cite

Software product line engineering is an established methodology for fast and effective development of software-intensive systems and services. To reap maximum benefits from the methodology, businesses typically need to implement coordinated changes in development methodologies, tools, product architectures, organizational designs, and business models. Product lines are developed in complex international software ecosystems, but there is no coordinated set of international standards for defining and leveraging the methodology. As a result, ecosystems cannot adopt standardized methods and tools for developing product lines, tool vendors face difficulties in developing tools to enable product line engineering, and universities cannot effectively set up product line engineering courses because an internationally accepted curriculum is missing. The International Organization for Standardization has initiated several projects to create a set of international standards for software product line engineering. Practitioners, researchers, and other stakeholders can contribute to these projects through their national standards bodies. This paper discusses the projects and future directions for product line standardization.