1992
DOI: 10.1002/j.2334-5837.1992.tb01524.x
|View full text |Cite
|
Sign up to set email alerts
|

COMPUTER‐AIDED SYSTEM ENGINEERING TOOLS —THE DESIGN SRATM FAMILY OF TOOLS

Abstract: The authors and others at PRC have developed a family of computer‐automated system engineering (CASE) tools which support system requirements analysis, automatic specification preparation, requirements traceability, and rapid access to system engineering reference data. The tools include the following: Design SRATM (requirements analysis tool) Spec WriterTM (automatic specification tool) SpecREFTM (digital image library access)* SpecTRACETM (requirement traceability)* SpecEditorTM (specification editing tool)… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

1994
1994
1995
1995

Publication Types

Select...
2

Relationship

0
2

Authors

Journals

citations
Cited by 2 publications
(1 citation statement)
references
References 0 publications
0
1
0
Order By: Relevance
“…(White et al 1992) hold out hope for improving the quality of system requirements analysis by standardizing and automating the processes used. Tools defined to date, however, do not address the need to relate the antecedents explicitly in the functional requirements data set as specific parts of the requirements analysis (Elliott and Vickers 1992). For example, using the standard requirements allocation sheets (RAS), the antecedent conditions are defined as part of the function description, but do not explicitly make it into the actual requirements documents.…”
Section: Automationmentioning
confidence: 99%
“…(White et al 1992) hold out hope for improving the quality of system requirements analysis by standardizing and automating the processes used. Tools defined to date, however, do not address the need to relate the antecedents explicitly in the functional requirements data set as specific parts of the requirements analysis (Elliott and Vickers 1992). For example, using the standard requirements allocation sheets (RAS), the antecedent conditions are defined as part of the function description, but do not explicitly make it into the actual requirements documents.…”
Section: Automationmentioning
confidence: 99%