SYSTEM ANALYSIS
Transaction Processing Systems (TPS) -
CHAPTER 1
Information Technology (IT) - The combination of
hardware and software products and services
used by companies to manage, access,
communicate, and share information.
Systems Analysis and Design - A step-by-step
process for developing high-quality information
systems.
Systems Analyst - A professional responsible for
planning, developing, and maintaining
information systems, as well as managing IT
projects and conducting various related tasks.
Information System -A set of related components
that produce specific results, consisting of
hardware, software, data, processes, and
people.
Hardware - The physical layer of an information
system, including devices like computers,
servers, and networking equipment.
Software -Programs and applications that run on
hardware, categorized into system software and
application software.
Data- Information stored in databases or other
formats, essential for business operations and
decision-making.
Processes -Tasks and functions performed by
users, managers, and IT staff to achieve specific
results within an organization.
People -Stakeholders involved in or affected by
the information system, including users,
managers, and other personnel.
Business Profiles - Overview of a company's
mission, functions, organization, products,
services, customers, suppliers, competitors,
constraints, and future direction.
Business Processes - Specific set of
transactions, events, and results that can be
described and documented within an
organization.
Enterprise Computing - Information systems that
support company-wide operations and data
management requirements, often facilitated by
enterprise resource planning (ERP) systems.
Systems that process data generated by day-to-
day business operations, such as customer
orders, accounts receivable, and warranty
claims.
Business Support Systems- Systems that
provide job-related information support to users
at all levels of a company, often working
alongside transaction processing systems.
Knowledge Management Systems- Systems
that use a large database called a knowledge
base to allow users to find information by
entering keywords, aided by inference rules to
identify data patterns and relationships.
User Productivity Systems - Technology aimed
at improving productivity, such as groupware
and systems integration.
Structured Analysis - A traditional method for
developing systems, organized into phases and
using process models to describe systems
graphically.
Object-Oriented Analysis - A more recent
method for developing systems, where objects
represent people, things, or events, and built-in
processes (methods) act on them.
Agile Methods -A modern software development
approach involving iterative development,
continuous feedback, and flexible adaptation to
changing requirements.
Prototyping - Creating early working versions of
an information system to speed up the
development process and gather feedback.
Computer-Aided Systems Engineering (CASE)
Tools - Tools that provide an overall framework
for systems development and support various
design methodologies, such as structured
analysis and object-oriented analysis.
Joint Application Development (JAD) - A method
focusing on team-based fact-finding to gather
requirements for systems development.
Rapid Application Development (RAD) - A
compressed version of the entire development
process, emphasizing speed and
responsiveness to change.
Systems Development Life Cycle (SDLC) - The
traditional approach to systems development,
typically including steps such as systems
planning, analysis, design, implementation, and
support.
Radio Frequency Identification (RFID) -
Technology using high-frequency radio waves to
track physical objects, often used in business
support systems for inventory management.
Feasibility Study- An investigation phase in
systems planning to determine the viability of a
proposed system, considering factors such as
technical, economic, and organizational
feasibility.
Agile Manifesto - A set of guiding principles for
agile software development, emphasizing
customer collaboration, flexibility, and
responsiveness to change.
Scrum - A specific agile development framework
focused on iterative and incremental
development.
Extreme Programming (XP) - An agile software
development methodology emphasizing
customer satisfaction, continuous feedback, and
rapid adaptation to changing requirements.
Quality Assurance - The process of reviewing
and testing applications and systems changes to
verify specifications and software quality
standards, ensuring a well-designed, secure,
and reliable system.
Continuation of the Information Technology
Department and Systems Analyst section:
Application Development - Systems are
developed collaboratively by teams comprising
users, managers, and IT staff members.
Knowledge, Skills, and Education
- Technical Knowledge - Understanding of
programming languages, development tools,
and methodologies.
- Communication Skills - Strong oral and written
communication abilities to convey technical
concepts effectively.
- Business Skills - Familiarity with business
operations and processes to align technical
solutions with organizational objectives.
- Critical Thinking Skills - Ability to analyze
problems, evaluate solutions, and make
informed decisions.
- Education - Degrees in computer science,
information technology, or related fields are
common, along with ongoing professional
development.
- Certification - Obtaining industry-recognized
certifications demonstrates proficiency and
competence in specific technologies or
methodologies.
Systems Support and Security - Ensures the
protection, maintenance, and security of
information systems to safeguard against threats
and ensure operational continuity.
User Support - Provides technical assistance,
training, and guidance to users to enhance their
productivity and proficiency with information
systems.
Database Administration - Involves the design,
management, security, backup, and access
control of databases to ensure data integrity and
availability.
Network Administration - Manages hardware
and software components of computer networks,
including maintenance, support, and security
measures.
Web Support - Design and construction of web
pages, monitoring web traffic, managing
hardware and software components, and
integrating web-based applications with the
company's information systems.
Quality Assurance - Team responsible for
reviewing and testing applications and system
changes to ensure adherence to specifications
and software quality standards.
Systems Analyst Role - Involves building
models, diagrams, and decision tables to
analyze and design information systems.
- Effective analysts possess strong listening
skills and actively involve users throughout the
development process.
Career Opportunities - Increasing demand for
systems analysts due to the adoption of new
information technologies and growth in e-
commerce.
- Factors such as job titles, organizational
structure, company size, salary, location, growth
prospects, and corporate culture influence
career opportunities in the field.
CHAPTER 2
Business Case and Strategic Planning
Business Case - A comprehensive justification
for a proposed project, outlining its objectives,
scope, costs, benefits, risks, and alternatives.
Strategic Planning Process- The systematic
process of defining an organization's direction
and making decisions on allocating resources to
pursue its objectives. It involves setting goals,
identifying strategies, and aligning resources
with long-term objectives.
Mission Statemen- A statement that defines an
organization's purpose, goals, and values. It
provides a framework for decision-making and
guides the organization's actions.
SWOT Analysis - A strategic planning tool used
to identify an organization's strengths,
weaknesses, opportunities, and threats. It helps
assess internal capabilities and external factors
affecting the organization's performance.
Systems Development Framework
SDLC (Systems Development Life Cycle
- A structured approach to developing
information systems, consisting of phases such
as planning, analysis, design, implementation,
and maintenance.
Planning Tools - Tools used by analysts to assist
in project planning, such as text-based methods
(e.g., Microsoft Word), spreadsheet methods
(e.g., Microsoft Excel), or Computer-Aided
Software Engineering (CASE) tools.
IT Department's Role - The evolving role of the
IT department in organizations, including
functions like project screening, evaluation, and
team-oriented systems development.
Reasons for Systems Projects and
Evaluation
Systems Requests - Formal requests made by
users or stakeholders for new information
systems or enhancements to existing systems.
Internal Factors - Factors within an organization
that influence systems projects, such as
strategic plans, user requests, management
directives, existing systems, and IT department
capabilities.
External Factors -Factors outside an
organization that impact systems projects,
including technological advancements, supplier
capabilities, customer needs, competitive
pressures, economic conditions, and
government regulations.
Feasibility Evaluation
Operational Feasibility - The assessment of
whether a proposed system will meet user
needs and expectations, including factors like
user support, system acceptance, and impact on
business operations.
Technical Feasibility - The evaluation of whether
a proposed system can be developed,
implemented, and maintained with available
technology and resources, considering
hardware, software, network requirements, and
technical expertise.
Economic Feasibility - The analysis of the costs
and benefits associated with a proposed system,
including tangible and intangible costs, potential
savings, return on investment (ROI), and
payback period.
Schedule Feasibility -The assessment of
whether a proposed system can be developed
and implemented within a reasonable time
frame, considering stakeholder expectations,
project milestones, and potential risks.
Setting Priorities and Preliminary
Investigation
Priority Setting - The process of determining the
order of importance or urgency for systems
projects based on criteria such as cost
reduction, revenue generation, information
improvement, customer service, organizational
needs, time constraints, and resource
availability.
Discretionary Projects - Projects where
management has the choice to implement them
based on organizational priorities and available
resources.
Nondiscretionary Projects - Projects that must
be implemented due to legal, regulatory, or
contractual requirements.
Preliminary Investigation -The initial phase of the
SDLC where analysts gather information, assess
feasibility, define project scope, and identify
constraints for proposed systems projects.
CHAPTER 3
Project Management - The application of
knowledge, skills, tools, and techniques to
project activities to meet project requirements.
Project Triangle - A model representing the
constraints of project management, typically
depicted as a triangle with corners representing
scope, time, and cost.
Scope - The defined features and functions of a
project, including what is within and outside the
boundaries of the project.
Cost - The financial resources required to
complete a project, including labor, materials,
and other expenses.
Time -The duration required to complete a
project, including start and end dates for each
task and the overall project timeline.
Project Manager -The individual responsible for
planning, executing, and closing a project,
including managing resources, schedules, and
budgets.
Project Planning - The process of defining
project goals, tasks, schedules, and resources
required for successful project completion.
Project Scheduling -Creating a timeline that
outlines when project tasks will be performed,
including dependencies and critical paths.
Project Monitoring -Supervising project progress
to ensure tasks are completed on time and
within budget, and addressing issues as they
arise.
Project Reporting - Providing regular updates on
project progress to stakeholders, including
management, users, and the project team.
Work Breakdown Structure (WBS) - A
hierarchical decomposition of project tasks into
smaller, more manageable components.
Gantt Chart - A bar chart that represents project
tasks and their durations, used for scheduling
and tracking progress.
- developed by mechanical engineer and
management consultant Henry L. Gantt almost
100 years ago
- Shows planned and actual progress on a
project
- Time usually displayed on horizontal axis
- Tasks shown on vertical axis
PERT/CPM Chart - A graphical representation of
project tasks, dependencies, and critical paths,
used for project scheduling and management.
- Program Evaluation Review Technique (PERT)
- Developed by the U.S. Navy to manage
complex projects
- PERT is more useful for scheduling,
monitoring, and controlling the actual work.
Critical Path Method -The sequence of project
tasks that determines the minimum duration
required to complete the project.
- similar to PERT, developed by private industry
- most analysts call both a PERT chart
Task Patterns - Common sequences of project
tasks, including dependent tasks, multiple
successor tasks, and multiple predecessor
tasks.
Risk Management - The process of identifying,
assessing, and mitigating risks that could impact
project success.
Qualitative Risk Analysis - Assessing the
likelihood and impact of project risks using
subjective measures.
Quantitative Risk Analysis - Assessing the
impact of project risks using numerical data and
calculations.
Project Management Software - Tools and
applications used to assist in project planning,
scheduling, monitoring, and reporting.

Business Issues - Challenges related to project
alignment with business goals, requirements,
and problem-solving capabilities.
Budget Issues - Challenges related to inaccurate
budget estimates, poor monitoring, and
unforeseen expenses during project execution.
Schedule Issues - Challenges related to delays,
milestones, and task dependencies affecting
project timelines.
FACTORS AFFECTING DURATION
- Project Size -Must identify all project tasks,
from initial fact-finding to system implementation
How much time will be needed to perform each
task?
- Allow time for meetings, project reviews,
training, and any other factors that could affect
the productivity of the development team
Human Resource Issues - Challenges related to
staffing, turnover, training, and motivation of
project team members.
Experience with Similar Projects - Develop time
and cost estimates based on the resources used
for similar, previously developed information
systems
- Use experience from projects that were
developed in a different environment
Constraint- Constraints are conditions,
restrictions, or requirement that the system must
satisfy
- Define system requirements that can be
achieved realistically within the required
constraints.
RISK MANAGEMENT
Steps in Risk Management
1. Develop a Risk Management Plan
- Review of the project’s scope, stakeholders,
budget, schedule, and any other internal or
external factors that might affect the project
- Define project roles and responsibilities, risk
management methods and procedures,
categories of risks, and contingency plans
2. Identify the risks – list each risk and assesses
the likelihood that it could affect the project.
3. Analyze the risks
2 Steps to analyze the risks
Qualitative risk – analysis evaluates each risk by
estimating the probability that will occur and the
degree of impact.
Quantitative Risk - Analysis is to understand the
actual impact in terms of dollars, time, project
scope, or quality.
4. Risk Management Software
Assigns specific dates as constraints
Aligns task dependencies
Notes external factors that might affect a task
Tracks progress
Displays tasks that are behind schedule
Links risks with specific tasks and projects
Specifies probability and impact
Assigns ownership
Tracks progress to manage projects more
efficiently.
MANAGING FOR SUCCESS
1. Business Issues - Every system is to provide
a solution to a business problem or
opportunity
If a system does not do this, it is a failure
2. Budget Issues
- Unrealistic estimates that are too optimistic or
based on incomplete information
- Failure to develop an accurate forecast that
considers all costs over the life of the project
- Poor monitoring of progress and slow response
to early warning signs of problems
- Schedule delays due to factors that were not
foreseen
- Human resource issues, including turnover,
inadequate training, and motivation.
3. Schedule Issues - Problems with timetables
and project milestones can indicate a failure to
recognize task dependencies, confusion
between effort and progress, poor monitoring
and control methods, personality conflicts
among team members, or turnover of project
personnel.
- The failure of an IT project also can be caused
by poor project management techniques