Chapter02 succeeding as a systems analyst

Copyright 2002 Prentice-Hall, Inc.
Chapter 2
Succeeding as a Systems
Analyst
2.1
Modern Systems Analysis
and Design
Third Edition
Jeffrey A. Hoffer
Joey F. George
Joseph S. Valacich

Learning Objectives
Discuss the analytical skills, including
systems thinking, needed for a systems
analyst to be successful
Describe the technical skills required of a
systems analyst
Discuss the management skills required of a
systems analyst
Identify the interpersonal skills required of a
systems analyst
Describe the systems analysis profession
2.2

Analytical Skills for Systems
Analysis
Four Sets of Analytical Skills
 Systems Thinking
 Organizational Knowledge
 Problem Identification
 Problem Analyzing and Solving
2.3

Systems Thinking
System
 A system is an interrelated set of business
procedures used within one business unit
working together for a purpose
 A system has nine characteristics
 A system exists within an environment
 A boundary separates a system from its
environment
2.4

Systems Thinking
Characteristics of a System
 Components
 Interrelated Components
 Boundary
 Purpose
 Environment
 Interfaces
 Input
 Output
 Constraints
2.5

Systems Thinking
Important System Concepts
 Decomposition
 The process of breaking down a system into
smaller components
 Allows the systems analyst to:
 Break a system into small, manageable subsystems
 Focus on one area at a time
 Concentrate on component pertinent to one group of
users
 Build different components at independent times
2.6

Systems Thinking
Important System Concepts (Continued)
 Modularity
 Process of dividing a system into modules of a relatively
uniform size
 Modules simplify system design
 Coupling
 Subsystems that are dependent upon each other are
coupled
 Cohesion
 Extent to which a subsystem performs a single function
2.7

Systems Thinking
Important System Concepts
(Continued)
 Logical System Description
 Portrays the purpose and function of the
system
 Does not tie the description to a specific
physical implementation
 Physical System Description
 Focuses on how the system will be materially
constructed2.8

Systems Thinking
Benefits
 Identification of a system leads to abstraction
 From abstraction you can think about essential
characteristics of specific system
 Abstraction allows analyst to gain insights into
specific system, to question assumptions, provide
documentation and manipulate the system without
disrupting the real situation
2.9

Systems Thinking
Applying Systems Thinking to Information
Systems
 Information systems are subsystems in larger
organizational systems
 Data flow diagrams represent information systems
as systems
 Inputs
 Outputs
 System boundaries
 Environment
 Subsystems
 Interrelationships
2.10

Organizational Knowledge
Understanding of how organizations work
Knowledge of specific functions and
procedures of organization and department
How work officially gets done
Internal policies
Competitive and Regulatory Environment
Organizational Strategies and Tactics
2.11

Problem Identification
Problem: Difference between an
existing situation and a desired situation
Identification is process of defining
differences
Differences are defined by comparing
the current situation to the output of a
model that predicts what the output
should be
2.12

Problem Analyzing and
Solving
Four Phases
 Intelligence
 All relevant information is collected
 Design
 Alternatives are formulated
 Choice
 Best alternative solution is chosen
 Implementation
 Solution is put into practice
2.13

Technical Skills for Systems
Analysis
Constant re-education is necessary as
technology changes rapidly
Activities to keep skills up-to-date
 Trade publications
 Professional societies
 Attend classes or teach at a local college
 Attend courses sponsored by organization
 Conferences and trade shows
 Browse Websites
 Participate in new groups and conferences
2.14

Technical Skills for Systems
Analysis
Understanding of a wide variety of
technologies is required
 Microcomputers, workstations, minicomputers and
mainframe computers
 Programming languages
 Operating systems
 Database and file management systems
 Data communication standards
 Systems development tools and environments
 Web development languages and tools
 Decision support system generators
2.15

Management Skills for
Systems Analysis
Four categories
 Resource Management
 Project Management
 Risk Management
 Change Management
2.16

Resource Management
Systems analyst needs to know how to get
the most out of the resources of an
organization, including team members
Includes the following capabilities
 Predicting resource usage
 Tracking resource consumption
 Effective use of resources
 Evaluation of resource quality
 Securing resources from abusive use
 Relinquishing resources when no longer needed
2.17

Project Management
Two Goals
 Prevent projects from coming in late
 Prevent projects from going over budget
Assists management in keeping track of
project’s progress
Consists of several steps
 Decomposing project into independent tasks
 Determining relationships between tasks
 Assigning resources and personnel to tasks
2.18

Risk Management
Ability to anticipate what might go
wrong in a project
Minimize risk and/or minimize damage
that might result
Placement of resources
Prioritization of activities to achieve
greatest gain
2.19

Change Management
Ability to assist people in making
transition to new system
Ability to deal with technical issues
related to change
 Obsolescence
 Reusability
2.20

Interpersonal Skills for
Systems Analysis
Mastery of interpersonal skills is
paramount to success as a Systems
Analyst
Four types of skills:
 Communication skills
 Working alone and with a team
 Facilitating groups
 Managing expectations
2.21

Communication Skills
Effective communication helps to
establish and maintain good working
relationships with clients and colleagues
Skills improve with experience
Three types used by Systems Analyst
 Interviewing and Listening
 Questionnaires
 Written and Oral Presentations
2.22

Interviewing and Listening
Means to gather information about a
project
Listening to answers is just as important
as asking questions
Effective listening leads to
understanding of problem and
generates additional questions
2.23

Questionnaires
Advantages:
 Less costly than interviews
 Results are less biased due to
standardization
Disadvantages
 Less effective than interviews due to lack
of follow-up
2.24

Written and Oral
Presentations
Used to document progress of project and
communicate this to others
Communication takes several forms:
 Meeting agenda
 Meeting minutes
 Interview summaries
 Project schedules and descriptions
 Memoranda requesting information
 Requests for proposals from vendors and
contractors
 Oral presentations2.25

Steps to Improving
Communication Skills
Practice
 Conduct a training class
 Volunteer to speak
Videotape presentation and do a self-
appraisal of your skills
Make use of college writing centers
Take classes on business and technical
writing
2.26

Working Alone and with a
Team
Working alone on aspects of project involves
managing:
 Time
 Commitments
 Deadlines
Team work involves establishing standards of
cooperation and coordination
Table 2-2 presents characteristics of a high-
performance team
2.27

Facilitating Groups
Involves guiding a group without being
a part of the group
Useful skill for sessions such as Joint
Application Development (JAD)
Figure 2-9 lists guidelines for running a
successful meeting
2.28

Managing Expectations
Managing expectations is directly related to
successful system implementation
Skills for successful expectation management
 Understanding of technology and workflows
 Ability to communicate a realistic picture of new
system to users
 Effective education of management and users
throughout systems development life cycle
2.29

Systems Analysis as a
Profession
Standards have been established for
education, training, certification and
practice
Several aspects:
 Standards of Practice
 Ethics
 Career Paths
2.30

Standards of Practice
Endorsed Development Methodology
 Specific procedures and techniques to be used
during development process
 Promote consistency and reliability across all of an
organization’s development projects
Approved Development Platforms
 Organizations standardize around a specific
platform, sometimes tied to development
methodology
2.31

Standards of Practice
Standardization of Roles
 Roles are becoming better defined across
organizations
Development of a Common Language
 Common programming languages
 Common modeling languages, such as
Unified Modeling Language (UML)
2.32

Ethics
Professional Ethics
 ACM Code of Ethics – See Figure 2-10
Business Ethics
 Stockholder approach
 Any action taken by a business is acceptable as long as
it is legal and maximizes stockholder profit
 Stakeholder approach
 Any action that violates rights of stakeholder must be
rejected
 Social Contract approach
 Any action that is deceptive, can dehumanize employees
or that could discriminate is rejected
2.33

Career Paths
Consulting
Information Systems within a large
corporation
Software vendors
Other opportunities outside of systems
analysis
2.34

Summary
Skills of Successful Systems Analyst
 Analytical
 Systems Thinking
 Technical
 Change over time
 Programming Languages
 Operating Systems
 Database Management Systems
 Data Communications
 Systems Development Techniques
2.35

Summary
Skills of a Successful Systems Analyst
(Continued)
 Management
 Resources
 Projects
 Risk
 Change
2.36

Summary
Skills of a Successful Systems Analyst
(Continued)
 Interpersonal
 Interviews and Questionnaires
 Written and Oral Presentations
 Facilitating Groups
Systems Analysis as a Career
 Standards of Practice
 Ethics
 Career Paths
2.37

Chapter02 succeeding as a systems analyst

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to Chapter02 succeeding as a systems analyst (20)

More from Dhani Ahmad (20)

Recently uploaded (20)

Chapter02 succeeding as a systems analyst