1 Pertemuan 26 Review Project Matakuliah: H0204/ Rekayasa Sistem Komputer Tahun: 2005 Versi: v0 / Revisi 1.

Slides:



Advertisements
Similar presentations
1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >
Advertisements

Pertemuan 13 Threads Matakuliah: H0483 / Network Programming Tahun: 2005 Versi: 1.0.
1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >
1 Pertemuan 16 First & Second Conditionals Matakuliah: G0134 – Grammar III Tahun: 2005 Versi: revisi 1.
Internetworking Pertemuan 07 Matakuliah: H0484/Jaringan Komputer Tahun: 2007.
1 Pertemuan 12 Binary Search Tree Matakuliah: T0026/Struktur Data Tahun: 2005 Versi: 1/1.
Arsitektur Jaringan Pertemuan 09 Matakuliah: H0484/Jaringan Komputer Tahun: 2007.
1 Pertemuan 17 Jaringan LAN (Local Area Network) Matakuliah: H0174/Jaringan Komputer Tahun: 2006 Versi: 1/0.
1 Pertemuan 04 Proxy/Cache Matakuliah: H0491/Praktikum Jaringan Komputer Tahun: 2005 Versi: 1/0.
1 Pertemuan 22 Radix Sort Matakuliah: T0016/Algoritma dan Pemrograman Tahun: 2005 Versi: versi 2.
1 Pertemuan 15 The Business Owner’s View Matakuliah: A0194/Pengendalian Rekayasa Ulang Informasi Tahun: 2005 Versi: 1/5.
1 Pertemuan 6 Elementary UDP Sockets Matakuliah: H0483 / Network Programming Tahun: 2005 Versi: 1.0.
12 - Organisation Matakuliah: G0622/Bahasa Inggris 1 Tahun: 2005 Versi: 1.01.
Session 5 JavaScript/JScript: Control Structures II Matakuliah: M0114/Web Based Programming Tahun: 2005 Versi: 5.
Pertemuan 10 Cara mengelola Sumber Daya Teknologi secara baik Matakuliah: H0402/PENGELOLAAN SISTEM KOMPUTER Tahun: 2005 Versi: 1/0.
1 Pertemuan 10 Arsitektur Jaringan Model OSI Matakuliah: H0174/Jaringan Komputer Tahun: 2006 Versi: 1/0.
1 Pertemuan 23 Object database design (Lanjutan bagian 2) Matakuliah: M0174/OBJECT ORIENTED DATABASE Tahun: 2005 Versi: 1/0.
1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >
1 Pertemuan 19 Layer Network Matakuliah: H0174/Jaringan Komputer Tahun: 2006 Versi: 1/0.
1 Pertemuan 07 Pendugaan Parameter Matakuliah: I0262 – Statistik Probabilitas Tahun: 2007 Versi: Revisi.
1 Pertemuan 13 BACK PROPAGATION Matakuliah: H0434/Jaringan Syaraf Tiruan Tahun: 2005 Versi: 1.
1 Pertemuan 17 Audit Performance Matakuliah:A0274/Pengelolaan Fungsi Audit Sistem Informasi Tahun: 2005 Versi: 1/1.
1 Pertemuan 09 Design and Production Matakuliah: T0553/Sistem Multimedia Tahun: 2005 Versi: 5.
1 Pertemuan 21 Internetworking Matakuliah: H0174/Jaringan Komputer Tahun: 2006 Versi: 1/0.
1 Pertemuan 15 ADAPTIVE RESONANCE THEORY Matakuliah: H0434/Jaringan Syaraf Tiruan Tahun: 2005 Versi: 1.
1 Pertemuan 02 LAN Matakuliah: H0451/Praktikum Jaringan Komputer Tahun: 2006 Versi: 1/0.
1 Pertemuan 20 Binomial Heap Matakuliah: T0026/Struktur Data Tahun: 2005 Versi: 1/1.
1 Pertemuan 14 Object Query Language (Lanjutan bagian 1) Matakuliah: M0174/OBJECT ORIENTED DATABASE Tahun: 2005 Versi: 1/0.
1 Pertemuan 5 The structure part of object data model Matakuliah: M0174/OBJECT ORIENTED DATABASE Tahun: 2005 Versi: 1/0.
07 - Advertising Matakuliah: G0622/Bahasa Inggris 1 Tahun: 2005 Versi: 1.01.
1 Pertemuan 9 Making an outline Matakuliah: G1072 – Reading 1 Tahun: 2005 Versi: revisi 0.
Teknik Routing Pertemuan 20 Matakuliah: H0484/Jaringan Komputer Tahun: 2007.
03 - Globalisation Matakuliah: G0622/Bahasa Inggris 1 Tahun: 2005 Versi: 1.01.
1 Pertemuan 21 Parallelism and Superscalar Matakuliah: H0344/Organisasi dan Arsitektur Komputer Tahun: 2005 Versi: 1/1.
1 Pertemuan 7 Scanning Matakuliah: G1072 Reading 1 Tahun: 2005 Versi: revisi 0.
1 Pertemuan 21 Audit Reporting Matakuliah:A0274/Pengelolaan Fungsi Audit Sistem Informasi Tahun: 2005 Versi: 1/1.
1 Pertemuan 11 QUIZ Matakuliah: J0274/Akuntansi Manajemen Tahun: 2005 Versi: 01/00.
11 - Innovation Matakuliah: G0622/Bahasa Inggris 1 Tahun: 2005 Versi: 1.01.
1 Pertemuan 1 Pendahuluan : Konsep Sistem Matakuliah: H0204/ Rekayasa Sistem Komputer Tahun: 2005 Versi: v0 / Revisi 1.
1 Pertemuan 06 Sebaran Penarikan Contoh Matakuliah: I0272 – Statistik Probabilitas Tahun: 2005 Versi: Revisi.
1 Pertemuan 02 Visual Basic Environment and Control Matakuliah: D0524 / Algoritma dan Pemrograman Komputer Tahun: 2005 Versi:
1 Pertemuan 20 Time & Condition Clauses with Future reference Matakuliah: G0134 – Grammar III Tahun: 2005 Versi: revisi 1.
Transport Layer Pertemuan 24 Matakuliah: H0484/Jaringan Komputer Tahun: 2007.
1 Pertemuan 09 Database Matakuliah: D0524 / Algoritma dan Pemrograman Komputer Tahun: 2005 Versi:
1 Pertemuan 18 I wish, If only Matakuliah: G0134 – Grammar III Tahun: 2005 Versi: revisi 1.
1 Pertemuan 7 The Object Definition Language Matakuliah: M0174/OBJECT ORIENTED DATABASE Tahun: 2005 Versi: 1/0.
1 Pertemuan 5 Bisnis Proses Matakuliah: H0472 / Konsep Sistem Informasi Tahun: 2006 Versi: 1.
1 Pertemuan 09 Model Fungsional Matakuliah: H0372/Manajemen Jaringan Tahun: 2005 Versi: 1/0.
1 Pertemuan 09 Pengujian Hipotesis 2 Matakuliah: I0272 – Statistik Probabilitas Tahun: 2005 Versi: Revisi.
1 Pertemuan #3 Clocks and Realtime Matakuliah: H0232/Sistem Waktu Nyata Tahun: 2005 Versi: 1/5.
1 Pertemuan 9 JARINGAN LEARNING VECTOR QUANTIZATION Matakuliah: H0434/Jaringan Syaraf Tiruan Tahun: 2005 Versi: 1.
1 Pertemuan 08 Pengujian Hipotesis 1 Matakuliah: I0272 – Statistik Probabilitas Tahun: 2005 Versi: Revisi.
1 Pertemuan 25 Making It Happen Matakuliah: A0194/Pengendalian Rekayasa Ulang Informasi Tahun: 2005 Versi: 1/5.
1 Pertemuan 18 HOPFIELD DESIGN Matakuliah: H0434/Jaringan Syaraf Tiruan Tahun: 2005 Versi: 1.
1 Pertemuan 8 The Object Definition Language (Lanjutan) Matakuliah: M0174/OBJECT ORIENTED DATABASE Tahun: 2005 Versi: 1/0.
1 Pertemuan 23 Normalisasi Matakuliah: >/ > Tahun: > Versi: >
1 Pertemuan 10 Summary Matakuliah: G1072 Reading 1 Tahun: 2005 Versi: revisi 0.
1 Pertemuan 26 Making It Happen Matakuliah: A0194/Pengendalian Rekayasa Ulang Informasi Tahun: 2005 Versi: 1/5.
Teknik Routing Pertemuan 10 Matakuliah: H0524/Jaringan Komputer Tahun: 2009.
Standby-redundancy-models.PPT Building Standby Redundancy Models Last revised 12/06/2006.
1 Pertemuan 24 Forming the Passive Matakuliah: G0134 – Grammar III Tahun: 2005 Versi: revisi 1.
1 Pertemuan 16 The Business Owner’s View Matakuliah: A0194/Pengendalian Rekayasa Ulang Informasi Tahun: 2005 Versi: 1/5.
Jaringan LAN Pertemuan 04 Matakuliah: H0524/Jaringan Komputer Tahun: 2009.
1 Pertemuan 23 Making It Happen Matakuliah: A0194/Pengendalian Rekayasa Ulang Informasi Tahun: 2005 Versi: 1/5.
Pertemuan 04 Proxy/Cache
Pertemuan 20 The Business Views of the Technology Architecture
Pertemuan 13 Perencanaan Perdagangan Saham
Pertemuan 22 The Business Views of the Technology Architecture
Pertemuan 10 Modal Verbs (2) + link words
Pertemuan 11 Model TCP/IP
Presentation transcript:

1 Pertemuan 26 Review Project Matakuliah: H0204/ Rekayasa Sistem Komputer Tahun: 2005 Versi: v0 / Revisi 1

2 Learning Outcomes Pada akhir pertemuan ini, diharapkan mahasiswa akan mampu : Menguraikan Rekayasa sistem berdasarkan paparan project / studi kasus

3 Outline Materi Paparan hasil project dengan Simulasi Software Kehandalan sistem (Relex Software / Reliability Expert)

4

5

6

7 Modeling Goals The system reliability requirement is an availability of for 80% of the users. This requirement can be further analyzed as follows: 1.The network availability goal is specified at a certain level of service delivery. Therefore, the system can operate at a degraded state and still achieve the network availability goal. 2.The metric for performance as stated in the specification is "Number of Connected Users." In our model, this translates to "Percentage of Total System Capacity". A capacity of 80% is equivalent to 80% of the users being connected. 3.The required availability is stated at the degraded operating point. Therefore, the software must be able to calculate the availability of at 80% capacity. Relex OpSim is capable of calculating availability at any capacity percentage desired. 4.The model should take into account the redundancy inherent in the components (in this case, the backbone switches). 5.It may be desirable to model the complete interconnections between the different components. While this is possible, it will complicate the model. For the purposes of this brief, these connections have been ignored. Due to the high MTBF and low MTTR of the connected components, the probability of connecting elements failing is extra-ordinarily low (MTBF of connection is >40,000,000 hrs).

8 Modeling Process Please note that this is a sample process used to model the system in incremental steps. Once a user gets more familiar with the software, it will be possible to perform the modeling steps in less of a sequential path. Determine the total number of users so that component contributions can be determined. The total number of users in this example is 525. Therefore, each RJ45V Card on the ITN22 backbone will support 23/525 = 4.38% of the total capacity (assuming that they are equally loaded). Create and connect the blocks for the RJ45V path as shown below: –The green blocks are the components in the system, and can have MTBFs, repair times and capacities (as well as many other values) assigned to them. Components may only have one input or output. –The purple blocks are junction nodes, and can have any numbers of inputs or outputs. The type of junction can be specified as well. For instance, the Power Supplies (PS) blocks are connected using 1 of 2 parallel operating redundancies, and the Supervisor cards (S1 and S2) are connected using standby redundancy.

9

10 Assign the MTBF and repair properties to the blocks above. All capacities are set to 100% except for the RJ45 cards, which were set to 4.38%. Create and connect the blocks for the GBIC connection, as shown next:

11

12 Enter the data for the new components. Note that the Chassis and Power supplies shown leading into the GBIC card are "repeats" of the initial components. This is because they are exactly the same components. "Repeats" share the same properties, fail, and are repaired at exactly the same time as the originals. Of the new components, the Assy: 3548, PN: GBIC components (on the bottom right) are the only components with capacities other than 100%. Their capacities are 30/525 = 5.71%. Copy and paste the system, then alter data where required, to create the final system as shown here:

13

14 Please note that the End node is a parallel operating node, with only 1 of the 20 incoming paths required for the system to operate. The required capacity is set during calculation. Changing requirements do not require a change to the model. At this point, the system was calculated, and it was determined that the system did meet the requirements specified. Results can then be print previewed in a report, then exported to Microsoft Word.

15