Definitions Priority terms: Use case User story Scenario Public Health event Participant / Actor Public Health report Public Health Reporting Trigger Data.

Slides:



Advertisements
Similar presentations
Writing Good Use Cases - Instructor Notes
Advertisements

1 Aspects of IEEE P1471 Viewpoints in Unified Modeling Language (UML) Manzur Ashraf, BRAC University Humayra Binte Ali, Dhaka University Md.Mahfuz Ashraf,
Design by Contract.
CPSC 333: Foundations of Software EngineeringJ. Denzinger 2.2. Use Cases: Scenario based requirements modeling Recommended: Booch, Rumbaugh, Jacobson:
PROJECT RISK MANAGEMENT
Analysis Modeling.
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
OASIS Reference Model for Service Oriented Architecture 1.0
Object-Oriented Analysis and Design
Use-case Modeling.
COST G9 - Work group 2 Cadastral science meeting Aalborg, Dk Modeling methodology for real estate transactions Radoš Šumrada Faculty.
© 2005 Prentice Hall4-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Clarke, R. J (2001) S213-02: 1 Multimedia in Organisations BUSS 213 Supplementary 2 Use Cases & Descriptions.
IMS1805 Systems Analysis Topic 3: Doing Analysis (continued from previous weeks)
Analysis Concepts and Principles
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
UML Sequence Diagrams Eileen Kraemer CSE 335 Michigan State University.
Use of epidemiologic methods in disaster management Dr AA Abubakar Dept of Community Medicine Ahmadu Bello University Zaria Nigeria.
Use Case Diagram.
Introduction to Computer Technology
USE Case Model.
System Sequence Diagrams
Use Case What is it?. Basic Definition Of who can do what within a system? TemplateDiagramModelDescription.
CS499 Use Cases References From Alistair Cockburn Writing Effective Use Cases (Book) - Use Case.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
The Next Stage in Analysis: Systems Use Case Diagrams 1 SYS366.
Epidemiology The Basics Only… Adapted with permission from a class presentation developed by Dr. Charles Lynch – University of Iowa, Iowa City.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
1 Object-Oriented Modeling Using UML (2) CS 3331 Fall 2009.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Chapter 9 요구사항 모델링: 시나리오 기반 방법론 Requirements Modeling: Scenario-Based Methods 임현승 강원대학교 Revised from the slides by Roger S. Pressman and Bruce R. Maxim.
UML – Unified Modeling Language Use-Case Diagrams.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Call: Wed, 10/05/11 4-5pm ET Agenda: 4:00 – 4:05 Welcome, Riki Merrick, co-lead [Note: attendance will be taken by livemeeting login] 4:05 – 4:15 Initiative.
Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.
UML-1 3. Capturing Requirements and Use Case Model.
UML-1 8. Capturing Requirements and Use Case Model.
7 Systems Analysis and Design in a Changing World, Fifth Edition.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
A Use Case Primer 1. The Benefits of Use Cases  Compared to traditional methods, use cases are easy to write and to read.  Use cases force the developers.
Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Engineering Lab Use Cases Faculty of Information system Technology.
1 Use Case Diagrams Use Case Actor Use case description Use case realization (Scenario) Use case relationships –Extends –Uses.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Use Case Diagrams.
Using Informatics to Promote Community/Population Health
1 System Analysis and Design Using UML INSTRUCTOR: Jesmin Akhter Lecturer, IIT, JU.
Discovering object interaction. Use case realisation The USE CASE diagram presents an outside view of the system. The functionality of the use case is.
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
Use Case Diagram The purpose is to communicate the system’s functionality and behaviour to the customer or end user. Mainly used for capturing user requirements.
Rational Unified Process Fundamentals Module 3: Disciplines I.
Modelling Class T07 Conceptual Modelling – Behaviour References: –Conceptual Modeling of Information Systems (Chapters 11, 12, 13 and 14)
System Sequence Diagrams Tutorial. Use-Case for Monopoly game Monopoly game Use Case UC1: Play Monopoly Game Scope: Monopoly application Level: user goal.
Requirements Engineering for Web Applications. SR: System Vision Document Written by key stakeholders Written by key stakeholders An executive summary.
HL7 Version 3 Veli BICER. Agenda HL7 Problems with Version 2.x HL7 Models Use Case Model Information Model Interaction Model Message Model.
Requirement engineering & Requirement tasks/Management. 1Prepared By:Jay A.Dave.
UML Course Instructor: Rizwana Noor. Overview  Modeling  What is UML?  Why UML?  UML Diagrams  Use Case  Components  Relationships  Notations.
CCT 333: Imagining the Audience in a Wired World Class 9: Scenarios and Requirements.
1 Software Testing and Quality Assurance Lecture 17 - Test Analysis & Design Models (Chapter 4, A Practical Guide to Testing Object-Oriented Software)
1 BTS330 Visual Modeling. What is Visual Modeling? 2 Copyright © 1997 by Rational Software Corporation Computer System Business Process Order Item Ship.
TA: Shreya Rawal.  A use case is a description of a system’s behavior as it responds to a request that originates from outside of that system (Usually.
Basics of RSA Rational Software Architect. What is RSA? Comprehensive Modeling and Development environment that leverages the Unified Modeling Language.
George Wang, Ph.D. COMP 380/L Lesson 2. Use Case Use cases are a way to capture system functionalities (i.e., functional requirements) Based on use case.
1 Advanced DataBases Unified Modelling Language An Introduction and Use Case Lecture 2 Susan Curtis.
Systems Analysis and Design in a Changing World, Fourth Edition
Chapter 4: Business Process and Functional Modeling, continued
Use Case Modeling - II Lecture # 27.
Software Engineering Furqan Rustam.
Seminar 2 Design of Informatics Systems
Chapter 22 Object-Oriented Systems Analysis and Design and UML
Presentation transcript:

Definitions Priority terms: Use case User story Scenario Public Health event Participant / Actor Public Health report Public Health Reporting Trigger Data element

Use case A written description of steps or actions between users (or actors) and software system, that enable the actor to achieve a goal Example: A provider (EHRsystem) identifies information that needs to be complied into a report and sent to a public health agency, because a certain trigger event has occurred.

User story User Story describes in technology-free terminology the business process that is used by its business actors (people) or technical actors (systems involved in the process) to achieve their goals. The User Story, synonym to the business case, describes WHAT the process does. It is written by users to establish user ownership of requirements and contains the user role, their goal, and their motivation for the functionality.

Scenario One instance of a use case, whether it is primary or alternate path through the use case. The primary or alternate path could be viewed as different user stories. Example: Birth of a baby can trigger several reports to public health agencies

Participant / Actor A term in Unified Modeling Language (UML) that specifies a role played by a user or any other system that interacts with the subject. Actors may represent roles played by human users, systems, external hardware, or other subjects.

Public Health event A risk exposure or occurrence of condition of concern (disease for example) to a public health program because of its impact or potential impact on one or more persons or animals. A public health event and a public health case are related but not synonymous. A public health event is a temporal occurrence that, in epidemiologic terms, is often conceptualized as an interaction or the result of an interaction between agent, host, and environment. A public health case is an observation about the host, i.e., person or animal, in the epidemiologic triad of agent-host environment.

Public Health report A collection of data (information) that describes a PH event is exchanged and is related to the execution of essential public health functions (assessment, policy and assurance). Initial PH report: Type of report that contains the initial (first time) notification about a PH event to a specific PH agency – It could also be called event detection or identification Follow up PH report: Any other type of report related to a PH event after the initial report (need to decide, if corrections to the initial report fall under this or not!) For example a response to a case investigation or an adverse event.

Public Health Reporting Trigger A trigger event is an explicit set of conditions that initiate the transfer of information between actors.

Data element atomic unit of data that has precise meaning or precise semantics. A data element has: An identification such as a data element namedata element name A clear data element definitiondata element definition Optional: One or more representation terms (synonyms)representation terms enumerated values Code (metadata)Code (metadata)