Introduction to Systems Analysis and Design
21 Questions
1 Views

Choose a study mode

Play Quiz
Study Flashcards
Spaced Repetition
Chat to lesson

Podcast

Play an AI-generated podcast conversation about this lesson

Questions and Answers

What is the primary purpose of the Systems Development Life Cycle (SDLC)?

  • To reduce project budgets significantly
  • To foster innovation in system design
  • To provide a formal process for system development (correct)
  • To ensure project teams work together seamlessly
  • What is the first step in the Planning Phase of the SDLC?

  • Develop a system request (correct)
  • Develop a design strategy
  • Monitor and control the project
  • Conduct a feasibility analysis
  • Which of the following is NOT part of the Design Phase in the SDLC?

  • Specify program functionality
  • Develop design architecture and interfaces
  • Develop databases and file specifications
  • Gather the requirements (correct)
  • Which type of feasibility is evaluated to determine if the technology needed for the system is available?

    <p>Technical feasibility</p> Signup and view all the answers

    Which phase involves modeling the current system and formulating a new system?

    <p>Analysis Phase</p> Signup and view all the answers

    What is the primary role of a system analyst in the SDLC?

    <p>To design a system that adds value</p> Signup and view all the answers

    During which phase is the system proposal developed?

    <p>Analysis Phase</p> Signup and view all the answers

    What aspect does the Implementation Phase primarily focus on?

    <p>Building and testing the system</p> Signup and view all the answers

    Which of the following is NOT a characteristic of Object-Oriented Analysis and Design (OOAD)?

    <p>Static and fixed</p> Signup and view all the answers

    What is the primary focus during the Elaboration phase of the Unified Process?

    <p>Analysis and design</p> Signup and view all the answers

    Which of the following methodologies is categorized under Agile Development?

    <p>SCRUM</p> Signup and view all the answers

    What describes the concept of encapsulation in Object-Oriented Systems?

    <p>Hiding implementation details from users</p> Signup and view all the answers

    Which of the following is an element of UML Structure Diagrams?

    <p>Class Diagram</p> Signup and view all the answers

    Which methodology emphasizes rapid development and iteration?

    <p>Rapid Application Development</p> Signup and view all the answers

    Which principle allows subclasses to inherit attributes and methods from superclasses?

    <p>Inheritance</p> Signup and view all the answers

    Which phase of the Unified Process focuses primarily on feasibility analysis?

    <p>Inception</p> Signup and view all the answers

    Which of the following describes the method where the type of an object is determined during runtime?

    <p>Dynamic Binding</p> Signup and view all the answers

    In the context of systems analysis, which skill is essential for dealing with non-technical audiences?

    <p>Interpersonal Skills</p> Signup and view all the answers

    What is a key benefit of using Object-Oriented Systems Analysis and Design (OOSAD)?

    <p>Breaking down complex systems into smaller modules</p> Signup and view all the answers

    What does the term 'use-case driven' imply in OOAD?

    <p>Each use-case represents a unique business process</p> Signup and view all the answers

    Which aspect is part of the enhanced Unified Process?

    <p>Maintenance and support</p> Signup and view all the answers

    Study Notes

    Introduction to Systems Analysis and Design

    • This chapter introduces systems analysis and design.
    • A formal process is needed for system development due to frequent failures, late projects, projects exceeding their budget, and delivering systems with fewer features than planned.
    • A systems analyst is key to a project; they design a system to add business value and must understand business processes.
    • The job of a systems analyst is challenging but rewarding.
    • Specific skills sets are required to perform the job of a systems analyst.

    Learning Objectives

    • Systems development life cycle (SDLC)
      • Identifying the four phases
      • Understanding how the SDLC came about
      • Methodology alternatives
    • Team roles and skill sets
    • Object-oriented systems characteristics
    • Object-oriented systems analysis and design
    • The Unified Process and its extensions
    • Unified Modeling Language (UML)

    Introduction

    • Why a formal process is required for systems development
      • Failures frequently occur.
      • System development is not always intuitive.
      • Projects may be late, over budget, or deliver fewer features than planned.
    • The role of a systems analyst
      • Designs systems to provide business value.
      • Must understand business processes.
      • The job is rewarding but challenging.
      • Requires specific skill sets.

    Systems Development Life Cycle (SDLC)

    • Planning, analysis, design, and implementation are the four phases of the SDLC.
    • Planning: the starting phase that determines the need for a new system and whether it's technically, economically, and organizationally feasible.
    • Analysis: the second phase where the existing system is examined and requirements are gathered for the new system, including determining who will use the system and what the system should do (for whom and when).
    • Design: the third phase where the specifications are defined including the program design.
    • Implementation: The fourth phase where the programming code is written, tested, and installed, and users are trained along with supporting the system through maintenance.
    • Phases are executed sequentially, incrementally, iteratively, or through some other pattern.

    The SDLC Process

    • The SDLC process consists of four phases.
    • Each phase has various steps and is documented.
    • Phases are often executed sequentially, incrementally, or iteratively rather than linearly.

    Questions to be Answered

    • Planning: Why build the system? What value does it provide? How long will it take to build?
    • Analysis: Who will use it? What should the system do for us? Where and when will it be used?
    • Design: How should we build it?

    SDLC: The Planning Phase

    • Project Initiation: Develop/receive system request, conduct feasibility analysis (technical, economic, organizational).
    • Project Management: Develop work plan, staff the project, monitor and control the project.

    SDLC: The Analysis Phase

    • Develop an analysis strategy: Model the current and new systems.
    • Requirements Gathering: Develop system concepts, create a business model representing data and processes.
    • Develop a system proposal: Present potential solutions.

    SDLC: The Design Phase

    • Develop a design strategy.
    • Design architecture and interfaces.
    • Develop databases and file specifications.
    • Develop the program design to specify what programs to write and what each program will do.

    SDLC: The Implementation Phase

    • Construct the system: building and writing code, testing extensively.
    • Install the system.
    • Training users.
    • Support the system or maintenance.

    SDLC: Methodologies

    • Methodology: a formalized approach to implementing the SDLC
    • Examples
      • Process oriented
      • Data centered
      • Object oriented
      • Structured
      • Rapid action development
      • Agile development

    Classes of Methodologies

    • Structured development: Waterfall, Parallel, Phased.
    • Rapid Application Development: Prototyping(Throwaway), Extreme Programming.
    • Agile: Scrum.

    Which Methodology to Use?

    • A table comparing various methodologies based on usefulness criteria like unclear requirements, unfamiliar technology, complex systems, reliable systems, short time schedule, and schedule visibility.

    The Systems Analyst: Skills

    • Agents of change: Identify ways to improve the organization, motivate and train others.
    • Skills needed: Technical, business, analytical, communications (technical and non-technical audiences), interpersonal, ethics.

    The Systems Analyst: Roles

    • Business analyst: analyzes key business aspects, identifies the system's business value.
    • Systems analyst: understands how technology can improve business processes, designs new business processes, designs the information system.
    • Infrastructure analyst: ensures the new system conforms to infrastructure standards.
    • Change management analyst: identifies infrastructure changes, develops and executes change management plan.
    • Project manager: manages the team, develops and monitors the project plan, assigns resources.

    Object-Oriented Systems Analysis & Design

    • Attempts to balance data and processes.
    • Utilizes UML and the Unified Process.
    • Key Characteristics
      • Use-case driven
      • Architecture-centric
      • Iterative and incremental

    Characteristics of Object-Oriented Systems

    • Classes & Objects: Object is an instance of a class.
    • Attributes: describes the class.
    • State: describes class values, relationships over time.
    • Methods & Messages: Methods represent class behavior, messages trigger methods.

    Characteristics of Object-Oriented Systems (cont.)

    • Encapsulation & Information Hiding: Combining process and data; Hiding functionality.
    • Inheritance: Creating general classes (superclasses), subclasses inherit data and methods.

    Characteristics of Object-Oriented Systems (cont.)

    • Polymorphism & Dynamic Binding: Same message has different meanings, the type of object is determined at run-time.

    Object-Oriented Systems Analysis & Design

    • Use-case driven: Defines system behavior, focuses on a process.
    • Architecture-centric: Functional, static, dynamic views. External view focused on user perspective. Methods, classes, relationships, and messages are emphasized in static and dynamic views.

    Object-Oriented Systems Analysis & Design (cont.)

    • Iterative & Incremental: Continuous testing, repeated improvement.
    • OO Systems benefits: breaking into manageable parts, making the system more realistic, and having better understanding from user perspective.

    The Unified Process

    • A methodology for object-oriented analysis and design.
    • A two-dimensional process consisting of phases and workflows.
    • Phases: Inception, Elaboration, Construction, Transition.
    • Workflows: Activities within phases (Business Modeling, Requirements, Analysis, Design, Implementation, Testing, Deployment).

    The Unified Process Phases

    • Inception: Feasibility analysis, basic business modeling, requirements gathering.
    • Elaboration: Focus on analysis and design, inclusion of various workflows.
    • Construction: Programming, implementation, emphasis on active work on programming and implementation.
    • Transition: Testing and deployment.

    Engineering Workflows

    • Business modeling
    • Requirements
    • Analysis
    • Design
    • Implementation
    • Testing
    • Deployment

    Supporting Workflows

    • Project management
    • Configuration and change management
    • Environment
    • Operations and support
    • Infrastructure management

    Extensions to the Unified Process

    • The Unified Process does not include staffing, budgeting, contract management, maintenance, and operations. Additional areas like cross- or inter-project issues are not included.
    • A production phase, new workflows/modifications of existing workflows (Operations & Support, Infrastructure management, Test workflow, Deployment, Environment, Project Management, and Configuration & Change management).

    Unified Modeling Language (UML)

    • A common language for object-oriented systems.
    • A standard set of diagramming tools for modelling any system development project from analysis through implementation.
    • UML Version 2.0 has 14 diagrams in 2 main groups.
      • Structuring diagrams: class, object, package, deployment, component, composite structure.
      • Behavior diagrams: activity, sequence, communication, interaction overview, timing, behavior state machine, protocol state machine, use-case diagrams.

    Summary

    • All systems development follows the SDLC
    • Methodologies formalize SDLC implementation.
    • Systems Analysts require numerous skills and roles.
    • Object-oriented systems differ from traditional systems.
    • Object-Oriented Systems Analysis and Design (OOSAD) is a use-case-driven, architecture-centric, iterative, and incremental information systems development approach.
    • The Unified Process is a two-dimensional system development process.
    • The Unified Modeling Language (UML) has a standard set of diagramming techniques.

    Studying That Suits You

    Use AI to generate personalized quizzes and flashcards to suit your learning preferences.

    Quiz Team

    Related Documents

    Description

    This quiz covers the fundamentals of systems analysis and design, focusing on the systems development life cycle (SDLC) and the roles of a systems analyst. It explores methodologies, object-oriented characteristics, and Unified Modeling Language (UML). Test your understanding of these key concepts and their importance in developing effective systems.

    More Like This

    Use Quizgecko on...
    Browser
    Browser