Modules and solution fit

What a module contributes

A module is a reusable part of an application, such as a record-management workflow, form, document process or reporting view. Reuse can provide a starting point, but a module still needs to fit the project’s data, permissions, workflow and integration requirements. Availability and configuration are established for the engagement.

Evaluate the whole workflow

Start with a user outcome, not a catalogue of screens. A request intake module, for example, is useful only when routing, assignment, notification, reporting and access rules support the service being delivered.

• Identify the capability you can reuse and the behavior you need to change.
• Confirm the fields, relationships, validation and record ownership.
• Check integrations, accessibility and required outputs.
• Test how the module behaves alongside the rest of the application.

Keep customization reviewable

Describe the difference between the starting behavior and the required result. Ask which changes are configuration and which require implementation. Include both in the plan, with test cases and an owner. Record any dependency on an external service or customer system.

Security follows the deployed solution

Using a reusable module does not confer a certification or authorization on the resulting application. Review permissions, hosting, data handling and applicable controls for the actual deployed system. Include customized behavior in testing and release approval.