Effort and Cost Estimation Using Cocomo II for "system Maintaining User Access Matrix Data for Perusahaan Xyz"

...

-

Data Management System User Access Matrix

Applications UAM (User Access Matrix ) is designed to enable employees of Company XYZ to manage Data UAM , formerly an employee of XYZ Company still did manage UAM manually in Microsoft Excel , with the application of the UAM web-based is expected to ease the work of employees of XYZ company in terms of Managing UID , adding Role, change the user the old and the new, preview the report tickets , view reports per month , see reports per year , see data UAM as a whole , saw logs admin , manage admin , and manage tables in the database easily and make the data UAM to be more structured . This application is web based with ASP.NET C# and using SQL Server Database.

Specification of software requirements are as follows:

- Managing UID = Can display employee data, do add, update, and delete.

- Conduct Addition Role in Employee.

- UID Replace the old with the new.

- Looking at ticket = view existing tickets and can be filtered by date, user group / ID_User, and may be in exports to MS Excel

- Manage Categories: can view, insert, and delete categories.

- Managing Group: can view, insert, and delete Group.

- Managing Role: can view, insert delete role.

- Looking at monthly review: see ticket by category and by date per month and can be exported to PDF and MS Excel.

- Seeing the annual review: see ticket by category and date annually and can be exported to PDF and MS Excel

- Viewing Data UAM: see all data UAM (User Access Matrix) and can be filtered by group and id_user.

- Saw Logs Admin: see what admin working on the application UAM.

[pic 3]

- Interface of sub-modul Review User Acces Matrix/month

-

METHODOLOGY

This section will explain how the calculation of the UFP and how to get the value of SLOC by UFP will be explained as follows .

-

Identification Function Point

Because this project has been completed, then the function point can be directly counted and identified more accurately without having interviewed the developers of the project. Function Point consists of External Interface, Input, Output, Inquiries, and Internal Logical Files. After counting all the number of Function Point will be calculated effort is needed to make this application. Each function point will have the weight of its own to determine the level of difficulty of the function of the low, average and high. Here are the weights for each value of the function points that are unadjusted.

- Weight of Unadjusted Function Point

Low

Average

High

Inputs

3

4

6

Outputs

4

5

7

Inquiry

3

4

6

ILF

7

10

15

External Interface

5

7

10

In table 1 we can see the weights for each unadjusted function point , the weight value will be multiplied by the number of inputs that have been assessed the level of complexity . example, if there are 3 categories of medium Input , then to get his UFP value then the value 3 will be multiplied by a value of 4 so that its UFP is 12.

-

Calculating SLOC based on UFP

After getting a total value of overall unadjusted function point, then the next value will be multiplied by the total value of a programming language that is used. SLOC calculation using the formula (1) described in the explanation UFP in section 2. The Value of SLOC / UFP can be seen in Figure 1:

[pic 4]

- SLOC/UFP

In Figure 1 we can see a wide variety of a programming language that is used with the value of SLOC / UFP her . In making the application of user access matrix is used where ASP.NET ASP.NET language belongs to the 4th generation programming languages ​​that have a point value of 20 LOC / UFP .

-

Value Effort Multiplier

After getting SLOC value , then the next thing to do is to calculate the value Effort Multiplier , used questionnaire method which would then be filled by the application developer . The form of the question is as follows .

- Question list quisionnaire

No

Questions

Cost Driver

1

How reliability of the software that has been made?

RELY

2

How big is the database contained in the application ?

DATA

3

whether the existing source code can be used again ? / When can be at what level (project , program , product line) ?

RUSE

4

...