1977
DOI: 10.1109/tse.1977.229902
|View full text |Cite
|
Sign up to set email alerts
|

PSL/PSA: A Computer-Aided Technique for Structured Documentation and Analysis of Information Processing Systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
42
0
3

Year Published

1980
1980
2015
2015

Publication Types

Select...
5
4

Relationship

0
9

Authors

Journals

citations
Cited by 401 publications
(49 citation statements)
references
References 2 publications
0
42
0
3
Order By: Relevance
“…Teichroew and his team of Ph.D. students had invented CASE, a set of technologies and processes for developing high quality code. The team continued the to make substantial progress on CASE tools for many years [67]. Nunamaker, however, remained focused on the question of how a systems analyst could bring 4000 stakeholders to consensus around the requirements for a large, complex system without having to hire consultants to sit with each stakeholder and write PSL.…”
Section: Last Research Mile For Group Support Systemsmentioning
confidence: 99%
“…Teichroew and his team of Ph.D. students had invented CASE, a set of technologies and processes for developing high quality code. The team continued the to make substantial progress on CASE tools for many years [67]. Nunamaker, however, remained focused on the question of how a systems analyst could bring 4000 stakeholders to consensus around the requirements for a large, complex system without having to hire consultants to sit with each stakeholder and write PSL.…”
Section: Last Research Mile For Group Support Systemsmentioning
confidence: 99%
“…The tools and methods of the time permitted and assisted in the organization of the requirements, refinement of details, consistency checking, preparation of the specification, and in some cases, formalization of these requirements (Alford, 1977;Ross, 1977;Teichroew, 1977;Alford, 1978;Zave, 1982;Burstin, 1984;Alford, 1985;Borgida, 1985;Sievert, 1985;Estrin, 1986). Some of these tools also provided a means to relate design and implementation artifacts to their individual requirements to assist in the eventual validation of the realization of the requirements.…”
Section: Brief History Of Requirements Engineering Methods and Toolsmentioning
confidence: 99%
“…Here again the prerequisite is rigor in the specification. A number of rigorous specification methodologies have been proposed (e.g., SAMM [26], SADT [27], PSL/PSA [28]). …”
Section: Software Lifecycle Considerationsmentioning
confidence: 99%