E. H. Bersoff, `Elements of software configuration management', IEEE Trans. Software Eng., 10, (1), 79--87 (1984).  Home/Search   Document Not in Database   Summary   Related Articles   Check

....processes. Software development environments, however, are still far from supporting these new forms of virtual workgroups through specific network aware services [7] As an example consider the case of configuration management (CM) tools. Software processes are typically supported by CM tools [2] that help developers to keep consistent their work, and, despite of dynamic nature of software teams, these are typically client server applications. For example, one of the simplest, but most popular of these tools, i.e. CVS [6] is based on the concept of the artifact repository. This is a ....

E. H. Bersoff. Elements of software configuration management. Software Engineering, 10(1):79--87, 1984.

.... for the purpose of systematically controlling changes to the configuration, recording and reporting change processing and implementation status, verifying compliance with specified requirements, and maintaining the integrity and traceability of the configuration throughout the system life cycle [6]. Responsibilities of each software project manager related to SCM include enforcing the practice of SCM activities for the project, distributing the activities to the relevant individuals, and managing and administrating the results of these activities. Figure 6 illusrtates the activities ....

Bersoff, E.H., Elements of Software Configuration Management. In: Dorfman, M., Thayer, R.H. (eds), Software Engineering. Los Alamitos: IEEE Computer Society Press, 1997, pp. 345-356.

.... Keywords Software configuration management, version control, software engineering 1 INTRODUCTION Today a wide selection of commercially available configuration management systems exist; one web site catalogs over 50 such packages [4] The technology of these systems is well understood [1, 3, 6, 7, 8, 10], but the actual use patterns and motivations for fine grain operations such as check in are not. For example, we expect a check in when the modification of an item is complete but motivations for check ins due to incremental changes are less predictable. We have observed differences in ....

E. H. Bersoff. Elements of software configuration management. IEEE Trans. on Software Engineering, 10(1):79--87, Jan. 1984.

.... engineering management; for example, how best to structure and manage software technical teams (Baker 1972) how to facilitate project communication through modular product design (Parnas 1972) how to control evolving software systems in a multi user, multi product development environment (Bersoff 1984), and how to streamline document flow and reporting mechanisms in medium to large IT projects (CCTA 1990) The benefits to be gained from effectively addressing this challenge remain substantial. Effective coordination leads to more efficient working practices, minimizes misunderstandings, reduces ....

Bersoff, E.H. (1984) "Elements of software configuration management." D@@@U...h+#'T's##h...r@tvrr...vt, Vol 10 No 1, pp 79-87.

....For such systems it is desirable to have an on line software modification system which eliminates the system shutdown for installing a new version of the software, thus allowing continuous service to the users of the software. This problem is different from the problem of configuration control [1] and version control [2] which are essentially means to manage the changes made during the development of software. The goal of these techniques is to prevent uncontrolled changes and extreme proliferation of program versions. On the other hand, on line replacement deals with the problem of ....

.... the file server.new and the, the change configuration file is named change config, then the new version is installed by giving the command re server.new change config init change: 16 init change( f extra1 = malloc(4 sizeof(char) extra2 = malloc(3 sizeof(char) extra1[0] f ; extra1[1] = p ; extra1[2] o ; extra1[3] 0 ; extra2[0] extra2[1] s ; extra2[2] 0 ; cause trap( g Figure 5: Change initialization routine for print server System Performance We have conducted some experiments to determine the overhead incurred due to on line ....

[Article contains additional citation context not shown here]

E. H. Bersoff. "Elements of software configuration management". IEEE Trans. on Software Engg., 10(1):79--87, 1984.

....configuration management also addresses the evolution of software systems. Problems such as those above can be thought of as problems of identification, control and validation, problems which are typical of those addressed by configuration management systems (as discussed, for example, in [9]) It is therefore clear that dynamically bound systems would benefit from configuration management, and that the integration of configuration management and dynamic binding is worthy of investigation. In considering how to provide configuration management support for dynamically bound systems, it ....

E. H. Bersoff. Elements of software configuration management. IEEE Transactions on Software Engineering., SE-10(1):79--87, 1984.

....hand, application of SCM methods and tools in a CASE supported development is connected with several problems. In the paper, we analyze some of the problems connected with integrating SCM with CASE. We concentrated mainly on configuration identification as one of the most fundamental SCM processes [1]. We propose a technique of identifying versions of software system process models as described by data flow diagrams. We report on a first experience with applying the technique. 2 Versioning CASE tools support various activities during the software life cycle, but the analysis and design are ....

E.H. Bersoff. Elements of software configuration management. IEEE Transactions on Software Engineering, SE-10(1):79--87, 1984.

....systems is then discussed. Keywords: Configuration management; dynamically composed systems; models. 1 Introduction Software changes. Among the many techniques and technologies developed to manage changes in software systems is the collection of ideas and tools known as configuration management [1,2]. Unfortunately, the vast majority of approaches to configuration management assume that, when in use, software systems are complete and remain unchanged. Specifying the configuration of a software system can thus be done statically, and building a configuration becomes a matter of following the ....

E. H. Bersoff. Elements of Software Configuration Management. IEEE Transactions on Software Engineering, SE-10(1):79--87, 1984.

....of module disconnectivity into being a programming language aspect, what remained was module interconnectivity, i.e. the identification and control of system composition. This is essentially what was the starting point for a new field of research, namely software configuration management [23] [24]. In this paper we will not consider the aspects of module disconnectivity any further, but focus our attention on the field of software configuration management and how it has developed. Early software configuration management grew out of the recommendations of Parnas [25] 26] to split up the ....

: Bersoff, Edward H.: Elements of Software Configuration Management, IEEE Transactions on Software Engineering, Vol. SE-10, No. 1, January 1984.

No context found.

E. H. Bersoff, `Elements of software configuration management', IEEE Trans. Software Eng., 10, (1), 79--87 (1984).

No context found.

E. H. Bersoff, "Elements of Software Configuration Management," IEEE Trans. Software Eng., Vol. 10, No. 1, Jan. 1984, pp. 79--87.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC