How to count the table maintained manually

There is a table, that is referenced by other modules. But the data in the table is maintained by developer in the database management tool manually rather than any transctional function.

Can we count the table as an ILF, EIF or nothing?

I think it should also be counted as an ILF no matter that developer is directly opearintg through your DBMS interface but the better way is that he should access it throug some Input Screen.

Exactly for what purpose you are using this table i mean there should be some Front End screen which is directly or indirectly effecting contents of this table.

Good query

I would say not only ILF but also CRUD (insert, delete, change, etc) elmentary processes

You can not count an ILF without any CRUD elmentary process (see in CPM). Therefore I would say an ILF with CRUD elmentary processes

I guess he is performing CRUD over it but not though EI but directly through DBMS

Hi, I do not see it as ILF. If we do not have any elementary process to update the ILF, it is not countable.

This message was edited 1 time. Last update was at 08/02/2012 07:08:45

Various applications to be counted use this data

It is user-identifiable from each applications

Hi all
The manual say :
An internal logical file (ILF) is a user recognizable group of logically related
data or control information maintained within the boundary of the application
being measured. The primary intent of an ILF is to hold data maintained
through one or more elementary processes of the application being measured.

An external interface file (EIF) is a user recognizable group of logically
related data or control information, which is referenced by the application
being measured, but which is maintained within the boundary of another
application. The primary intent of an EIF is to hold data referenced through
one or more elementary processes within the boundary of the application
measured. This means an EIF counted for an application must be in an ILF in
another application.

In this case there is no application that maintains the Logical Files, so we cannot consider
the table as a logical file.
Without logical file we can not consider any elementary process to maintain the data.

This manual activities would be perhaps be counted as non functional requirements through the SNAP counting manual released by IFPUF in September 2011.

Best regards

I agree with Glanza, there is no ILF or EIF to count in this situation because the data and the maintenance are not within the boundary of the software being counted or another application boundary.

Carol

I too agree with Carol. This file should not be counted as part of functional size, as it is neither maintained by the application under consideration nor by any other application. Hence this file should not be counted as ILF or EIF.

Hi moeztuerk,

As you said, there is no transaction function to maintain the table, it will not be qualified to be an ILF. Also, CPM says "An EIF counted for an application must be in an ILF in
another application" hence, it's not EIF either.

Regards,
Faisal Shakeel

This message was edited 1 time. Last update was at 04/03/2012 07:32:09

This file could not be counted as part of functional size. The data must be maintained through one or more elementary processes (EI or EO), of the application being measured (ILF) or another application (EIF).
The size of a software product contains three dimensions: functional size, technical size and quality size

Hi psoneira,

thanks for the following statement..

>>The size of a software product contains three dimensions: functional size, technical size and quality size

So the packet forwarding operation becomes simply a task of determining the ... Routing tables may be prepared and maintained manually or dynamically.