Itzhak Shemer
Skip Abstract Section
Abstract
Adopting an appropriate model for systems analysis, by avoiding a narrow focus on the requirements specification and increasing the use of the systems analyst's knowledge base, may lead to better software development and improved system life-cycle management.
- 1 Alford. M. SREM at the age of eight: The distributed computing design system. Computer 18, 4 (Apr. 1985), 36-46.Google Scholar
Digital Library
- 2 Alford, M.W. A requirements engineering methodology for real time processing requirements. IEEE Trans. Softw. Eng. SE-3, 1 (Jan. 1977), 60-69.Google ScholarDigital Library
- 3 Barstow, D.R. Knowledge-Based Program Construction. North-Holland, Amsterdam, 1979.Google Scholar
- 4 Barstow, D.R. A perspective on automatic programming. In Proceedings of the 8th International Joint Conference on Artificial Intelligence (Karlsruhe. West Germany, Aug. 8-12). International Joint Conferences on Artificial Intelligence, 1983, pp. 1170-1179.Google Scholar
- 5 Ball, T.E., Bixler, DC. and Dyer, M.E. An extendible approach to computer-aided software requirements engineering. IEEE Trans. Soffw. Eng. SE-3, 1 (Jan. 1977), 49-60.Google ScholarDigital Library
- 6 Boehm, B.W. Software and its impact: A quantitative assessment. Datamation 19, 5 (May 1973), 48-59.Google Scholar
- 7 Boehm, B.W. Software engineering. IEEE Trans. Comput. C-25, 12 (Dec. 1976), 1226-1241.Google ScholarDigital Library
- 8 Chen, P.P.-S. The entity-relationship model-Toward a unified view of data. ACM Trans. Database Syst. 1, 1 (Mar. 1976), 9-36. Google ScholarDigital Library
- 9 Churchman, C.W. The System Approach. Dell, New York, 1969.Google Scholar
- 10 Churchman, C.W. The Design ofInquiring Systems. Basic Books, New York, 1971.Google Scholar
- 11 Colter, M.A. A comparative examination of system analysis techniques. Manage. 1nf Syst. Q. 8, 1 (Mar. 1984). 51-66.Google Scholar
- 12 Cotterman. W.W. Gouger, J.D., Enger, N.L., and Harold, F., Eds. System Analysis and Design: A Foundation for the 1980s. North- Holland, Amsterdam, 1981.Google Scholar
- 13 Gouger, J.D., and Knapp, R.W. System Analysis Techniques. Wiley, New York, 1974.Google Scholar
- 14 Davis, G.B. Strategies for information requirements determination. IBM Syst. J. 27, 1 (1982), 4-30.Google Scholar
- 15 DeMarco. T. Structured Analysis and System Specification. Yourdon, New York, 1976. Google ScholarDigital Library
- 16 Ein-Dor, P., and Segev. E. Managing Management Information Systems. D.C. Heath/Lexington Books, Lexington, Mass., 1978.Google Scholar
- 17 Freeman, P. Why Johnny can't analyse. In System Analysis and Design: A Foundation for the 1980's, W.W. Cotterman, J.D. Gouger,Google Scholar
- 18 N.L. Enger, and F. Harold, Eds. North-Holland, Amsterdam, 1981.Google Scholar
- 19 Gane, C., and Sarson, T. Structured Systems Analysis. Prentice-Hall, Englewood Cliffs, N.J., 1979. Google ScholarDigital Library
- 20 Iverson, K.E. Notation as a tool of thought. Commun. ACM 23, 8 (Aug. 1980), 444-465. Google ScholarDigital Library
- 21 Lientz. B.P., and Swanson, E.B. Software Maintenance Management. Addison-Wesley, Reading, Mass., 1980. Google ScholarDigital Library
- 22 Manna, 2. Mathematical Theory of Computation. McGraw-Hill, New York, 1974. Google ScholarDigital Library
- 23 Martin, J. Application Development without Programmers. Prentice- Hall, Englewood Cliffs, N.J., 1982. Google ScholarDigital Library
- 24 McCracken, D.D. A maverick approach to systems analysis and design. In System Analysis and Design: A Foundation for the 1980's, W.W. Cotterman, J.D. Gouger, N.L. Enger, and F. Harold, Eds. North-Holland, Amsterdam, 1981, pp. 446-451.Google Scholar
- 25 McHenry, RX., and Walston. C.E. Software life cycle management. IEEE Trans. So@. Eng. SE-4,4 (July 19781, 334-344.Google Scholar
- 26 Mendes, KS. Structured systems analysis: A technique to define business requirements. Sloan Manage. Rev. (Summer 1980), 51-63.Google Scholar
- 27 Munro, MC, and Wheeler, B.R. Planning, critical success factors, and management's information requirements. Manage. Inf Syst. Q. 4,4 (Dec. 1980), 27-38.Google ScholarDigital Library
- 28 Parnas, D.L. Software aspects of strategic defense systems. Am. Sci. 73, 5 (Sept.-&t. 1985), 432-440.Google Scholar
- 29 Ramamoorthv. C.V. Prakash. A. Tsai. W. and Usuda. Y. Software engineering: Problems and perspectives. domputer 17,'10 (Oct. 1984), 191-209. Google ScholarDigital Library
- 30 Rockart. J.F. Chief executives define their own data ceeds. Harvard Bus. Rev. 57, 2 (Mar.-Apr. 1979), 81-93.Google Scholar
- 31 Ross, D.T. Reflections on requirements. IEEE Trans. Softv. Eng. SE-3, 1 (Jan. 1977), 2-5.Google Scholar
- 32 Ross, D.T. Structured analysis (SA): A language for communicating ideas. IEEE Trans. Softw. Eng. SE-3. 1 (Jan. 1977), 16-34.Google ScholarDigital Library
- 33 Ross, D.T. Applications and extensions of SADT. Com,outer 18.4 (Apr. 1985), 25-35.Google Scholar
- 34 Ross, D.T., and Schoman, K.E. Structured analysis for requirements definition. IEEE Trans. Softw. Eng. SE-3, 1 (Jan. 1977), 6-15.Google ScholarDigital Library
- 35 Schindler. M. 1981 technology forecast-Software. Electron. Des. 29, 1 (Jan. 1981), 190-199.Google Scholar
- 36 Shemer, 1. An expert system approach to systems analysis. Doctoral dissertation, Faculty of Management, Tel-Aviv Univ., Ramat-Aviv. June 1985. (In Hebrew.)Google Scholar
- 37 Shemer, 1. SYS-AIDE-An expert aide to systems analysis. Work. Pap. 887/86, Faculty of Management, Tel-Aviv Univ., Ramat-Aviv, Jan. 1986.Google Scholar
- 38 Swartout, W., and Balzer, R. On the inevitable intertwining of specification and implementation. Commun. ACM 25, 7 (July 1982). 438-440. Google ScholarDigital Library
- 39 Taggart, W.M., Jr., and Tharp, M.O. A survey of information requirements analysis techniques. ACM Comput. Sara 9,4 (Dec. 1977), 273-290. Google ScholarDigital Library
- 40 Teichroew, D., and Hershey, E.A. PSL/PSA: A computer-aided technique for structured documentation and analysis of information processing systems. IEEE Trans. Softw. Eng. SE-3, 1 (Jan. 1977), 41-48.Google ScholarDigital Library
- 41 Teichroew, D., and Sagani, H. Automation of system building. Datamation 17, 16 (Aug. 15, 1971).Google Scholar
- 42 Wasserman, A.I. Information system design methodology. I. Am. Sot. If. Sci. 31, 1 (Jan. 1980).Google ScholarCross Ref
- 43 Wasserman, A.I., and Gutz, S. The future of programming. Commun. ACM 25.3 (Mar. 1982), 196-206. Google ScholarDigital Library
- 44 Wegner, P. Programming languages: The first 25 years. IEEE Trans. Comput. C-25, 12 (Dec. 1976), 1207-1225.Google ScholarDigital Library
- 45 Weinberg, G.M. General systems thinking and its relevance to systems analysis and design. In System Analysis and Design: A Foundation for the 1980's, W.W. Cotterman, J.D. Gouger, N.L. Enger, and F. Harold, Eds. North-Holland, Amsterdam, 1981, pp. 498-513.Google Scholar
- 46 Winograd, T. Beyond programming languages. Commun. ACM 22, 7 (July 1979), 391-401. Google ScholarDigital Library
- 47 Yadav, S.B. Determining an organization's information requirements: A state of the art survey. Data Base 14, 3 (Spring 1983). 3-20. Google ScholarDigital Library
Index Terms
- Systems analysis: a systemic analysis of a conceptual model
Recommendations
OO Systems Analysis: Is It or Isn't It?
Systems analysis is the study of a system for the purpose of understanding and documenting its essential characteristics. Analysis is neither design nor implementation. Analysis focuses on real-world problems, whereas design and implementation focus on ...
Using on ethnographic process to conduct requirements analysis for agile systems developmet
Since the late 1990s, agile or lightweight software development methodologies have experienced a meteoric rise of interest among systems developers who consider traditional systems development methodologies (such as Structured Systems Development, ...
Comments