1. 1-1
© Prentice Hall, 2004
Chapter 1:Chapter 1:
The Object-Oriented SystemsThe Object-Oriented Systems
Development EnvironmentDevelopment Environment
Object-Oriented Systems Analysis and
Design
Joey F. George, Dinesh Batra,
Joseph S. Valacich, Jeffrey A. Hoffer

2. Chapter 1 1-2
© Prentice Hall, 2004
Chapter ObjectivesChapter 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, and DSS.
– Describe the role of systems analyst.
– Recount the evolution of system development
methodologies.

3. Chapter 1 1-3
© Prentice Hall, 2004
What Is Systems Analysis andWhat Is Systems Analysis and
Design?Design?
The process of implementing and operating
an information system
Requires knowledge of:
– Organization’s objectives, structure, processes
– Information technology opportunities and
constraints

4. Chapter 1 1-4
© Prentice Hall, 2004

5. Chapter 1 1-5
© Prentice Hall, 2004
What Is a System?What Is a System?
A group of interrelated procedures used for
a business function, with an identifiable
boundary, working together for some
purpose.

6. Chapter 1 1-6
© Prentice Hall, 2004

7. Chapter 1 1-7
© Prentice Hall, 2004
Characteristics of SystemsCharacteristics of Systems
Boundary – divides system from environment
Inputs – data from environment to system
Output – data from system to environment
Components – subparts of systems operating
independently (objects)
Interrelationships – associations between
components of a system
Interfaces – mechanism for interacting with a
component

8. Chapter 1 1-8
© Prentice Hall, 2004
Important System ConceptsImportant System Concepts
Decomposition – breaking down a system
into smaller constituents
Modularity – the result of decomposition;
parts of a system
Coupling – dependencies between
subsystems
Cohesion – extent to which a subsystem
performs a single function

9. Chapter 1 1-9
© Prentice Hall, 2004

10. Chapter 1 1-10
© Prentice Hall, 2004
Transaction Processing SystemTransaction Processing System
(TPS)(TPS)
Automate the handling of data for business
activities or transactions
Goal: improve transaction processing by
increasing speed, enhancing productivity,
simplifying processes

11. Chapter 1 1-11
© Prentice Hall, 2004
Management Information SystemManagement Information System
(MIS)(MIS)
Use raw data from TPS systems, and
converts them into meaningful aggregate
form
Goal: provide the information that helps
managers in their jobs

12. Chapter 1 1-12
© Prentice Hall, 2004
Decision Support System (DSS)Decision Support System (DSS)
Interactively assist with decision making by
applying mathematical or logical models
and a dialogue of interactions to solve
unstructured problems
Goal: provide comparisons of alternatives
and recommendation of preferred option

13. Chapter 1 1-13
© Prentice Hall, 2004

14. Chapter 1 1-14
© Prentice Hall, 2004
The Role of the Systems AnalystThe Role of the Systems Analyst
Skills required: analytical, technical,
managerial> how to manage time,
interpersonal> to comunicate
Liaison between users, programmers, and
other systems professionals

15. Chapter 1 1-15
© Prentice Hall, 2004

16. Chapter 1 1-16
© Prentice Hall, 2004

17. Chapter 1 1-17
© Prentice Hall, 2004

18. Chapter 1 1-18
© Prentice Hall, 2004
Systems Planning and SelectionSystems 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 .>knal pasti msalah,cari jln
penyelsain,cos bajet,duration,saper yg akn
pkai.stakeholder.
Feasibility analysis: determine economic and
organizational impact of the system
Make detail planning

19. Chapter 1 1-19
© Prentice Hall, 2004
Systems AnalysisSystems 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
Menyelesaikn masalh yg dah kite kaji.

20. Chapter 1 1-20
© Prentice Hall, 2004
Systems DesignSystems Design
Translating alternative solution
generated by analysis phase into detailed
logical and physical system
specifications.design for solution is built.
– 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

21. Chapter 1 1-21
© Prentice Hall, 2004
System Implementation andSystem Implementation and
OperationOperation
Information system is coded, tested, and
installed, and undergoes periodic
corrections and enhancements/prbaiki
Goal: provide a fully operational system

22. Chapter 1 1-22
© Prentice Hall, 2004
Evolution of SystemEvolution of System
Development MethodologiesDevelopment 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

23. Chapter 1 1-23
© Prentice Hall, 2004
The current trend is to use OOSAD, but many organizations
are still using structured analysis and design

24. Chapter 1 1-24
© Prentice Hall, 2004
Inception/PELANCARANInception/PELANCARAN
Defining the scope, determining the
feasibility, understanding user
requirements, preparing a software
development plan
Relatively short, low resource requirements
Focus on planning and analysis

25. Chapter 1 1-25
© Prentice Hall, 2004
ElaborationElaboration
Detailed user requirements and baseline
architecture is established
Fairly long, but not high in resource
demand
Focus on analysis and design

26. Chapter 1 1-26
© Prentice Hall, 2004
ConstructionConstruction
Coding, testing, and documenting code
Longest and most resource-intensive
Focus is on implementation tasks

27. Chapter 1 1-27
© Prentice Hall, 2004
TransitionTransition
System is deployed and users are trained
and supported/KOS UNTK TRAIN
Short-term, but resource-intensive
Focus is on installation, training, and
support

28. Chapter 1 1-28
© Prentice Hall, 2004
Construction is the hardest part

29. Chapter 1 1-29
© Prentice Hall, 2004

30. Chapter 1 1-30
© Prentice Hall, 2004
RecapRecap
After studying this chapter we learned to:
– Define information systems analysis and
design.
– Explain the basics about systems.
– Describe the information systems development
cycle (SDC).
– Describe TPS, MIS, and DSS.
– Describe the role of systems analyst.
– Recount the evolution of system development
methodologies.