Some concepts on a life-cycle methodology proven to work in real - world BI and DW enterprise system integration projects.

1. LDI Inc.
Methodology and Template
Repository
Service, Integrity, Effectiveness
© December 11th 2008

2. LDI Service, Integrity, Effectiveness Framework Approach
initiate define Leverages
assess
the features
of the
Enterprise
design Architect
maintain Modeling
environment
build
deploy
review test
2

3. Enterprise Architect and modeling business and technology components
3

4. The enterprise component model
Existing
artifacts may
be considered
or substituted
where they are
comprehen -
sive and
current or if
they are not
relevant or not
specifically
included in the
scope or
deliverables, at
all stages of
the
methodology
and project
phases.
4

5. Initiate
•Process: •Product :
• Identify Opportunity • Initial communications
• Determine synergies • Position statements
• Complete proposal and initial • Proposal or Response to
meeting RFP request
• Complete contractual • Master Consulting
documentation agreement signed if not
• Agree terms and objectives already in place
• Create resource plan • Statement of work prepared
• Assemble resources and refined, executed L eader Detefu International Inc.
Statement of Work
Versio n 0.0
[ Date pub lish ed]
• Detail project plans,
Pre sented by :
[P res ent er's na me ]
milestones, deliverables, Microsoft Office
Project Document
responsibility matrix
• Identify resources and set
project kick-off and project
GeneralAccounting.EAP
repository/forums
5

6. Define
•Process: •Product :
• Review existing systems and • Domain model
GeneralAccounting.EAP
structures, understand • Process model
GeneralAccounting.EAP
organization GeneralAccounting.EAP
• Opportunity Definitions
• Carry out a capability and • Formal Requirements GeneralAccounting.EAP
maturity model analysis against • Use Case models GeneralAccounting.EAP
industry benchmarks or identified • Class model for MDM/Meta
specific goals data architecture
GeneralAccounting.EAP
• Identify gaps and determine • User interface strategy
GeneralAccounting.EAP
remediation, tactical and • Technology solution
strategic opportunities Architectural overview GeneralAccounting.EAP
• From opportunities, derive a • Testing Strategy GeneralAccounting.EAP
range of roadmaps and
approaches
• Identify key requirements to
drive the selection of the
appropriate roadmap options
6

7. Assess
•Process: •Product :
• Review with all stakeholders • Mission Statement for
• Gain consensus and sign-off of project(s)
scenario to adopt
• Gain consensus and sign-off of
requirements
• Revise project plan and
resourcing in light of decisions
• Commence change control
mechanism
7

8. Design
•Process: •Product :
• Detail technical design • Implementation model GeneralAccounting.EAP
• Identify, acquire any additional • Technical requirements
hardware and software • Source-target mappings Microsoft Office
Excel 97-2003 Worksheet
• Identify data items • Data Model
• Identify data quality criteria • User Interface design GeneralAccounting.EAP
• Identify Data Governance topics • Change control orders for
• Identify operational items modifications to scope where
• Identify user interface items impact is agreed and
• Determine quality criteria assessed as to be greaterGeneralAccounting.EAP
• Develop test plan and test than ‘minor’, to cover
scenarios additional effort required.
• Monitor and review any change of • Quality assurance model GeneralAccounting.EAP
scope including test cases and
scenarios.
• Issues Log GeneralAccounting.EAP
• Change Log
8

9. Build
•Process: •Product :
• Execute technical requirement • Code
to specifications • Data Objects
• Unit Test • Data Movement
• Control objects
• User Interface objects
• Metadata update objects
• Milestone reviews
9

10. Test
•Process: •Product :
• Execute test plans for all • Test plan records
scenarios • Error logs
• Remediate where necessary • Version control components
• Retest where necessary • Initial data loading
• Sign-off and audit test output • Migration preparation
• Prepare Migration to Production document
protocols
10

11. Review
•Process: •Product :
• Review / Acceptance test of • Development sign-off
system or module
• Sign-off and agreement of
move to production
11

12. Deploy
•Process: •Product :
• Document for operational • Initial communications
support • Deployment checklist
• Run backup routines and
validate
• Instantiate new system or
modules
12

13. Maintain
•Process: •Product :
• Post-Deployment review • Maintenance model
• Backup and disaster recovery • Impact sensitivity model
strategy test
• Capacity and throughput monitoring
and tuning
• Release Planning
• Sunset Planning
• Enhancement request evaluation
• Operations support log review
13

14. Project repository elements
Documentation is entered into the project tool, and may be
exported as word or XMI to other repository management
tools. Sparx Software has a free project viewer, and the
software has a very low base price for implementation on a
corporate-wide basis. Other documents can be generated as
text or rtf/word documents.
14