dc.contributor.author | Bjorner, D | |
dc.date.accessioned | 2018-06-06T14:09:24Z | |
dc.date.available | 2018-06-06T14:09:24Z | |
dc.date.issued | 1998 | |
dc.identifier.citation | Bjorner D (1999) Where do software architectures come from? Systematic development from domains and requirements. A re-assessment of software engineering? South African Computer Journal, Number 22, 1998 | en |
dc.identifier.issn | 2313-7835 | |
dc.identifier.uri | http://hdl.handle.net/10500/24291 | |
dc.description.abstract | In this paper we show how details of a software design emerges in two steps: software architecture and program organisation and from first having established careful descriptions of the application domain and of functional and non-functional requirements. A major aim & objective of this paper is a reassessment of software engineering in the context of extensive use of formal techniques (formal methods: specification and calculi) and programming methodological: to illustrate how software designs partially evolve from careful (formal) requirements descriptions which themselves partially evolve from careful (formal) application domain descriptions. We believe that this paper covers some new concepts: • the careful construction of informal as well as formal descriptions of application domains without any reference to software (i.e. computing); • the systematic (posit/invent & verify/prove) "derivation" of requirements from domain descriptions; • and the separation of requirements and software design concerns: - functional requirements as implemented through software architectures, and - non-functional requirements as implemented through program organisations. | en |
dc.language.iso | en | en |
dc.publisher | South African Computer Society (SAICSIT) | en |
dc.subject | Software engineering | en |
dc.subject | Domain engineering | en |
dc.subject | Requirements engineering | en |
dc.subject | Software design | en |
dc.subject | Software architecture | en |
dc.subject | Program organisation | en |
dc.subject | Abstraction | en |
dc.subject | Modelling | en |
dc.subject | Development validation | en |
dc.subject | Correctness verification | en |
dc.subject | Formal specification | en |
dc.subject | RAISE | en |
dc.subject | RSL | en |
dc.title | Where do software architectures come from? Systematic development from domains and requirements. A re-assessment of software engineering? | en |
dc.type | Article | en |