A Triptych Software Development Paradigm: Domain, Requirements and Software

A paradigmatic three stage approach to software development is sketched in terms of a torso-like, but schematic development of informal and formal descriptions (i) of the domain of sustainable development, (ii) of requirements to decision support software for developing models for and monitoring development (claimed to be sustainable), and (iii) of rudiments of a software architecture for such a system. In "one bat we tackle three problems": (i) illustrating a fundamental approach to separation of concerns in software development: From domain via requirements to software descriptions; (ii) contributing towards a theory of sustainable development: Bringing some precision to many terms fraught by "political correctness"; and (iii) providing, we believe, a proper way of relating geographic information system+demographic information system systems to decision support software. Perhaps a fourth result of this paper can be claimed: (iv) Showing, as we believe it does, the structural main parts of a proper presentation of software.

[1]  A. Steer,et al.  Sustainable development: Theory and practice for a sustainable future , 1993 .

[2]  Dave Roberts,et al.  Developing Software Using , 1997 .

[3]  Diana Liverman,et al.  Global sustainability: Toward definition , 1987 .

[4]  Dines Bjørner.  Domain Modelling: Resource Management: Strategics, Tactics and Operations , 2000 .

[5]  John Handmer,et al.  Contradictions in Sustainability , 1993, Environmental Conservation.

[6]  Alison J. Gilbert,et al.  Modelling for Population and Sustainable Development , 1991 .

[7]  J. Simon.  The Ultimate Resource , 1983 .

[8]  Dines Bjørner,et al.  Domains as a Prerequisite for Requirements and Software Domain Perspectives & Facets, Requirements Aspects and Software Views , 1997, Requirements Targeting Software and Systems Engineering.

[9]  N. Georgescu-Roegen.  The Entropy Law and the Economic Process , 1973 .

[10]  D Bjorner.  Where do software architectures come from? Systematic development from domains and requirements. A re-assessment of software engineering? , 1998 .

[11]  G. Brundtland,et al.  Our common future , 1987 .

[12]  Dave Roberts,et al.  Developing Software Using OVID , 1997, IEEE Softw..

[13]  Dines Bjørner,et al.  Pinnacles of software engineering: 25 years of formal methods , 2000, Ann. Softw. Eng..

[14]  Julius T. Tou,et al.  Information Systems , 1973, GI Jahrestagung.

[15]  M. Redclift.  Sustainable development: exploring the contradictions. , 1987 .

[16]  Lynton K. Caldwell,et al.  Political Aspsects of Ecologically Sustainable Development , 1984, Environmental Conservation.

[17]  Dines Bjørner,et al.  Software Engineering Education: R^ Oles of Formal Speciication and Design Calculi , 1998 .

[18]  L LuisGuillermoPosada,et al.  Nicholas Georgescu-Roegen. , 1999 .

[19]  T. Bernhardsen.  Geographic Information Systems: An Introduction , 1999 .

[20]  Clive Ponting.  Historical Perspectives on Sustainable Development , 1990 .

[21]  Dines Bj.  Where do Software Architectures come from ? Systematic Development from Domains and RequirementsA Re-assessment of Software Engineering ? , 1998 .