.NET Function Point Configuration - 1.1

Compatibility: v2 v3 Express
What's new? Release Notes
ID: com.castsoftware.dotnet.config.tcc

What’s new?

Introducing a brand-new extension dedicated to entry/exit definitions. In order to get accurate transactions with specific definition of entry/exit points and to avoid duplication across extensions.

This simplifies some transactions’ call graph, by removing:

  • Entry/end points property on objects
  • classes, methods, functions, interfaces objects that are not actual entry/end points

Example of simplification in a transaction

(Examples from Java, but it’s similar for .Net)

Entry point: on the right, the newly calculated transaction, with 2 nodes removed. The entry point is identified more precisely. deleted-entry-points-before-after

End point: on the right, the newly calculated transaction, with 2 nodes removed, and 3 methods whose end points have been deleted. Only the actual End point remains. deleted-end-points-before-after

Names of deleted packages and objects

  • Entry points

    Deleted definition Extension with new modelisation
    System.Net (C#) REST Service Calls for .NET
    Xamarin.Forms (VB, C#) .NET XAML

  • End points

    Deleted definition Extension with new modelisation
    Microsoft.Practices.EnterpriseLibrary (C#) MS Enterprise Library Framework
    SQLite (C#) ADO.NET
    System.Data (C#) ADO.NET
    System.Data.Common (C#) ADO.NET
    System.Data.Entity.DbContext (C#) .NET Entity Framework
    System.Net (C#) REST Service Calls for .NET

Description

This extension defines entry/end points to compute Automated Function Points (ISO/IEC 19515). This is also used to create CAST Imaging Blueprint.

It will be installed automatically as a dependency of .NET Analyzer version ≥ 1.5.6-funcrel.

Transactions

Transaction support is derived from metamodel concepts used to build CAST Imaging Blueprint and structural transaction flows. Entry Points start transactions; Exit Points include both output/boundary concepts and Data Entities manipulated by transactions.

Role Support Breakdown
Entry Point No direct concept type details
Exit Point
  • Communication - FTP
  • Communication - I/O
  • Communication - LDAP
  • Communication - Mail
  • Communication - Messaging
  • System - Gateway
  • Toolkit - Reporting

Data version: 1.1.0-funcrel

ISO 5055 Structural Rules

Quality support is based on ISO 5055 structural rules available for the selected extension version. Counts are grouped by ISO 5055 characteristic.

Reliability Maintainability Security Performance Efficiency

Data version: 1.1.0-funcrel

Supported releases

.NET Analyzer Supported
≥ 1.5.6-funcrel ✅

Download and installation instructions

This extension will be downloaded and installed automatically when .NET Analyzer version ≥ 1.5.6-funcrel is installed.