Coordinating programming responsibilities
As part of implementing an IBM Sterling® Order Management System service, you,
and your primary Business Partner that serves as your Systems
Integrator, must
determine how your developers and your Systems
Integrator are to coordinate
development efforts to create the code changes and assets for your site.
For instance,
you must determine how each developer is to connect their developer toolkit environment to a shared
source code repository that stores the code for your IBM Sterling Order Management System
service.
Engagement models
If you use one or more Business Partners for implementing and developing code for your IBM Sterling Order Management System service, work with each of your Business Partners to plan how your
programming efforts are to coordinate. If you, and your Business Partners share development
responsibilities, base your environment on one of the following common engagement models.
| Engagement model | Implementer (release 1) |
SaaS extension support (release 1) |
Implementer (release 2) |
SaaS extension support (release 2) |
Notes |
|---|---|---|---|---|---|
| You are the primary implementer for the solution. As the primary implementer, you are responsible for the deliverables or results of the IBM Sterling Order Management System project. | Business Partner A | Business Partner A | Business Partner A | Business Partner A | You arrange all of your developer toolkit environments as you like within your private network. You can then upload your completed deployable artifacts to your repository. |
| You are the primary implementer for the first release and then hand-off implementation responsibilities to the Business Partner that is the primary implementer for the second release. | Business Partner A | Business Partner B | Business Partner B | Business Partner B | You and your Business Partner coordinate how to transfer code. You can work the same as though you are the primary implementer. You can copy and transfer code, or you can use a web-based source and build process and then transfer account ownership. Alternatively, you can have your Business Partner start with a source and build process that is under their control. |
| You are the primary implementer for the second release and take over implementation responsibilities from the Business Partner that is primary implementer of the first release. | Business Partner B | Business Partner A | Business Partner A | Business Partner A | You support code your Business Partner wrote. You and your Business Partner coordinate how to transfer the code. You can work the same as though you are the primary implementer. You can copy and transfer code, or you can use a web-based source and build process and then transfer account ownership. Alternatively, you can have your Business Partner start with a source and build process that is under your control. |
| You are the primary implementer for the first release and hand-off implementation responsibilities to a different developer that is to be the primary implementer for the second release. | Business Partner A | You (or your development team) | You (or your development team) | You (or your development team) | You and another developer coordinate how to transfer the code. You can work the same as though you are the primary implementer. You can copy and transfer code, or you can use a web-based source and build process and then transfer account ownership. Alternatively, you can have the other developer start with a source and build process that is under their control. |
| You are sharing implementation responsibilities for the first release with another developer and then hand-off implementation responsibilities to the other developer. | You (or your development team) and Business Partner A | You (or your development team) | You (or your development team) | You (or your development team) | You and the other developer coordinate how to both contribute to the code repository. You can use a web-based source and build process. Alternatively, you can have the other developer start with a source and build process that is on their network. |