|
1
|
- The University of Tennessee Space Institute
|
|
2
|
- Craig A. Stevens, PMP
- craigastevens@westbrookstevens.com
- (615) 834-8838
- Cell (615) 414-7736
- Find the POD Cast, Presentation, Paper, and Related Material at
- http://www.westbrookstevens.com/business_intelligence.htm
- Free eBook related to Excellent Management at
- www.geronimostone.com
|
|
3
|
- Linda Erzah, CBAP
- IIBA Greater Atlanta Chapter
- Professional Development
- Jim Bozeman, PMP
Project Manager - Business Intelligence
State of TN - Dept. of Revenue
|
|
4
|
- Change Management Phases
- Compare Change Phases to Systems
- Summary
|
|
5
|
|
|
6
|
|
|
7
|
|
|
8
|
|
|
9
|
|
|
10
|
|
|
11
|
|
|
12
|
- PM
- Different Lifecycle Phases
- Compared to Change Management
- BA
- Lifecycles and Phases
- Compared to PM
- Compared to Change Management
- BI
- Lifecycles and Phases
- Compared to Change Management
|
|
13
|
|
|
14
|
|
|
15
|
|
|
16
|
- The Concept Phase
- The Planning Phase
- The Implementation Phase
- The Closedown Phase
|
|
17
|
- CDEF
- The Concept Phase
- The Design Phase
- The Execute Phase
- The Finish Phase
|
|
18
|
|
|
19
|
|
|
20
|
|
|
21
|
- Feasibility (User Needs)
- Requirements and System Specification
- Design
- Coding/Development (Build)
- Testing
- Implementation (User Product)
- Post-Implementation Review
|
|
22
|
|
|
23
|
|
|
24
|
- Project Life-Cycle Phases & Activities
|
|
25
|
|
|
26
|
|
|
27
|
|
|
28
|
- PM
- Different Lifecycle Phases
- Compared to Change Management
- BA
- Lifecycles and Phases
- Compared to PM
- Compared to Change Management
- BI
- Lifecycles and Phases
- Compared to Change Management
|
|
29
|
- Set of tasks, knowledge, and techniques required to identify business
needs and determine solutions to business problems.
- Solutions often include a systems development component, but may also
consist of process improvement or organizational change.
|
|
30
|
- Distinct from financial analysis, project management, quality assurance,
organizational development, testing, training and documentation
development.
- However, individual BA’s may perform some or all of these related
functions.
|
|
31
|
- Works as a liaison among stakeholders in order to elicit, analyze,
communicate and validate requirements for changes to business processes,
policies and information systems.
- The BA understands business problems and opportunities in the context of
the requirements and recommends solutions that enable the organization
to achieve its goals.
|
|
32
|
- Definitions vary based on the problem domain and methodology that the
Business Analyst works with.
- • Business Requirements
- • User Requirements
- • Functional Requirements
- • Quality of Service Requirements
- • Assumptions and constraints
- • Implementation requirements
|
|
33
|
- Enterprise Analysis - Pre-project or early project activities and
approaches for capturing the necessary view of the business to provide
context to requirements and functional design work for a given
initiative and/or for long term planning.
- Requirement Planning and Management - Defines the resources and tasks
associated with the planning and management of requirements gathering
activities throughout the requirements process.
- Requirement Elicitation - Defines standards and techniques used to
collect the requirements of the system.
- Requirement Communication - Defines the methods, tools and techniques
used to structure the raw data collected during Requirement Elicitation,
identifying gaps in the information and define the capabilities of the
solution, which must be documented.
- Requirement Analysis and Documentation - Collection of activities and
considerations for expressing the output of the requirements analysis
and documentation to a broad and diverse audience.
- Solution Assessment and Validation - Covers tasks necessary to ensure
that the solution meets the stakeholder objectives, is thoroughly
tested, and is implemented smoothly.
|
|
34
|
- Enterprise Analysis - Before
- Requirement Planning and Management - Before
- Requirement Elicitation - Before
- Requirement Communication - Before, During, and After
- Requirement Analysis and Documentation - Before and During
- Solution Assessment and Validation - During and After
|
|
35
|
|
|
36
|
|
|
37
|
|
|
38
|
|
|
39
|
- PM
- Different Lifecycle Phases
- Compared to Change Management
- BA
- Lifecycles and Phases
- Compared to PM
- Compared to Change Management
- BI
- Lifecycles and Phases
- Compared to Change Management
|
|
40
|
- Designing and Implementing BI
Systems
- Using BI to help make decisions
|
|
41
|
- Transaction-process Projects
- been around for almost 50 years.
- specific development life cycles
- Feasibility Study
- Requirements Analysis
- Logical Design
- Physical Design
- Coding
- Testing
- Deployment
|
|
42
|
- Business Requirements Definition
- gathering of the business indicators, aspects, purpose and needs.
Identify the Key Primary Indicators (KPI) driving the business versus
the traditional approach of data-driven requirements. A job for a
Business Analyst.
- Technical Architecture Design
- Detailed Design (user interface, data model, ETL)
- Data Model and ETL Development
- User Interface Development
- User Acceptance Test
- Deployment and Support
- Project Management
|
|
43
|
- Business Requirements Definition
- Technical Architecture Design
- has three factors to consider: business requirements, current technical
environment and planned strategic technical directions, simultaneously.
- Detailed Design (user interface, data model, ETL)
- Data Model and ETL Development
- User Interface Development
- User Acceptance Test
- Deployment and Support
- Project Management
|
|
44
|
- Business Requirements Definition
- Technical Architecture Design
- Detailed Design (user interface, data model, ETL)
- Data Model and ETL Development
- User Interface Development
- User Acceptance Test
- Deployment and Support
- Project Management
|
|
45
|
- Detailed Design (user interface, data model, ETL)
- Identifying the key business processes and dimensionality and mapping
these over time to be sure there are no gaps. This is used to identify the fact
table grain, associated dimensions, attributes and hierarchical drill
paths and facts. Source-to-Target
(or Target-to-Source) Maps are generated.
- the logical data model is defined with relationships between the
entities and from that the physical data model is designed giving the
tables with their primary keys and subsequent indexes.
- Extract – Transform – Load – involves two efforts: initial population
(snapshot) and the refresh (keeping the data warehouse current based
upon a pre-determined frequency.
|
|
46
|
- Business Requirements Definition
- Technical Architecture Design
- Detailed Design (user interface, data model, ETL)
- Data Model and ETL Development
- The structuring / arranging of
the data around the KPI’s (facts) of the business creating dimensions
around them based on the drivers of the business. This includes establishing the
relationships and hierarchical drill paths of the dimensions associated
with the facts, as well as any aggregation deemed appropriate. This allows for the slicing and
dicing of the business
- User Interface Development
- User Acceptance Test
- Deployment and Support
- Project Management
|
|
47
|
- Business Requirements Definition
- Technical Architecture Design
- Detailed Design (user interface, data model, ETL)
- Data Model and ETL Development
- User Interface Development
- Establishing an environment whereby the business users are not
confounded or confronted with technical jargon and issue allowing the
business users to easily obtain the information needed to facilitate
their jobs and decision processes.
This environment includes predefined, prompted reports which can
be easily modified and the capability and training to create ad-hoc
reports if warranted.
- User Acceptance Test
- Deployment and Support
- Project Management
|
|
48
|
- Business Requirements Definition
- Technical Architecture Design
- Detailed Design (user interface, data model, ETL)
- Data Model and ETL Development
- User Interface Development
- User Acceptance Test
- Providing a systematic process to prove concept, design and content to
ensure the business users’ acceptance.
This includes a hands-on process following a user training
course.
- Deployment and Support
- Project Management
|
|
49
|
- Business Requirements Definition
- Technical Architecture Design
- Detailed Design (user interface, data model, ETL)
- Data Model and ETL Development
- User Interface Development
- User Acceptance Test
- Deployment and Support
- The convergence of technology, data, and end (business) user
applications accessible from the business users’ desktop. This includes user education
integrating all aspects of the convergence that must be developed and
delivered. User support,
communication and feedback strategies are to be established before
allowing business users access.
- Project Management
|
|
50
|
- Business Requirements Definition
- Technical Architecture Design
- Detailed Design (user interface, data model, ETL)
- Data Model and ETL Development
- User Interface Development
- User Acceptance Test
- Deployment and Support
- Project Management
- ensures that the Business Dimensional Lifecycle activities remain on
track and in sync with a comprehensive project communication plan to
address all levels of the business community to manage expectations so
as to achieve the ultimate BI goals.
|
|
51
|
|
|
52
|
|
|
53
|
- Designing and Implementing BI
Systems
- Using BI to help make decisions
|
|
54
|
- Using BI is the process of
|
|
55
|
|
|
56
|
- Change Management Phases
- Compare Change Phases to Systems
- Summary
|
Notes
