This is a classic External Inquiry (EQ). The primary intent is to present data (transaction history) retrieved from internal logical files (the account ILF) to a user through a processing logic that contains no derived data or mathematical calculations—it’s a simple retrieval and display of stored data. EIs and EOs involve processing that alters the behavior of the system (e.g., updating data, creating new derived data), which is not the case here.

According to the CPM, when an elementary process (like this fee override EI) maintains (creates, updates, or deletes) data in more than one Internal Logical File (ILF), it is still counted as a single EI. The creation of the audit log entry is a consequence of the same triggering event and is part of the same transactional function. It is not counted separately unless it is triggered by a separate, distinct business event.

The key distinguishing characteristic between an EO and an EQ is the intent of the processing logic. An EQ’s primary intent is to present data retrieved directly from storage. An EO’s primary intent includes additional processing beyond simple retrieval: it must contain derived data (like calculated averages and percentages) or maintain an ILF. Since this report creates significant derived data not stored elsewhere, it qualifies as an EO.

Classification depends on the context of the count (the application boundary). For the application that maintains the User Profile (updates password, preferences, and the last login timestamp), it is an ILF. For a separate, external application that only reads this data (e.g., for authentication), the same data group is an EIF. A data group’s classification is not inherent; it’s defined by its relationship to the application being measured.

This is an External Inquiry (EQ). The primary intent is to present data (article titles/authors) from internal storage. The fact that it is automated and emailed does not change its fundamental classification. Since the processing involves no derivation of new data (it’s a simple retrieval and list) and does not alter system behavior, it meets the criteria for an EQ. The triggering event (a daily schedule) is still a valid event for an EQ.

The CPM states that an elementary process is the smallest unit of activity that is meaningful to the user. Here, the user’s single intent is to ‘request a license.’ All subsequent steps (validation, creation, budget update, notification) are part of fulfilling that single business event. Therefore, it is counted as one External Input (EI), provided all the data maintenance (updating the budget ILF, creating the license ILF record) is within the boundary of the application being measured.

For complexity assessment of an EI, the File Types Referenced (FTR) count includes every Internal Logical File (ILF) maintained (created, updated, or deleted) AND every ILF or External Interface File (EIF) that is only read during the process. In this case, the ‘Customer’ ILF is maintained (counted once). If the process reads a ‘States’ EIF or ILF to validate the state code in the address, that file is also referenced and must be counted.

The primary intent of this process is to maintain (update) an Internal Logical File—the user’s profile data that stores their favorite restaurants. The act of toggling the status is an update to stored data. This fits the definition of an External Input (EI). The change to the UI icon is a consequence of the update, not a separate output transaction.

The complexity of a transactional function (EI, EO, EQ) is determined by two factors: 1) the number of File Types Referenced (FTRs) and 2) the number of Data Element Types (DETs). For this EI, the key driver is the FTR count. We must identify how many ILFs are involved: the ‘Book Copy’ ILF (updated), the ‘Borrower Account’ ILF (updated with fine), and likely the ‘Book Title’ ILF (updated copy count). This FTR count places the EI in a specific complexity range (Low, Average, High).

This is a classic External Inquiry (EQ). The primary intent is to present data (transaction history) retrieved from internal logical files (the account ILF) to a user through a processing logic that contains no derived data or mathematical calculations—it’s a simple retrieval and display of stored data. EIs and EOs involve processing that alters the behavior of the system (e.g., updating data, creating new derived data), which is not the case here.0