CRIM log

CRIM stands for configuration, report, integration and modification. Every tailored object gets a line here, so its update and test cost stays visible.

This page applies to the Confirm prototype stage.

IDK templates: IDK-10

Page in the app: /p/{projectId}/r/crim

Life of a CRIM object

You may adopt standard instead, or reject the need. A failed test sends the object back to build.

  1. Identified
  2. Approved for spec
  3. Specified
  4. In build
  5. In test
  6. Accepted
  7. Handed over

How to do it

  1. Try standard first. Meet the need with standard IFS functions when you can.
  2. Specify. Write a functional spec and a test spec before you build.
  3. Check the update effect. Say how an IFS update could break it and how you will retest.

Good to know

  • Each tailored object adds cost at every update. Keep the list short.

Related topics

Based on the IFS Implementation Docs Kit (IDK-01 to IDK-24), described in our own words.

Last updated: