1 1 1 2 2 3 3 4 4 5 5 Objective Roles Definition Blueprint Structure EA Diagrams IZAZI BA Standards EA Integration to Add-On Roadmap Going Forward Q &

Slides:



Advertisements
Similar presentations
Account Planning The purpose of these slides is to describe the Account Planning Process, the methodology, and the workload involved in running an account.
Advertisements

Building Together One process at a time…. Presented By: Cheryl Harbison, PMP, CBAP IIBA St. Louis Local Chapter Meeting July 30, 2009.
Page 2 Agenda Page 3 History –Blue Print, 2000 –GIS Process 1.2, 2001 (training only) –GIS Process 2.0, (ITIL based - not implemented) –Supply/Demand.
Enterprise Resource Planning
Systems Analysis & IT Project Management Pepper. System Life Cycle BirthDeathDevelopmentProduction.
1 Dr. Djamal Ziani SAP Project Management. 2 ASAP Accelerated SAP (ASAP) is SAP's standard implementation methodology. It contains the Roadmap, a step-by-step.
Fahri BaturOctober 2013 SAP GRC AC ARA Access Risk Analysis Requirements Gathering Workshop.
Steps, Tools, and Techniques
GAI Proprietary Information
6-1 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Chapter 6 Systems Development.
1. Failure is when users do not feel they get what they paid for. 2. Failure is when the overall organization fails to adopt the solution.
University of Southern California Enterprise Wide Information Systems Instructor: Richard W. Vawter.
DFD Using a Case Tool: Visible Analysts Yong Choi BPA CSUB.
Integrating Learning Resources in to a MLE Paul Hudson Learning Technology Development Unit Learning and Information Services University of Hertfordshire.
University of Southern California Enterprise Wide Information Systems Functionality and the Reference Model Instructor: Richard W. Vawter.
METIMEA.ca The Systematic Enterprise: How to synchronize EA, PM and other management methods Alana Boltwood Consultant in Enterprise Architecture, Methodology.
Function Definition  From Investigation to Specification  Defining Functions  The Universal Function Model  Identifying and Documenting Functions.
1004INT Information Systems Week 11 Databases as Business Tools.
Delivery Methodology.
Tech Indira IT Solutions Pvt Ltd
Effort in hours Duration Over Weeks Or Months Inception Launch Web Lifecycle Methodology Maintenance Phases Copyright Wonderlane Studios.
Kris Hicks-Green April 23, 2013 IIBA Austin
Chapter 1 Introduction to Databases
Software Engineering Tutorial. Tutorial objectives  Direct application for the SW engineering activities.  Discuss real software development case studies.
Louisa Lambregts, What Makes a Web Site Successful and Effective? Bottom Line... Site are successful if they meet goals/expectations.
© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 1 August 15th, 2012 BP & IA Team.
Complete and Integrated Lifecycle Management. Challenges 1.
VirtualWorks.
Project Management Process Overview
ERP Lifecycle.
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
SAP Variant Configuration Services. Variant Configuration Services Consulting Implementations Project teams or individual consultants Support Upgrades.
Describing Methodologies PART II Rapid Application Development*
Project Management for RIM Professionals Last Updated: 3/13/2011 Sarina Arcari, PMP VP Implementation & Product Planning Amerigroup Corporation 3/15/11.
Information Services, Griffith University Problem Management Implementation Service Desk Project Phase 2 Project
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
- 1 - Roadmap to Re-aligning the Customer Master with Oracle's TCA Northern California OAUG March 7, 2005.
Chapter 7 Developing a Core Knowledge Framework
RMsis – v Simplify Requirement Management for JIRA.
ISYS 562 Microcomputer Business Applications David Chao.
TEXAS NODAL Board of Directors Austin, Texas July 15, 2003.
普 华 永 道 Phase 1: Project Preparation Phase 1: Project Preparation Phase Overview Phase Overview.
CIP Quality System for Genebank ISO 17025
SmartNets Results Overview SmartNets SmartNets Methods.
OpenVCE Support for the Virtual Collaboration Protocol.
Chapter 15 GIS Design and Implementation Management Information Systems –Systems Analysis –Systems Design –Systems Implementation.
Guide to Requirements Gathering. 2 Contents  What is requirements gathering?  Why requirements gathering is key  Requirements gathering activities.
Evaluate Phase Pertemuan Matakuliah: A0774/Information Technology Capital Budgeting Tahun: 2009.
1)History of water fall model. 2)Features of water fall model. 3)Phase of water fall model. 4)Brief description of phases. 5)Advantages. 6)Disadvantages.
PMO Advisors, LLC PMO Advisor © Release 2.1. The PMO Advisor Portal The PMO Advisor is a gateway to Project Management tools. This portal has two primary.
RMsis – v now with JIRA 5.0 support Simplify Requirement Management for JIRA.
METIS 2011 Workshop Session III – National Implementation of the GSBPM Alice Born and Tim Dunstan Thursday October 6, 2011 Implementation of the GSBPM.
IT platform development of the FNRBA website IAEA Headquarters, Vienna, Austria 25–26 February 2013 M. Youssif Safety and Security Section Department of.
Problem Management for ITSD “Getting to the root of it” Thatcher Deane Feb 28, 2013.
Business and Systems Aligned. Business Empowered. TM Global ERP Projects Author:Andrew McCumiskey Presentation for:University of Birmingham Course: Commercial.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
ROLAND GAREIS Management of the project-oriented Company ® PMUni Project: pm education mature Workshop: Questionnaire Development November 26th, 2007 Esbjerg.
Implementation Overview EOB Methodology John PolichSeptember 2014.
Eyes Wide Open A little about us…..
Data Architecture World Class Operations - Impact Workshop.
Alma at Strathclyde.
Identify the Risk of Not Doing BA
Enterprise Architecture Guide Project at MIT CSG Presentation 9/23/04 Jerry Grochow MIT’s ITAG team sponsored a six week initiative to document the.
ServiceNow Implementation Knowledge Management
THE BUSINESS ANALYSIS PROCESS MODEL
VENDORS, CONSULTANTS AND USERS
IS&T Project Reviews September 9, 2004.
SAP GRC EOH GRC Solutions Divisional divider Option 1.
Compliance Manual Update Staff Requirements Check
Presentation transcript:

Objective Roles Definition Blueprint Structure EA Diagrams IZAZI BA Standards EA Integration to Add-On Roadmap Going Forward Q & A Workshop

All templates will be standardised across all business streams within IZAZI A central repository for all streams to access, thereby no longer creating duplicate or redundant data. Predefined functions and features with a common understanding, preventing any confusion between the client and IZAZI, and within IZAZI team members. A single source of information containing both business and system processes to base project blueprinting on. Initial project start up phase is defined

ProductProject EA EI Add On SOL MAN *Blueprints *Addendum DESIGNDELIVERY UPLOAD FROM EA Business Analysts Functional Consultant

The Business Analyst gathers the requirements from the business. They will deal with the ‘what’ not the ‘how’. The Functional Consultant has an in depth understanding of how the SAP product works and what can be done to achieve the business requirement. They will also have the SAP business specific knowledge

The Business Analyst will be responsible for the final document including sign-off. 1 1

Any queries that the functional consultant has regarding the Blueprint will need to be channelled through the business analyst in order for the functional consultant to complete WRICEF. Any queries with business will need to be resolved by the business analyst, who in return will update the functional consultant

The Business Analyst will be responsible for the final document including sign-off. Any queries that the functional consultant has regarding the Blueprint will need to be channelled through the business analyst in order for the functional consultant to complete WRICEF. Any queries with business will need to be resolved by the business analyst, who in returned will update the functional consultant. The final blueprint document will be handed over from the functional consultant to the business analyst who will then obtain sign-off

Blueprints will be done per a level 4 business process, therefore each level 4 will be a new blueprint For example: Maintain Business Partner 1 1 BABA

Blueprints will be done per a level 4 business process, therefore each level 4 will be a new blueprint For example: Maintain Business Partner Record Each level 4 process will then need to be broken into the level 5 processes and requirements. These requirements will be very detailed and specific to the clients requirements BABA BABA

Blueprints will be done per a level 4 business process, therefore each level 4 will be a new blueprint For example: Maintain Business Partner Record Each level 4 process will then need to be broken into the level 5 processes and requirements. These requirements will be very detailed and specific to the clients requirements. Implementation considerations BABA BABA FCFC

Blueprints will be done per a level 4 business process, therefore each level 4 will be a new blueprint For example: Maintain Business Partner Record Each level 4 process will then need to be broken into the level 5 processes and requirements. These requirements will be very detailed and specific to the clients requirements. Implementation considerations WRICEF BABA BABA FCFC FCFC

Blueprints will be done per a level 4 business process, therefore each level 4 will be a new blueprint For example: Maintain Business Partner Record Each level 4 process will then need to be broken into the level 5 processes and requirements. These requirements will be very detailed and specific to the clients requirements. Implementation considerations WRICEF Glossary BABA BABA BABA FCFC FCFC

13 Requirements Diagram Activity Diagram Class Diagram Business Rules Diagram Fact Diagram Rules Flow Diagram Rules Composer

1 1 Link to EA Standards Document Link to Blueprint Template Link to Generated Blueprint EA Model

1 1 Requirements - Inserts - Updates Processes 2 2

Continual update to the Blueprint and EA standards documents. 1 1

Data mapping between EA and Add-on  EA gaps further requirements  ADD on gaps and further requirements

Continual update to the Blueprint and EA standards documents. Data mapping between EA and Add-on  EA gaps further requirements  ADD on gaps and further requirements Internal training

Continual update to the Blueprint and EA standards documents. Data mapping between EA and Add-on  EA gaps further requirements  ADD on gaps and further requirements Internal training Catch up of existing products into EA by product owners -Functional Catalogue (Level 4 Processes & Requirements) -Blueprint (Level 5 Process & Screen Info)

Continual update to the Blueprint and EA standards documents. Data mapping between EA and Add-on  EA gaps further requirements  ADD on gaps and further requirements Internal training Catch up of existing products into EA by product owners -Functional Catalogue (Level 4 Processes & Requirements) -Blueprint (Level 5 Process & Screen Info) Competent MS word expert on templates

Getting Started Level 5 Activity Diagrams Generate Document