Structured analysis: Difference between revisions

Revision as of 22:44, 23 July 2019

Revision as of 23:27, 28 January 2020

Line 91:

* data dictionary.

The [[structure chart]] aims to show "the module hierarchy or calling sequence relationship of modules. There is a module specification for each module shown on the structure chart. The module specifications can be composed of pseudo-code or a program design language. The [[data dictionary]] is like that of structured analysis. At this stage in the [[software development lifecycle]], after analysis and design have been performed, it is possible to automatically generate data type declarations",<ref>Belkhouche, B., and J.E. Urban. (1986). "Direct Implementation of Abstract Data Types from Abstract Specifications". In: ''IEEE Transactions on Software Engineering'' pp. 549-661, May 1986.</ref> and procedure or subroutine templates.<ref name="HeSi86" />

=== Structured query language ===

The [[structured query language]] (SQL) is a standardized language for querying information from a [[database]]. SQL was first introduced as a commercial database system in 1979 and has since been the favorite query language for database management systems running on minicomputers and mainframes. Increasingly, however, SQL is being supported by PC database systems because it supports distributed databases (see definition of distributed database). This enables several users on a computer network to access the same database simultaneously. Although there are different dialects of SQL, it is nevertheless the closest thing to a standard query language that currently exists.<ref name="USDT01"/>

== Criticisms ==