Formality‚ Evolution‚ and Model−driven Software Engineering
This paper introduces an approach to software development in which a series of working implemen- tations are generated automatically from a series of formal specifications. The implementations are data stores, communicating through standard protocols. The specifications are precise object models, in...
| Main Authors: | , , , , |
|---|---|
| Format: | Journal article |
| Published: |
2005
|
| _version_ | 1797099868456484864 |
|---|---|
| author | Davies, J Crichton, C Crichton, E Neilson, D Sørensen, I |
| author_facet | Davies, J Crichton, C Crichton, E Neilson, D Sørensen, I |
| author_sort | Davies, J |
| collection | OXFORD |
| description | This paper introduces an approach to software development in which a series of working implemen- tations are generated automatically from a series of formal specifications. The implementations are data stores, communicating through standard protocols. The specifications are precise object models, in which operations are described in terms of pre- and post-conditions. The approach is evolutionary, in the sense that the specification may evolve while the system is in use, in response to changes in requirements, and any changes to the specification are automatically reflected in the structure of the implementation, and in the representation of any data currently stored. |
| first_indexed | 2024-03-07T05:29:45Z |
| format | Journal article |
| id | oxford-uuid:e1d61b89-5850-4847-8362-114634b3e261 |
| institution | University of Oxford |
| last_indexed | 2024-03-07T05:29:45Z |
| publishDate | 2005 |
| record_format | dspace |
| spelling | oxford-uuid:e1d61b89-5850-4847-8362-114634b3e2612022-03-27T09:56:59ZFormality‚ Evolution‚ and Model−driven Software EngineeringJournal articlehttp://purl.org/coar/resource_type/c_dcae04bcuuid:e1d61b89-5850-4847-8362-114634b3e261Department of Computer Science2005Davies, JCrichton, CCrichton, ENeilson, DSørensen, IThis paper introduces an approach to software development in which a series of working implemen- tations are generated automatically from a series of formal specifications. The implementations are data stores, communicating through standard protocols. The specifications are precise object models, in which operations are described in terms of pre- and post-conditions. The approach is evolutionary, in the sense that the specification may evolve while the system is in use, in response to changes in requirements, and any changes to the specification are automatically reflected in the structure of the implementation, and in the representation of any data currently stored. |
| spellingShingle | Davies, J Crichton, C Crichton, E Neilson, D Sørensen, I Formality‚ Evolution‚ and Model−driven Software Engineering |
| title | Formality‚ Evolution‚ and Model−driven Software Engineering |
| title_full | Formality‚ Evolution‚ and Model−driven Software Engineering |
| title_fullStr | Formality‚ Evolution‚ and Model−driven Software Engineering |
| title_full_unstemmed | Formality‚ Evolution‚ and Model−driven Software Engineering |
| title_short | Formality‚ Evolution‚ and Model−driven Software Engineering |
| title_sort | formality evolution and model driven software engineering |
| work_keys_str_mv | AT daviesj formalityevolutionandmodeldrivensoftwareengineering AT crichtonc formalityevolutionandmodeldrivensoftwareengineering AT crichtone formalityevolutionandmodeldrivensoftwareengineering AT neilsond formalityevolutionandmodeldrivensoftwareengineering AT sørenseni formalityevolutionandmodeldrivensoftwareengineering |