1. Systems Analysis and Design With UML 2
Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition
Chapter 1: Introduction to Systems Analysis and Design
Alan Dennis, Barbara Wixom, and David Tegarden

2. Copyright John Wiley & Sons, Inc.
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.
Request 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 use only and not for redistribution or resale.
The Publisher assumes no responsibility for errors, omissions, or damages, caused by the use of these programs or from the use of the information contained herein.

3. INTRODUCTION
Chapter 1

4. Key Ideas
Many failed systems were abandoned because analysts tried to build wonderful systems without understanding the organization.
The primarily goal is to create value for the organization.

5. Key Ideas
The systems analyst is a key person analyzing the business, identifying 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 systems.

6. THE SYSTEMS DEVELOPMENT LIFE CYCLE

7. Major Attributes of the Lifecycle
The project
Moves systematically through phases where each phase has a standard set of outputs
Produces project deliverables
Uses deliverables in implementation
Results in actual information system
Uses gradual refinement

8. Project Phases Planning Analysis Design Implementation System delivery
Why build the system?
Analysis
Who, what, when, where will the system be?
Design
How will the system work?
Implementation
System delivery

9. A “Simple” Process for Making Lunch

10. A “Simple” Process for Making Lunch

11. Planning Identifying business value Analyze feasibility
Develop work plan
Staff the project
Control and direct project

12. Analysis
Analysis
Information gathering
Process modeling
Data modeling

13. Design Physical design Architectural design Interface design
Database and file design
Program design

14. Implementation
Construction
Installation

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

16. THE EVOLUTION OF SYSTEM DEVELOPMENT

17. What Is a Methodology? A formalized approach or series of steps
Writing code without a well-thought-out system request may work for small programs, but rarely works for large ones.

18. Structured Design Projects move methodically from one to the next step
Generally, a step is finished before the next one begins

19. Waterfall Development Method

20. Pros and Cons of the Waterfall Method
Identifies systems
requirements long
before programming
begins
Design must be
specified on paper
before programming
begins
Long time between
system proposal and
delivery of new
system

21. Alternatives to the SDLC
Rapid Application Development (RAD)
Phased Development
Prototyping
Throw-Away Prototyping

22. Rapid Application Development
Critical elements
CASE tools
Joint Aplication Design ()JAD sessions
Fourth generation/visualization (Visual Basic) programming languages
Code generators

23. Rapid Application Development Categories
Phased development
A series of versions
Prototyping
System prototyping
Throw-away prototyping
Design prototyping

24. How Prototyping Works

25. Throwaway Prototyping

26. Object-Oriented Analysis and Design
Attempts to balance emphasis on data and process
Uses Unified Modeling Language (UML) for diagramming
Use-case Driven
Architecture Centric
Iterative and Incremental

27. BASIC CHARACTERISTICS OF OBJECT-ORIENTED SYSTEMS

28. Key Elements Classes -- template to define objects
Instances -- specific examples of class members
Objects -- building block of the system
Attributes -- describe data aspects of the object
Methods -- the processes the object can perform
Messages -- instructions sent to or received from other objects

29. A Class and Its Objects Instantiated Objects of the Class Class
PATIENT 1: TOP PACKAGE: PATIENT
-Name = Teresa Marks
-Birthdate = March 16, 1975
-Phone number =
PATIENT
-Name
-Birthdate
-Phone Number
+Insert ()()
+Delete ()()
Attributes
PATIENT 2: TOP PACKAGE: PATIENT
-Name = Mel Bourne
-Birthdate = May 11, 1965
-Phone number =
Methods

30. The Key to Reusability
Information hiding is the principle that only information required to use the object is available outside the object
Encapsulation is the mechanism that combines data and processes in a single object

31. Class Hierarchy

32. Inheritance

33. Polymorphism

34. OBJECT-ORIENTED ANALYSIS AND DESIGN USING UML

35. UML
The full UML provides 9 separate diagramming techniques

36. PROJECT TEAM ROLES AND SKILLS

37. Information Systems Roles
Business analyst
System analyst
Infrastructure analyst
Change management analyst
Project manager

38. Summary -- Part 1
The Systems Development Lifecycle consists of four stages: Planning, Analysis, Design, and Implementation
There are three major development methodologies: the waterfall method, RAD, and the Object-Oriented approach.

39. Summary -- Part 2
There are six major elements in Object-Oriented design: classes, objects, instances, attributes, methods, and messages.
Encapsulation, Inheritance, and Polymorphism are also important object-oriented concepts
There are five major team roles: business analyst, systems analyst, infrastructure analyst, change management analyst and project manager.

40. Expanding the Domain For complete description of UML see: