No label defined (Q3747711)
From MaRDI portal
!
This is the item page for this Wikibase entity, intended for internal use and editing purposes. Please use the normal view instead:
scientific article; zbMATH DE number 3984558
| Language | Label | Description | Also known as |
|---|---|---|---|
| default for all languages | No label defined |
||
| English | No label defined |
scientific article; zbMATH DE number 3984558 |
Statements
1985
0 references
software design
0 references
very high level data types
0 references
software development tool
0 references
control structures
0 references
parallelism
0 references
synchronisation
0 references
sub-components in complex systems
0 references
collections of objects
0 references
implementation
0 references
module construct
0 references
software units
0 references
abstract data types
0 references
module type
0 references
0.648018479347229
0 references
0.6411516070365906
0 references
The term 'software engineering' was first coined in the 1960s in response to the realisation that the activity of software construction could be viewed as an engineering discipline. This view enabled a clearer insight into the shortcomings of software construction methods by encouraging comparisons with other branches of engineering. These shortcomings can to a large extent be traced to inadequacies in programming language support for common engineering techniques. Despite some progress in recent years several major areas of difficulty remain. Those particularly focused on this thesis are: the lack of a powerful, general model for sub-components in complex systems, the poor understanding of collections of objects and their internal structures, and confusion concerning the relationship between design and implementation. The thesis examines the requirements for a general module construct and it is argued that the module construct of Leibniz fulfills these requirements to a greater degree than the module constructs of other languages. In particular more uniformity is achieved in the definition of different kinds of software units. Files (including standard input and output) are seen simply as instances of abstract data types. Records are also seen simply as module type, allowing the definition of operations on these types.
0 references