...

So, there could be 20 sessions for User A accessing application Z in a period of 7 days but if that user only accessed the application on day 1 and 5 of that period with 14 sessions occurring on the first day and 6 on the fifth day the User Access Days number will still only be 2. In several graphs this distinction is used to eliminate the risk of skewed numbers and to allow you to make a more balanced decision when it comes to usage numbers.

Design Complexity, Design Complexity

...

score, Design Similarities and Design Insights

Design Complexity is based on the magnitude of design elements and the amount of source code in these elements. The calculation is refined by several considerations like code language type, usage of Reader/Author fields, custom XPages control, etc.

...

Design Insights are combinations of certain patterns occurring in the source code. These combinations are called "Findings" and can be anything from identifying platform dependencies when local DLLs are referenced to understanding if a piece of code interacts with other databases.

Design Complexity Index is score is a categorization of seven levels from "Insignificant" to "Exceptional" that indicate the impact redesigning or migrating the application would have. The Design impact is calculated from three main sources: Complexity, Insights and Similarity.

...