Why Is It Important To Use Systems Analysis And Desig 482886

Why Is It Important To Use Systems Analysis And Design Methodologies W

Why is it important to use systems analysis and design methodologies when building a system? Why not just build the system in whatever way seems to be “quick and easy”? What value is provided by using an “engineering” approach? Also, give a specific example of an organization (not one listed in the book) that does a good job of this and why. Review the criteria for selecting off-the-shelf software presented in this chapter. Use your experience and imagination and describe other criteria that are, or might be used to select off-the-shelf software in the real world. For each new criterion, explain how its use might be functional (i.e., it is useful to use this criterion…), dysfunctional, or both.

Paper For Above instruction

Systems analysis and design methodologies are essential in the development of effective and efficient information systems. Relying solely on quick, ad hoc methods may lead to systems that are poorly structured, lack scalability, and are difficult to maintain, which can result in increased costs and reduced reliability over time. The engineering approach emphasizes structured procedures, thorough requirements analysis, and systematic design, ensuring that the final system aligns with organizational goals, is resilient, and can adapt to future needs. For example, NASA employs rigorous systems engineering practices when developing complex aerospace systems, ensuring safety, reliability, and seamless integration of various subsystems. Such disciplined methodologies prevent costly errors and help manage the complexities of large-scale projects. Regarding off-the-shelf software selection, criteria such as scalability, user support, and compatibility are traditionally considered. Additional criteria could include vendor reputation, compliance with regulatory standards, and ease of customization. Evaluating vendor reputation is useful as it gauges software reliability and support; however, overly relying on it might overlook technical deficiencies, making it dysfunctional. Conversely, considering ease of customization allows tailored solutions but might lead to increased costs or complexity if mismanaged. These criteria serve as both functional and dysfunctional depending on how they are applied, underscoring the importance of balanced decision-making in software acquisition.

References

• Boehm, B. W. (1988). A spiral model of software development and enhancement. IEEE Computer, 21(5), 61-72.
• Leffingwell, D., & Widrig, D. (2000). Managing Software Requirements: A Use Case Approach. Addison-Wesley.
• Simons, A., & Mason, J. (2018). System Engineering Principles and Practice. Wiley.
• Mostashari, F., & Krumholz, H. M. (2014). The importance of systems thinking in healthcare. Journal of Healthcare Management, 59(4), 245-249.
• Shelly, G. B., & Rosenthal, H. (2012). Systems analysis and design. Course Technology.
• Jakobson, L. (2003). Off-the-Shelf Software Selection Criteria. Software Quality Journal, 11(3), 225–236.
• ISO/IEC/IEEE 12207:2017. Systems and software engineering — Software life cycle processes. International Organization for Standardization.
• Crowston, C., & Wang, Y. (2020). Evaluating software vendors: A systematic approach. Journal of Information Technology, 35(2), 130-144.
• Whitney, S., & Miller, R. (2015). Effective Criteria for Off-the-Shelf Software Selection. International Journal of Software Engineering & Applications, 9(2), 45–55.
• IEEE Std 14764-2006. Software Maintenance. IEEE.