Systems Analysis and Design

Chapter 1

Computer application

A software program that executes on a computing device to carry out a specific set of functions (modest scope)

Information System

Set of interrelated components that collects, processes, stores, and provides as output the information needed to compete business tasks (broader in scope than “app”, includes database and related manual processes)

System analysis

Activities that enable understanding and specify what an information system should accomplish

System Design

Activities that enable a person to define and describe in detail the system that solves the need

System Analysis

What is required for the new system to solve the problem

System Design

How the system will operate to solve the problem

Software Development

Understand the need, Capture the vision, Define a solution, Communicate the vision and solution, Build the solution, Confirm that the solution meets the need, Launch the solution system

System Development Life Cycle (SDLC)

Process consisting of all activities required to build, launch, and maintain an information system.

System Development Life Cycle (SDLC) 6 core processes

1. Identify the problem or need and obtain approval

2. Plan and monitor the project

3. Discover and understand the details of the problem or need

4. Design the system components that solve the problem

5. Build, test, and integrate system components

6. Complete system tests and then deploy the solution

(SDLC) Project

Planned undertaking that has a beginning and end and that produces some definite result

Project

Used to develop an information system and requires knowledge of systems analysis and systems design tools and techniques

System development process

Actual approach used to develop a particulate information system (methodology)

System development process

Unified process (Up), Extreme programming (XP), Scrum

Agile Development

Information system development process that emphasizes flexibility to anticipate new requirements during development

Iterative development

Approach to system development in which the system is “grown” piece by piece through multiple iterations

Iterative development

Complete small part of system (mini project), then repeat process to refine and add more, then repeat to refine and add more, until done

Subsystem

Fully functional part of the complete information system.

Planning process for an iteration (3 steps)

1. Identify the tasks required for the iteration.

2. Organize and sequence these tasks into a schedule.

3. Identify required resources, and assign people to tasks

Use Case

Case or situation where the system is used

Use Cases

Identifying and describing use cases it the way to document what the users need to do with the system

Domain Classes

Diagrams that are powerful and frequently used way to understand and document the information requirements of a system

Use Case Diagram

Used to graphically portray the use cases and users involved in the subsystem

Design schema

Uses the domain class diagram and develops the detailed database schema that can be directly implemented by a database management system.

Design Class Diagram

Developing the set of software classes and their methods that will be needed for the system

High Structural design

Architectural blueprint defining core systems components, data flows and tech stacks without low-level code

Screen layout

Structural arrangement of visual user interface (UI) elements