Abstract
This paper considers aspects of Software Configuration Management (SCM) in its role of supporting configurations that arise in development of software using the refinement calculus. From an SCMperspective, the primary difference between formal development methods, such as the refinement calculus, and traditional development methods is the nature of relationships within the development configuration. The relationships are very precise; occur at much finer levels of granularity; and evolve through an iterative/intertwined development process. In analysing support for the refinement calculus, this paper proposes a configuration model which defines the relationships that occur during development and how these relationships evolve as development activities are applied and modifications are made. The configuration model enables properties regarding relationships to be formally inferred. The results of these inferences may be used in developing automated support for refinement calculus developments, such as change impact analysis, traceability and remanufacturing services.
Highlights
During software development a system will evolve to satisfy particular requirements
This paper introduces the use of configuration models to capture properties of software development configurations, in particular those which arise using the refinement calculus
In summary this paper provided a configuration model of refinement calculus developments
Summary
During software development a system will evolve to satisfy particular requirements. Many requirements of the methodology involve how the components of the development documentation The refinement calculus [7] defines a development methodology for the correct transformation of program specifications into implementations. In the refinement calculus there is a precise notion of a refinement relationship which indicates when an implementation satisfies a specification. In providing SCM support for the refinement calculus there are many requirements of the methodology based on the nature of the refinement relationship. This paper introduces the use of configuration models to capture properties of software development configurations, in particular those which arise using the refinement calculus. A configuration model defines the structure of the configurations which occur within the development documentation, as well as the relationships which exist within and between these configurations. The model identifies the relationships required to meet the methodology (e.g. the refinement relationship), and identifies how these relationships are established as process activities are applied and how they are affected as changes are made
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
