Introduction to Systems Analysis and Design Quiz

Course Information

• Course title: Introduction to Systems Analysis and Design
• Course code: IS 335
• Institution: Al-Imam Muhammad Ibn Saud Islamic University

Learning Objectives

• Familiarize students with the roles and skills of a systems analyst
• Understand the fundamental systems development life cycle (SDLC) and its phases
• Understand the evolution of systems development methodologies
• Orient students to object-oriented systems analysis and design principles
• Introduce the Unified Process, its extensions, and the Unified Modeling Language (UML)
• Cover basic characteristics of object-oriented systems

Introduction

• System Analysis: Understanding and detail the required functionality of an information system
• System Design: The process of describing how information system components will be implemented physically

Introduction to Systems Development Life Cycle (SDLC)

• SDLC: Designing, building, and delivering an information system to fulfill business needs.
• Systems analyst: Key person in developing a system, analysis, improvement identification, and system design for implementation.

Why a Formal Process is Needed

• Failures are frequent; system development is not always intuitive
• Projects often exceed deadlines and/or budget
• Systems often have fewer features than planned

Systems Analyst Skills

• Agents of change: Identifying organizational improvements and training others
• Technical skills: Deep technology comprehension
• Business skills: Deep understanding of business processes
• Analytical skills: Problem-solving and analysis ability
• Communication skills: Effective communication with various audiences—technical and non-technical
• Interpersonal skills: Leadership and management
• Ethical skills: Ethical behavior and confidential information protection

Systems Analyst Roles

• Business analyst: Assessing business aspects, design value, and business processes & policies
• Systems analyst: Identifying technology improvements and designing new technologies.
• Infrastructure analyst: Adapting infrastructure.
• Change management analyst: Managing change plans and training users.
• Project manager: Managing resources, project planning, and technical writers.

Systems Development Life Cycle (SDLC) Phases

• Planning, Analysis, Design, Implementation.
  • Phases are executed sequentially, incrementally, iteratively, or in another pattern
  • Each phase is documented and includes specific documents, helping understanding project progress.

Questions To Be Answered

• Planning phase: Reasons for building, value provision, and build time estimation.
• Analysis phase: User identification, system functionality, and use locations.
• Design phase: Methodology for system building.

SDLC: Planning Phase

• Project Initiation: System request (develop/receive), feasibility analysis (technical, economic, organizational).
• Project Management: Developing, staffing, monitoring, and controlling projects.

SDLC: Analysis Phase

• Develop analysis strategy: Model existing and designed systems.
• Gather requirements: Develop system concepts and create business models (business data, processes).
• Develop system proposal: Formal documentation.

SDLC: Design Phase

• Develop design strategies: System architecture and interfaces design
• Develop databases and file specifications
• Develop program design (specific programs, their functions)

SDLC: Implementation Phase

• System construction: Writing and executing codes. Testing
• System installation: User training
• System maintenance and support

SDLC: Methodologies

• Process, data, object oriented
• Structured, rapid action, agile
• Object oriented analysis and design methodologies, DevOps, custom methodologies.

Classes of Methodologies

• Structured Development:
  • Waterfall model: Sequential phases, complete definition before programming, long time delay
  • Parallel model: Parallel development of subprojects, less time on projects with less chance of rework
• Rapid Application Development
  • Phased: System development through versions
  • Prototyping: Quick and dirty system—minimal features
  • Throwaway prototyping: Detailed analysis, reliable solution; requires extensive time—More stability
• Agile Development: Streamlined process; eliminates modeling and documentation
  • Extreme programming (XP): Communication, simplicity, feedback, and courage
  • Scrum: Agile approach

Which Methodology to Use?

• Chart outlining the usefulness of methodologies for different situations

Object-Oriented Systems Analysis & Design (OOSAD)

• Third methodology category. Aims to balance data and process.
  • Uses UML, Unified Process

Characteristics of OOSAD

• Use-case driven: Use cases define system behavior; focuses on individual business processes
• Architecture-centric:
  • Functional view: User perspective
  • Static view: Attributes, methods, classes, and relationships
  • Dynamic view: Messages between classes, behaviors
• Iterative and incremental: Continuous testing and refinement enabling systems understanding over time

Benefits of OOSAD

• Break complex systems into modules
• Works on modules individually
• Understand system through realistic user interaction

The Unified Process

• Methodology for object-oriented analysis and design implementations
• Two-dimensional process composed of phases and workflows
  • Phases: Time periods in development
  • Workflows: Activities in specific phases

Unified Process Phases

• Inception: Feasibility assessment (technical, economic, organizational).
• Elaboration: Focus on analysis and design; other workflows might be included.
• Construction: Emphasis on programming/implementation.
• Transition: Focus on testing and deployment

Workflows

• Engineering and supporting workflows.
• Descriptions of duties or activities developers will undergo to progress an information system.

Engineering Workflows

• Business modeling, requirements, analysis, design, implementation, testing, and deployment

Supporting Workflows

• Project management, configuration and change management, and environment management.

Extensions to the Unified Process

• Clarification regarding the details that the Unified Process does not include.
• Addition of a Production Phase after the product has been deployed
• Modifications to the workflows: operations, infrastructure management

Unified Modeling Language (UML)

• Common object-oriented vocabulary, diagrams, and implementation modeling.
• 2.5 current version. Has 15 diagrams in two parts: structure diagrams and behavior diagrams.

Test your understanding of the roles and skills of systems analysts, the systems development life cycle (SDLC), and object-oriented principles in systems analysis and design. This quiz will help reinforce your knowledge of the methodologies and tools used in system development.