Anjar Priandoyo

Catatan Setiap Hari

Archive for the ‘Science’ Category

Peta Bank di Indonesia

leave a comment »

Menarik, apa yang diucapkan, bisa jadi berbeda dengan apa yang terjadi dilapangan. Percaya boleh, cek harus.

In 2016, BCA overtook DBS Bank of Singapore as Southeast Asia’s biggest lender by value

https://www.cnbcindonesia.com/market/20180727131117-17-25712/aset-turun-rp-5-t-kinerja-bank-dki-kurang-memuaskan (Bank DKI aset 46T, Jun 2018)

https://keuangan.kontan.co.id/news/berikut-20-bank-dengan-aset-terbesar-tanah-air (4 Mei 2018)

https://en.wikipedia.org/wiki/List_of_largest_banks_in_Southeast_Asia

Written by Anjar Priandoyo

Februari 24, 2020 at 10:39 pm

Ditulis dalam Science

ISO Standard

leave a comment »

ISO Standard

Written by Anjar Priandoyo

Februari 8, 2020 at 7:39 am

Ditulis dalam Science

IT Cost Estimation

leave a comment »

IT Cost Estimation is an essential part of project management.

Written by Anjar Priandoyo

Februari 8, 2020 at 4:37 am

Ditulis dalam Science

IFPUG GSC

leave a comment »

The value adjustment factor (VAF) is based on 14 general system characteristics (GSC’s) that rate the general functionality of the application being counted. Each characteristic has associated descriptions that help determine the degrees of influence of the characteristics. The degrees of influence range on a scale of zero to five, from no influence to strong influence. The IFPUG Counting Practices Manual provides detailed evaluation criteria for each of the GSC’S, the table below is intended to provide an overview of each GSC. ref

General System Characteristic

Brief Description

1. Data communications How many communication facilities are there to aid in the transfer or exchange of information with the application or system?
2. Distributed data processing How are distributed data and processing functions handled?
3. Performance Was response time or throughput required by the user?
4. Heavily used configuration How heavily used is the current hardware platform where the application will be executed?
5. Transaction rate How frequently are transactions executed daily, weekly, monthly, etc.?
6. On-Line data entry What percentage of the information is entered On-Line?
7. End-user efficiency Was the application designed for end-user efficiency?
8. On-Line update How many ILF’s are updated by On-Line transaction?
9. Complex processing Does the application have extensive logical or mathematical processing?
10. Reusability Was the application developed to meet one or many user’s needs?
11. Installation ease How difficult is conversion and installation?
12. Operational ease How effective and/or automated are start-up, back-up, and recovery procedures?
13. Multiple sites Was the application specifically designed, developed, and supported to be installed at multiple sites for multiple organizations?
14. Facilitate change Was the application specifically designed, developed, and supported to facilitate change?

Once all the 14 GSC’s have been answered, they should be tabulated using the IFPUG Value Adjustment Equation (VAF)

Written by Anjar Priandoyo

Februari 8, 2020 at 1:14 am

Ditulis dalam Science

Function Point Analysis

leave a comment »

Windows, Office, SAP, Oracle: 100K function points
Linux, Android, Google Search: 10K function points

Written by Anjar Priandoyo

Februari 2, 2020 at 1:29 pm

Ditulis dalam Science

The problem with TOGAF/Enterprise Architecture

leave a comment »

1. There are many vocabularies and terms that is not common or not popular
e.g Business Scenario, Pattern, Building Blocks, View. Even if its popular, some term is defined differently, for example Business Scenario define as business problem description to help define requirements.

Business Scenario: A business scenario is essentially a complete description of a business problem, both in business and in architectural terms, which enables individual requirements to be viewed in relation to one another in the context of the overall problem

2. TOGAF usually describe a term in generic term, but the real meaning is different

E.g Architecture view: representation of a system from the perspective of a related set of concerns. It consists of one or more architecture models of the system.

Architecture view: is used to decribe the concern of stakeholders.

3. The purpose is sometimes unclear (or philosophical)
E.g the purpose of ADM is not to get alignment, but to suit the specific needs of enterprise

E.g the purpose of enterprise architecture is not to create “standard” but to optimise an enterprise into an environment that is responsive to business needs

Written by Anjar Priandoyo

Februari 1, 2020 at 12:51 pm

Ditulis dalam Science

Core Banking: Software Modernization

leave a comment »

I found that there are many articles on software modernization, the idea is simple. Regularly something need to be updated, however there is a risk. Therefore the consulting basically an insurance business ref, ref, ref, ref

Written by Anjar Priandoyo

Februari 1, 2020 at 10:30 am

Ditulis dalam Science