Oracle tools in the Enterprise Architecture world - part 2

Oracle tools in the Enterprise Architecture world - part 2

In April I have kept a presentation about the Oracle tools in the Enterprise Architect world on the Hungarian Oracle User Group (HOUG) conference in the database section. 

Topics of the presentation

• Introduction of the Enterprise Architecture 
• What is EA?
• TOGAF
• Oracle EAF
• Oracle solutions
• Oracle products in the Enterprise Continuum
• OAEF data governance
• Data as a Service place
• Solution for system governance

The first post was talked about the introduction of the EA and TOGAF, OEAF frameworks . This post is the second one which is giving examples for categories of the Enterprise Continuum of TOGAF.  The third one will contain all remaining topices

Oracle tools in the Enterprise Architecture world - part 1

Oracle tools in the Enterprise Architecture world - part 1

In April I have kept a presentation about the Oracle tools in the Enterprise Architect world on the Hungarian Oracle User Group (HOUG) conference in the database section. 

Topics of the original presentation

• Introduction of the Enterprise Architecture 
• What is EA?
• TOGAF
• Oracle EAF
• Oracle solutions
• Oracle products in the Enterprise Continuum
• OAEF data governance
• Data as a Service place
• Solution for system governance

Because of largeness of these topics I have splitted into three post. This blog post will talk about the introduction of the EA. The other two one will give some Oracle solution examples for some EA category. (part 2, part 3)

Useful strategy documents that help in going live

Useful strategy documents - part 4.

Finally I have reached my latest post in the useful strategy document series.

Now I would like to talk about the

• going live procedures
• handover/takeover criterias
• acceptance/goal criterias

Why are they so important? Because they could be the most important documents near the going live milestone. It's very important for both side, for the solution provider as well as for the customer too.
Usually what happens on a project? At the first phase of a project lots of people sit together to plan the whole project, the resources, the timeline, the milestones etc. Once the project team decide when will be the Going Live Date (GLD) then ones modify again the whole project plan to ensure that all design, all implementation, all develop, all test step will be finished until that point. So we plan everything but we usually create plan only from one viewpoint, from the first step viewpoint. What I mention is to create new viewpoints and create plans for these viewpoint then merge all plans into the final project plan.

What are these viewpoints?

• What steps should be done near GLD, how will the project's outcome go into production?
• How will done the takeover, when the solution providers team member give all maintance responsibilites to the customer team members. 
• Who and how will accepted the outcome.

So let's go through them