Business Analysis Sequence Diagrams Chris Russell O2.41

Slides:



Advertisements
Similar presentations
Grid Performance with tkeden A Simple Walkthrough.
Advertisements

Software Engineering-II
Agate Ltd Case Study-Requirments Analysis
© 2010 Bennett, McRobb and Farmer1 Use Case Description Supplementary material to support Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
Use Cases & Requirements Analysis By: Mostafa Elbarbary.
OOAD Using the UML - Use-Case Analysis, v 4.2 Copyright  Rational Software, all rights reserved 1 Interaction Diagrams.
Eva TrosborgSlide no.: 1Requirement Specification Requirement Specification Fall 2005 Agenda Requirement definition through use cases by Eva Trosborg.
03/12/2001 © Bennett, McRobb and Farmer Use Case Diagrams Based on Chapter 6 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and.
IMS1805 Systems Analysis Topic 2: Introduction to some key techniques for systems analysis in IS.
Get Started in 4 Easy Steps!
HOW TO WRITE THE PERFECT GBC REPORT David Harris FCMA, CGMA Management Consultant and Lecturer.
From use cases to classes (in UML). A use case for writing use cases Use case: writing a use case Actors: analyst, client(s) Client identifies and write.
Foundation in Business Analysis
Project Analysis Course ( ) Week 2 Activities.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
CB1004 Modelling Business Systems 71 Modelling Business Systems 7 Systems Methods.
Introduction to Sequence Diagrams
ECE450 Software Engineering II Lecture 4– Object Oriented Analysis part 2.
SE3183 Advance Web Programming Programming Session 2013/2014.
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
 A software application is like a city  Modeling = Architecture  OOP = Civil Engineering  UML Classes = Blueprints of Buildings  UML is a common.
Submitted By: Memon Khurshed (Group Leader) Hamed Abdollahpur
Quick Intro to Business Process Re-engineering Basic Introduction Important notice: –This handout is a much simplified version of three handouts: –11.2.
CS206 System Analysis and Design Note 1 By ChangYu 1 Course Information Lecturer NameCHANG YU Web sitewww.chuhai.edu.hk/changyu/
Sept. 18, 2003CS WPI1 CS 509 Design of Software Systems Lecture #3 Thursday, Sept. 18, 2003.
CALL on the cheap Using services freely available on the Internet.
CPSC 203. Use Case Diagram  A description of a system’s behavior as it responds to a request that originates from outside of that system. Specifies the.
Ist.psu.edu School of Information Sciences and Technology IST 311 – Object-Oriented Design & Software Steven Haynes IST 311 – Class 7 17 January 2006
Use Case Diagrams.
The BGSU Psychology Department uses the SONA system for scheduling research participation.
A Student Guide to Object-Oriented Development
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 3: Outlining Use Cases.
OOAD (part 2) diagrams CSCI577a TAs: Alexey. Outline UML diagrams: – Use case diagrams – Robustness diagrams – Sequence diagrams – Artifacts diagrams.
Research topic here Name Surname Faculty Research Proposal CS10A0862 INTRODUCTION TO RESEARCH METHODS.
HNC Flow Chart 1 IT Systems Analysis and Design SSADM – Design.
Technical Report Writing Dr. Shelley Thomas. Overview Selecting effective report topics Using worksheets to plan projects Developing and proposing project.
Requirements capture: Using UML Use Cases David Millard and Yvonne Howard {dem,
1 Week 5 Software Engineering Fall Term 2015 Marymount University School of Business Administration Professor Suydam.
1 Week 5 Software Engineering Spring Term 2016 Marymount University School of Business Administration Professor Suydam.
COM 117 Introduction to Application Building Introduction to the module Learning outcomes Assessment Lecture on DFDs Practical activity Tutorial activity.
CompSci 280 S Introduction to Software Development
Welcome to M301 P2 Software Systems & their Development
Crisis Commander Mobile App
Writing Technical Proposals
MADAM HAZWANI BINTI RAHMAT
Object-Oriented Analysis & Design
Analisis Bisnis.
BTS430 Systems Analysis and Design using UML
Use case Diagram.
Use case diagrams A use case diagram is UML’s notation for showing the relationships among a set of use cases and actors A use case diagram can help the.
Week 10: Object Modeling (1)Use Case Model
UML Use Case Diagrams.
Rob Gleasure IS4445 Principles of Interaction Design Lecture 8: Use Cases and Storyboarding Rob Gleasure
Behavioral Modeling.
Increasing Student Engagement and Learning in the MLIS Program
Two part course Software Engineering option only!
Technical Instructions
Business Analysis Entity Modelling Chris Russell O2.41
How do we convince people that in programming simplicity and clarity —in short: what mathematicians call "elegance"— are not a dispensable luxury, but.
Business Analysis DFD Levelling Chris Russell O2.41
Software Design Lecture : 15.
Business Analysis Introduction to Classes Chris Russell O2.41
Business Analysis Entity Life History Chris Russell O2.41d
Rob Gleasure IS4445 Principles of Interaction Design Lecture 8: Use Cases and Storyboarding Rob Gleasure
Business Analysis More on Classes Chris Russell O2.41
Systems Analysis and Design I
Business Analysis Good Enough Software Chris Russell O2.41
Software design and architecture
Group Project: Expectation
Determine whether the sequence converges or diverges. {image}
Presentation transcript:

Chris Russell O2.41 02920 41 6431 crussell@cardiffmet.ac.uk Business Analysis Sequence Diagrams Chris Russell O2.41 02920 41 6431 crussell@cardiffmet.ac.uk Lecture BA17 Sequence Diagrams

Lecture BA17 Sequence Diagrams Session schedule Business Analysis Schedule Academic Year 2014-5 Semester 2 Week Topic 1 Introduction 2 Investigate situation: rich picture, context diagrams 3 Consider perspectives: types of participation, CATWOE, Power-Interest, Thomas-Kilmann 4 Analyse needs 1: Use Cases 5 Analyse needs 2: structured techniques 6 Define requirements 1a: SSADM 7 Define requirements 1b: SSADM EASTER 8 Define requirements 2: UML 9 Generic assignment feed-forward and task review 10 Balance good enough software against quality costs; Prioritise requirements 11 Assignment submisison Lecture BA17 Sequence Diagrams

Activities and Paradigms Investigate Situation Consider Perspectives Analyse Needs Define Requirements Socio-technical Rich picture CATWOE Types of participation Thomas-Kilmann Power-Interest X Functional Level 0 diagram Structured techniques DFD, ERM and ELH Object-Oriented Context diagram Use Cases Class and Sequence diagrams Lecture BA17 Sequence Diagrams

Lecture BA17 Sequence Diagrams Client’s use cases Lecture BA17 Sequence Diagrams

Detail of Subscribes address Actor: Client Standard Scenario: The client views the list of subscribers. The client enters their email address. The client selects to subscribe this email address. The client presses a button to submit this information to the System. The client receives the response that their address has been subscribed. Alternative: Invalid address The client receives the response that their address is invalid. Alternative: Address already subscribed The client receives the response that their address has already been subscribed. Lecture BA17 Sequence Diagrams

Lecture BA17 Sequence Diagrams Standard scenario Lecture BA17 Sequence Diagrams

Lecture BA17 Sequence Diagrams Alternative scenario Lecture BA17 Sequence Diagrams

Administrator’s use cases Lecture BA17 Sequence Diagrams

Detail of Calculates moving averages Actor: Administrator Standard Scenario: The administrator views the list of moving averages. The administrator presses a button to calculate the latest moving averages. The administrator receives the response that the moving averages have been added. Alternative: Less than 17 share prices The administrator receives the response that there are insufficient values to calculate the moving averages. Alternative: Less than 2 moving averages The administrator receives the response that there are insufficient values to calculate moving average convergence divergence. Alternative: A crossover has happened The administrator receives a link to email the subscribers. Lecture BA17 Sequence Diagrams

Lecture BA17 Sequence Diagrams Group task Draw sequence diagrams (2 in total) for the standard and alternative scenarios of the Calculates moving averages use case Start with the standard scenario (as should be more straightforward) Lecture BA17 Sequence Diagrams