0% found this document useful (0 votes)
49 views65 pages

01 System Analysis Fundamental

This document provides an overview of system analysis and design. It discusses the objectives of the lecture which are to recall different types of computer systems, understand how users and technologies impact systems, know the roles of systems analysts, understand the system development life cycle as it relates to human-computer interaction, explore CASE tools and other methodologies. It also defines information systems, discusses why system analysis and design is important, and covers major topics like the types of systems analysts work with and the phases of the system development life cycle.

Uploaded by

Shazad osman
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
49 views65 pages

01 System Analysis Fundamental

This document provides an overview of system analysis and design. It discusses the objectives of the lecture which are to recall different types of computer systems, understand how users and technologies impact systems, know the roles of systems analysts, understand the system development life cycle as it relates to human-computer interaction, explore CASE tools and other methodologies. It also defines information systems, discusses why system analysis and design is important, and covers major topics like the types of systems analysts work with and the phases of the system development life cycle.

Uploaded by

Shazad osman
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 65

SCSD2613

System Analysis and Design

PART I
Fundamentals of Systems Analysis & Design
Lecturer: Kanar Tahir Hama-Salih

update: August 2019 (sharinhh)


OBJECTIVES
By the end of this lecture, you will be able to:
• Recall the basic types of computer-based systems that a systems analyst
needs to address
• Understand how users working in context with new technologies change
the dynamics of a system
• Realize what the many roles of the systems analyst are
• Know the steps of the SDLC as they relate to HCI and how to apply them to
a real system
• Understand what CASE tools are and how they help a systems analyst
• Explore other methodologies such as object-oriented systems design and
prototyping
INFORMATION – A KEY RESOURCE
• Fuels business and can be the critical factor in
determining the success or failure of a business
• Needs to be managed correctly
• Managing computer-generated information differs
from handling manually produced data

3
WHAT IS INFORMATION SYSTEMS (IS)?
A system which assembles, stores,
processes and delivers information relevant to
an organization, in such a way that the
information is accessible and useful to those
who wish to use it, including managers, staff,
clients and citizens.
An IS is human activity (social system) which
may or may not involve the use of computer
systems
…Buckingham et al. (1987)

4
WHAT & WHY SYSTEM ANALYSIS AND
DESIGN (SAD)?
Systems analysis and design is a systematic approach
to identifying problems, opportunities, and
objectives; analyzing the information flows in
organizations; and designing computerized (in this
case) information systems to solve a problem

(Computerized)
Information
Systems

5
WHAT & WHY SYSTEM ANALYSIS AND
DESIGN (SAD)?
• System development needs proper planning.
• There is a cost in system development.
• It is time consuming and needs project management.
• SAD is about problem solving that needs to be
creative, critical, and innovative.

6
ORGANIZATION AS SYSTEMS
Organization as systems, is composed of subsystems and so on.

It is mainly involves levels of management and culture.

These will impact the information system development.

The different levels of management will produce the different levels of decisions.

The culture influences the way people in subsystems interrelate.

7
ORGANIZATION AS SYSTEMS

Goals
OUTPUT
/INPUT

STUDENT AFFAIR

FACULTY

OUTPUT
/INPUT 8
6 Generic
Components
SYSTEM
Processing

Control

Boundary Output
Input
Feedback

Data People
Data People
6 Generic 6 Generic
+ Components Hardware Software + Components

Procedures
Procedures

Information Systems Automated Information


Systems
9
ORGANIZATION AS SYSTEMS
Level of Management

What ?
Strategic
Mgt

Tactical Mgt
How ?

Operations Mgt
Implement ?
10
System: a collection of
PRODUCTION SYSTEM (SUPER-SYSTEM)
interrelated components
that function together
to achieve some
outcome Inventory
management
system
Information System:
Manufacturing
a collection of System
interrelated components
that collect, process,
store, and provide as
output the information
needed to complete Customer
Order-entry
business tasks. maintenance
subsystem
subsystem
Customer
Sub-system: a system support
that is part of a larger system
system Catalog Order
maintenance fulfillment
subsystem subsystem
Super-system: a
larger system that
contains other systems
11
A FRAMEWORK FOR IS

12
BUSINESS DRIVERS FOR TODAY’S
INFORMATION SYSTEMS
• Globalization of the Economy
• Electronic Commerce and Business
• Security and Privacy
• Collaboration and Partnership
• Knowledge Asset Management
• Continuous Improvement and Total Quality Management
• Business Process Redesign
13
BUSINESS DRIVERS FOR TODAY’S
INFORMATION SYSTEMS
•Networks and the Internet
•Mobile and Wireless Technologies
•Object Technologies
•Collaborative Technologies
•Enterprise Applications
14
• Fundamentals of different kinds of
information systems
• Roles of systems analysts
MAJOR • Phases in the systems development life
cycle as they relate to Human-Computer
TOPICS Interaction (HCI) factors
• Computer-Aided Software Engineering
(CASE) tools

15
TYPES OF SYSTEMS
Systems analysts recommend, design, and maintain many types of systems
for users:
• Transaction Processing Systems (TPS)
• Office Automation Systems (OAS)
• Knowledge Work Systems (KWS)
• Management Information Systems (MIS)
• Decision Support Systems (DSS)
• Expert Systems (ES)
• Executive Support Systems (ESS)
• Group Decision Support Systems (GDSS)
• Computer-Supported Collaborative Work Systems (CSCWS)
16
Strategic
Level
A systems analyst may be
involved with any or all of
Higher Level
these systems at each
organization level
Knowledge
Level

Operational
Level

17
OPERATIONAL LEVEL

Transaction Processing System (TPS)


• Process large amounts of data for routine
business transactions
• Boundary-spanning
• Support the day-to-day operations of the
company
• Examples: Payroll Processing, Inventory
Management

18
OPERATIONAL LEVEL
A Payroll TPS
A TPS for payroll
processing captures
employee payment
transaction data
(such as a time card).
System outputs
include online and
hard-copy reports for
management and
employee paychecks.
KNOWLEDGE LEVEL
Office Automation System (OAS)
•Supports data workers who share information, but do
not usually create new knowledge
•Examples: Word processing, Spreadsheets, Desktop
publishing, Electronic scheduling, Communication
through voice mail, Email, Video conferencing

Knowledge Work System (KWS)


•Supports professional workers such as scientists,
engineers, and doctors
•Examples: computer-aided design systems, virtual
reality systems, investment workstations

20
HIGHER LEVEL Management Information System (MIS)
•Support a broad spectrum of organizational tasks including
decision analysis and decision making
•Examples: profit margin by sales region, expenses vs. budgets

Decision Support System (DSS)


•Aids decision makers in the making of decisions
•Examples: financial planning with what-if analysis, budgeting
with modeling

Expert System (ES)


•Captures and uses the knowledge of an expert for solving a
particular problem which leads to a conclusion or
recommendation
•Examples: MYCIN, XCON

21
HIGHER LEVEL
Management Information System (MIS)

22
HIGHER LEVEL
Decision Support System (DSS)

23
STRATEGIC LEVEL Executive Support System (ESS)
•Helps executives to make unstructured strategic decisions in
an informed way
•Examples: drill-down analysis, status access

Group Decision Support System (GDSS)


•Permit group members to interact with electronic support
•Examples: email, Google Doc

Computer-Supported Collaborative Work System (CSCWS)


•CDCWS is a more general term of GDSS
•May include software support called “groupware” for team
collaboration via network computers
•Example: video conferencing, Web survey system

24
INTEGRATING • Ecommerce and Web Systems
NEW • Enterprise Resource Planning Systems
TECHNOLOGIES • Wireless Systems
INTO • Open Source Software
TRADITIONAL • Need for Systems Analysis and Design
SYSTEMS

25
ENTERPRISE APPLICATION ARCHITECTURE

Enterprise applications
automate processes that
span multiple business
functions and
organizational levels and
may extend outside the
organization.
ENTERPRISE APPLICATION ARCHITECTURE
• Systems analysts need to be aware that integrating technologies affects all
types of systems.

27
E-COMMERCE AND WEB SYSTEMS
Increasing user awareness of the
BENEFITS availability of a service, product,
industry, person, or group

The possibility of 24-hour access for users

Creating a system that can extend


globally rather than remain local, thus
reaching people in remote locations
without worry of the time zone in which
they are located

Improving the usefulness and


usability of interface design

28
ENTERPRISE RESOURCE PLANNING SYSTEMS (ERP)
• Performs integration of many
information systems existing
on different management
levels and within different
functions
• Example: SAP, Oracle

29
WIRELESS SYSTEMS
• System analyst may be asked to
design standard or wireless
communication networks that
integrate voice, video and email
into organizational intranets or
industry extranets
• System analyst may also be asked to
develop intelligent agents
• Example: Microsoft's new software
based on Bayesian statistics
• Wireless communication is referred
as m-commerce (mobile commerce)

30
OPEN SOURCE SOFTWARE
• An alternative of traditional
software development where
proprietary code is hidden from
the users
• Open source software is free to
distribute, share and modify
• Characterized as a philosophy
rather than simply the process
of creating new software
• Example: Linux Operating
System, Apache Web Server,
Mozilla Firefox Web browser
31
NEED FOR SYSTEM ANALYSIS AND DESIGN
• Installing a system without proper planning leads to great
user dissatisfaction and frequently causes the system to
fall into disuse
• Lends structure to the analysis and design of information
systems
• A series of processes systematically undertaken to improve
a business through the use of computerized information
systems

32
SYSTEM ANALYST

ENVIRONMENT ROLES QUALITIES


System analyst (SA) studies the • The analyst must be able to • Problem solver
problems and needs of an work with people of all • Communicator
organization to determine how descriptions and be • Strong personal and
people, data, process, experienced in working with professional ethics
communications and computers
• Self-disciplined and self-
information technology can best • Three primary roles: motivated
accomplish improvements for 1. Consultant
the business (organizations) 2.Supporting Expert
3.Agent of change
33
SYSTEM ANALYST

34
SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
SYSTEM DEVELOPMENT LIFE CYCLE
(SDLC)
• The systems development life cycle is a phased approach to solving business
problems
• Developed through the use of a specific cycle of analyst and user activities
• Each phase has unique user activities.
• Incorporating Human-Computer Interaction (HCI) Considerations
• The demand for analysts who are capable of incorporating HCI into the systems
development process keeps increasing, as companies begin to realize that the quality
of systems and the quality of work life can be improved by taking a human-centered
approach at the outset of a project

36
SDLC – THE SEVEN PHASES

37
PHASE 1: Identifying Problems, Opportunities & Objectives
ACTIVITY:
• Interviewing user management
• Summarizing the knowledge obtained
• Estimating the scope of the project
• Documenting the results

OUTPUT: FEASIBILITY REPORT


• containing problem definition and objective
summaries from which management can make
a decision on whether to proceed with the
proposed project (come out with your system
proposal)
38
PHASE 2: Determining Human Information Requirements
Activity:
• Interviewing
• Sampling and investing hard data
• Questionnaires
• Observe the decision maker’s behavior and environment
• Prototyping
• Learn the who, what, where, when, how, and why of the current system

Output:
• Analyst understands how users accomplish their work when interacting
with a computer; and begin to know how to make the new system more
useful and usable.
• The analyst should also know the BUSINESS FUNCTIONS and have
complete information on the people, goals, data and procedure
involved.
39
PHASE 3: Analyzing System Needs
Activity:
• Create data flow diagrams
• Complete the data dictionary
• Analyze the structured decisions made
• Prepare and present the system proposal

Output:
• Recommendation on what, if anything, should
be done

40
PHASE 4: Designing the Recommended System
Activity:
• Design procedures for data entry
• Design the human-computer interface
• Design system controls
• Design files and/or database
• Design backup procedures

Output
• Model of the actual system
41
PHASE 5: Developing and Documenting Software
Activity:
• System analyst works with programmers to develop any
original software
• Works with users to develop effective documentation
• Programmers design, code, and remove syntactical
errors from computer programs
• Document software with help files, procedure manuals,
and Web sites with Frequently Asked Questions

Output:
• Computer programs
• System documentation

42
PHASE 6: Testing & Maintaining the System
Activity:
• Test the information system
• System maintenance
• Maintenance documentation
Output:
• Problems (if any)
• Updated programs
• Documentation
43
PHASE 7: Implementing & Evaluating the System
Activity:
• Do user training
• Analyze the plan to make sure smooth
conversion from old system to new system
• Review and evaluate system

Output:
• Trained personnel
• Installed system

44
SYSTEM MAINTENANCE

Figure 1.4 Some researchers estimate that the amount of time spent on systems
maintenance may be as much as 60 percent of the total time spent on systems projects
45
THE IMPACT OF MAINTENANCE
• Maintenance is performed for TWO reasons:
• Removing software errors, and
• Enhancing existing software

• Over time the cost of continued maintenance will be greater


than that of creating an entirely new system. At that point it
becomes more feasible to perform a new systems study

46
RESOURCE CONSUMPTION OVER THE
SYSTEM LIFE

47
IS DEVELOPMENT METHODOLOGIES

Comprehensive guidelines to follow


for completing every activity in the
systems development life cycle,
including specific models, tools and
techniques

48
IS DEVELOPMENT METHODOLOGIES

PROCESS- BLENDED OBJECT- RAPID PEOPLE- ORGANIZATIONAL FRAMEWORK


-ORIENTED
ORIENTED ORIENTED ORIENTED
•Soft-System
• Multiview
•Structured •James Martin’s • Strategic
•STRADIS •Booch Method RAD •CommonKADS Methodology
Methodology - System Analysis & (SSM) options
•OOSE •Extreme •ETHICS
Gane & Sarson’s Design Method •IS work and development
(SSADM) •OMT Programming (XP) •KADS
Methodology Analysis of and analysis
•Unified Approach •Web IS
•Yourdon System Methodology Changes (ISAC) (SODA)
Method (YSM) development
•Rational Unified methodology •Process Innovation • Capability
•Jackson System Process (WISDM) (PI) Maturity Model
Development •Project in (CMM)
(JSD) controlled
environments
(PRINCE)
49
•Traditional Systems Development
Life Cycle (discussed in previous sub-topic)
SDLC •Object-Oriented Systems Analysis
APPROACHES and Design
•CASE Systems Development Life
Cycle
2 GENERAL APPROACHES

Structured
Approach Object-
Traditional
Oriented
Approach
Approach

All system developers should be


familiar with two very general
approaches (STRUCTURED & OO) to
system development, because they
form the basis of virtually all
methodologies
51
OBJECT ORIENTED SYSTEM ANALYSIS &
DESIGN
• Alternate approach to the structured approach of the SDLC
that is intended to facilitate the development of systems that
must change rapidly in response to dynamic business
environments
• Analysis is performed on a small part of the system followed
by design and implementation. The cycle repeats with
analysis, design and implementation of the next part and
this repeats until the project is complete
1-52
STRUCTURED vs OBJECT ORIENTED

O-Oriented
Structured
Methodologies
Methodologies
1. Booch
1. STRADIS
2. OMT
2. SSADM
3. OOSE
3. JSD
4. Unified Approach
4. YSM
5. Rational Unified
5. More…
Process
6. More…

53
STRUCTURED vs OBJECT ORIENTED

?????
PROCESS 3
Problem

OBJECT 3
54
CASE TOOLS
• CASE tools are productivity tools for systems analysts that
have been created explicitly to improve their routine work
through the use of automated support
• Reasons for using CASE tools
• Increasing Analyst Productivity
• Improving Analyst-User Communication
• Integrating Life Cycle Activities
• Accurately Assessing Maintenance Changes

55
CASE TOOLS CLASSIFICATION
• Upper CASE tools perform
analysis and design (mainly for
analyst & designers)
• Lower CASE tools generate
programs from CASE design
(use by programmers)
• Integrated CASE tools perform
both upper and lower CASE
functions

56
UPPER CASE TOOLS
• Create and modify the system design
• Help in modeling organizational
requirements and defining system
boundaries
• Can also support prototyping of
screen and report designs

57
LOWER CASE TOOLS
• Lower CASE tools generate
computer source code from the
CASE design
• Source code is usually generated in
several languages

58
TRADITIONAL vs CASE SDLC

59
•Agile approach
•Prototyping
ALTERNATE •ETHICS
SDLC
APPROACHES •Project champion
•Soft Systems Methodology
•Multiview
MAIN COMPONENTS OF METHODOLOGY
Techniques is a Tool is software
collection of tool that helps
guidelines that Techniques Tools create models or
help an analyst other components
complete a system required in the
development. METHODOLOGY project

1. Strategic Planning 1. CASE


TECHNIQUE SAMPLES

2. User interviewing
Models 2. Drawing/graphic

TOOLS SAMPLES
techniques
applications
3. Data-Modeling
techniques 3. Reverse-engineering
tool
4. Software-testing
techniques 4. Code generator tool
1. Flowchart

MODEL SAMPLES
5. Project Mgt 5. Database
2. Data Flow Diagram
techniques Model is a (DFD) management
6. Structured analysis & representation of 3. Entity-Relationship
application
design techniques some important Diagram (ERD) 6. Word processor
aspect of the real 4. Structure Chart
world 5. Class diagram
6. Sequence diagram 61
• Information is a key resource
• Systems analysts deal with many types of
information systems
• Integration of traditional systems with new
TOPIC technologies
SUMMARY • Roles and qualities of the systems analyst
• The systems Development Life Cycle
• CASE tools
• Alternatives to structured analysis and design
and to the SDLC
OVERALL PICTURE OF SYSTEM SYS. ANALYSIS
Information

ANALYSIS & DESIGN


Gathering

Analyze Project Mgt


▪WFD, AD,
Process Information
etc
Models
▪Logical DFD
current & new
system
▪ Decision table, Data Model SYS. PLANNING
decision trees, etc
Process Design Feasibility
(Convert DFD to Str. Chart Probl. Definition
Report – first
Output Design mile stone
Program Design
Input Design
Database Design
SYS. DESIGN
Design spec Report 2 nd SYS. IMPLEMENTATION final
milestone output (present the system)
63
REFERENCES
• Kendall, K.E. & Kendall, J.E., 2014. System Analysis and Design. 9th Ed.
Essex:Pearson.

64
update: August 2019 (sharinhh)

You might also like