What do you do during systems analysis to determine if a solution is practical?
Systems analysis is a broad term applied to the study of real-world processes. It involves the careful examination of systems -- entities, organisms, organizations, beings and things. Systems analysis breaks problems associated with entities down into their component parts and relationships in order to formulate a conceptual definition of the situation. The purpose is to develop “an overall understanding of optimal solutions to executive type problems” (Churchman et al. 1957, p. 7). The resulting conceptual definition is then often translated into a Web site, a process-support system, or a mathematical model. Systems analysis has been applied to complex, dynamic systems — both physical and social — such as businesses, governments, and computer software, as well as to economic, weapons, mechanical, and manufacturing systems. While it is ultimately a subjective form of innovation, systems analysis is based on a growing set of key theories: systems, cybernetics, mathematical... Show
This is a preview of subscription content, access via your institution. Buying optionsChapter EUR 29.95 Price includes VAT (Singapore)
eBookEUR 748.99Price includes VAT (Singapore)
Hardcover BookEUR 749.99Price excludes VAT (Singapore)
Learn about institutional subscriptions Fig. 1 Fig. 2 Fig. 3 Fig. 4 Fig. 5 Fig. 6 Fig. 7 Ackoff, R. L., & Rivett, P. (1963). A manager’s guide to operations research. New York: Wiley. Google Scholar Alavi, M., & Leidner, D. (2001). Review: Knowledge management and knowledge management systems: Conceptual foundations and research issues. MIS Quarterly, 25(1), 107–136. CrossRef Google Scholar Applebaum, R., Cline, M., & Girou, M. (1998). CORBA FAQs. Downloaded September 10, 1998, from http://octavia.anu.edu.au/markus/corbafaq Avison, D., & Wood-Harper, T. (1990). Multiview: An exploration in information systems development. Oxford, UK: Blackford Press. Google Scholar Beck, K., Beedle, M., van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M., et al. (2001). The agile manifesto. http://agilemanifesto.org/ Berge, C. (1962). The theory of graphs and its applications. New York: Wiley. Google Scholar Booch, G. (1987). Software engineering with Ada (2nd ed.). Menlo Park: Benjamin/Cummings Publishing. Google Scholar Booch, G. (1991). Object oriented design with applications. Redwood City: Benjamin/Cummings Publishing. Google Scholar Booch, G., Rumbaugh, J., & Jacobson, I. (1999). The unified language user guide. Reading: Addison-Wesley. Google Scholar Buchanan, B., & Feigenbaum, E. (1981). DENDRAL and meta DENDRAL: Their application dimension. Artificial Intelligence, 11(1), 5–24. Google Scholar Buckland, M. (1991). Information and information systems. New York: Praeger. Google Scholar Checkland, P. (1981). Systems thinking, systems practice. Chichester: Wiley. Google Scholar Checkland, P., & Holwell, S. (1998). Information, systems and information systems. Making sense of the field. Chichester: Wiley. Google Scholar Checkland, P., & Scholes, J. (1990). Soft systems methodology in action. Chichester: Wiley. Google Scholar Chen, P. P.-S. (1981). A preliminary framework for entity-relationship models. In P. P.-S. Chen (Ed.), Entity-relationship approach to information modeling and analysis. Saugus: ER Institute. Google Scholar Churchman, C. W. (1968). The systems approach. New York: Delta (Dell) Publishing. Google Scholar Churchman, C. W. (1971). The design of inquiring systems. New York: Basic Books. Google Scholar Churchman, C. W., Ackoff, R. L., & Arnoff, E. L. (1957). Introduction to operations research. New York: Wiley. Google Scholar Codd, E. F. (1972). A relational model of data for large shared data banks. Communications of the ACM, 13(6), 377–387. CrossRef Google Scholar Conger, S. (1994). The new software engineering. Belmont: Wadsworth. Google Scholar Conger, S. (2011, forthcoming). Software development life cycles and methodologies: Fixing the old and adopting the new. International Journal of Information Technologies and the Systems Approach (IJITSA), 4(1). Google Scholar Conger, S., & Mason, R. O. (1998). Planning and designing effective web sites. Boston: Course Technology. Google Scholar Dantzig, G. (1963). Linear programming and extensions. New Jersey: Princeton University. Google Scholar Date, C. J. (1990). An introduction to database systems (5th ed.). Reading: Addison-Wesley. Google Scholar DeLone, W. H., & McLean, E. R. (1992). Information systems success: The quest for the dependent variable. Information Systems Research, 3(1), 60–95. CrossRef Google Scholar DeLone, W. H., & McLean, E. R. (2003). The DeLone and McLean model of information systems success: A ten-year update. Journal of Management Information Systems, 19(4), 9–30. Google Scholar DeMarco, T. (1979). Structured analysis. New York: Yourdon Press. Google Scholar Feigenbaum, E., Buchanan, B., & Lederberg, J. (1971). On generality and problem solving. In B. Beltzer & D. Michie (Eds.), Machine intelligence (pp. 165–190). New York: Elsevier. Google Scholar Hackman, J. R., & Oldham, G. R. (1980). Work redesign. Reading: Addison-Wesley. Google Scholar Inmon, W. H. (1993). Building the data warehouse (1st ed.). New York: Wiley. Google Scholar Jackson, M. (1983). Systems development. London: Prentice-Hall. Google Scholar Jarke, M., & Vassiliou, Y. (1997). Data warehouse quality: A review of the DWQ project. In Proceedings of the 2nd conference on information quality. Cambridge: Massachusetts Institute of Technology. Google Scholar Kasabov, N. K. (1996). Foundations of neural networks, fuzzy systems, and knowledge engineering (computational intelligence). Boston: The MIT Press. Google Scholar Kaufmann, K., & McCorduck, P. (1979). Machines who think. New York: W. H. Freeman. Google Scholar Kent, W. (1983). A simple guide to five normal forms in relational database theory. Communications of the ACM, 26(2), 120–125. CrossRef Google Scholar Langefors, B. (1966). Theoretical analysis of information systems. Lund: Studentlitteratur. Google Scholar Laszlo, E. (1972). The systems view of the world. New York: Wiley. Google Scholar Martin, J., & Finkelstein, C. (1981). Information engineering. Englewood Cliffs: Prentice-Hall. Google Scholar Minsky, M. (Ed.). (1968). Semantic information processing. Cambridge, MA: MIT Press. Google Scholar Nelson, T. (1981). Literary machines. Sausalito: Mindful Press. Google Scholar Nielsen, J. (2000). Usability engineering. San Diego: Kaufmann. Google Scholar Object Management Group. (1998). As downloaded September 10, 1998, from http://www.omg.org Papert, S. (1980). Mind-storms: Children, computers, and powerful ideas. New York: Basic Books. Google Scholar Parasuraman, A., Zeithaml, V., & Berry, L. L. (1988). SERVQUAL: A multiple-item scale for measuring consumer perceptions of service quality. Journal of Retailing, 64(1), 12–37. Google Scholar Petter, S., Delone, W., & Mclean, E. (2008). Measuring information systems success: Models, dimensions, measures, and interrelationships. European Journal of Information Systems. Basingstoke, 17(3), 236–263. CrossRef Google Scholar Schlaer, S., & Mellor, S. J. (1992). Object lifecycles: Modeling the world in states. Englewood Cliffs: Yourdon Press. Google Scholar Smith, D., Buchanan, B., Engelmore, R., Adlercreutz, J., & Djerassi, C. (1973). Application of artificial intelligence for chemical inference IX. Journal of the American Chemical Society, 95, 6078. CrossRef Google Scholar Ward, P. T., & Mellor, S. J. (1985, 1986). Structured development for real-time systems. New York: Yourdon Press. Google Scholar Warnier, J. D. (1981). The logical construction of systems. New York: Van Nostrand Reinhold. Google Scholar Winograd, T., & Flores, F. (1986). Understanding computers and cognition. Norwood: Alex. Google Scholar Yourdon, E., & Constantine, L. L. (1979). Structured design: Fundamentals of a discipline of computer program and systems design. Englewood Cliffs: Prentice-Hall. Google Scholar Download references Author informationAuthors and Affiliations
Authors
Corresponding authorCorrespondence to Sue A. Conger . Editor informationEditors and Affiliations
Rights and permissionsReprints and Permissions Copyright information© 2013 Springer Science+Business Media New York About this entryCite this entryConger, S.A., Mason, R.O. (2013). Systems Analysis. In: Gass, S.I., Fu, M.C. (eds) Encyclopedia of Operations Research and Management Science. Springer, Boston, MA. https://doi.org/10.1007/978-1-4419-1153-7_1032 What are the 4 main activities of systems analysis phase?These activities, or phases, usually include planning, analysis, design, implementation, and maintenance/support.
What are the steps involved in system analysis?7 Steps of Agile System Analysis Process. Identify System Users. This is the most important question. ... . Define Main Users Goals. ... . Define System Usage Patterns. ... . Invent Functional Solution to Meet Users Goals and Usage Patterns. ... . Define Main Navigation Paths. ... . Create UI Mockups. ... . Polish UI Elements.. What are the 5 approaches process of system analysis?Describe scope definition, problem analysis, requirements analysis, logical design, and decision analysis phases in terms of information system building blocks.
What happens during system analysis?System analysis refers to the process of gathering data, interpreting information, identifying issues and using the results to recommend or develop possible system improvements. During this stage, companies may also evaluate future business needs and how improvements may answer them.
|