Databae Instance Usage Strategy

8/10/2019 Databae Instance Usage Strategy

1/11


2/11

Table of Content

1 Purpose.................................................................................................................................. 22 igration Paths To Production................................................................................................2! igration Paths "fter Production............................................................................................2# $ata%ases..............................................................................................................................!

#.1 Patch..................................................................................................................................!#.2 $&'#........................................................................................................................ ......... !#.! P(&P()$......................................................................................................................... ##.# T(*.............................................................................................................................. ..... ##.+ $&'.............................................................................................................................. ..... +#., P(&T&-T.......................................................................................................................... +#. T&-T..................................................................................................................................,#.8 (P................................................................................................................................... ,#.9 *'...................................................................................................................................

#.10 ".................................................................................................................................+ lone (efresh uidelines......................................................................................................, hange Tracer......................................................................................................................8 Testing "pproach.................................................................................................................... 88 Instance 3lo4 hart...............................................................................................................9

Updated: 1/9/08 1


3/11

1 Purpose

The *5 $ata%ase Instance Usage -trategy supports and coordinates custom de6elopment7system testing7 data%ase migration7 user training7 and issue resolution. $ata%ases are usedfor limited purposes %y specific indi6iduals and are refreshed on a regular %asis or atparticular times. igration paths are defined for *5 production support and moduleimplementation.

2 Migration Paths To Production

Production Support

Path: $&'# P(&P()$ P()$

Production Support Small Patch

Path: P"T5 $&'# P(&P()$ P()$

Production Support Large Patch

Path: P"T5 $&'# P(&P()$ P()$"lternate: P"T5 $&' T&-T P()$

Implementation

Path: $&' P(&T&-T T&-T " P()$ P(&P()$* Conversions/CRPs: CNV or CRP (optional)

Fast Track Implementation

Path: $&' T&-T " P()$ P(&P()$* Conversions/CRPs: CNV or CRP (optional)

3 Migration Paths After Production

To ensure consistency7 4ithin the instances7 it is imperati6e all code7 patches7 setups andsta%iliation %e propagated %ac do4n through the %elo4 Production -upport orImplementation paths. (esponsi%ilities are as follo4s: T&5 Team code changes7 3U*Team setups7 $" Team patches.

Implementation

Path: P()$ " T&-T P(&T&-T $&'

Production Support

Path: P()$ P(&P()$ $&'#

Updated: 1/9/08 2


4/11

4 Databases

The *5 Instance Usage -trategy 4ill use ele6en data%ases. &ach data%ase 4ill %e supported%y *5 I/T Technical -upport and utilied %y 6arious indi6iduals to support the se6en migrationpaths.

4.1 Patch

Name: P"T5

Users: $" Team*FUNC Team / TECH Team - Optional

ChangeContro:

(efreshed from P()$ as needed.

* Reres! o P"TCH is o#tsi$e %nstan&e Revie' oar$s overnan&e

Paths: Production -upport ; -mall Patch / Production -upport ;


5/11

4.! P"EP"#D

Name: P(&P()$

Users: P()$ -upport / 3U* Team / T&5 Team / -uperusers / 4s. (efresh re=uest in addition to the #>4cycle 4ill %e re6ie4ed and appro6ed %y the Instance anagement Team.P(&P()$ must %e refreshed in con?unction 4ith $&'#.

Paths: Production -upport / Production -upport ; -mall Patch / Production -upport;


6/11

4.% DE

Name: $&'

Users: T&5 Team

*FUNC Team / +#per#sers - Optional

ChangeContro:

(efreshed from T&-T e6ery 8>4s. (efresh re=uest in addition to the 8>4cycle 4ill %e re6ie4ed and appro6ed %y the Instance anagement Team.

Paths: Implementation / 3ast Trac Implementation

Testing: Unit Testing @ $e6elopment

Notes: $&' is considered the primary instance for unit testing de6elopment andpatches in support of all Implementations.

* +et#ps are perorme$ in ,EV as re#este$ . t!e te&!ni&al team

4.& P"ETEST

Name: P(&T&-T

Users: T&5 Team / 3U* Team / -uper Users /


7/11

4.' TEST

Name: T&-T

Users: T&5 Team / 3U* Team / -uper Users / months. (efresh re=uest in addition to the ,>month cycle 4ill %e re6ie4ed and appro6ed %y the Instance anagementTeam.

Paths: Implementation / 3ast Trac Implementation

Testing: (PAs7 Unit7 -ystem and Integration Testing

Notes: T&-T is considered the primary instance for testing in support of pro?ects onthe Implementation and 3ast Trac Implementation path. This is 4here 4eensure all rollouts are %eing tested together.

T&-T is considered the primary instance for (PAs in support of pro?ects onthe 3ast Trac Implementation path.

4.( )"P

Name: (P

Users: 3U* Team / -uperusers /


8/11

4.* )$

Name: *'

Users: T&5 Team / 3U* Team / -uperusers /


9/11

$ Change Trac%er

Technical and 3unctional users must enter production changes7 as defined %elo47 into hangeTracer. "t this time 4e do not ha6e a re=uirement in place to use change tracer for otherinstances.

Functional Changes

- Concurrent Jobs- Profle Settings- Setups (options)- Descriptive Flexible Fields (DFF)- Personalizations (shared with ech ea!)

Tech Team Changes- Code Changes- For! Changes- "iews- #eports- Personalizations(shared with Functional ea!)

- $or%&ow

& Testing Approach

Testing is a significant part of our instance migration strategy. *5 employs a method ofcontinuous testing to help ensure the system deli6ers functions according to specification andeach group of rollouts is %eing tested together. Test cycles are tied to %usiness re=uirements andsigned off %y %usiness users and I/T. " fe4 o%?ecti6es of our testing cycles are:

'alidating the $etailed usiness $esign -olution

Testing focuses on actual %usiness scenarios and processes

'erifying system configuration and master data

-ystematically testing interfaces7 con6ersions7 enhancements7 and reports &sta%lishing system security %ased on actual 4or roles

Testing proper control criteria for each transaction

'erifying compliance criteria

)ur detailed system testing methodology is made up of se6eral components:

o Unit Testing; 6erifies that indi6idual programs eBecute 4ithout error7 perform 4ithin

set standards and are of good =uality. Unit testing is an iterati6e process that occursduring the system de6elopment effort.

o '(stem Testing; functional testing eBecuted to 6erify that the transactions selected

and/or any configuration performed in )racle and C%olt>onsD 4or to support aspecific %usiness process. " single %usiness process typically spans a num%er oftransactions.

o )ntegration Testing; 6erifies that the appropriate transactions7 %usiness processes7

policies7 procedures7 controls and systems are integrated and performing aseBpected.

o User Acceptance Testing; pro6ides an opportunity for the end>user community to

test and tae o4nership of the designed system7 processes and procedures. -uper

Updated: 1/9/08 8


10/11

users and other identified mem%ers of the organiation conduct this testing so thatthey can 6erify the %usiness is supported.

Updated: 1/9/08 9


11/11

* )nstance +o, Chart

Updated: 1/9/08 10

Databae Instance Usage Strategy

Documents

Transcript of Databae Instance Usage Strategy