Download as pdf or txt
Download as pdf or txt
You are on page 1of 25

Systems Analysis and

Design, and Modeling


MGS567 –Analysis Modeling and Design
Professor Rajiv Kishore
Systems Analysis and Design
Ê Systems Analysis
Ê understand and specify an information system (existing or proposed)
Ê the “PROBLEM” domain
Ê the “WHAT” of the information system
Ê the “ESSENCE” of the information system

Ê Systems Design
Ê design and specify an information system (usually proposed system only)
Ê the “SOLUTION” domain
Ê the “HOW” of the information system
Ê the “IMPLEMENTATION” of the information system

Ê The “Mouse” Example

2 MGS567-F15-Kishore
The Layering of What and How
What Level 1

How Level 2 What

What Level 3 How

How Level 4

Level …

3 MGS567-F15-Kishore
Systems Development Life Cycle

Ê The entire process consisting of all activities required to


build, launch, and maintain an information system
Ê Identify the problem or need and obtain approval
Ê Plan and monitor the project
Ê Discover and understand the details of the problem or need
Ê Design the system components that solve the problem or
satisfy the need
Ê Build, test, and integrate system components
Ê Complete system tests and then deploy the solution

4 MGS567-F15-Kishore
Iterative and Agile Systems Development
Lifecycle (SDLC)

5 MGS567-F15-Kishore
But what is a system?
The Systems View Initial Thinking:
Von Bertalanffy, Herbert Simon, and others, circa 1960s

Environment

System System
Boundary
Inputs
System
Components

Outputs

Assets (Resources)

7 MGS567-F15-Kishore
Explaining Systems using the Systems
View

Ê Healthcare System

Ê Transportation System

Ê University System

Ê Information System

8 MGS567-F15-Kishore
The IPOD Model of Information Systems
System Interface (Boundary)

Process
Inputs Outputs

Data Information
Programs
I- Input
P- Process
O -Output
D-Data Store

Data
Store

9 MGS567-F15-Kishore
The Automation Boundary

10 MGS567-F15-Kishore
Information Systems and Subsystems

11 MGS567-F15-Kishore
Information Systems and Component
Parts

12 MGS567-F15-Kishore
Information Systems and Computer Apps

Ê Computer application (app) – a computer


software program that executes on a computing
device to carry out a specific set of functions
Ê Modest scope

Ê Information system – a set of interrelated


components that collects, processes, stores,
and provides as output the information needed
to complete business tasks
Ê Broader in scope than “app”
Ê Includes database and related manual processes

13 MGS567-F15-Kishore
Systems Analyst Skills
Knowledge and Skills of a Systems
Analyst

15 MGS567-F15-Kishore
Business Knowledge and Skills
Ê What business functions do organizations perform?

Ê How are organizations structured?

Ê How are organizations managed?

Ê What type of work goes on in organizations (finance, manufacturing,


marketing, customer service, etc.)?

Ê What does the specific organization do?

Ê What makes it successful?

Ê What are the strategies and plans of a specific organization?

Ê What are the traditions and values of a specific organization?

16 MGS567-F15-Kishore
People Knowledge and Skills
Ê Interpersonal skills
Ê because analysts rely on others, including managers, users, programmers,
technical specialists, customers, and vendors, to take a system from initial
idea to final implementation

Ê The analyst must


Ê develop rapport with users who may be resistant to change
Ê negotiate with management for such resources as budget, time, and
personnel, and
Ê manage development personnel with many different skills, capabilities,
and attitudes

Ê The analyst must be an effective teacher, mentor, confidant,


collaborator, manager, and leader, shifting easily among those roles
many times over the course of a typical work day

17 MGS567-F15-Kishore
Technical Knowledge and Skills

Ê Computers and how do they work

Ê File, database, and storage hardware and software

Ê Input and output hardware and software

Ê Computer networks and protocols

Ê Programming languages, operating systems, and utilities

Ê Communication and collaboration technology such as digital


telephones, videoconferencing, and Web-based document
management systems
Business Systems Analysts need only high level technical knowledge and skills

18 MGS567-F15-Kishore
Making Assumptions as an Analyst

Ê Do NOT make unnecessary assumptions in analysis work


without knowing they are assumptions
Ê If unclear about something, ask the domain experts – the users

Ê Solve the problem below WITHOUT making unnecessary


assumptions:

Ê There were six apples in a basket and six girls in a room.


Each girl took one apple, yet one apple remained in the
basket! How come?

19 MGS567-F15-Kishore
Systems Modeling
System Models and Systems Modeling

Ê How do we define/specify system requirements?

Ê After collecting information, create models

Ê Model
Ê a representation of some aspect of the system being built

Ê Types of Models
Ê Textual model– something written down, described
Ê Graphical models– diagram, schematic
Ê Mathematical models– formulas, statistics, algorithms

Ê Unified Modeling Language (UML)


Ê Standard graphical modeling symbols/terminology used for modeling
information systems

21 MGS605-S15-Kishore
Types of Models

Ê Textual
Ê Line

Ê Graphical

Ê Mathematical
Ê y = mx + c

22 MGS605-S15-Kishore
Some UML Models

þ þ

þ þ þ

23 MGS605-S15-Kishore
Reasons for Systems Modeling
Ê Precise and accurate specification of system requirements
Ê Removing ambiguity from system requirements specifications

Ê Identifying gaps in information gathering


Ê Remember, no assumption making

Ê Reducing complexity by abstraction


Ê Removing unnecessary details

Ê Learning from the modeling process


Ê Asking the right questions is tough, systems modeling helps

Ê Communicating with others


Ê Both programmers and users

Ê Documenting the system for future maintenance/enhancement

24 MGS605-S15-Kishore
Summary and Recap
Ê Systems Analysis and Systems Design
Ê Systems Development Life Cycle

Ê The Systems View

Ê Information Systems
Ê The IPOD Model of Information Systems
Ê The Automation Boundary

Ê Systems Analysts
Ê Do NOT make assumptions

Ê Systems Modeling

25 MGS567-F15-Kishore

You might also like