Skip to ContentGo to accessibility pageKeyboard shortcuts menu
OpenStax Logo
Foundations of Information Systems

Summary

Foundations of Information SystemsSummary

4.1 Systems Analysis and Design for Application Development

  • Systems analysis and design is a stepwise process for evaluating and developing information systems by understanding the needs of the business to improve on or develop effective and efficient functioning solutions to technical challenges.
  • The benefits of systems analysis and design include the identification of operational efficiencies achieved by improvements to existing systems, the alignment of system functionality with organizational strategic objectives, early risk identification of potential threats to processes, the minimization or reduction of resources and costs, and the overall improved quality, efficiency, productivity, and usability of the system.
  • A systems analyst is a professional whose primary functions are to utilize systems analysis and design techniques to support information systems and solve challenges presented when using information systems.
  • Systems design generally involves the following activities: designing the data, interface design, and process design. The tools used in systems analysis and design are varied and aid in the understanding of the system in its current and/or future state.
  • SDLC is a framework that defines the stages of software development, from its inception to its retirement, providing a blueprint of the tasks to be completed for each stage of the cycle: analysis, design, development, testing, deployment, and maintenance.
  • Agile is an iterative approach to software development that considers uncertainty in changing environments and allows Agile teams to respond to those changes quickly to deliver smaller, consumable work packages. The Manifesto for Agile Software Development maintains the four Agile Manifesto values and describes how Agile development works, including the planning and preparation involved and the importance of sprint planning.
  • An analysis and design team includes members such as the designer, systems architect, user experience researcher, and systems analyst, among other important participants in the systems analysis and design process.

4.2 Defining the Business Problem and User Requirements

  • Defining the business problem is multifaceted and includes asking directed questions to uncover the issues that need to be addressed and the problem at hand.
  • Various tools can be used to understand user needs and how users will interact with the system. These include both visual tools, such as flowcharts, and textual tools, such as user stories.
  • Not having complete or correct user requirements can delay a project and result in additional costs. Taking time up front will save valuable resources in the long run.
  • Through proper planning in the early stages of systems development, analysts can feel confident in delivering a system that works for the stakeholders and meets the user requirements.

4.3 Technical Design Methodologies and Practical Applications

  • The systems design process defines the architecture, interfaces, and data for a system that satisfies the specified requirements.
  • Systems designs can be logical (a high-level view of the system, including actors and the relationships between the actors and the system) or physical (the specific hardware and software components, along with detailed systems diagrams and layout of the systems).
  • Data move through the system in a cycle from initial data creation to the eventual archiving or destruction of the data.
  • Prototypes are used for early detection of problems, expanded user engagement, increased satisfaction with the final product, and greater savings of time and money associated with rework. CAD is used by designers and engineers because of its ease of visualization, level of detail, capacity for specialization, and ability to optimize products and render a physical product, which can greatly inform the design process.
  • Input/output control is a component of the design process. Input is the raw data that are processed through the functions of the system. It is controlled by the directives used to submit responses into the system by the user, producing an output according to the system logic. Output is the information delivered to users through an information system; it is the data that result from the inputs being processed according to the system logic.
  • A systems design task list provides a road map through each step of the design process, allowing teams to have an organized workflow and make informed decisions through each step.
  • The enterprise network system is composed of interconnected computers and other devices that allow for the exchange of data and information and the sharing of resources.
  • The most commonly used network architectures are peer-to-peer and client/server.

4.4 Designing for Mobile Devices and Other Design Considerations

  • User-centered design (UCD) creates a product that uses an interdisciplinary approach to design with focus on the user experience and feedback. Applying user feedback to guide the design process strengthens the output of the design and creates a relationship with the user.
  • UCD is iterative in nature and includes the practices of building, refining, and improving a product, project, or initiative.
  • Best practices associated with a UCD approach include defining the business goals, understanding users and aligning business goals, generating the design solution, evaluating the final product, and continuing to refine the product.
  • Mobile applications require special design considerations. This includes keeping the flow simple, highlighting key features of the application, and designing features for touch screens.
  • Effective website design includes making sure accessibility standards are met for images, text, and sound. The website design should also incorporate mobile accessibility in the process.
PreviousNext
Citation/Attribution

This book may not be used in the training of large language models or otherwise be ingested into large language models or generative AI offerings without OpenStax's permission.

Want to cite, share, or modify this book? This book uses the Creative Commons Attribution-NonCommercial-ShareAlike License and you must attribute OpenStax.

Attribution information
  • If you are redistributing all or part of this book in a print format, then you must include on every physical page the following attribution:
    Access for free at https://openstax.org/books/foundations-information-systems/pages/1-introduction
  • If you are redistributing all or part of this book in a digital format, then you must include on every digital page view the following attribution:
    Access for free at https://openstax.org/books/foundations-information-systems/pages/1-introduction
Citation information

© Feb 17, 2025 OpenStax. Textbook content produced by OpenStax is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike License . The OpenStax name, OpenStax logo, OpenStax book covers, OpenStax CNX name, and OpenStax CNX logo are not subject to the Creative Commons license and may not be reproduced without the prior and express written consent of Rice University.