Process Automation: focus on imagination and modeling

Slides:



Advertisements
Similar presentations
Week 2 The Object-Oriented Approach to Requirements
Advertisements

XP New Perspectives on Microsoft Excel 2003, Second Edition- Tutorial 8 1 Microsoft Office Excel 2003 Tutorial 8 – Developing an Excel Application.
7M701 1 Activity Diagram. 7M701 2 Example 7M701 3 Activity Diagram: what is it? Describes activities and flows of data or decisions between activities.
Chapter 6 Supporting Processes with ERP Systems Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall 6-1.
Systems Analysis and Design in a Changing World, Fourth Edition
SE 555 Software Requirements & Specification 1 Activity Diagrams.
Slide 10B.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.
1 CS 691z/791z Topics in Software Engineering Chapter 13: Activity Diagrams & Chapter 19: Basic Statecharts [Arlow and Neustadt, 2002] March 8, 2007.
SE-565 Software System Requirements More UML Diagrams.
7M822 UML Sequence Diagrams 5 October 2009.
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 6 - Use cases and activity diagrams Dr.
Chapter 7: The Object-Oriented Approach to Requirements
Financial Information Management Managing Financial Information Critical Thinking Business Process Modeling WINIT Control Structures Homework.
Activity Diagram.
Business Requirements Using Unified Modeling Language Eric H. Castain, SVP Internet Services Group, Architecture Wells Fargo March 2005.
Chapter 8: Modelling Interactions and Behaviour UML Activity Diagram
1 Advanced Software Engineering Association for Computing Machinery High School Competition System Prof: Masoud Sadjadi Fall 2004 First Deliverable By:
Slide 16B.51 © The McGraw-Hill Companies, 2005 Object-Oriented and Classical Software Engineering.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 21. Review ANALYSIS PHASE (OBJECT ORIENTED DESIGN) Functional Modeling – Use case Diagram Description.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 The Analysis Phase System Requirements Models and Modelling of requirements Stakeholders as a source of requirements.
1 Devon M. Simmonds University of North Carolina, Wilmington CSC450 Software Engineering WorkFlow Modeling with Activity Diagrams.
Chapter 12: Design Phase n 12.1 Design and Abstraction n 12.2 Action-Oriented Design n 12.3 Data Flow Analysis n Data Flow Analysis Example n
User Interface Theory & Design Lecture 6a 1.  User interface is everything the end user comes into contact with while using the system  To the user,
Copyright © 2013 Curt Hill UML Unified Modeling Language.
OOA&D - 1© Minder Chen, Models, Views, and Diagrams Use Case Diagrams Use Case Diagrams Use Case Diagrams Scenario Diagrams Scenario Diagrams.
IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.
Object Oriented Analysis & Design & UML (Unified Modeling Language)1 Part VI: Design Continuous Activity Diagams State Diagrams.
Systems Analysis and Design in a Changing World, Fourth Edition
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
Your Trusted Adviser Minimizing Risk Maximizing Your Value Quality Management for Procurement with Vendor Evaluation.
1 Unified Modeling Language Michael K. Wildes University of California, Riverside – Extension Program Presentation 2.
7 Systems Analysis – ITEC 3155 The Object Oriented Approach – Use Cases.
1 7 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 7 The Object-Oriented Approach to Requirements.
UML Activity and Sequence Diagrams David Millard
© Stefano Grazioli - Ask for permission for using/quoting: Stefano Grazioli.
Systems Analysis and Design in a Changing World, Fourth Edition
COMPUTERISED ACCOUNTING USING QUICKBOOKS SOFTWARE
Analysis Classes Unit 5.
Instructor: Dr. Hany H. Ammar
System Design, Implementation and Review
Fundamentals of Information Systems, Sixth Edition
Unified Modeling Language
System Design.
Activity and State Transition Diagram
IS301 – Software Engineering V:
FORMAL SYSTEM DEVELOPMENT METHODOLOGIES
Chapter 8: Modelling Interactions and Behaviour UML Activity Diagram
Online Shopping APP.
UML Activity Diagrams.
Software Engineering Chapter 5 (Part 3) System Modeling Dr.Doaa Sami.
Overview of Business Processes
Click on the Create Student Account Link
Unified Modeling Language
Activity Diagrams.
Dynamic SQL Queries Stefano Grazioli.
Supporting Processes with ERP Systems
Process Automation: From models to code
Loops, Subs, & Functions Stefano Grazioli.
BI and data quality Stefano Grazioli.
Math Talk Which is bigger 24∙6 or 26∙4?.
Loops, Subs, & Functions Stefano Grazioli.
Dynamic SQL Queries Stefano Grazioli.
An Introduction to Embedded Software Architecture and Design
Dynamic SQL Queries Stefano Grazioli.
Chapter 5 Architectural Design.
BI and data quality Stefano Grazioli.
Microsoft Office Excel 2003
Identifying & Creating Use Cases - Part 3
Process Automation: focus on imagination and modeling
Supporting Processes with ERP Systems
Presentation transcript:

Process Automation: focus on imagination and modeling Stefano Grazioli

Critical Thinking Common error: submitting a shortcut Grade fairness is important to me: come and see me EasyMeter 

SAP at Renacer

Process automation Identify the requirements (what needs to be done) Create a description of the business process (how it works) Implement the BP using IT (build it) Business Analyst / Consultant Technical Analyst / Consultant Developer / Consultant

It begins with figuring out what needs to be done User perspective “Use cases” Talk about it Sketch it Show it Dream it Prototype with paper and pencil Hey, I need a financial calculator to compute the interest for my loans…

Then make sure you understand how it works International standard State Diagrams Class Use Case Diagrams State Diagrams Package Use Case Diagrams Activity State Diagrams Sequence Scenario Diagrams Deployment Component Diagrams Collaboration Scenario Diagrams Component Scenario Diagrams Statechart

An Activity Diagram Understand & communicate Reengineer & change Specify software We will use it to describe the homework

An Activity Diagram [Returned goods] [Errors] [OK] RECEIVING A/P Starting point Activity Decision Point End point [Guard] Model guards only if they add value Swimlane Fork Join Actor Merge RECEIVING A/P VENDOR Receive goods Inspect content Return some goods [Returned goods] Receive returns [Errors] Notify Vendor and A/P [OK] Update A/R Accept all goods Update A/P Pay vendor Reconcile Account

A decision has one entry point and multiple exits A join has a single exit point, that is traversed when all the input activities have occurred. A merge has a single exit and is traversed when any one of the input activities occurs. A fork has one entry point and multiple exits to show activities that can be done in parallel A decision has one entry point and multiple exits Can do this or that or this

Homework H3

Activity Diagram H3 - Simple Financial Calculator Principal is <=0 User inputs on spreadsheet: principal, years, and interest rate Alert the user User presses button Year is <1 or >25 Alert the user Principal is missing Alert the user Rate is <= 0 or > 10 Alert the user Year is missing Alert the user Compute formulas, output results Rate is missing Alert the user

H3: Financial Math Functions Interest = Principal * [(1+ Interest Rate) t – 1] "Principal" is the same as "capital" pay attention to the unit of measure!

What Is New In Technology? WINIT What Is New In Technology?

Suggestions Give yourself plenty of time Google is your friend Come and see me.