ACM Home Page
Please provide us with feedback. Feedback
An object-oriented requirements specifications method
Full text PdfPdf (1.60 MB)
Source
Communications of the ACM archive
Volume 32 ,  Issue 5  (May 1989) table of contents
Pages: 608 - 623  
Year of Publication: 1989
ISSN:0001-0782
Author
S. C. Bailin  CTA Inc., Laurel, MD
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 19,   Downloads (12 Months): 90,   Citation Count: 33
Additional Information:

abstract   references   cited by   index terms   review   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/63485.63491
What is a DOI?

ABSTRACT

Analyzing requirements for object-oriented software is examined in an alternative methodology from the more standard structured analysis approach. Through parallel processes of decomposing objects and allocating functions, the methodology is explained in detail.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Alford, M. SREM at the age of eight: The distributed computing design system. IEEE Comput. 18, 4 (Apr. 1985), 36-46.
 
2
Andreu, R., and Madnick, S. A systematic approach to design of complex systems: An application to DBMS design and evaluation. 32-Working Paper. Center for Information Systems Research, MIT Sloan School of Management, Cambridge, Mass., 1977.
 
3
Bailin, S. An automated quality assessor for Ada object-oriented designs. In Proceedings of the 40th IEEE National Aerospace and Electronics Conference (NAECON) (Dayton, Ohio, May 23-27), vol. 2. iEEE, Piscataway, N.J., 1988.
 
4
Baxter, I.D. Domain connection discovery. Res. Tech. Pub., RPT067. Univ. of California, Irvine, 1987a.
 
5
Baxter, I.D. PGL: A production control language. STP-375-87 Tech. Rep. Microelectronics and Computer Corp., Austin, Tex., 1987b.
 
6
 
7
Borgida, A., et al. Knowledge representation as the basis for requirements specification. IEEE Comput. 18, 4 (Apr. 1985}, 82-91.
 
8
Cherry, G, PAMELA Designer's Handbook. The Analytic Science Corp., Reading, Mass., 1987.
 
9
CTA INCORPORATED. Human Factors Analysis: Servicing of Attached Payloads within the Servicing Facilty. Laurel, Md., 1987.
 
10
 
11
 
12
 
13
Neighbors, J.M. The Draco approach to constructing software from reusable components. IEEE Trans. Softw. Eng. SE-IO, 5 (Sept. 1984), 564-574.
 
14
 
15
Seidewitz, E., and Stark, M. General object-oriented software development. SEL-86-002, Software Engineering Laboratory, NASA Goddard Space Flight Center, 1986.
 
16
 
17

CITED BY  33


REVIEW

"Dimitris N. Christodoulakis : Reviewer"

The issue of devising methods for requirements analysis is as old as the software crisis, and a lot of proposals have been put forward and many solutions have emerged. In this paper, the author attempts to solve the problem by proposing a variat  more...