Best Practices for Production Development
This chapter is a general overview that prepares team members to work on production projects. It outlines development tasks and identifies sources of information about InterSystems IRIS® data platform and about enterprise integration. The information in this chapter pertains to all types of production projects.
The goal of any production development project is to connect two or more systems. A production is a specialized package of software and documentation that solves a specific integration problem for an enterprise customer. For an overview, see Introducing Interoperability Productions.
This section describes InterSystems IRIS in terms of the software elements that application developers must create and configure in order to deliver a solution. The next section, “Project Delivery”, summarizes the sequence and outcome of an InterSystems IRIS development project.
The InterSystems IRIS product architecture supports various styles of delivery to the enterprise:
A production might comprise the entire integration solution for an enterprise, or the production can fit into existing solutions — or partial solutions — that are already in place at the enterprise.
A production can replace, upgrade, or add new features to a legacy system as needed, without requiring any part of the legacy system to be removed or changed.
InterSystems IRIS supports incremental development projects, so a development team can choose to advance the boundary between old and new systems as rapidly or as slowly as the enterprise requires.
Many InterSystems IRIS development projects follow a phase sequence similar to this one:
|1||Specification||Specify the requirements for the production.||What must the production be able to do?|
|2||Design||Design the production software.||How must the elements interact?|
|3||Coding||Build the production software.||Are additional elements needed?|
|4||Test||Test the production software.||Does the production satisfy the requirements that you specified?|
|5||Deployment||Install the software in its target location.||Are you prepared to test, design, create, and rework as needed?|
|6||Release||Deliver software and project artifacts.||What will be useful to the system administration team?|
It is a fundamental best practice to read the InterSystems IRIS documentation. Your best starting points are the following books and chapters. Each provides further cross-references:
Introducing Interoperability Productions introduces the terminology and basic concepts.
Developing Productions describes the development tasks.
Configuring Productions describes how to perform the configuration tasks related to creating a production.
Later chapters in this book apply to deploying interface routing solutions. See “Design Model for a Routing Production” and “Converting Interfaces to Production Elements.”
It is also important to understand the platform features of InterSystems IRIS that support productions. A useful starting point is the Orientation Guide for Server-Side Programming.
Helpful background materials include the following:
Other useful development guides include:
Language reference materials include:
For information about system utilities and security, consult the following documents: