Systems analysis: a systemic analysis of a conceptual model

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]  Douglas T. Ross,et al.  Structured Analysis (SA): A Language for Communicating Ideas , 1977, IEEE Transactions on Software Engineering.

[2]  J. Daniel Couger,et al.  System analysis techniques , 1974 .

[3]  Brian Hollocks,et al.  Managing Management Information Systems , 1978 .

[4]  Thomas E. Bell,et al.  An Extendable Approach to Computer-Aided Software Requirements Engineering , 1976, IEEE Transactions on Software Engineering.

[5]  Peter P. Chen.  The entity-relationship model: toward a unified view of data , 1975, VLDB '75.

[6]  David Lorge Parnas,et al.  Software aspects of strategic defense systems , 1985, CACM.

[7]  Mel A. Colter.  A Comparative Examinati on of Systems Analysis Techniques , 1984, ICIS.

[8]  David R. Barstow,et al.  A Perspective on Automatic Programming , 1984, AI Mag..

[9]  Terry Winograd,et al.  Beyond programming languages , 1979, CACM.

[10]  Douglas T. Ross,et al.  Applications and Extensions of SADT , 1985, Computer.

[11]  J. Rockart.  Chief executives define their own data needs. , 1979, Harvard business review.

[12]  Guy Doumeingts,et al.  System Analysis Techniques , 1988, Computer-Aided Production Management.

[13]  James Martin,et al.  Application Development Without Programmers , 1981 .

[14]  J. Daniel Couger,et al.  System analysis and design: a foundation for the 1980's , 1982, SOEN.

[15]  Gordon B. Davis,et al.  Strategies for Information Requirements Determination , 1982, IBM Syst. J..

[16]  Ernest A. Hershey,et al.  A computer-aided technique for structured documentation , 1976, DATB.

[17]  Peter Wegner,et al.  Programming Languages - The First 25 Years , 1976, IEEE Trans. Computers.

[18]  Mack W. Alford.  SREM at the Age of Eight; The Distributed Computing Design System , 1985, Computer.

[19]  Ernest A. Hershey,et al.  PSL/PSA: A Computer-Aided Technique for Structured Documentation and Analysis of Information Processing Systems , 1976, IEEE Transactions on Software Engineering.

[20]  Kenneth E. Iverson,et al.  Notation as a tool of thought , 1980, APLQ.

[21]  Douglas T. Ross,et al.  Structured Analysis for Requirements Definition , 1977, IEEE Transactions on Software Engineering.

[22]  Robert Balzer,et al.  On the inevitable intertwining of specification and implementation , 1982, CACM.

[23]  William M. Taggart,et al.  A Survey of Information Requirements Analysis Techniques , 1977, CSUR.

[24]  M A Branch,et al.  Software maintenance management , 1986 .

[25]  P. Ein-Dor,et al.  A paradigm for management information systems , 1981 .

[26]  Atul Prakash,et al.  Software Engineering: Problems and Perspectives , 1984, Computer.

[27]  David R. Barstow,et al.  Knowledge-based program construction , 1979 .

[28]  Mack W. Alford.  A Requirements Engineering Methodology for Real-Time Processing Requirements , 1977, IEEE Transactions on Software Engineering.

[29]  Surya B. Yadav,et al.  Determining an organization's information requirements: a state of the art survey , 1983, DATB.

[30]  Robert G. Estell.  Software life cycle management , 1976, IMRE.

[31]  Malcolm Munro,et al.  Planning, Critical Success Factors, and Management's Information Requirements , 1980, MIS Q..

[32]  ChenPeter Pin-Shan.  The entity-relationship modeltoward a unified view of data , 1976 .

[33]  Anthony I. Wasserman.  Information system design methodology , 1980, J. Am. Soc. Inf. Sci..