Close category search window
 

Distributed techniques in software systems integration

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)
Ramamoorthy, C.V. ; Div. of Comput. Sci., California Univ., Berkeley, CA, USA

Many aspects of software development use varieties of distributed computing techniques. We focus on a specific phase known generally as testing but more appropriately as iterative test and integration. Traditional software development is mandated by methodologies. These methodologies follow from the waterfall model of software development, and provide automation support via software tools for coding, documentation analysis and evaluation. Quality and productivity have become the driving forces and this in turn emphasized modularity, reusability and use of formal methods where possible. The traditional waterfall model of software development partitions the processing sequence into phases of requirements, specification, design, implementation, and testing and validation. While this is still the basic conceptual model used in most of the development methodologies, this does not explicitly include the feedback and revisions between phases due to errors, problems, omissions and changes. Also it does not include the process of integration that takes place at every step and most importantly in the later stages namely, iterative testing and integration. We discuss our approach to the system integration problems which are outlined. The system integration process mainly depends on (a) a formal methodology that leads to an efficient integration testing plan, and (b) a consistency checking mechanism that validates the module subsystem interfaces and intermodule interactions during all the changes of the integration testing process. The integration plan that is produced should be good in the sense that the scheduling and partitioning of a collection of modules to be integrated should be done to reduce the interactions and dependencies between program units as modifications are made at the different phases of the development and assist in localizing errors during integration testing. We investigate issues in the generic integration lifecycle including properties that individual software modules should possess for efficient integration and guidelines for designing modules

Published in:
Distributed Computing Systems, 1995., Proceedings of the Fifth IEEE Computer Society Workshop on Future Trends of

Date of Conference: 28-30 Aug 1995

Need Help?


IEEE Advancing Technology for Humanity About IEEE Xplore | Contact | Help | Terms of Use | Nondiscrimination Policy | Site Map | Privacy & Opting Out of Cookies

A not-for-profit organization, IEEE is the world's largest professional association for the advancement of technology.
© Copyright 2013 IEEE - All rights reserved. Use of this web site signifies your agreement to the terms and conditions.