Systems Analysis and Design Overview for COMI-1230 Course

comi 1230 systems analysis design n.w
1 / 12
Embed
Share

Explore the fundamentals of systems analysis and design in the COMI-1230 course, covering topics such as understanding information systems, system components, design implementation, the importance of analysis, key skills for a systems analyst, and system development life cycle frameworks.

  • Systems Analysis
  • Design
  • COMI-1230
  • Information Systems
  • Frameworks

Uploaded on | 0 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.

E N D

Presentation Transcript


  1. COMI-1230 Systems Analysis & Design

  2. Week 1 Outline Systems Analysis & Design Overview Overview of Systems Analysis

  3. Systems Analysis & Design Overview What is Systems Analysis? Understanding and specifying in detail what the information system should do Much of what you do as an analyst will be gathering and digesting data and information What about Systems Design? Specifying in detail how the components of the system should be implemented It is critical that the Analysis is done before Design

  4. Systems Analysis & Design Overview Why is Systems Analysis & Design important? Critical to the design and support of Information Systems What is an Information System? Set of interrelated components that function to provide required information for a specified purpose Can be described using the simple systems model I P O

  5. Simple System Model Page 9 of text

  6. Information Systems Abstraction & Functional Decomposition You need to see the big picture then be able to drill down to understand the key components You also need to understand: System and it s boundaries Type of business it supports Key stakeholders Type of system strategy being used Transaction Processing Office Support MIS EIS

  7. The Systems Analyst Key skills: Technical knowledge and capability Business knowledge Of the specific business or at least the business sector Communication skills Teamwork and collaboration are critical Ability to communicate to a variety of different audiences in way they understand

  8. Framework to manage Systems Analysis & Design System Development Life Cycle Types: Traditional approach JAD RAD OOAD (Chapter 3) Agile

  9. Traditional Approach Use Structured Analysis Rely on process models that show how data flows into a system and is processed by applying business rules resulting in the desired result More detailed I P O DFD s are key element Primarily sequential AKA Waterfall Model Five Phases Plan (or Initiation) Analysis Design Implementation Support (or Maintenance)

  10. Traditional Approach Text page 13

  11. Alternate Approaches to Systems Development JAD (Joint Application Development) Team based Involves the development teams and stakeholders to get more input throughout the process and hopefully speed up development RAD (Rapid Application Development) Similar to JAD where it involves stakeholders and the development team in a very interactive iterative way to get feedback early and often in the process to speed up the development Agile More current approach Flexible alternative to Traditional Approach Builds upon the ideas of JAD and RAD

  12. Agile Approach Intent is to produce a working product as soon as possible using a more adaptive approach that can react better to changes in requirements Interactive / iterative approach where small prototypes are enhanced over time following regular meetings with stakeholders until it becomes a finished product Scrums Includes: Design, Code, and Test activities over a short period of time called Sprints Usually 1 to 4 weeks Text page 14

Related


More Related Content