System Requirements and Specifications
James D. Palmer,
James D. Palmer
George Mason University, 860 Cashew Way, Fremont, CA, 94536
Search for more papers by this authorJames D. Palmer,
James D. Palmer
George Mason University, 860 Cashew Way, Fremont, CA, 94536
Search for more papers by this authorFirst published: 27 December 1999
Abstract
The sections in this article are
- 1 Problems and Issues Concerning System Requirements and Specifications Development
- 2 System Requirements and Specifications Processes
- 3 Characteristics of System Requirements and Specifications That Influence The Process
- 4 Tool Support For Management of System Requirements and Specifications
- 5 Final Observations
Bibliography
- 1 J. D. Palmer N. A. Fields An integrated environment for software requirements engineering, Software, 80–85, May 1992.
- 2 A. P. Sage J. D. Palmer Software Systems Engineering, New York: Wiley, 1990.
- 3 B. W. Boehm Improving software productivity, Computer, 20 (9): 43–57, 1987.
- 4 A. D. Gordon Classification, New York: Chapman and Hall, 1981.
- 5 J. D. Palmer Y. Liang Indexing and clustering of software requirements specifications, Inf. Decision Technol., 18: 283–299, 1992.
- 6 M. R. Anderberg Clustering Analysis for Application, New York: Academic Press, 1973.
- 7 J. D. Palmer S. Park Automated support to system modeling from informal software requirements, Sixth Int. Conf. Software Eng. Knowledge Eng., Latvia, June 20–23, 1994.
- 8 G. Salton M. J. McGill Automatic Information Organization and Retrieval, New York: McGraw-Hill, 1983.
- 9 IEEE Software Engineering Standards, 1987.
- 10 H. Gomaa A software design method for real-time systems, Commun. ACM, 27 (9): 657–688, 1984.
- 11 A. M. Davis Software Requirements: Objects, Functions, and States, Englewood Cliffs, NJ: Prentice-Hall, 1993.
- 12 F. P. Brooks, Jr. No silver bullet: Essence and accidents in software engineering, Computer, 20 (4): 10–19, 1987.
- 13 D. T. Ross K. E. Shoman, Jr. Structured analysis for requirements definition, IEEE Trans. Softw. Eng., SE-3 (1): 69–84, 1977.
- 14 RDD-100—Release Notes Release 3.0.2.1, October, 1992, Requirements Driven Design, Ascent Logic Corporation, San Jose, CA, 1992.
- 15 M. D. Vertal Extending IDEF: Improving complex systems with executable modeling, 1994 Annu. Conf. Bus. Re-eng., IDEF Users Group, Richmond, VA, May 1994.
- 16 M. W. Alford SREM at the age of eight: The distributed computing design system, Computer, 18 (4): 36–46, 1985.
- 17 R. F. Flynn M. Dorfman The automated requirements traceability system (ARTS), AIAA Third Computers in Aerospace Conf., AIAA, pp. 418–428, 1981.
- 18 Document Director—The Requirements Tool, B.G. Jackson Associates, Houston, TX, 1989.
- 19 J. Nallon Implementation of NSWC requirements traceability models, CSESAW 94, White Oak, MD, NSWCDD/MP-94/122, pp. 15–22, July 19–20, 1994.
- 20 N. Rundley W. D. Miller DOORS to the digitize battlefield: Managing requirements discovery and traceability, CSESAW 94, White Oak, MD, NSWCDD/MP-94/122, pp. 23–28, July 19–20, 1994.
- 21 W. L. Johnson M. Feather D. Harris Representing and presenting requirements knowledge, IEEE Trans. Softw. Eng., SE-18 (10), 853–869, 1992.
- 22 R. G. Mays et al. PDM: A requirements methodology for software system enhancements, IBM Systems J., 24 (2): 134–149, 1985.
- 23
C. Rich
R. Waters
The programmers apprentice: A research overview,
Computer,
21 (11):
10–25,
1988.
10.1109/2.86782 Google Scholar
- 24 S. Faulk et al. The CoRE method for real-time requirements, Software, 9 (5): 22–33, 1992.
- 25
H. Kaindl
The missing link in requirements engineering,
ACM SIGSOFT Softw. Eng. Notes,
18 (2):
30–39,
1993.
10.1145/159420.155836 Google Scholar
- 26 J. D. Palmer R. P. Evans An integrated semantic and syntactic framework for requirements traceability: Experience with system level requirements for a large complex multisegment project, CSESAW 94, White Oak, MD, NSWCDD/MP-94/122, pp. 9–14, July 19–20, 1994.
Wiley Encyclopedia of Electrical and Electronics Engineering
Browse other articles of this reference work:
