Week 2- Lecture 2 Business Processes: What Are They?

Slides:



Advertisements
Similar presentations
10 Software Engineering Foundations of Computer Science ã Cengage Learning.
Advertisements

Software Engineering 2003 Jyrki Nummenmaa 1 A BASIC OO SOFTWARE DEVELOPMENT PROCESS Earlier, we saw a number of different software lifecycle models.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Chapter 4 - Object-Oriented Analysis and Design in a Nutshell1 Chapter 4 Object-Oriented Analysis and Design in a Nutshell.
SYS366 The Last Stage in Analysis: System Use Case Descriptions created through the Use Case Authoring Process.
Lecture 2: Businesses and Business Processes  archaic : purposeful activity : BUSYNESSBUSYNESS  usually commercial or mercantile activity engaged in.
GUIDELINES FOR INFORMATIVE SPEAKING Don’t assume what audience knows Relate the subject directly to the audience Don’t be too technical Avoid abstractions.
IS Terms and Introductory Concepts. Contemplative Questions What is an information system? What is an information system? Why do we care about the difference.
1 Software Testing and Quality Assurance Lecture 14 - Planning for Testing (Chapter 3, A Practical Guide to Testing Object- Oriented Software)
6. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain how events can be used to identify use cases that define requirements.
Lecture 4 Business Use Cases: How to document them 1 SYS366.
IS Terms and Introductory Concepts. Contemplative Questions What is an information system? What is an information system? What is data, information and.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 32 Slide 1 Aspect-oriented Software Development 2.
SYS366 Week 6 - Lecture 1 Business Use Cases: How to Identify them & How to Document them.
The Next Stage in Analysis: Systems Use Case Diagrams 1 SYS366.
1 SYS366 Week 10, Lecture 3 Systems Requirements Gathering: Identifying Operating Requirements.
RST Labs Automatic Synthesis of Program- based Triggers for Intrusion Tolerance Mechanisms C C Michael Reliable Software Technologies.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design.
UML Use Case Diagramming Guidelines. What is UML? The Unified Modeling Language (UML) is a standard language for specifying, visualizing, constructing,
1 SYS366 Business Use Cases and Business Actors: How to Identify Them.
1 SYS366 Lecture - Business Use Cases How to Identify Them.
Conceptual Model or Domain Models Chapter10 Applying UML and pattern.
1 BTS330 Lecture: Businesses and Business Processes.
1 SYS366 Lecture: Businesses and Business Processes.
Identifying needs and establishing requirements Data gathering for requirements.
CSCI-383 Object-Oriented Programming & Design Lecture 12.
Requirements Engineering Requirements Elicitation Overview of Requirements Analysis.
Computer Science 340 Software Design & Testing Software Architecture.
1 SYS366 Business Use Cases. 2 Today Business Use Cases Identifying Stakeholders & Actors.
1 BTS330 Visual Modeling. What is Visual Modeling? 2 Copyright © 1997 by Rational Software Corporation Computer System Business Process Order Item Ship.
1 BTS330 Week 4 - Lecture 1 Businesses and Business Processes.
Chapter 5 – System Modeling Lecture 1 1Chapter 5 System modeling.
Lecture 5d: Systems Use Case Descriptions.  Review  Systems Use Case Descriptions  Systems Use Case Authoring SYS3662.
1 SYS366 More on (Systems) Use Cases. 2 Identifying Actors and Systems Use Cases Requirements Gathering Need to find out what the user requires in the.
Logical Architecture and UML Package Diagrams. The logical architecture is the large-scale organization of the software classes into packages, subsystems,
Slide design: Dr. Mark L. Hornick
CompSci 280 S Introduction to Software Development
CompSci 280 S Introduction to Software Development
Case Study -- Weather system
Software Engineering (CSI 321)
Lecture 2: Business Use Cases and Actors - How to identify them
CSE 374 Programming Concepts & Tools
Designing for people CPSC 481: HCI I.
SOFTWARE DESIGN AND ARCHITECTURE
Object-Oriented Static Modeling of the Banking System - I
The Next Stage in Analysis: Systems Use Case Diagrams
Week 10: Object Modeling (1)Use Case Model
Chapter 8 Analysis & Modeling
The Next Stage in Analysis: Systems Use Case Diagrams
UML dynamic Modeling (Behavior Diagram)
COMP 350: Object Oriented Analysis and Design Lecture 2
Chapter 13 Logical Architecture.
3. Object-oriented Design
Software Engineering Lecture #14.
Starting Design: Logical Architecture and UML Package Diagrams
Chapter 13 Logical Architecture.
CS240: Advanced Programming Concepts
Conceptual Model or Domain Models
CSCI1600: Embedded and Real Time Software
The Basics of Information Systems
Bachelor's degree computer science (21) Programming Exercises Part 3
Software design and architecture
Power BI Streaming Datasets with MS Flow
Instructor: Craig Duckett
Prototype Electronics
Week 8 Lecture 1: Identifying Actors and Activities
Software Requirements
Automating Profitable Growth
The Basics of Information Systems
Software Requirements
Presentation transcript:

Week 2- Lecture 2 Business Processes: What Are They? SYS366 Week 2- Lecture 2 Business Processes: What Are They?

Today Identifying Business Processes In-class exercise 4

Business Process “A combination of organizationally potentially distributed, but technically related activities needed to process a commercial event (for example a lease application form) in a result-oriented fashion.”* OK, what do we all do when this thing happens? * Developing Software with UML by Bernard Oestereich, p. 68.

Business Process “The activities of a business process are usually chronologically and logically related to each other.”* Time is Nature's way of preventing everything from happening all at once. what comes first? what’s next? what must be done sequentially? what can be done in parallel? what can be done independently? * Developing Software with UML by Bernard Oestereich, p. 68.

Business Process “A commercial event is usually triggered by an event (for example receipt of an application form) and has at least one visible domain-specific result (e.g., a contract)”* a customer walks in — sell them something. * Developing Software with UML by Bernard Oestereich, p. 68.

Domain “An area of knowledge or activity characterized by a set of concepts and terminology understood by practitioners in that area.”* * Use Case Modeling by Kurt Bittner and Ian Spence, p. 332.

Business Processes Processes could be an event that the business needs to respond to or it could be an event where the business needs to generate some kind of response back Can include manual as well as automated processes

Today Identifying Business Processes In-class exercise 4

In-class Exercise 4 Now back to your teams! 366ClassExercise4.doc