Information Systems Analysis and Design Quiz

Modern Systems Analysis and Design

• Information Systems Analysis and Design is a complex organizational process used to develop and maintain computer-based information systems.
• It's performed by a team of business and systems professionals.
• Application software is computer software designed to support organizational functions or processes.
• Systems Analysts are organizational roles responsible for the analysis and design of information systems.
• Methodologies, techniques, and tools drive a systems analysis and design approach.

Learning Objectives

• Define information systems analysis and design.
• Describe the information systems development life cycle (SDLC).
• Explain computer-aided software engineering (CASE) tools.
• Describe Agile Methodologies and eXtreme Programming.
• Explain object-oriented analysis and design and the Rational Unified Process (RUP).

Introduction

• Information Systems Analysis and Design is a complex organizational process used to develop and maintain computer-based information systems.
• It is performed by a team of business and systems professionals.

Introduction (Cont.)

• Application software is computer software designed to support organizational functions or processes.
• A systems analyst is an organizational role responsible for the analysis and design of information systems.

Introduction (Cont.)

• System analysis and design is driven by methodologies, techniques, and tools.

A Modern Approach to Systems Analysis and Design

• 1950s: Focus on efficient automation of existing processes.
• 1960s: Advent of procedural third-generation languages (3GL), faster and more reliable computers.
• 1970s: System development becomes more like an engineering discipline.
• 1980s: Major breakthrough with 4GL languages, CASE tools, and object-oriented methods.
• 1990s: Focus on system integration, GUI applications, client/server platforms, and the internet.
• New Century: Web application development, wireless PDAs and smart phones, component-based applications, and per-use cloud-based application services.

Developing Information Systems

• System Development Methodology is a standard process followed in an organization to analyze, design, implement, and maintain information systems.

Systems Development Life Cycle (SDLC)

• Traditional methodology used to develop, maintain, and replace information systems.
• Phases in SDLC: Planning, Analysis, Design, Implementation, and Maintenance.

Standard and Evolutionary Views of SDLC

• Systems development life cycle.
• Evolutionary model.

Systems Development Life Cycle (SDLC) (Cont.)

• Planning: Identifying, analyzing, prioritizing, and arranging an organization's total information system needs.
• Analysis: Studying and structuring system requirements.
• Design: Converting a recommended solution into logical and then physical system specifications.

Systems Development Life Cycle (SDLC) (Cont.)

• Logical design: Describes all functional features of a system, independent of the computer platform.
• Physical design: Transforming logical specifications into technology-specific details for programming and system construction.

Systems Development Life Cycle (SDLC) (Cont.)

• Implementation: Coding, testing, installing, and supporting the information system within the organization.
• Maintenance: Systematically repairing and improving the information system.

Products of SDLC Phases

• Planning: Priorities for systems and projects; architecture for data, networks, and information systems management.
• Analysis: Detailed steps/work plan; system scope and requirements.
• Design: Functional specifications of system elements (data, processes, inputs, and outputs); technical specifications of system elements.
• Implementation: Acquisition plan; code, documentation, training, and support capabilities.
• Maintenance: New versions and releases with documentation, training, and support updates.

A Specialized Systems Development Life Cycle

• Microsoft's Security Development Lifecycle (SDL).
• Training on security.
• Requirements analysis, design, implementation, verification, release, and response.

The Heart of the Systems Development Process

• Analysis-design-code-test loop.
• Combination of analysis, design, and implementation into an iterative and parallel process.

Traditional Waterfall SDLC

• One phase begins when another completes with little backtracking and looping.

Problems with Waterfall Approach

• Feedback is ignored. Milestones lock in design specs, even when conditions change.
• Limited user involvement (only in requirements phase).
• Too much focus on milestone deadlines of SDLC phases to the detriment of sound development practices.

Different Approaches to Improving Development

• CASE tools. Agile Methodologies. eXtreme Programming

Computer-Aided Software Engineering (CASE) Tools

• Diagramming tools that enable graphical representation.
• Computer displays and report generators help prototype how systems "look and feel".
• Analysis tools automatically check for consistency in diagrams, forms, and reports.
• Central repository for integrated storage of diagrams, reports, and project management specifications.
• Documentation generators that standardize technical and user documentation.
• Code generators for automatic program and database code generation from design documents.

CASE Tools (Cont.)

• Examples of CASE usage in different SDLC phases.

Agile Methodologies

• Motivated by recognizing software development as fluid, unpredictable, and dynamic.
• Three key principles-Adaptive, people-centric, self-adaptive processes.

Agile Methodologies (Cont.)

• Software development methodologies (Agile Manifesto).
• Key principles that emphasize continuous delivery of valuable software in response to changing requirements. The principles focus on customer collaboration, working software, and responding to change.
• Agile methods don't fit with real world software development from the Engineering methodologies.

When to use Agile Methodologies

• Projects with unpredictable or dynamic requirements.
• Teams with responsible and motivated developers.
• Customers who understand the process and are involved.

eXtreme Programming

• Short, incremental development cycles.
• Automated tests.
• Two-person programming teams.
• Coding, testing, listening, and designing.

eXtreme Programming (Cont.)

• Coding and testing operate together.
• Advantages include high communication, productivity, and high-quality code between developers.

Object-Oriented Analysis and Design (OOAD)

• Based on Objects rather than processes or data.
• Object: A structure encapsulating attributes and behaviors of a real-world entity.

Object-Oriented Analysis and Design (OOAD) (Cont.)

• Object class: A logical grouping of objects sharing the same attributes and behaviours.
• Inheritance: Hierarchical arrangement of classes enabling subclasses to inherit properties of super classes.

Rational Unified Process (RUP)

• An object-oriented systems development methodology.
• Establishes four phases for development: inception, elaboration, construction, and transition.
• Each phase is structured into multiple iterations.

Our Approach to Systems Development

• Criticisms of the SDLC, including forcing timed phases on intangible processes and favoring formal processes and documentation, which can slow things down, resulting in waterfall approaches.
• The value of the SDLC model and its variations.

Summary

• Highlights of the chapter, including how to define information systems, describe the SDLC, explain CASE tools, describe Agile and Extreme Programming, and explain object-oriented analysis and design, and the Rational Unified Process (RUP).