How to count Detailed Functionality

This group of Quanter elements contains the functionality of the software application that we have a very detailed description of.

This group is composed of the following subgroups.

  • User interaction.
  • Interaction with other Applications.
  • Internal Batch Processes.
  • Databases.

1.1 User interaction

This subgroup of Quanter elements contains the different functionalities that interact with the user of the application. Understanding as a user a person. For example,entering data, pressing action buttons,… 

This subgroup is composed of the following elements:

  • Data maintenance.
    • Operations related to create, update or delete data of the application. For example, Entering data from a screen.
  • Data query (without performing calculations with the data).
    • Operations with the purpose of extracting data from the application without performing calculations. For example, List of customers extracts the info of the customers as stored into the database.
  • Data query (performing calculations with the data).
    • Operations with the purpose of extracting data from the application performing calculations. For example, Report of customer extract the info of customer calculating the overall sales rate til the moment.
  • Data reception (without performing calculations with the data).
    • Operations with the purpose of receiving information from outside the application without performing calculations. For example, Receiving a file with the list of customers.
  • Data reception (performing calculations with the data).
    • Operations with the purpose of receiving information from outside the application performing calculations. 

1.2 Interaction with other Applications

This subgroup of Quanter elements contains the different functionalities that describe the interaction with other applications (without user intervention). That interaction could be through interfaces, web services, microservices, etc.

This subgroup is composed of the following elements:

  • Data maintenance.
    • Operations related to create, update or delete data of the application. For example, Update of data received in a file from another application.
  • Sending data (without performing calculations with the data).
    • Operations with the purpose of extracting data from the application without performing calculations. For example, Sending out the list of customers as stored into the database.
  • Sending data (performing calculations with the data).
    • Operations with the purpose of extracting data from the application performing calculations. For example, Sending out the report of a customer calculating the overall sales rate till the moment to another application.
  • Sending / Receiving data (without performing calculations with the data).
    • Operations as the precedent but could send and receive information. 
  • Sending / Receiving data (performing calculations with the data).
    • Operations as the precedent but could send and receive information. 

1.3 Internal Batch Processes

This subgroup of Quanter elements contains the different functionalities that describe the internal processes of the application that do not interact with actors outside the system. In other words, they run on a scheduled basis and do not require user action or third-party applications. Internal processes, batch processes, etc.

This subgroup is composed of the following element:

  • Data maintenance.
    • Operations related to create, update or delete data of the application. Could imply calculations and/or other processing. For example, Weekly internal rate regularization process.

1.4 Databases

This subgroup of Quanter elements contains the different functionalities that describe storage needs of the application. One such element will be identified for each “conceptual” entity, from a business user point of view.

This subgroup is composed of the following elements:

  • Internal Business Tables.
    • Business tables that are maintained inside the application (created, updated, deleted, etc. the information of the table). The information could be accessed by the application. For example, Customer information table. 
  • External Business Tables.
    • Business tables that are maintained outside the application but the application access to the information storage inside. For example, Exchange rates table residing in other application.