Project Based Internship Klinikgo Health System Analyst - Company Coaching Video 1

VIX Rakamin Academy
17 Sept 202309:25

Summary

TLDRIn this company coaching video, Director Oggy introduces the audience to system development methodologies, focusing on software development life cycle (SDLC), particularly the Waterfall and Agile methods. The importance of understanding user needs, technology familiarity, and project structure is emphasized. The video delves into Unified Modeling Language (UML) for object-oriented design, highlighting its role in creating detailed documentation for developers. It also covers the types of UML diagrams, such as use case and class diagrams, essential for static and dynamic system modeling. The script concludes with a case study on designing UML for a new clinic feature, illustrating the practical application of these concepts.

Takeaways

  • 😀 The video is an introductory coaching session by Oggy, a director at a clinic, focusing on system development methodologies.
  • 📚 The material covers software development methodologies, including the Waterfall and Agile models, and discusses their characteristics and applications.
  • 💡 Understanding user needs, technology familiarity, project scale, timeline, and complexity are crucial for selecting an appropriate software development method.
  • 🔍 The Software Development Life Cycle (SDLC) is a popular approach in application development, with Waterfall and Agile being commonly used methodologies.
  • 💧 The Waterfall model is sequential and documentation-intensive, where each phase's output feeds into the next phase.
  • 🦄 Agile methodology emphasizes client-developer interaction and allows for frequent requirement changes, leading to simpler and more general project designs.
  • 📈 Unified Modeling Language (UML) is a standardized visual language for object-oriented software design, which can also be associated with programming languages.
  • 🛠 UML diagrams describe the system's structure, behavior, and objects, and tools like StarUML and Visio are used for creating these diagrams.
  • 👥 A system analyst should master UML for detailed requirement documentation, guiding developers in a team to build or develop software systems.
  • 📊 UML diagrams are categorized into structural diagrams, which show static system structure, and behavioral diagrams, illustrating dynamic system interactions.
  • 🔑 The video also introduces a new clinic feature, a chat function, which includes private messaging and video calls with doctors, and group chats for specific topics.
  • 🚀 The clinic's team faces the challenge of creating UML for this new feature, highlighting the importance of UML in guiding software development.

Q & A

  • What is the main topic of the first company coaching video?

    -The main topic of the first company coaching video is about the development of systems, focusing on software development methodologies, the Agile model, and Unified Modeling Language (UML).

  • Why is it important for a system analyst to understand software development methodologies?

    -It is important for a system analyst to understand software development methodologies to effectively analyze and design complex software systems, ensuring that the development is efficient in terms of time and cost, and to prevent potential loss of customers.

  • What are the two SDLC methodologies introduced in the video?

    -The two SDLC methodologies introduced in the video are Waterfall and Agile.

  • What is the Waterfall methodology and why is it called so?

    -The Waterfall methodology is a step-wise process in software development where the output of one phase becomes the input for the next phase. It is called so because of its cascading nature, resembling a waterfall.

  • What are the key features of the Agile methodology?

    -The Agile methodology is based on iterative and incremental development, with a strong emphasis on client-developer interaction and flexibility to accommodate changing requirements.

  • What is Unified Modeling Language (UML) and its purpose?

    -Unified Modeling Language (UML) is a standardized visual language used for modeling software systems. It describes the structure, behavior, and relationships of the system components and is essential for creating detailed documentation for developers.

  • What are the two main categories of UML diagrams?

    -The two main categories of UML diagrams are structural diagrams, which describe the static structure of the system, and behavioral diagrams, which describe the dynamic interactions within the system.

  • Can you name some tools that can be used to create UML diagrams?

    -Some tools that can be used to create UML diagrams include StarUML and Visio.

  • What is the significance of use case diagrams in the software development process?

    -Use case diagrams are significant in the software development process as they help to identify the functionalities or features of the system from the user's perspective and guide the development of those features.

  • What are the differences between group chat and private chat features in the context of the video?

    -Group chat is used for sharing information with all online users without limitations, while private chat or one-on-one consultation with a doctor is a more personal communication service, including video and audio streaming, and is subject to the doctor's availability.

  • How does the video script suggest enhancing the understanding of UML for developers?

    -The video script suggests creating UML diagrams such as use case diagrams, class diagrams, and sequence diagrams to provide a clear understanding of the system's static and dynamic structures, which serves as a guide for developers during the software development process.

Outlines

00:00

😀 Introduction to Software Development Methodologies

Oggy, as a director, introduces the first company coaching video, focusing on system development methods. The material covers software development methodologies, the Agile model, and language. A case study and a discussion on related topics will be presented by a selected delegation from the clinic. As a system analyst, understanding the software development life cycle (SDLC) is crucial to prevent potential customer loss and ineffective software development in terms of time and cost. The video will introduce two popular SDLC methods: Waterfall and Agile, highlighting their characteristics and the importance of understanding user needs, technology, project structure, and complexity.

05:01

📚 Exploring UML and Software Behavior Modeling

This paragraph delves into Unified Modeling Language (UML), a standardized visual language for object-oriented software design. UML is essential for system analysts to document detailed requirements for application development, serving as a reference for developers. The paragraph explains the two main categories of UML diagrams: structural and behavioral. Structural diagrams, such as class diagrams and deployment diagrams, illustrate how system components relate to each other, while behavioral diagrams, including use case diagrams, activity diagrams, and sequence diagrams, model the dynamic interactions within a system. The importance of using UML tools for designing and the challenges faced by the clinic's team in creating UML for a new feature are also discussed.

Mindmap

Keywords

💡System Development Method

A system development method refers to a structured approach used to develop information systems. In the video, this concept is central as it discusses the importance of understanding these methods to prevent ineffective software development in terms of time and cost, which could harm the company.

💡Software Development Life Cycle (SDLC)

SDLC is a process involving several stages used to design, develop, test, deploy, and maintain software. The video introduces two common SDLC methodologies, emphasizing their significance in the systematic development of applications.

💡Waterfall Model

The Waterfall Model is a linear and sequential approach to SDLC where each phase must be completed before the next one can begin. It is characterized by intensive documentation, as mentioned in the script, and is used to illustrate the structured process of software development.

💡Agile Method

The Agile Method is a flexible approach to SDLC that promotes iterative development, allowing for continuous improvement and customer feedback. The video highlights this method's adaptability to change in requirements, which is a common occurrence in software projects.

💡Unified Modeling Language (UML)

UML is a standardized modeling language used to visualize and specify the design of software systems. The video script discusses UML as a crucial tool for system analysts to create detailed documentation of software requirements and system behavior.

💡System Analyst

A system analyst is a professional who understands both business and IT to analyze, design, and develop information systems. In the video, the role of a system analyst is emphasized in creating software applications and the necessity to master UML for effective documentation.

💡Use Case Diagram

A use case diagram in UML represents the relationship between actors and the system's functionality. The video script uses the example of a patient using a login feature, chat for consultation with a doctor, and logout, to illustrate how use case diagrams can outline the functionalities of a system.

💡Class Diagram

A class diagram in UML is used to model the static structure of a system by showing classes, their attributes, and the relationships between them. The video mentions the creation of a class diagram to help developers understand the details and sequence of feature development.

💡Sequence Diagram

A sequence diagram is a type of UML diagram that illustrates the interactions between objects or participants in a particular scenario. The video script describes the login process and chat feature interactions, which could be effectively modeled using sequence diagrams.

💡Chat Feature

The chat feature mentioned in the video refers to a communication tool within an application, specifically designed for group discussions and private consultations with doctors. It exemplifies the practical application of system development methods and UML in creating interactive software functionalities.

💡Consultation

Consultation in the context of the video refers to a private communication feature within the application for one-on-one communication with a doctor, including video and audio streaming. This highlights the importance of understanding user needs and the application of technology in software development.

Highlights

Introduction of Oggy as a director discussing system development methods.

Emphasis on the importance of understanding user needs and technology familiarity in software development.

Explanation of the Software Development Life Cycle (SDLC) as a popular method in application development.

Introduction of two SDLC methods: Waterfall and Agile, with their characteristics and applications.

Description of Waterfall method as step-by-step with intensive documentation.

Agile method highlighted for its iterative nature and client-developer interaction.

Introduction to Unified Modeling Language (UML) as a standardized language for software modeling.

UML's role in describing system structure, behavior, and objects within it.

Mention of tools needed for UML, such as Star UML and Visio.

The necessity for system analysts to master UML for detailed requirement documentation.

UML divided into two main categories: structural and behavioral diagrams.

Explanation of structural diagrams for modeling system architecture and design.

Behavioral diagrams described for visualizing dynamic system interactions.

Examples of UML diagrams including use case, class, deployment, and sequence diagrams.

Discussion on the challenges of creating UML for new features in the Cliniko application.

Basic UML diagrams required for feature development: use case, class, and sequence diagrams.

Detailed explanation of the use case diagram components: actors, activities, and sub-activities.

Sequence diagram's role in illustrating the process flow and interactions within the application.

Differentiation between group chat and private chat features in the application.

Feature of private consultation with doctors, including video and audio streaming.

Logout feature allowing users to exit the application.

Announcement of new features in Cliniko, including private and group chat functionalities.

Conclusion and appreciation for the audience's attention to the company coaching video.

Transcripts

play00:00

Halo semuanya perkenalkan saya Oggy

play00:02

sebagai director di klinikku pada

play00:04

company coaching video pertama ini kita

play00:06

akan membahas materi mengenai metode

play00:08

pengembangan sistem

play00:10

pada materi ini terdapat beberapa

play00:12

pembahasan yaitu mengenai software

play00:13

development metodologi anyvite model

play00:16

language dan juga di akhir nanti akan

play00:18

ada studi kasus beserta pembahasan

play00:20

mengenai materi terkait yang akan

play00:22

disampaikan oleh delegasi yang telah

play00:23

dipilih oleh klinik Go dan telah kami

play00:25

beri pemahaman dan pengetahuan terkait

play00:27

hal sistem analis di perusahaan kami

play00:30

simak video selengkapnya ya

play00:33

sebagai seorang sistem analis kita

play00:35

sering mendapatkan request dari klient

play00:36

atau SMA untuk membuat suatu software

play00:39

application atau sistem yang cukup

play00:40

kompleks dan rancangan sistemnya belum

play00:42

ada jika kita tidak bisa menganalisis

play00:45

dan membuat desain atau rancangan sistem

play00:47

ada dua kemungkinan yang mungkin terjadi

play00:49

satu kita bisa saja kehilangan potensial

play00:52

customer dua pengembangan software Bisa

play00:55

jadi Tidak Efektif baik dari segi time

play00:57

maupun cost hal itu akan merugikan

play00:59

perusahaan bukan Lalu bagaimana hal itu

play01:02

tidak terjadi pada kita untuk mencegah

play01:05

hal itu kalian harus mengetahui mengenai

play01:07

metode pengembangan sistem atau software

play01:09

development system dan pengaplikasiannya

play01:12

dalam pengembangan software aplikasi

play01:16

untuk memilih metode pengembangan

play01:18

aplikasi penting bagi kita memiliki

play01:20

kemampuan memahami kebutuhan user

play01:22

wawasan yang familiar dengan teknologi

play01:23

yang akan digunakan untuk pengembangan

play01:25

aplikasi struktur tim skala Project

play01:28

timeline dan tingkat kompleksitas

play01:30

Project itu sendiri dengan memahami

play01:31

hal-hal tersebut kita bisa lebih

play01:33

mengetahui apa yang harus kita lakukan

play01:35

terhadap sistem yang akan kita bangun

play01:37

atau kita kembangkan nantinya

play01:41

software development life cycle atau

play01:43

sdlc merupakan metode yang paling

play01:45

populer dan sering digunakan dalam

play01:46

pengembangan aplikasi pada materi ini

play01:49

akan kami perkenalkan dua metode sdlc

play01:52

yang biasa digunakan yaitu Waterfall dan

play01:55

Agel metode yang pertama adalah

play01:58

Waterfall metode ini sering disebut

play02:00

sebagai metode air terjun karena

play02:02

prosesnya yang bertahap mulai dari awal

play02:05

sampai akhir dalam metode Waterfall

play02:08

hasil dari satu fase menjadi input untuk

play02:10

fase berikutnya metode Waterfall juga

play02:12

bersifat dokumentasi intensif karena

play02:15

pada fase awal kita banyak

play02:17

mendokumentasikan Apa yang perlu

play02:20

dilakukan pada fase berikutnya yang

play02:22

kedua metode gel metode ini memiliki

play02:26

basis metode ini memiliki basis model

play02:29

literatif dan infermental karena itu

play02:31

interaksi antara client dan developer

play02:33

sangat menentukan langkah berikutnya

play02:35

dalam Project sejalan dengan hal

play02:37

tersebut perubahan requirement menjadi

play02:39

hal yang lazim sehingga

play02:41

rancangan desain Project dengan metode

play02:42

Agel cenderung disusun secara sederhana

play02:44

dan umum

play02:46

Nah kita masuk ke pembahasan andifand

play02:50

model language Mari kita kenali lebih

play02:52

dalam tentang UML atau unifie model

play02:55

language teknik yang digunakan untuk

play02:57

membuat perancangan berorientasi objek

play02:59

adalah unifi model language atau UML UML

play03:03

disebut sebagai bahasa yang telah

play03:05

distandarisasi untuk digunakan dalam

play03:07

memodelkan suatu software atau sistem

play03:10

meski pada dasarnya UML merupakan bahasa

play03:13

visual namun dalam beberapa kasus juga

play03:15

dapat dihubungkan sebagai bahasa

play03:17

pemrograman seperti

play03:19

Javas dan lain-lainnya secara

play03:22

keseluruhan diagram UMR mendeskripsikan

play03:24

batasan struktur dan perilaku sistem

play03:27

serta objek di dalamnya

play03:29

untuk membuat UML tentunya butuh tools

play03:32

berupa aplikasi baik menggunakan desktop

play03:34

application maupun web application

play03:36

beberapa aplikasi yang biasa kamu coba

play03:40

gunakan dan eksploitasi diantaranya

play03:43

Star UML dan fisio

play03:46

sistem analis selain perlu memiliki

play03:48

kemampuan analisis dan memahami coding

play03:50

logic sudah tentu wajib menguasai UML

play03:53

karena dia yang membuat dokumentasi

play03:56

berisi detail requirement pengembangan

play03:58

aplikasi atau sistem agar dapat menjadi

play04:01

acuan bagi para developer yang bekerja

play04:03

dalam satu sistem dalam satu tim yang

play04:06

sama dengannya

play04:08

untuk kalian yang bertanya-tanya diagram

play04:11

UML ada jenisnya nggak sih jawabannya

play04:14

ada UML terbagi menjadi dua kategori

play04:17

utama yaitu diagram struktur dan diagram

play04:20

behavior atau perilaku

play04:23

diagram struktur ialah berupa struktur

play04:25

statis atau sistem yang menggambarkan

play04:27

bagaimana komponen sistem berhubungan

play04:29

satu sama lain diagram struktur

play04:32

digunakan untuk memodelkan arsitektur

play04:34

dan desain sistem software diagram ini

play04:38

juga berguna untuk

play04:40

mengkomunikasikan struktur sistem pada

play04:42

stracode stakeholder dengan kepentingan

play04:45

teknis dan non teknis Berikut adalah

play04:48

contoh diagram struktur

play04:51

contoh diagram struktur adalah kelas

play04:53

diagram dan diployment diagram

play04:56

diagram behavior menggambarkan perilaku

play04:59

dinamis dari suatu sistem yang

play05:01

menunjukkan Bagaimana komponen-komponen

play05:03

suatu sistem berinteraksi satu sama lain

play05:06

diagram ini digunakan untuk memodelkan

play05:08

interaksi antara objek proses dan

play05:11

peristiwa dalam suatu sistem

play05:13

diagram behavior merupakan tool yang

play05:16

efektif untuk memvisualisasikan dan

play05:19

memahami aspek dinamis pada sistem

play05:21

software contoh diagram antara lain use

play05:26

case diagram activity diagram dan

play05:28

Sequence

play05:30

Oke kita masuk ke materi yang

play05:32

ditunggu-tunggu kalian Nih pasti yaitu

play05:34

cash tadi pada bagian ini kalian bisa

play05:36

menjeda video untuk mengerjakan secara

play05:39

mandiri cash tadi yang diberikan di

play05:41

video di video di akhir video akan ada

play05:43

pembahasan yang bisa dicocokkan dengan

play05:45

hasil pekerjaan kalian

play05:48

jadi klinik goal akan meluncurkan fitur

play05:51

chatting yang terdiri dari private untuk

play05:54

memudahkan customer untuk berkirim pesan

play05:56

atau video call dengan dokter

play05:59

atau antara calon Mitra dan SDM klinik

play06:03

lo dan grup chat untuk membahas topik

play06:05

tertentu

play06:07

tim clinigo menghadapi tantangan untuk

play06:09

membuat UML dari fitur baru tersebut

play06:12

menurut kamu seperti apa rancangan

play06:14

desain UML untuk fitur setting clinikku

play06:19

Oke Mari kita bahas

play06:22

biasanya ada 3 basic UML yang perlu kita

play06:24

buat yaitu use case diagram kelas

play06:27

diagram dan sekunder

play06:30

komponen utama dalam penggunaan use case

play06:32

diagram yaitu aktor aktivitas atau fitur

play06:35

dan Sub aktivitas atau fitur

play06:38

pada contoh tes tadi berikut aktor

play06:41

adalah pasien yang akan menggunakan

play06:42

fitur user login yang biasanya menerima

play06:45

inputan berupa username dan password

play06:47

fitur chat untuk melakukan konsultasi

play06:50

dengan dokter dan fitur logout untuk

play06:52

keluar dari aplikasi

play06:55

lalu selanjutnya kita akan membuat class

play06:58

diagram dan sekunder diagram untuk

play07:01

struktur statis dan dinamisnya sehingga

play07:03

developer bisa lebih memahami dan

play07:05

tergambarkan mengenai detail dan urutan

play07:07

pengembangan fitur pembuatan UML ini

play07:10

penting kita lakukan untuk membuat

play07:12

mengarahkan serta sebagai acuan bagi

play07:15

developer saat mengembangkan software

play07:18

untuk contoh use case pada slide

play07:20

sebelumnya Mari kita bahas Lebih Detail

play07:22

Sequence

play07:24

jadi sebagai user atau aktor yang

play07:27

berperan sebagai perilaku dalam konteks

play07:30

ini Tentunya user perlu melakukan proses

play07:32

login terlebih dahulu tampilan login

play07:35

akan muncul saat user mengakses aplikasi

play07:37

clinik Go ketika melakukan login user

play07:40

akan diminta untuk memasukkan nama yang

play07:42

akan digunakan sebagai identitas atau

play07:45

pengenal saat bertukar data seperti

play07:47

pesan video atau audio proses validasi

play07:52

akan dilakukan saat user melakukan login

play07:54

untuk mencegah adanya nama user yang

play07:56

tidak valid seperti null atau kosong

play07:59

setelah proses validasi dari tampilan

play08:02

login user akan beralih ke fitur chat

play08:04

aplikasi ini gua ingin memiliki

play08:06

spesialisasi dalam fitur obrolannya

play08:08

dengan fitur pertama adalah obrolan grup

play08:11

dan yang kedua adalah obrolan pribadi

play08:13

untuk konsultasi dengan dokter

play08:16

perbedaan antara kedua fitur ini

play08:18

terletak pada fungsi dan penggunaannya

play08:20

dari segi fungsi obrolan group digunakan

play08:23

untuk berbagi informasi kepada seluruh

play08:25

user yang sedang online dari segi

play08:28

penggunaan setiap pengguna dapat

play08:30

menggunakan fitur ini tanpa batas dan

play08:32

tanpa syarat tertentu di sisi lain

play08:34

obrolan pribadi atau fitur konsultasi

play08:37

one on one dengan dokter disediakan

play08:39

sebagai layanan komunikasi yang lebih

play08:41

pribadi termasuk fitur streaming video

play08:43

dan audio

play08:46

untuk menggunakan fitur ini user harus

play08:48

memilih dokter yang available untuk

play08:50

berkomunikasi atau konsultasi secara

play08:52

pribadi jika diizinkan user atau pasien

play08:57

dapat menggunakan fitur ini sedangkan

play08:59

jika ditolak user tidak dapat melakukan

play09:01

obrolan pribadi atau konsultasi dan akan

play09:03

kembali ke halaman menu utama terakhir

play09:06

user dapat melakukan logout dari

play09:08

aplikasi

play09:11

oke sekian materi dan company coaching

play09:13

video pertama ini Terima kasih

play09:15

teman-teman sudah ikut menyimak materi

play09:17

kita semoga bermanfaat dan menyenangkan

play09:19

ya sampai jumpa pada video selanjutnya

play09:21

dadah

Rate This

5.0 / 5 (0 votes)

Related Tags
Software DevelopmentUMLCoaching VideoMethodologySDLCWaterfall ModelAgile ModelSystem AnalysisDesign DocumentationCase StudyTechnical Tutorial