5. Pemodelan Bisnis (Bagian 1)

Transkripsi

1 5. Pemodelan Bisnis (Bagian 1) SIF15001 Analisis dan Perancangan Sistem Informasi Agi Putra Kharisma, S.T., M.T. Genap 2014/2015 Desain slide ini dadaptasi dari University of San Fransisco

2 Unified Process

3 Pemodelan Bisnis Dilakukan sebelum menentukan kebutuhan sistem (system requirements)

4 Pemodelan Bisnis an activity that supports the discovery of system requirements by helping the team perceive the wider business context where the future system will operate (Wazlawick, 2014)

5 Pemodelan Bisnis Pada umumnya, artifak yang dihasilkan tidak terlalu detail

6 Artifak yang dihasilkan Artifak yang dihasilkan dapat berupa teks maupun diagram.

7 Artifak yang dihasilkan Diagram yang umum digunakan adalah business use-case diagram dan business activity diagram. Selain itu, pada kasus tertentu dapat pula berupa state machine diagram.

8 Artifak yang dihasilkan BPMN (Business Process Model and Notation) juga dapat digunakan sebagai alternatif dari UML activity diagram.

9 Tujuan Pemodelan Bisnis (1/4) 1. Understand the structure and dynamics of the target organization in which the software will be used.

10 Tujuan Pemodelan Bisnis (2/4) 2. Understand the current problems of the target organization and identify potential improvements that can be obtained with the software..

11 Tujuan Pemodelan Bisnis (3/4) 3. Assure that clients, users, and the development team share a consistent understanding of the target organization.

12 Tujuan Pemodelan Bisnis (4/4) 4. Derive the requirements that will lead to the desired improvements..

13 Langkah pertama, membuat General View The general view of the system or executive summary is a free format document, where the analyst may report the relevant items she discovered about the system after the initial interviews with the stakeholders. The document usually includes the scope declaration for the project. (Wazlawick, 2014)

14 General View Berisi kurang lebih: Laporan analis tentang sistem dari hasil wawancara awal dengan stakeholder. Lingkup proyek Main deliverable yang akan diterima klien Acceptance criteria yang terukur (telah dikuantifikasi).

15 Contoh (Wazlawick, 2014)

16 Business Use Case Business Use Case dibuat untuk memodelkan perusahaan. Bukan memodelkan sistem perangkat lunak. The business use case model considers the entire company as a system, and the actors may be people, companies, or other organizations that create business or maintain relationships with the business (Kroll and Kruchten, 2003).

17 Business Use Case Business Use Case berisi proses bisnis dengan level abstraksi paling tinggi, sehingga jumlahnya relatif sedikit. Contoh proses bisnis: 1. Selling products 2. Conducting marketing 3. Providing services 4. Solving customer problems dsb

18 Ilustrasi Proses bisnis selling products dapat berisi banyak subproses, diantaranya: registering customers, offering products, sending products, applying discounts...dsb Sub-proses tersebut akan diidentifikasi pada system use cases, jika proses tersebut akan di-otomatisasi.

19 Contoh Notasi Business Use Case

20 Praktek Terbaik Penamaan Use Case (1/7) Tyner Blain, memiliki 7 best practices untuk penamaan use case. 1. Good use case names reflect user goals. Good Generate invoice Cancel invoice Pay invoice Bad Access system Open main window Invoice

21 Praktek Terbaik Penamaan Use Case (2/7) 2. Good use case names are as short as possible. Good Not Good Collect late payment Collect late payment from customers that are past due

22 Praktek Terbaik Penamaan Use Case (3/7) 3. Good use case names use meaningful verbs. Good Separate ordered items for dispatch Not Good Process order

23 Praktek Terbaik Penamaan Use Case (4/7) 4. Good use case names use active voice. Good Not Good Pay for order The order is paid

24 Praktek Terbaik Penamaan Use Case (5/7) 5. Good use case names use present tense. Good Not Good Create New Account New Account Was Created

25 Praktek Terbaik Penamaan Use Case (6/7) 6. Good use case names do not identify the actor. Good Bad Create sales report Manager creates sales report

26 Praktek Terbaik Penamaan Use Case (7/7) 7. Good use case names are consistent. Good Produce reservations report Produce sales report Bad Generate sales report Produce reservations report ATAU Generate reservations report Generate sales report

27 Business Actors & Business Workers 1. Business Actors: People, organizations, or even systems that perform some activities belonging to the process, but which are not part of the target company. That is, they are not under company control. 2. Business Workers: People, organizations, or even systems that perform some activities belonging to the process and that are part of the target company. They could be the company s employees, its departments, or even existing software systems belonging to the company.

28 Mengapa Jenis Aktor Dibedakan? This differentiation is important because business actors usually cannot be automated, that is, they will not be replaced by computational systems. However, business workers roles can possibly be replaced by automatic systems (English, 2007).

29 Contoh Notasi Business Actor & Business Worker (Wazlawick, 2014)

30 Contoh Business Use-Case Toko Buku Fiktif (Wazlawick, 2014)

31 Peluang Otomatisasi (Wazlawick, 2014)

32 Role vs Person There is no one-to-one equivalence between a role and a person: a person may perform many roles and a role may be performed by many different people. (Wazlawick, 2014)

33 Versi Perbaikan Dari Diagram Sebelumnya Setelah Keputusan Otomatisasi Pada Role Clerk Aktor dipecah menjadi dua karena hanya sebagian role-nya yang dapat diotomatisasi. (Wazlawick, 2014)