By Topic

Change-oriented version descriptions in EPOS

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
$33 $33
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

3 Author(s)
B. Gulla ; Div. of Comput. Syst. & Telematics, Norwegian Inst. of Technol., Trondheim, Norway ; E. -A. Karlsson ; D. Yeh

In EPOS, software configuration management is based on the change-oriented versioning model. As part of a configured system specification, a version description is used to select the desired versions of different components that constitute the product. Furthermore, version descriptions are used to specify which versions are affected by a certain change. For large software systems comprising many variants, building a consistent configuration meeting specified requirements is not an easy task. The authors propose a set of version description mechanisms and exemplify their use. An abstract description specifying the desired properties and functional requirements is expanded, using validities characterising properties of versions, preferences and defaults.<>

Published in:

Software Engineering Journal  (Volume:6 ,  Issue: 6 )