Chapter 1:
The Object-Oriented Systems
Development Environment
Object-Oriented Systems Analysis and
Design
Joey F. George, Dinesh Batra,
Joseph S. Valacich, Jeffrey A. Hoffer
© Prentice Hall, 2007
1-1
Chapter Objectives
 After studying this chapter you should be able to:
– Define information systems analysis and design.
– Explain the basics about systems.
– Describe the information systems development cycle
(SDC).
– Describe TPS, MIS, DSS, and ES/EIS.
– Describe the role of systems analyst.
– Recount the evolution of system development
methodologies.
Chapter 1
© Prentice Hall, 2007
1-2
What Is Systems Analysis and
Design?
 The process of developing and maintaining an
information system
 Main goal – improve organizational systems via
software to help accomplish business tasks
efficiently and easily
 Requires knowledge of:
– Organization’s objectives, structure, processes
– How to exploit information technology for advantage
Chapter 1
© Prentice Hall, 2007
1-3
Chapter 1
© Prentice Hall, 2007
1-4
Core Concepts
Major goal of systems analysis – improve
organizational systems
Development/acquisition of application
software
Other elements of IS – hardware, system
software, documentation, training materials,
job roles, controls and security, people
Chapter 1
© Prentice Hall, 2007
1-5
Chapter 1
© Prentice Hall, 2007
1-6
What Is a System?
A group of interrelated procedures used for
a business function, with an identifiable
boundary, working together for some
purpose.
Chapter 1
© Prentice Hall, 2007
1-7
Chapter 1
© Prentice Hall, 2007
1-8
Characteristics of Systems
 Components – irreducable or aggregate parts of a
system (also called subsystems)
 Interrelationships – associations and dependencies
between components of a system
 Boundary – divides system from environment
 Purpose – goal or function of a system
 Interfaces – points of contact between system and
environment
 Inputs – data from environment to system
 Output – data from system to environment
 Constraints – limit to what the system can accomplish
Chapter 1
© Prentice Hall, 2007
1-9
Important System Concepts
Decomposition – breaking down a system
into smaller constituents
Modularity – the result of decomposition;
parts of a system
Coupling – extent of dependencies between
subsystems
Cohesion – extent to which a subsystem
performs a single function
Chapter 1
© Prentice Hall, 2007
1-10
Chapter 1
© Prentice Hall, 2007
1-11
Transaction Processing System
(TPS)
Automate the handling of data for business
activities or transactions
Goal: improve transaction processing by
increasing speed, enhancing productivity,
improving efficiency and accuracy
Chapter 1
© Prentice Hall, 2007
1-12
Management Information System
(MIS)
Use raw data from TPS systems, and
converts them into meaningful aggregate
form, resulting in summary reports
Goal: provide the information that helps
managers in their jobs
Chapter 1
© Prentice Hall, 2007
1-13
Decision Support System (DSS)
 Combine databases, mathematical or graphical
models, and interactive user interfaces or
dialogues allowing users to manipulate data and
models
 Include what-if analyses, executive information
systems, data warehouses, knowledge
management systems
 Goal: support decision-making with unstructured
and unpredictable problems
Chapter 1
© Prentice Hall, 2007
1-14
IS Department Organization Chart
Chapter 1
© Prentice Hall, 2007
1-15
IS Components
Chief information officer
Chief Technology officer
Operation group
Development group
Outsourcing relation group
Data administration staff
Chapter 1
© Prentice Hall, 2007
1-16
Characteristics of Sucessful
Teams
 Diversity of backgrounds, skills, and goals
 Tolerance of diversity, uncertainty, and ambiguity
 Clear and complete communications
 Trust
 Mutual respect and putting personal interests
second to the team
 Reward structure that promotes shared
responsibility and accountability
Chapter 1
© Prentice Hall, 2007
1-17
The Role of the Systems Analyst
Skills required: analytical, technical,
managerial, interpersonal
Fluency in “systems thinking”
Liaison between users, programmers, and
other systems professionals
Chapter 1
© Prentice Hall, 2007
1-18
Chapter 1
© Prentice Hall, 2007
1-19
Evolution of System
Development Methodologies
 SDLC
– Systems Development Life Cycle
 Structured Analysis and Design
– Use of Data Flow Diagrams
 Data-Oriented Methodology
– Use of Entity Relation Diagrams
 Object-Oriented Methodology
– Use of Unified Modeling Language (UML) Diagrams
 Agile Methodologies
– Adaptive, people-oriented approach
Chapter 1
© Prentice Hall, 2007
1-20
Chapter 1
© Prentice Hall, 2007
1-21
Systems Planning and Selection
Analyze and arrange organization’s
information needs, identify and describe
potential project, determine system scope,
and provide a business case for continuing
with the project
Feasibility analysis: determine economic
and organizational impact of the system
Chapter 1
© Prentice Hall, 2007
1-22
Systems Analysis
Thorough study of organization’s current
system and processes, determination of
system requirements, structuring
requirements, generate alternative design
strategies.
Use of UML for system modeling
Goal: describe what needs to be done
Chapter 1
© Prentice Hall, 2007
1-23
Systems Design
Translating alternative solution generated
by analysis phase into detailed logical and
physical system specifications.
– Logical design: not tied to any hardware or
software platform
– Physical design: specific programming
languages, databases, architectures
Goal: identify how the task will be
accomplished
Chapter 1
© Prentice Hall, 2007
1-24
System Implementation and
Operation
Information system is coded, tested, and
installed, and undergoes periodic
corrections and enhancements
Goal: provide a fully operational system
Chapter 1
© Prentice Hall, 2007
1-25
Key Differences Between Structured and
Object-Oriented Analysis and Design
Structured
Object-Oriented
Methodology SDLC
Iterative/Incremental
Focus
Processs
Objects
Risk
High
Low
Reuse
Low
High
Maturity
Mature and widespread
Emerging
Suitable for
Well-defined projects with
stable user requirements
Risky large projects
with changing user
requirements
Chapter 1
© Prentice Hall, 2007
1-26
Construction
is the hardest
part
Chapter 1
© Prentice Hall, 2007
1-27
Inception
Defining the scope, determining the
feasibility, understanding user requirements,
preparing a software development plan
Relatively short, low resource requirements
Focus on planning and analysis
Chapter 1
© Prentice Hall, 2007
1-28
Elaboration
Detailed user requirements and baseline
architecture is established
Fairly long, but not high in resource
demand
Focus on analysis and design
Chapter 1
© Prentice Hall, 2007
1-29
Construction
Coding, testing, and documenting code
Longest and most resource-intensive
Focus is on implementation tasks
Chapter 1
© Prentice Hall, 2007
1-30
Transition
System is deployed and users are trained
and supported
Short-term, but resource-intensive
Focus is on installation, training, and
support
Chapter 1
© Prentice Hall, 2007
1-31
Chapter 1
© Prentice Hall, 2007
1-32