Download presentation
1
Lesson 1 Week01
2
Agenda Course Learning Objectives Introductions Contact: Office Hours
SLATE Lesson notes Weekly outline Course Evaluation Breakdown Textbook Drawing[Modelling] tool Course Learning Objectives This Course and the CP/SA - Program Today: Introduce Object Oriented Analysis & Design © Jerry Kotuba SYST39409-Object Oriented Methodologies
3
© Jerry Kotuba SYST39409-Object Oriented Methodologies
4
Course Learning Outcomes
The objectives, strengths and weaknesses of object-oriented 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 SYST39409-Object Oriented Methodologies
5
Lesson - Learning Outcomes
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 SYST39409-Object Oriented Methodologies
6
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
7
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
8
The Programmer/Analyst as a Business Problem Solver
Analyst background: computer technology, object-oriented 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 SYST39409-Object Oriented Methodologies
9
The Programmer/Analyst’s Approach to Problem Solving
10
Information Systems and Subsystems
11
Information Systems © Jerry Kotuba Information system: collects, processes, stores, and outputs information 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
12
Information Systems and Component Parts
13
The System Boundary versus the Automation Boundary
14
Types of Information Systems
© Jerry Kotuba There are many types of information systems Six common systems are found in most businesses Business systems center around transactions Systems must adapt to changing technology SYST39409-Object Oriented Methodologies
15
Types of Information Systems
16
Required Skills of the Programmer/Systems Analyst
© Jerry Kotuba Manage issues ranging from technical to interpersonal Must commit to lifelong learning How does the Computer Programmer/Systems Analyst Program prepare you? SYST39409-Object Oriented Methodologies
17
Required Skills of the Computer Programmer/Systems Analyst
18
Typical Job Titles and Places of Employment
© Jerry Kotuba Many job titles encompass duties of system 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
19
The Analyst as a System Developer (The Heart of the Course)
© Jerry Kotuba Central theme: planning and executing an information systems project Text organized into four conceptual components SYST39409-Object Oriented Methodologies
20
Part 1: System Development and the Unified Process
© Jerry Kotuba Chapters describe work of Systems Analyst 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
21
Part 2: Business Modeling and the Requirements Discipline
© Jerry Kotuba Chapters detail object-oriented analysis (OOA) Two key OOA concepts Use cases Problem domain classes SYST39409-Object Oriented Methodologies
22
Part 3: The Design Discipline
Chapters cover system design issues Object interactions defined for use cases Advance design models developed © Jerry Kotuba SYST39409-Object Oriented Methodologies
23
Part 4: Implementation, Test, and Deployment Disciplines
© Jerry Kotuba Chapter 13 describes the latter part of the UP Chapter 14 discusses emerging topics and technologies SYST39409-Object Oriented Methodologies
24
Summary Solve business problems with IS technology
© Jerry Kotuba Solve business problems with IS technology 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
25
Summary (continued) Problem solving: understand, design, implement
© Jerry Kotuba 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 SYST39409-Object Oriented Methodologies
26
Summary (continued) Broad skill set: technical, business, people
© Jerry Kotuba Broad skill set: technical, business, people 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
28
The Waterfall Approach to the SDLC
29
Predictive versus adaptive approaches to the SDLC
30
The Spiral Life Cycle Model
31
The Unified Process System Development Life Cycle
32
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
35
Relationships of Models, Tools, and Techniques in a System Development Methodology
36
What is a Model? © Jerry Kotuba
SYST39409-Object Oriented Methodologies A minature A pattern A design Something to be copied Surrounded by them every day!
37
Why build models? © Jerry Kotuba
SYST39409-Object Oriented Methodologies
38
Surface Skeleton Structure Scope Strategy
© Jeff Patton, All rights reserved, Scope Strategy
39
Surface Skeleton Structure Scope Strategy
© Jeff Patton, All rights reserved, Scope Strategy
40
Surface Skeleton Structure Scope Strategy
© Jeff Patton, All rights reserved, Scope Strategy
41
What is UML? © Jerry Kotuba SYST39409-Object Oriented Methodologies
42
The Unified Modeling Language
UML is the industry standard for: Specifying Visualizing Constructing Documenting UML simplifies the process of making a blueprint for construction Website: © Jerry Kotuba SYST39409-Object Oriented Methodologies
43
The Unified Modeling Language
Combination of all diagrams depicts the system as a whole © Jerry Kotuba SYST39409-Object Oriented Methodologies
44
Use Case Diagram © Jerry Kotuba
SYST39409-Object Oriented Methodologies
45
Class Diagram © Jerry Kotuba SYST39409-Object Oriented Methodologies
46
Sequence Diagram © Jerry Kotuba
SYST39409-Object Oriented Methodologies
47
State Chart © Jerry Kotuba SYST39409-Object Oriented Methodologies
48
Tools © Jerry Kotuba SYST39409-Object Oriented Methodologies
49
A Case Tool Repository Contains All Information About the System
50
Techniques © Jerry Kotuba SYST39409-Object Oriented Methodologies
51
T Exercise Hospital Pharmacy System © Jerry Kotuba
SYST39409-Object Oriented Methodologies
52
Your turn… Construct a context diagram… External Entities… People
Organizations Systems Other things outside our system that either provide data to it or draw data from it. © Jerry Kotuba SYST39409-Object Oriented Methodologies
53
For Next Class Read Chapters 1,2 Use Case Diagrams
Narratives Activity Diagrams (work flow) Discuss Assignment No1 © Jerry Kotuba SYST39409-Object Oriented Methodologies
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.