Enterprise Use Cases CCB December 10, 2008. Agenda Enterprise Use Case Status Report Enterprise Use Case Artifacts Enterprise Use Case Development Process.

Slides:



Advertisements
Similar presentations
Adesh Singh, Madhuri Kolhatkar, Jayanth Ananthakrishnan
Advertisements

1 IBM Software Group ® PRJ270: Essentials of Rational Unified Process Module 3: RUP Structure and Navigation.
Gerhard Dueck -- CS3013Capturing Requirements as Use Cases 1 Capturing the Requirements as use Cases  Requirements Description  We need to describe –The.
IBM Business Consulting Services © Copyright IBM Corporation 2006 Unified Process March 27, 2006 Chris Armstrong.
A framework for describing IT Project Management Processes and Tool Set Features Enterprise Project Management Framework.
Knowledge, Skills, and Abilities Working Group Hua Min Jahangheer Shaik Natasha Sefcovic Kahn Aleksey.
1 ECCF Training 2.0 Introduction ECCF Training Working Group January 2011.
SwE 313 Introduction to Rational Unified Process (RUP)
Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared.
December 3, 2010 SAIF Governance Framework A Brief Update on work to date.
Enterprise Architecture
RUP Requirements RUP Artifacts and Deliverables
RUP Fundamentals - Instructor Notes
1 Our Expertise and Commitment – Driving your Success An Introduction to Transformation Offering November 18, 2013 Offices in Boston, New York and Northern.
Copyright © The Open Group 2011 Your Name Your title 44 Montgomery Street Suite 960 San Francisco, CA USA Tel
Business Requirements Using Unified Modeling Language Eric H. Castain, SVP Internet Services Group, Architecture Wells Fargo March 2005.
FLORIDA PUBLIC HURRICANE LOSS MODEL V6.1 Computer Science February 2-4, Dr. Shu-Ching Chen School of Computing and Information Sciences Florida.
Software Engineering Chapter 8 Fall Analysis Extension of use cases, use cases are converted into a more formal description of the system.Extension.
RUP Design RUP Artifacts and Deliverables
Chapter 3 – The Analysis Workflow CSC532: Fall 2003 Original presentation by Joshua Hughes Zehra Raoshan Kiran Balagani Guang Li This presentation will.
Software Engineering Chapter 7 Fall Capturing the Requirements as Use Cases Capturing the Requirements as Use Cases By using use cases analysts.
IBM Software Group ® Overview of SA and RSA Integration John Jessup June 1, 2012 Slides from Kevin Cornell December 2008 Have been reused in this presentation.
Apps.  Understand the list of applications or application components that are required, based on the baseline Application Portfolio, what the requirements.
Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
ANALYSIS - II REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
2 2009/10 Object Oriented Technology 1 Topic 2: Introduction to Object-Oriented Approach Reference: u Ch.16 Current Trends in System Development (Satzinger:
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
1 ECCF Training 2.0 Implemental Perspective (IP) ECCF Training Working Group January 2011.
1 ECCF Training 2.0 Introduction ECCF Training Working Group January 2011.
Identifying & Creating Use Cases – Part 1 Month Day, Year.
Agenda 1. Key Activities, Accomplishments and Status 2. Task Review 3. Meeting Notes and Action Items.
Analysis Yaodong Bi. Introduction to Analysis Purposes of Analysis – Resolve issues related to interference, concurrency, and conflicts among use cases.
18/13/2009 Enterprise Architecture & Standards Setting MnGeo Council - Nonmember 2010.
1 ECCF Training Computationally Independent Model (CIM) ECCF Training Working Group January 2011.
ESSRT In-Process Review September 10, Agenda 1.Work Completed Till Date 2.Scope of future activities and deliverables 2.
CONNECTING COMPONENT Pertemuan Matakuliah: M Analisis dan Perancangan Sistem Informasi Lanjut Tahun:
Next Steps.  Uses a backward planning process:  Scope and Sequence: identifies the appropriate DP competencies and state content standards students.
1 HL7 SAIF Enterprise Conformance and Compliance Framework (ECCF) Overview Baris E. Suzek Bob Freimuth VCDE Monthly Meeting December, 2010.
VA Internal Use Only 1 Product Architecture Recommendation Briefing Template.
California Health and Human Services Agency - Office of Systems Integration (OSI) PMO Forum November 19,
OSLC PLM Workgroup1 Towards detailed use cases and alignment to OSLC V0.1 Gray Bachelor 18 th July 2011.
Systems Analysis and Design in a Changing World, Fourth Edition
Working out the Details
EI Architecture Overview/Current Assessment/Technical Architecture
Rob Cramer – BPM Practice Manager
Data Architecture World Class Operations - Impact Workshop.
Software Configuration Management
Software Engineering Management
EIN 6133 Enterprise Engineering
Project Process Discussion
Project Management Process Overview
The Open Group Architecture Framework (TOGAF)
CIMI Enterprise Architecture Proposal
CMGT 445 Competitive Success/snaptutorial.com
CMGT 445 MASTER Perfect Education/ cmgt445master.com.
CMGT 445 Education for Service/snaptutorial.com
CMGT 445 Teaching Effectively-- snaptutorial.com.
Overview – Processes Overview Purpose Roles & Responsibilities
Website Content Management System
IS&T Project Reviews September 9, 2004.
Project Process Discussion
Software Engineering Management
Product Life cycle (RUP)
Highlights for Readers.
PPT1: Basics of software engineering
Engineering Processes
EA Framework TOGAF is a framework - a detailed method and a set of supporting tools - for developing an enterprise architecture.
On Premise High Availability DR Template
Web Application Diagram Template
Presentation transcript:

Enterprise Use Cases CCB December 10, 2008

Agenda Enterprise Use Case Status Report Enterprise Use Case Artifacts Enterprise Use Case Development Process Next Steps

Use Case Inventory Enterprise Use Case Development Dashboard Legend

Standard enterprise use case package components Each Enterprise Use Case will have a complete Use Case Template detailing the following: 1.0Background - one half to one page summary Overview of the use case Unmet medical/biological needs How this case represents an instance of the new care/research paradigm Listing of the translational "touchpoints" between disciplines 2.0Detailed use case description Relevant actors, classes of data and flows Conventional use case components: Storyboards, Activity Diagrams, Sequence Diagrams 3.0Reusable components and related materials Existing caBIG tools, data sets, etc. that can be utilized to support the use case Non-caBIG tools, data sets, methods, etc. that can be utilized to support the use case 4.0Gap analysis Tools, data, workflows, etc. that are required to fill gaps in the use case Groups within the program and within NCI that would need to participate in use-case realization

How use cases integrate with development and budget decisions Portfolio projects by domain: Maintenance integration points Rearchitecture integration points Current new projects Cutting edge projects Enterprise Use Cases Defined Artifacts Review with community (WS, CDLs, etc.) Legend Associated symbol denotes participation in activity CC-Team CATComposite Architecture Teams WSDomain Workspaces Integration with Enterprise BAM BAM Integration points highlighted Key integration points by WS WS Approve/ Release Budget C Review/Approve Portfolio Prioritization Requirements Document CAT C CAT WS Portfolio Analysis Prioritization of Integration Points Guidelines Goals C CAT WS CAT WS Enterprise Use Case Development Portfolio Analysis and Prioritization

Next Steps December 2008: Roll out use case definition, artifacts and process to workspaces. End December Mid-January 2009: Work with each workspace to build a plan outlining the completion of the use case artifacts for each use case with the workspaces. End January 2009: Prioritize integration points from two current enterprise use cases and work with the CAT to determine portfolio fit and prioritization. Next CCB report mid-January 2009.

Appendix

Appendix Summary Appendix A: Use Case Inventory By Workspace Detailed inventory of workspace use case status, including: Originating workspace Enterprise Business Architecture Model (BAM) integration status Use case artifact development status (artifacts including: use case template, storyboards, actors, activity diagrams, sequence diagrams) Appendix B: Enterprise Use Case Artifacts: Translational Research Use Case (Sample Package) Enterprise Use Case Template Actor Diagram Activity Diagram

Appendix A: Use Case Inventory By Workspace

Enterprise Use Case Template Appendix B: Enterprise Use Case Artifacts: Translational Research Use Case

Actor DiagramActivity Diagram Use case specifications with roles and responsibilities distributed across swim lanes Actors with specified functional roles and responsibilities Appendix B: Enterprise Use Case Artifacts: Translational Research Use Case