There is no other two steps calculated by the function point. We start directly from the third step: how to calculate the data complexity!
No now you have to determine those data files. The files are divided into two types in the FPA:
ILF [internal logical file]: It is approved by the user, logically relevant data is fast or control information in internal maintenance, logically related data. The primary intent of the ILF is to save data through several or more basic processing of the application.
Users recognize: Just certified by users and developers. There is no discounted data; for example, the check account in the financial system is an ILF logic: it is to have a logical relationship between the data block, when logic is related. For example: the student's name and age are related. Student information and bank password information do not want to turn an ILF cannot rely on other ILFs. If dependent is dependent, you need to merge two ILFs. An ILF can be calculated by multiple applications as ILF but in the same application, one ILF can only be calculated once
EIF [external input file]: Maintained by other applications. Files referenced by this application. An EIF can be introduced as a multiple application as an EIF, but only one in the same application is applied.
I know what a file we now know how to calculate the complexity of the file. What file is quantified? Here is two concepts: DET, RET
DET [Data Element Type]: Simply said that the properties of the class. For example: the age, name, etc. of the student class. Each field in a RET can be seen into DET. It should be noted that some fields introduced by the reasons for technology implementation are not included. Such as ID field
RET [record element type]: is a class. A subset of an ILF or EIF can be used as a RET. If there is no subset, then an ILF or EIF can be seen as a RET. If a RET also has a RET of the father and child relationship, then the parent RET is not included.
Popular saying: people are an abstract object, teacher and student are example objects. The properties here are: number, name, age; teacher's attributes are: name, age, education; students' properties are: name, age, post dates. Note: The above example is just to understand the people of OOAD for a better item. In fact, since the concept is not the user's identification, it means that there will be no such concept in user needs. So he can't act as an ILF.
It is recognized here: Name, Teacher, Age, Admission Date, because people have two sub-objects of teachers and students. So people cannot count RET. Ret has two teachers, students
Now we consider the complexity of the file, the start is very simple, as long as I determine the ILF, EIF's DET, RET then check the table, the table is the table: -> DET
1 ~ 19 20 ~ 50> = 51 || 1 low low average // 2 ~ 5 low average high RET> 5 average high
