Togaf

[cha_n]

ya ampun dirimu kenapa harus terjebak sama definisi per kata? ga praktis banget. intinya... coba pahami intinya!
yang disuruh bikin oleh togaf itu matrix pemetaan atau definisi kata?

cari business strategy perusahaan, lebih bagus kalau punya it masterplan.

buat function berdasarkan tugas2 yang ada dalam bisnis (terserah itu didefinisikan sebagai function kek role kek ga penting) contoh diatas ada call center dll
lalu dari strategi bisnis perusahaan akan diketahui juga aplikasi apa yang dibutuhkan.
kalau udah ketemu aplikasi apa aja yang dibutuhkan kita bisa menentukan infrastuktur apa yang diperlukan untuk mendukung aplikasi2 tersebut

[cha_n]

eniwei lihat lagi 2 tabel diatas dua2nya bikin keterangan x axis = function

[Shaka_RDR]

uhm... actually cha_n, ditempat gw, gw perlu ada definisi satu persatu. klo nggak apa yang gw design akan dibantah total.
seperti ini contohnya, klo gw bilang actor pada use case = role pada togaf, maka gw perlu menyertakan link/journal pendukung baru pembahasan bisa dilanjutkan.

http://www.togaf-modeling.org/models...rams-menu.html
System use case diagrams use UML use cases. TOGAF roles and actors are used in place of UML actors. "Component realization" links enable you to express which application components implement which use cases.

[cha_n]

kalau dari tabel itu udah dibilang role = function
silakan soal definisi dicari sendiri ya
yang penting dirimu udah memahami dari mana asal usul togaf.
inget cari business strategy perusahaan.

eniwei tempat mu lucu, minta definisi lengkap tapi fase2 yang dilalui loncat2.

[cha_n]

eh kamu ikut kursus sertifikasi togaf aja. di ui ada.
kalau perusahaan mu niat beneran dapat penilaian togaf yang bisa dipertanggung jawabkan, suruh modal dikit kursus in kamu

[Shaka_RDR]

bisa minta link web soal kursus TOGAF ga chan ? berapa lama kursusnya yah ?

---------- Post Merged at 08:06 PM ----------

The functions and capabilities of activity systems
Business Function as logical Component
In TOGAF, a Business Function is a bounded unit of business capability. It is an
encapsulated component that delivers business services - a container of business
processes (or partial processes) that are logically related, and for which you can define
the skills needed.
Successive composition of elementary functions into composite functions produces a
Business Function hierarchy - a logical composition structure - a structural model akin
to a management hierarchy, but devoid of managers or resources. A bottom-level
Business Function may be a role, which may or may not be supported by IT. If it is a
purely clerical role (does nothing but data processing) then it might be automatable as
a software application.
Organisation unit as physical Component
When you allocate managers and resources to execute the processes of a Business
Function, then you have something new, an Organisation. To make an enterprise
work, you can devise various management hierarchies. You may divide the
Organisation by customer, by location, by product (or indeed by Business Function).
But you still have your logical Business Services, Business Functions and roles,
which should be more stable than the physical Organisation structure.
For more on this topic: http://avancier.co.uk. > Methodology > “Business Architecture Rationalisation”.
Capability conceived as broad Business Function
The idea of defining a Business Function as an organisation-independent unit of a
business is very old. The concept of Capability is a relative newcomer, which has
become fashionable through cross-organisational capability-based planning. But does
the new word add a new concept?
In TOGAF, a Capability is a macro-level Business Function. In the TOGAF meta
model, Capability is not related to other architectural entities - surely because to
connect it would reveal it has all the same relationships as a Business Function.
Capability realised as Organisation
A colleague says: “I think of a Capability as a collection of skills, resources, processes
and systems, brought together from one or more parts of the enterprise or extended
enterprise, to meet a business outcome.”
OK. So you set out to develop an enterprise architecture (EA) Capability. You define
an EA Business Function, along with the processes, skills and roles required. Then, to
realise it, you must add objectives, a budget, a manager, and employees with the skills
needed to play roles and perform processes. So, the result (your managed EA team)
has all the properties you would associate with an Organisation unit.
Capability-based planning is a process that starts with a high-level Business Function,
then extends it for implementation to become an Organisation. The Organisation for a Capability is likely to be cross-organisational. It may also be temporary. But it is still
an Organisation, with all the properties you would expect an Organisation to have.

OK.

kumpulan Logical component membentuk Physical.

Capability = broad Business Function (Logical Component) = Organization (Physical Component).
Dimana Organization Unit =

•A self-contained unit of resources with goals, objectives, and measures. Organization units may include external parties and business partner organizations.
•Example : HR, Corporate Finance, Procurement, Customer Service

maka........................ apakah bisa kita bilang klo :


Role = actor dalam use case = Job desc / Rights didalam app (menyebutkannya itu nggak "mentah2", tapi disesuaikan dengan perannya saat menggunakan aplikasi tersebut)
Function = Job Titles (juga nggak "mentah2" nyebutin job title, tapi disesuaikan dengan fungsi yang dilakukan)
Organization Units = Division/Sub Division ?

[Shaka_RDR]

Sekarang masuk ke Data Architecture

ada 3 metamodel yg mau dibahas dulu

1. Data Entity
An encapsulation of data that is recognized by a business domain expert as a thing. Logical data entities can be tied to applications, repositories, and services and may be structured according to implementation considerations

2. Physical Data Component
A boundary zone that encapsulates related data entities to form a physical location to be held. For example, a purchase order business object, comprising purchase order header and item business object nodes

3. Logical Data Component
A boundary zone that encapsulates related data entities to form a logical location to be held. For example, external procurement information.

[cha_n]

shaka, mau paparan materi kuliahku ga?
aku ambil matkul perancangan infrastuktur ti, pake pendekatan togaf. lumayan buat memahami (dan pastinya bahasa indonesia)

[Shaka_RDR]

mauuuuuuuuuuuuuu... mau.. mau mauuuuu.....
thanks a lot cha_n.
gw download dari mana ? atau mau kirim ke email gw?