The architect determines the interfaces defined by selecting boundaries.
In other words, the interface (or view) also determines how those boundaries will be represented.
In the case of the display of information (information management), what is displayed through access privileges determines how a message is presented
and interpreted by an end user.
In the case of Enterprise Resource Planning (ERP) solutions, boundaries are created by traditional business functions such as HR,
Strategic Ledger, Workflow, Order Entry.
These packaged back-office solutions provide a quick means to jump past competition who were not using automated business ERP systems.
Another example is linking a company's existing ERP solution directly into their supply chain providers via a VPN, or secure socket connection.
Drawing boundaries and/or expanding boundaries can push a company forward in terms of locking into a relationship,
increasing flexibility for the company, or increasing timeliness between two companies or processes.
Architects and package selection
The architect's involvement with package selection includes:
But it does not include:
Package selection through standards, guidelines, and cost/benefit analysis.
Recommendation of package customization, not addressing detailed customization designs.
Focus on internal workings of software packages, but rather the external interfaces
Detailed integration, or specifications for package implementation