This is a presentation about the introduction to system and analysis design. The topic talks about what are the system development life cycle and how it works. It also talks about the professions or the team conducting a study.

1. Chapter 1:
Introduction to System
Analysis and Design

2. Objectives
Understand the fundamental systems development life cycle and its
four phases.
Understand the evolution of systems development methodologies.
Be familiar with the Unified Process and its extensions.
Be familiar with the different roles on the project team.

3. Why Should We Care?
Would you buy a car that only had a 28% chance
of driving off the lot with no problems?

4. Recent Significant IT Failures
Company Year Outcome
Hudson Bay (Canada) 2005 Inventory system problems lead to $33.3
million loss.
UK Inland Revenue 2004/
5
$3.45 billion tax-credit overpayment
caused by software errors.
Avis Europe PLC (UK) 2004 Enterprise resource planning (ERP) system
cancelled after $54.5 million spent.
Ford Motor Co. 2004 Purchasing system abandoned after
deployment costing approximately $400
M
Hewlett-Packard Co. 2004 ERP system problems contribute to $160
million loss.
AT&T Wireless 2004 Customer relations management system
upgrade problems lead to $100M loss

5. Systems development
life cycle

6. Systems Development Life Cycle
Planning
Analysis
Design
Implementation

7. SDLC: Planning
1. Project Initiation
◦ Develop a system request
◦ Conduct a feasibility analysis
2. Project Management
◦ Develop work plan
◦ Staff the project
◦ Control and direct the project
Why should we build this system?

8. SDLC: Analysis
1. Develop analysis strategy
2. Gather requirements
3. Develop a system proposal
What should the system do for us?
Where and when will it be used?

9. SDLC: Design
1. Develop a design strategy
2. Design architecture and interfaces
3. Develop databases and file specifications
4. Develop the program design
How will we build the system?

10. SDLC: Implementation
1. Construct system
2. Install system
◦ Implement a training plan for the users
3. Establish a support plan
Build the system!

11. Putting the SDLC Together
Each phase consists of steps that lead to specific
deliverables
The system evolves through gradual refinement
Once the system is implemented, it may go back into a
planning phase for its next revision, a follow-on system, or
maintenance releases

12. Processes and Deliverables
Process Product
Planning
Analysis
Design
Implementation
Project Plan
System Proposal
System
Specification
New System and
Maintenance Plan

13. Systems development
methodologies

14. Systems Development Methodologies
A methodology is a formalized approach to implementing the SDLC
Well-known methodologies include:
◦ Waterfall development
◦ Parallel development
◦ V-model
◦ Rapid application development
◦ Agile development

15. W a t e r f a l l
T h e W a t e r f a l l S D L C m o d e l i s t h e c l a s s i c
m e t h o d o f d e v e l o p m e n t . A s e a c h p h a s e
c o m p l e t e s , t h e p r o j e c t s p i l l s o v e r i n t o
t h e n e x t s t e p . T h i s i s a t r i e d - a n d - t e s t e d
m o d e l , a n d i t w o r k s . O n e a d v a n t a g e o f
t h e W a t e r f a l l m o d e l i s e a c h p h a s e c a n
b e e v a l u a t e d f o r c o n t i n u i t y a n d
f e a s i b i l i t y b e f o r e m o v i n g o n . I t ’ s l i m i t e d
i n s p e e d , h o w e v e r , s i n c e o n e p h a s e m u s t
f i n i s h b e f o r e a n o t h e r c a n b e g i n .

17. A g i l e
T h e A G I L E m o d e l w a s d e s i g n e d b y
d e v e l o p e r s t o p u t c u s t o m e r n e e d s f i r s t . T h i s
m e t h o d f o c u s e s s t r o n g l y o n u s e r e x p e r i e n c e
a n d i n p u t . T h i s s o l v e s m u c h o f t h e p r o b l e m s
o f o l d e r a p p l i c a t i o n s t h a t w e r e a r c a n e a n d
c u m b e r s o m e t o u s e . P l u s , i t m a k e s t h e
s o f t w a r e h i g h l y r e s p o n s i v e t o c u s t o m e r
f e e d b a c k . A g i l e s e e k s t o r e l e a s e s o f t w a r e
c y c l e s q u i c k l y , t o r e s p o n d t o a c h a n g i n g
m a r k e t . T h i s r e q u i r e s a s t r o n g t e a m w i t h
e x c e l l e n t c o m m u n i c a t i o n . I t c a n a l s o l e a d t o
a p r o j e c t g o i n g o f f - t r a c k b y r e l y i n g t o o
h e a v i l y o n c u s t o m e r f e e d b a c k .

19. I t e r a t i v e
I n t h e I t e r a t i v e d e v e l o p m e n t m o d e l ,
d e v e l o p e r s c r e a t e a n i n i t i a l b a s i c v e r s i o n
o f t h e s o f t w a r e q u i c k l y . T h e n t h e y r e v i e w
a n d i m p r o v e o n t h e a p p l i c a t i o n i n s m a l l
s t e p s ( o r i t e r a t i o n s ) . T h i s a p p r o a c h i s
m o s t o f t e n u s e d i n v e r y l a r g e
a p p l i c a t i o n s . I t c a n g e t a n a p p l i c a t i o n u p
a n d f u n c t i o n a l q u i c k l y t o m e e t a b u s i n e s s
n e e d . H o w e v e r , t h i s p r o c e s s c a n e x c e e d
i t s s c o p e q u i c k l y a n d r i s k s u s i n g
u n p l a n n e d r e s o u r c e s .

21. D e v O p s
T h e D e v O p s s e c u r i t y m o d e l i n c o r p o r a t e s
o p e r a t i o n s – t h e p e o p l e w h o u s e t h e s o f t w a r e
– i n t o t h e d e v e l o p m e n t c y c l e . L i k e A g i l e , t h i s
s e e k s t o i m p r o v e t h e u s a b i l i t y a n d r e l e v a n c e
o f a p p l i c a t i o n s . O n e s i g n i f i c a n t a d v a n t a g e o f
t h i s m o d e l i s t h e f e e d b a c k f r o m a c t u a l
s o f t w a r e u s e r s o n t h e d e s i g n a n d
i m p l e m e n t a t i o n s t e p s . O n e d r a w b a c k i s t h a t i t
r e q u i r e s a c t i v e c o l l a b o r a t i o n a n d
c o m m u n i c a t i o n . T h o s e a d d i t i o n a l c o s t s c a n b e
o f f s e t b y a u t o m a t i n g p a r t s o f t h e d e v e l o p m e n t
p r o c e s s .

23. O t h e r M o d e l s
M a n y o t h e r S D L C m o d e l s a r e e s s e n t i a l l y a
v a r i a n t o f t h e s e c o r e p r o c e s s e s . O r g a n i z a t i o n s
u s e L E A N m a n u f a c t u r i n g p r o c e s s e s f o r s o f t w a r e
d e v e l o p m e n t . V - s h a p e d d e v e l o p m e n t i s a t y p e o f
W a t e r f a l l t h a t i m p l e m e n t s t e s t i n g , v e r i f i c a t i o n ,
a n d v a l i d a t i o n . S p i r a l d e v e l o p m e n t m a y p i c k a n d
c h o o s e m o d e l s f o r e a c h s t e p i n t h e d e v e l o p m e n t
p r o c e s s .
I n a d d i t i o n t o t h e m o d e l s a n d s t a g e s o f
s o f t w a r e d e v e l o p m e n t , t h e r e a r e a f e w o t h e r
h e l p f u l p r a c t i c e s . T h e s e c a n b e a p p l i e d t o
p a r t o r a l l o f t h e d e v e l o p m e n t c y c l e .

24. Object-Oriented Analysis & Design
Attempt to balance emphasis on data and process
Uses Unified Modeling Language (UML)
Characteristics of OOAD:
◦ Use-case Driven
◦ Architecture Centric
◦ Iterative and Incremental

25. The Unified process

26. The Unified Process
A specific methodology that maps out when and how to use the various UML techniques for
object-oriented analysis and design
A two-dimensional process consisting of phases and flows
◦ Phases describe how the system evolves over time
◦ Workflows are collections of tasks that occur throughout the lifecycle, but vary in intensity

27. The Unified Process

28. Unified Process Phases
Inception
Elaboration
Construction
Transition

29. Engineering Workflows
Business modeling
Requirements
Analysis
Design
Implementation
Testing
Deployment

30. Supporting Workflows
Project management
Configuration and change management
Environment
Operations and support*
Infrastructure management*
* Part of the enhanced unified process

31. The unified modeling
language

32. Unified Modeling Language
Provides a common vocabulary of object-oriented terms and diagramming techniques rich
enough to model any systems development project from analysis through implementation
Version 2.0 has 14 diagrams in 2major groups:
◦ Structure diagrams
◦ Behavior diagrams

33. UML Structure Diagrams
Represent the data and static relationships in an information system
◦ Class
◦ Object
◦ Package
◦ Deployment
◦ Component
◦ Composite structure

34. UML Behavior Diagrams
Depict the dynamic relationships among the
instances or objects that represent the business
information system
◦ Activity
◦ Sequence
◦ Communication
◦ Interaction overview
◦ Timing
◦ Behavior state machine
◦ Protocol state machine,
◦ Use-case diagrams

35. Project team roles and
skills

36. Project Team Skills
Project team members are change agents who find ways to improve their organization
A broad range of skills is required, including
◦ Technical
◦ Business
◦ Analytical
◦ Interpersonal
◦ Management
◦ ethical

37. Project Team Roles
Role Responsibilities
Business Analyst Analyzing the key business aspects of the system
Identifying how the system will provide business value
Designing the new business processes and policies
Systems Analyst Identifying how technology can improve business processes
Designing the new business processes
Designing the information system
Ensuring the system conforms to IS standards
Infrastructure Analyst Ensuring the system conforms to infrastructure standards
Identifying infrastructure changes required by the system
Change Management
Analyst
Developing and executing a change management plan
Developing and executing a user training plan
Project Manager Managing the team
Developing and monitoring the project plan
Assigning resources
Serving as the primary point of contact for the project

38. Summary
All systems development projects follow essentially the same process, called the system
development life cycle (SDLC)
System development methodologies are formalized approaches to implementing SDLCs
Object-Oriented Systems Analysis and Design (OOSAD) uses a use-case-driven, architecture-
centric, iterative, and incremental information systems development approach

39. Summary
The Unified Process is a two-dimensional systems development process described with a set of
phases and workflows
The Unified Modeling Language, or UML, is a standard set of diagramming techniques
The project team needs a variety of skills