Transcript SYST39409 - Sheridan College

Lesson 1
Week01
• Course Learning Objectives
• This Course and the CP/SA - Program
• Today: Introduce Object Oriented Analysis & Design
SYST39409-Object Oriented
Methodologies
• Introductions
• Contact: Office Hours
• SLATE
• Lesson notes
• Weekly outline
• Course Evaluation Breakdown
• Textbook
• Drawing[Modelling] tool
© Jerry Kotuba
Agenda
2
3
SYST39409-Object Oriented
Methodologies
© Jerry Kotuba
SYST39409-Object Oriented
Methodologies
• The objectives, strengths and weaknesses of objectoriented analysis and design methodologies
• The terms and concepts of object-oriented analysis and
design
• Construct from a case study narrative object-oriented model
diagrams and documentation including; use-case diagrams
and narratives, activity, class, state, and sequence
diagrams.
© Jerry Kotuba
Course Learning Outcomes
4
SYST39409-Object Oriented
Methodologies
• What is UML?
• What is modeling?
Why is it important?
How is it used in analysis & design
• How UML and object orientation differ from structured methods
• What are the main components of UML
• Which components of UML will be covered in this course
• Introduce and describe the Unified Modeling (UP) process and
contrast it with the classical Waterfall Methodology
© Jerry Kotuba
Lesson - Learning Outcomes
5
Objectives
• Explain the key role of a systems analyst in business
• Describe the various types of systems an analyst might work on
• Explain the importance of technical, people, and business skills
for an analyst
• Explain why ethical behavior is crucial for a systems analyst’s
career
© Jerry Kotuba
SYST39409-Object Oriented
Methodologies
6
Objectives (continued)
• Describe the many types of technology an analyst needs to
understand
• Describe various job titles and places of employment where
analysis and design work is done
• Discuss the analyst’s role in strategic planning for an
organization
• Describe the analyst’s role in a system development project
© Jerry Kotuba
SYST39409-Object Oriented
Methodologies
7
SYST39409-Object Oriented
Methodologies
• Analyst background: computer technology, objectoriented analysis and design, curiosity
• Chief task: define problem and outline solution
• Challenge: develop alternatives consistent with corporate
strategic
• Develop system requirements and design models
• Systems design models: databases, user interfaces,
networks, operating procedures, conversion plans, and,
software classes
© Jerry Kotuba
The Programmer/Analyst as a
Business Problem Solver
8
The Programmer/Analyst’s Approach to Problem Solving
Information Systems and Subsystems
• Subsystem: components of another system
• Components: hardware, software, inputs, outputs,
data, people, and procedures
• Supersystem: collection of systems
• Automation boundary: separates automated part of
system from manual (human)
SYST39409-Object Oriented
Methodologies
• Information system: collects, processes, stores, and
outputs information
© Jerry Kotuba
Information Systems
11
Information Systems and Component Parts
The System Boundary versus the Automation Boundary
• Six common systems are found in most businesses
• Business systems center around transactions
• Systems must adapt to changing technology
SYST39409-Object Oriented
Methodologies
• There are many types of information systems
© Jerry Kotuba
Types of Information Systems
14
Types of Information Systems
• Must commit to lifelong learning
• How does the Computer Programmer/Systems Analyst Program
prepare you?
SYST39409-Object Oriented
Methodologies
• Manage issues ranging from technical to interpersonal
© Jerry Kotuba
Required Skills of the
Programmer/Systems Analyst
16
Required Skills of the Computer Programmer/Systems Analyst
• Programmer analyst, system liaison, software engineer, Web
developer, Project manager
• Assumptions
• Analysts works on information systems
• Information systems solve business problems
• Work arrangements
• In-house, consultancy, independent contracting, representing
application service provider
SYST39409-Object Oriented
Methodologies
• Many job titles encompass duties of system analyst
© Jerry Kotuba
Typical Job Titles and Places of
Employment
18
• Text organized into four conceptual components
SYST39409-Object Oriented
Methodologies
• Central theme: planning and executing an information systems
project
© Jerry Kotuba
The Analyst as a System Developer
(The Heart of the Course)
19
• Emphasize Unified Process (UP)
• Unified Process defines project phases
• Phases require one or more cycles, or iterations
• Nine disciplines and associated tools complete iterations
SYST39409-Object Oriented
Methodologies
• Chapters 1 - 3 describe work of Systems Analyst
© Jerry Kotuba
Part 1: System Development and
the Unified Process
20
• Two key OOA concepts
• Use cases
• Problem domain classes
SYST39409-Object Oriented
Methodologies
• Chapters 4 - 6 detail object-oriented analysis (OOA)
© Jerry Kotuba
Part 2: Business Modeling and the
Requirements Discipline
21
• Object interactions defined for use cases
• Advance design models developed
SYST39409-Object Oriented
Methodologies
• Chapters 7 - 12 cover system design issues
© Jerry Kotuba
Part 3: The Design Discipline
22
• Chapter 14 discusses emerging topics and technologies
SYST39409-Object Oriented
Methodologies
• Chapter 13 describes the latter part of the UP
© Jerry Kotuba
Part 4: Implementation, Test, and
Deployment Disciplines
23
• Define requirements, design software, write code,
complete extensive testing
• Systems analysis/design: included in many job titles
• Unified Process/Disciplined Agile Development: approach
to system development
• Object-oriented technology: incorporated in Unified
Process
SYST39409-Object Oriented
Methodologies
• Solve business problems with IS technology
© Jerry Kotuba
Summary
24
SYST39409-Object Oriented
Methodologies
Problem solving: understand, design, implement
Writing code just one piece of the puzzle
System: contains set of interrelated components and
outcome
Information systems: generate an information
systems outcome
System types: transaction processing, management
information, executive information, decision
support, communication support, office support
© Jerry Kotuba
Summary (continued)
25
Integrity and ethical behavior: critical to success
Strategic planning: special projects, process
reengineering
Enterprise resource planning: turnkey solution
RMO customer support system project is an
ongoing illustration
SYST39409-Object Oriented
Methodologies
Broad skill set: technical, business, people
© Jerry Kotuba
Summary (continued)
26
The Waterfall Approach to the SDLC
Predictive versus adaptive approaches to the SDLC
The Spiral Life Cycle Model
The Unified Process System Development Life Cycle
DISCIPLINED AGILE DELIVERY [1]
33
[1] Disciplined Agile Delivery (DAD):The Foundation for Scaling Agile, Scott W. Ambler,
2012, IBM Corporation
34
DAD Inception Phase
[1] Disciplined Agile Delivery (DAD):The Foundation for Scaling Agile, Scott W. Ambler,
2012, IBM Corporation
Relationships of Models, Tools, and Techniques in a System
Development Methodology
SYST39409-Object Oriented
Methodologies
© Jerry Kotuba
What is a Model?
36
SYST39409-Object Oriented
Methodologies
© Jerry Kotuba
Why build models?
37
Structure
Scope
© 2006-2007 Jeff Patton, All
rights reserved,
www.agileproductdesign.com
Surface
Skeleton
Strategy
38
Structure
Scope
© 2006-2007 Jeff Patton, All
rights reserved,
www.agileproductdesign.com
Surface
Skeleton
Strategy
39
Structure
Scope
© 2006-2007 Jeff Patton, All
rights reserved,
www.agileproductdesign.com
Surface
Skeleton
Strategy
40
SYST39409-Object Oriented
Methodologies
© Jerry Kotuba
What is UML?
41
•
•
•
•
Specifying
Visualizing
Constructing
Documenting
• UML simplifies the process of making a blueprint for
construction
• Website: http://www.omg.org/
SYST39409-Object Oriented
Methodologies
• UML is the industry standard for:
© Jerry Kotuba
The Unified Modeling Language
42
The Unified Modeling Language
SYST39409-Object Oriented
Methodologies
© Jerry Kotuba
• Combination of all diagrams depicts the system as a whole
43
SYST39409-Object Oriented
Methodologies
© Jerry Kotuba
Use Case Diagram
44
SYST39409-Object Oriented
Methodologies
© Jerry Kotuba
Class Diagram
45
SYST39409-Object Oriented
Methodologies
© Jerry Kotuba
Sequence Diagram
46
SYST39409-Object Oriented
Methodologies
© Jerry Kotuba
State Chart
47
SYST39409-Object Oriented
Methodologies
© Jerry Kotuba
Tools
48
A Case Tool Repository Contains All Information About the System
SYST39409-Object Oriented
Methodologies
© Jerry Kotuba
Techniques
50
Hospital
Pharmacy System
© Jerry Kotuba
Exercise
SYST39409-Object Oriented
Methodologies
T
51
• External Entities…
•
•
•
•
People
Organizations
Systems
Other things outside our system that either provide data to it or draw data
from it.
SYST39409-Object Oriented
Methodologies
• Construct a context diagram…
© Jerry Kotuba
Your turn…
52
• Narratives
• Activity Diagrams (work flow)
• Discuss Assignment No1
SYST39409-Object Oriented
Methodologies
• Read Chapters 1,2
• Use Case Diagrams
© Jerry Kotuba
For Next Class
53