You are on page 1of 13

TAKLIMAT PENGIRAAN SAIZ

APLIKASI SISTEM
MENGGUNAKAN KAEDAH
FUNCTION POINT ANALYSIS

BAHAGIAN PERUNDINGAN ICT (BPI) MAMPU 1


DATA
FUNCTION

BAHAGIAN PERUNDINGAN ICT (BPI) MAMPU 2


DATA FUNCTION

Data Function
 A data function represents functionality
provided to the user to meet internal and
external data storage requirements.
 Data functions may be identified as:
o Internal Logical File (ILF)
o External Interface File (EIF)

3
INTERNAL LOGICAL FILE (ILF)

DEFINITION

• An 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.

COUNT AS ILF DO NOT COUNT AS ILF

• Temporary files or various iterations of the same file


• Application transaction data such as inventory issue
• Work files
records, employee training records, payroll records,
• Sort files Extract files, or view files,
product sales, customer calls, or user records
• Files introduced because of technology
• Help data maintained within the application
• Copies of the same file
• Edit rules maintained within the application
• Audit or historical data
• Parameter data maintained within the application
• Files maintained by other applications and read or referenced
• Error files and their descriptions maintained within the
only
application 4
• Back-up data
EXTERNAL INTERFACE FILE (EIF)

DEFINITION

• An EIF is a user-recognizable group of logically related data or control information that 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, referenced but not maintained by the
application being measured

COUNT AS EIF DO NOT COUNT AS EIF


• Data received from another application that maintains one
• Application data extracted and read from other
or more ILFs within the application being measured
applications
• Data maintained by the application being measured
• Application security or password data maintained outside
• Temporary files or various iterations of the same file
of the application
• Work files
• Help data maintained outside of the application
• Sort files
• Edit rules maintained outside of the application
• Extract files, or view files, that contain data extracted from
• Parameter data maintained outside of the application
previously counted EIFs prior to display or print 5
• Error files and their descriptions maintained outside of the
• Files introduced because of technology
application
• Audit or historical data
SAMPLE SCENARIO FOR ILF&EIF

STUDENT MANAGEMENT APPLICATION


SCHOLARSHIP MANAGEMENT
APPLICATION

Application STUDENT COURSE


being
measured Reference SCHOLARSHIP

FEE COLLECTION
6
RECORD ELEMENT TYPE (RET)

DEFINITION

• A Record Element Type (RET) is a user-recognizable subgroup of Data Element Types within an ILF or EIF.

COUNT AS RET DO NOT COUNT AS RET


• Count one RET for each data function (by default, each data • Do not count RETs for any data that exists because of
function has one subgroup of DETs to be counted as one RET). technology or methodology (e.g., headers, trailers,
• Count one additional RET for each of the following additional separate text files).
logical subgroups of DETs (within the data function) that contains
more than one DET:
o Associative entity
o Subtype (other than the first subtype)
o Attributive entity
• Assume and count each RET as 1 for every ILF/EIF if the relationship
between entities is still unknown (early stage of SDLC). If the
relationship is known or can be determined, refer next page.
7
ENTITY RELATIONSHIP FOR ILF/EIF&RET

1 ILF/EIF, 2RET 1 ILF/EIF, 1RET 1 ILF/EIF, 1RET

Entiti A Entiti B Entiti C Entiti D

Hubungan A dan B adalah dependent antara satu sama Hubungan C dan D adalah independent antara satu sama lain.
lain. Bilangan adalah sebanyak 1ILF/EIF dan 2 RETs. Bilangan dikira asing iaitu 1ILF dan 1RET bagi setiap entiti berkenaan.

Entity dependent must satisfies both conditions: Entity independent must satisfies the condition below:
 an occurrence of entity B must be linked to an occurrence of  The occurrence and/or deletion of entity C or D can be done in
entity A and of itself without the presence of other entities.
 the deletion of an occurrence of entity B results in the deletion  Is not an extension of entity C
of all related occurrences of entity A
 can be considered as an extension of entity A
8

*rujuk Jadual 110 di 8.4 Pengiraan Saiz Fungsian Sistem Aplikasi di Fasa Analisis KRISA untuk keterangan terperinci.
SAMPLE SCENARIO FOR RET

STUDENT MANAGEMENT APPLICATION


SCHOLARSHIP MANAGEMENT
APPLICATION

STUDENT STUDENT’S COURSE


PARENTS

SCHOLARSHIP

STUDENT’S
PERMANENT &
MAILING ADDRESS FEE
COLLECTION 9
DATA ELEMENT TYPE(DET)

DEFINITION

• A Data Element Type is a unique, user-recognizable, non-repeated attribute/field on the ILF or EIF.

COUNT AS DET

• Count one DET for each unique user-recognizable, non-repeated attribute maintained in or retrieved from the data function
through the execution of an elementary process within the counting scope.

• Count only those DETs being used by the application being measured when two or more applications maintain and/or
reference the same data function. Attributes that are not referenced by the application being measured are not counted.

• Count one DET for each attribute required by the user to establish a relationship with another data function (i.e. keys).

• Review related attributes to determine if they are grouped and counted as a single DET or whether they are counted as
multiple DETs; grouping will depend on how the elementary processes use the attributes within the application.

10
PENENTUAN KOMPONEN DATA FUNGSI

STUDENT MANAGEMENT APPLICATION

STUDENT STUDENT’S ADDRESS COURSE

Student ID Student ID Course ID

Name Mailing Address 1 Course Name

Picture Mailing Address 2 Faculty

E-mail Mailing Address 3 Semester Offered

Phone Number Permanent Address 1 Lecturer Assigned

Permanent Address 2
STUDENT’S PARENTS
Permanent Address 3
Parent ID
FEE COLLECTION
Student ID
Student ID
Parent Name
Collected Fee
Parent’s Phone Number
11
Course ID
Parent’s E-mail
CODE DATA

DEFINITION

• Code Data, sometimes referred to as List Data or Translation Data, provides a list of valid values that a descriptive attribute
may have (i.e. StateID and StateName, AirportCode and AirportName ). Also known sometimes as look-up table.
• Logically, the code and its related description have the same meaning.

COUNTING CODE DATA

• Code Data is not considered part of the functional size, so:

o Do not count Code Data as a logical file.

o Do not count Code Data as RETs or DETs.

o Do not count Code Data as a File Type Referenced (FTR).

o Do not count functions to maintain or view Code Data.


12
EXERCISE

Maklumat Agensi Kerajaan:

13

You might also like