systems analysis and design with uml 2miftakulamin.polsri.ac.id/adbo/ch01 introduction to... · lif...
TRANSCRIPT
Systems Analysis and Design With UML Systems Analysis and Design With UML Systems Analysis and Design With UML Systems Analysis and Design With UML 2.02.0
An ObjectAn Object--Oriented Approach, Second EditionOriented Approach, Second Edition
Chapter 1: Introduction to Systems Analysis and Designa d es g
Alan Dennis, Barbara Wixom, and David Tegarden© 2005John Wiley & Sons, Inc.
Slide 1
Copyright © 2005J h Wil & S IJohn Wiley & Sons, Inc.
All rights reserved. Reproduction or translation of this All rights reserved. Reproduction or translation of this work beyond that permitted in Section 117 of the 1976 United States Copyright Act without the express written permission of the copyright owner is unlawful. p py gRequest for further information should be addressed to the Permissions Department, John Wiley & Sons, Inc. The purchaser may make back-up copies for his/her own The purchaser may make back up copies for his/her own use only and not for redistribution or resale. The Publisher assumes no responsibility for errors, omissions, or damages, caused by the use of these omissions, or damages, caused by the use of these programs or from the use of the information contained herein.
Slide 2
INTRODUCTION
Chapter 1
Slide 3
K IdKey Ideas
Many failed systems were Many failed systems were abandoned because analysts
d b ld d f ltried to build wonderful systems without understanding the gorganization.The primarily goal is to create The primarily goal is to create value for the organization.
Slide 4
K IdKey Ideas
The systems analyst is a key person The systems analyst is a key person analyzing the business, identifying opportunities for improvement, and opportunities for improvement, and designing information systems to implement these ideas.It is important to understand and develop through practice the skills needed to successfully design and implement new information
tSlide 5
systems.
THE SYSTEMS DEVELOPMENT LIFE DEVELOPMENT LIFE CYCLE
Slide 6
Major Attributes of the Lif lLifecycle
The projectThe projectMoves systematically through phases where each phase has a standard set where each phase has a standard set of outputsProduces project deliverablesp jUses deliverables in implementationResults in actual information systemyUses gradual refinement
Slide 7
P j t PhProject Phases
PlanningPlanningWhy build the system?
AnalysisAnalysisWho, what, when, where will the system be?
D iDesignHow will the system work?
l iImplementationSystem delivery
Slide 8
A “Simple” Process for Making LunchA Simple Process for Making Lunch
Slide 9
Pl i
Identifying business value
Planning
Identifying business valueAnalyze feasibilityDevelop work planStaff the projectStaff the projectControl and direct projectp j
Slide 10
A l i
Analysis
Analysis
AnalysisInformation gatheringProcess modelingData modelingData modeling
Slide 11
D i
Physical design
Design
Physical designArchitectural designInterface designDatabase and file designDatabase and file designProgram designg g
Slide 12
I l t ti
Construction
Implementation
ConstructionInstallation
Slide 13
Processes and D li blDeliverables
Process ProductProcess Product
Planning Project Plan
Analysis System Proposal
Design System Specification
Implementation New System and Maintenance Plan
Slide 14
SYSTEM DEVELOPMENTSYSTEM DEVELOPMENTMethodologies
Slide 15
What Is a Methodology?What Is a Methodology?
A formalized approach or series A formalized approach or series of stepsWriting code without a well-thought-out system request thought out system request may work for small programs, but rarely works for large onesbut rarely works for large ones.
Slide 16
St t d D iStructured Design
Projects move methodically Projects move methodically from one to the next stepGenerally, a step is finished before the next one beginsbefore the next one begins
Slide 17
Waterfall Development Method
Slide 18
Pros and Cons of the W t f ll M th dWaterfall Method
Pros Cons
Identifies systems Design must be Identifies systems requirements long before programming begins
Design must be specified on paper before programming beginsbegins begins
Long time between system proposal and system proposal and delivery of new system
Slide 19
P ll l D l tParallel Development
Slide 20
Alternatives to the SDLCAlternatives to the SDLC
Rapid Application Development Rapid Application Development (RAD)Phased DevelopmentPrototypingPrototypingThrow-Away Prototyping
Slide 21
Rapid Application D l tDevelopment
Critical elementsCritical elementsCASE toolsJAD sessionsFourth generation/visualization Fourth generation/visualization programming languagesCode generatorsCode generators
Slide 22
Rapid Application D l t C t iDevelopment Categories
Phased developmentPhased developmentA series of versions
P iPrototypingSystem prototyping
Throw-away prototypingDesign prototypingg p yp g
Agile DevelopmentExtreme DevelopmentSlide 23
Extreme Development
How Prototyping WorksHow Prototyping Works
Slide 24
Throwaway PrototypingThrowaway Prototyping
Slide 25
Selecting the Appropriate M h d lMethodology
Clarity of User RequirementsClarity of User RequirementsFamiliarity with TechnologySystem ComplexitySystem ReliabilitySystem ReliabilityShort Time SchedulesSchedule Visibility
Slide 26
Criteria for Selecting a M h d lMethodology
Slide 27
Project Team Roles and Project Team Roles and Skills
Slide 28
Information Systems Roles
Business analystBusiness analystSystem analystInfrastructure analystChange management analystChange management analystProject managerj g
Slide 29
P j t T R lProject Team Roles
Slide 30
S P t 1Summary -- Part 1
The Systems Development Lifecycleconsists of four stages: Planning, g g,Analysis, Design, and ImplementationThe major development methodologies:
Structured designStructured designthe waterfall methodParallel development
RAD d l tRAD developmentPrototyping (regular and throwaway)
Agile development
Slide 31
g pXP streamline SDLC
S P t 2Summary -- Part 2There are five major team roles: There are five major team roles: business analyst, systems analyst, infrastructure analyst, change
t l t d j t management analyst and project manager.
Slide 32
EOC Q ti Ch t 1EOC Question Chapter 11. Compare and contrast phases, steps, techniques and deliverables.
ib h j h i h d l lif l ( )2. Describe the major phases in the systems development life cycle (SDLC).3. Describe the principal steps in the planning phase. What are the major deliverables4. Describe the principal steps in the analysis phase. What are the major deliverables?5. Describe the principal steps in the design phase. What are the major deliverables?6. Describe the principal steps in the implementation phase. What are the major deliverables?7. What are the roles of a project sponsor and the approval committee?8. What does gradual refinement mean in context of SDLC?9. Compare and contrast process-centered methodologies with data-centered methodologies.10. Compare and contrast structured-design based methodologies in general to RAD-based
methodologies in general.11. Compare and contrast extreme programming and throwaway prototyping.12. Describe the major elements and issues with waterfall development.13. Describe the major elements and issues with parallel development14. Describe the major elements and issues with phased development.15. Describe the major elements and issues with prototyping.16. Describe the major elements and issues with throwaway-prototyping.17. What are the key factors in selecting a methodology?18. What are the major roles on a project team?19. Compare and contrast the role of a systems analyst, business analyst, and infrastructure
analyst.20. Which phase in the SDLC is most important and why?
Slide 33