2 - Memahami Stakeholders dan Aktivitas Rekayasa Kebutuhan

Summary

In this software requirement analysis lecture, the importance of understanding stakeholders is emphasized. The session highlights the necessity of avoiding assumptions in software development and stresses the need for clear communication between developers and clients. It discusses the role of requirement development and management, emphasizing the collaboration between developers and stakeholders to ensure software meets customer needs. The lecture also introduces the concept of a project owner as a bridge between internal teams and external entities, crucial for successful project execution.

Takeaways

• 😀 The importance of understanding stakeholders in software development is emphasized, as it affects the alignment of software features with customer needs.
• 👨‍💻 The script discusses the common problem of developers assuming what the client needs without proper communication, leading to potential misalignment of software features.
• 🤝 Effective communication between the development team and stakeholders is highlighted as a key factor in accurately mapping out software requirements.
• 📝 The script outlines the process of requirement development and management, which includes activities like requirement analysis, documentation, and ensuring project timeliness.
• 🔍 The difference between 'requirements development' and 'requirements management' is explained, with the former focusing on analyzing and documenting business processes and the latter on managing project timelines and scope.
• 🏢 Stakeholders can be individuals, groups, or organizations that have an interest or are affected by the project's activities and decisions.
• 👨‍🏫 The script uses an analogy of a misunderstanding between a customer and a developer to illustrate the importance of clear communication in software development.
• 📈 The role of the project owner is introduced as a bridge between internal and external stakeholders, which is crucial for the project's success.
• 📚 The script mentions the need for a good understanding of the client's business processes to design software that meets their needs.
• 📋 The importance of documentation in the software development process is stressed, as it serves as a guide for developers to build the application based on the specified requirements.

Q & A

What is the main topic discussed in the second meeting of the software requirement analysis and specification course?

The main topic discussed is the importance of understanding stakeholders in the context of software development.

What is the expected learning outcome for the students after the second meeting?

The expected learning outcome is for the students to be able to explain what stakeholders are and their significance in software development.

Why is it crucial to perform a repairman for an application?

Performing a repairman is crucial as it determines the goals and requirements needed by the customer, and it helps in deciding whether the application meets the customer's expectations.

What is the common problem that arises between developers and customers according to the script?

The common problem is that developers often assume what features the customer needs without verifying, leading to potential misunderstandings and undesired features.

What does the script suggest as a key factor in ensuring that software development meets customer needs?

The script suggests that good communication between the development team and stakeholders is a key factor in accurately mapping out the requirements needed for software development.

What are the two main activities in the requirement engineering phase as mentioned in the script?

The two main activities in the requirement engineering phase are requirement development and requirement management.

What is the purpose of requirement development in the context of the script?

Requirement development involves activities for analyzing and exploring requirements that will be documented and used for development by the developers.

What is the role of requirement management in the software development process?

Requirement management ensures that the project is completed on time and according to the plan, managing the requirements to keep them up to date.

What is the difference between requirement development and requirement management as per the script?

Requirement development focuses on creating documents that define the business processes and rules, while requirement management deals with ensuring the project's success by managing these requirements effectively.

Who are the stakeholders involved in the application discussed in the script?

The stakeholders involved include external parties like staff, lecturers, and students, as well as internal parties like project managers, developers, business analysts, and the project owner.

Why is it important to identify all stakeholders before starting the development process?

Identifying all stakeholders is important to ensure that the application can meet the needs of all involved parties and to facilitate effective communication among them.

Outlines

00:00

😀 Understanding Stakeholders in Software Requirement Analysis

The first paragraph introduces the topic of the video, which is about analyzing and specifying software requirements. The speaker, Supardianto, sets the learning objectives for the session, emphasizing the importance of understanding stakeholders. The discussion highlights the significance of client understanding and the common issue where developers assume what the client needs without proper communication. The analogy of a misunderstanding between a customer and a developer about a software feature is used to illustrate the importance of clear communication. The paragraph concludes with the necessity of good communication between the development team and stakeholders to accurately map out the requirements for software development.

05:01

😀 The Role of Communication in Software Development

The second paragraph delves into the misconception that developers or analysts can understand client needs without extensive discussions, leading to assumptions that may not align with client expectations. It stresses the importance of a balanced approach where developers and clients work together to meet software requirements. The paragraph also outlines the activities involved in software engineering, such as requirement development and management, and how they relate to project planning and execution. The speaker explains the division of tasks between developers and managers, emphasizing the need for effective communication and collaboration to ensure that software development meets the needs identified through requirement analysis.

10:01

😀 Stakeholder Involvement in Software Projects

The third paragraph focuses on the involvement of stakeholders in software projects, using a university scheduling system as an example. It identifies the various internal and external stakeholders, including staff, lecturers, students, project managers, developers, business analysts, and project owners. The paragraph discusses the importance of recognizing all stakeholders and the need for effective communication among them to develop a software system that meets the needs of all involved parties. It also touches on the documentation and information required during the requirement process to guide developers in creating a system that aligns with the project's goals and stakeholders' expectations.

Keywords

💡Stakeholders

Stakeholders are individuals, groups, or organizations that have an interest or are affected by the decisions and activities of a project. In the context of the video, stakeholders include both internal and external parties such as developers, project managers, business analysts, and clients. The script emphasizes the importance of understanding and communicating with stakeholders to ensure that software development meets their needs and expectations.

💡Requirements

Requirements refer to the specific needs and expectations that a software system must meet. The script discusses the importance of accurately capturing and documenting these requirements to guide the development process. It highlights the need for clear communication between developers and stakeholders to ensure that the software meets the desired goals and functionalities.

💡Communication

Communication is the process of exchanging information, ideas, or feelings between stakeholders and the development team. The video script underlines the necessity of good communication to prevent misunderstandings and to ensure that the software development aligns with the client's vision. Effective communication helps in capturing the right requirements and in managing expectations throughout the project lifecycle.

💡Assumptions

Assumptions are presuppositions or things taken for granted without proof or evidence. In the script, it is mentioned that developers should not make assumptions about what the client needs without proper communication. Assumptions can lead to the development of features that are not required or desired by the client, resulting in a product that does not meet the actual needs.

💡Software Development

Software development is the process of creating and maintaining applications or systems. The video script discusses various aspects of software development, including requirement development and requirement management, which are crucial for creating software that meets the client's needs. It also touches on the roles of different stakeholders in the development process.

💡Requirement Development

Requirement development involves activities aimed at analyzing and exploring the needs that will be documented and used as a basis for software development. The script mentions that this process includes identifying business processes and rules that influence the requirements, which are then translated into user requirements and quality attributes.

💡Requirement Management

Requirement management is the process of planning, organizing, and controlling the requirements of a project. It ensures that the project stays on track and meets the necessary deadlines and goals. The script refers to requirement management as a way to keep the project requirements up to date and aligned with the project plan.

💡Project Owner

The project owner is a key stakeholder who is responsible for the overall success of the project. In the script, the project owner is described as a bridge between internal teams (like developers and business analysts) and external stakeholders (like clients). They play a crucial role in ensuring that the project meets the objectives and satisfies the needs of all parties involved.

💡Functional Requirements

Functional requirements specify the tasks that the software system must be able to perform. The script discusses how these requirements are influenced by the system's internal workings and external interfaces. They are a critical part of the software requirement specifications (SRS) that guide developers in building the application.

💡Software Requirement Specification (SRS)

SRS is a document that outlines the functional and non-functional requirements of a software system. It serves as a contract between the development team and the stakeholders, detailing what the software should do and how it should perform. The script mentions that SRS is derived from user requirements and is a key reference for developers during the software development process.

💡Quality Attributes

Quality attributes refer to the non-functional aspects of a software system, such as performance, reliability, and usability. The script discusses the importance of determining these attributes during the requirement development phase to ensure that the software not only meets the functional needs but also the quality expectations of the stakeholders.

Highlights

Introduction to the second meeting on software requirement analysis and specification.

Learning outcomes: Understanding the concept of stakeholders.

Importance of client understanding and the role of stakeholders in software development.

Recap of the previous meeting's discussion on the importance of repairman for an application.

Analogy of a misunderstanding between a customer and a developer regarding software features.

The problem of developers making assumptions about client needs without proper communication.

Software teams' inability to understand the client's business processes leading to unmet requirements.

The client's inability to articulate their needs effectively in technical documentation.

The impact of poor communication between clients and developers on capturing customer needs.

Emphasis on the necessity of good communication between the development team and stakeholders.

The misconception that developers or analysts can understand client needs without discussion.

Developers' assumption that they know what features the customer needs without verification.

The importance of a balanced approach in software development based on good planning and execution of requirements.

The role of effective communication and collaboration between developers and customers in defining software requirements.

Overview of the activities in software engineering, including requirement development and management.

The difference between modern requirement engineering and management.

The process of requirement development leading to the creation of user requirement documents.

The role of software requirement specifications (SRS) in guiding developers in application development.

Example of a case study involving the development of a scheduling system for a university.

Identification of stakeholders involved in the application, including external and internal parties.

The significance of understanding all stakeholders' roles in the application for effective communication.

Definition of stakeholders as individuals, groups, organizations, or anyone related to the project's activities and decisions.

The necessity of information and documentation in the requirement process for developers.

Anticipation of the next meeting's discussion on further topics in requirement analysis.

Transcripts

[Musik]

Halo semuanya Jumpa lagi bersama saya

supardianto di pertemu di pertemuan kita

yang kedua di mata kuliah analisis dan

spesifikasi kebutuhan perangkat lunak

pada pertemuan kita kali ini kita akan

membahas mengenai

Oke ini adalah capaian pembelajaran pada

pertemuan kita kali ini yaitu diharapkan

teman-teman nanti bisa menjelaskan

mengenai apa itu stakeholders gitu ya

dan ini adalah outline nya yang akan

menjadi pembahasan kita kali ini yaitu

membahas mengenai

membahas mengenai Important of the

client understanding stakeholders

Oke sebelum kita membahas atau masuk ke

dalam pertemuan kita kali ini saya

Recall sedikit pada pertemuan kita

sebelumnya bahwa di pertemuan kita

sebelumnya kita membahas mengenai

Seberapa penting dilakukannya suatu

reparman terhadap suatu aplikasi

jawabannya adalah sangat penting gitu ya

karena memang reforman itu nanti akan

menentukan mengenai goal dan beach yang

dibutuhkan oleh si customer dan juga

akan menjadi atau titik penentu Apakah

aplikasinya bisa sesuai dengan yang si

customer inginkan atau tidak seperti itu

Nah pada pertemuan kita kali ini kita

akan mulai dari adanya suatu analogi

lihat di sini

si bapak yang berjas itu dia bertanya

apa yang sedang terjadi dengan program

saat ini apakah itu adalah suatu bak

atau suatu kesalahan atau tidak si

programmer ya dia menjawab bahwa Oh

bukan itu bukan bank itu adalah yang

saya sebut sebagai suatu fitur nah

Berarti dari penggambaran ini saja kita

bisa melihat bahwa si customernya tidak

paham bahwa Apakah memang itu yang

diinginkan atau kita juga bisa berasumsi

bahwa si developernya yang membuat suatu

fitur yang tidak dibutuhkan oleh si

customer Nah itu adalah gambaran dari

kedua hal yang bisa teman-teman lihat di

gambar di sini

makanya kita masuk ke point kita yang

pertama yaitu Important of client

beforementnya yang pertama adalah

mengatakan bahwa

tidak bisa dibuat hanya berdasarkan

asumsi dari si developer ini yang juga

kemarin pada pertemuan kita sebelumnya

itu dianggap sebagai

the common problem atau permasalahan

yang sering muncul yaitu si developernya

berasumsi bahwa si clien pasti butuh nih

dengan fitur ini tapi nyatanya tidak

poin berikutnya mengatakan bahwa the

software usually

don't have of the client artinya

sekarang masalahnya dari sisi software

timnya dia nggak bisa

merancang atau melihat bahwa bisnis

proses apa yang terdapat di si clientnya

lalu kemudian tidak bisa memenuhi

pengetahuan pengetahuan dasar mengenai

si kebutuhan dari si customernya ini

lalu client understand 2 in the system

Nah sekarang masalahnya adalah layarnya

tahu apa yang dia inginkan yang ada di

sistem tetapi ya mereka tidak bisa

mempunyai suatu mempunyai kemampuan

untuk menjelaskannya dengan benar atau

memasukkannya ke dalam technical dokumen

agar itu nanti bisa dimengerti oleh si

Developer

kemudian kekurangan komunikasi diantara

klien dan developer itu juga kemudian

akan mempengaruhi seberapa banyak

kebutuhan dari si customer yang bisa

ditangkap oleh si developer gitu ya

makanya poin yang paling penting adalah

This is why we need a good communication

between the development team dan juga

stakeholder makanya komunikasi jadi

salah satu kunci agar bisa mampu dengan

tepat memetakan requirement apa yang

kemudian akan kita gunakan di dalam

pengembangan suatu aplikasi tidak bisa

hanya dari sisi developer saja tidak

bisa hanya dari sisi customer saja

kedua-duanya Kemudian harus bisa saling

berkomunikasi

namun problemnya ini muncul juga di sini

ya

berasumsi bahwa si developernya atau si

analis akan mengetahui kebutuhan yang

mereka miliki yang mereka inginkan dan

akan membangun software itu tanpa perlu

banyak diskusi jadi dia berantakan bahwa

udahlah satu kali pertemuan cukup kalian

nanti pasti paham lah dengan apa yang

saya ingin bangun yang biasanya customer

atau client

kasih tahu gitu ya atau pikirkan lalu

sekarang dari sisi sebaliknya bahwa si

developernya sekarang merasa bahwa udah

deh nggak usah sering-sering diskusi

saya juga sudah tahu deh apa yang mereka

mau paling asumsinya seperti ini Nah

sekarang dari sisi developernya yang

kemudian

pandai-pandai bahwa fitur ini itu bisa

kok menjawab dari kebutuhan customer Nah

makanya tidak bisa berat sebelah jadi

semua harus saling

timbang suatu software yang terbaik itu

adalah dengan berdasarkan eksekusi yang

baik terhadap suatu perencanaan dan juga

eksekusi yang baik terhadap kebutuhan

yang diperlukan

dimana kebutuhan ini tentu saja berasal

dari komunikasi dan juga kolaborasi yang

efektif diantara developer dan juga sih

customer

lalu kita lihat bahwa di kuadrat

engineering itu ya memiliki beberapa

aktivitas ada requirement development

ada requirement management ini juga

hampir serupa atau kita ingat lagi

pertemuan kita sebelumnya ada project

recorder ada produk requirement Nah

sekarang kita lihat di qurban developer

kalau requirement development ini adalah

aktivitas-aktivitas yang ketika

dilakukan untuk mencari analisis

kebutuhan dieksplorasi yang nantinya

akan dimasukkan menjadi dokumentasi yang

akan digunakan sebagai bahan

pengembangan oleh si developer

kalau requirement management ini adalah

kebutuhan-kebutuhan yang nantinya bisa

me-mana bahwa project ini itu bisa

selesai dengan tepat waktu Seperti apa

apa yang dibutuhkan agar bisa up to date

gitu ya Sesuai dengan perencanaan yang

sudah dibuat Nah ini masuk ke bagian

requirement management kalau teman-teman

lihat ada di bagian di sebelahnya

engineering dibagi dua ada

developernya lagi terbagi atas

spesifikasi dan juga validasi

kemudian ini adalah perbedaan diantara

Rival modern

lihat di bagian atasnya dimulai dari

marketing customer management

melakukan analisis dokumen review

defisien dan menentukan batas dari

requirementnya kayak gitu ya kemudian

yang di bawahnya adalah berkaitan dengan

si manajemennya Apa yang dibutuhkan

kemudian dikaitkan dengan Project dan

seterusnya

hal-hal yang nantinya akan dikerjakan

terkait dengan kelancaran pekerjaan

Project itu yang menjadi bagian

requirement management

lalu ini adalah

basis atau relationship diantara

requirement

development ya dimana pada requirement

development akan menghasilkan banyak

dokumen ini kita lihat di paling atas

itu adalah dengan melakukan yang namanya

requirement terkait dengan proses bisnis

yang dia nanti akan terhubung kepada

aturan bisnis tersebut ya Sehingga

keluaran dari aktivitas 2 ini nanti akan

menjadi suatu dokumen yang namanya

ya Design and Scope akan menentukan atau

memberi pengaruh kepada user requirement

dan juga nanti akan

terdapat aktivitas menentukan quality

atributnya Nah dari dua Aktivitas ini

nanti kemudian akan menjadi user

reparban Documents

akan menjadi salah satu

penyedia untuk menentukan fungsional

requirementnya dimana functional itu

akan diisi oleh atau berisikan sistem

repartment

tapi akan terkena pengaruh juga dari

adanya eksternal interface dan juga

nanti akan ada konstrate 4 Aktivitas ini

akan membentuk suatu dokumen yang akan

menjadi pegangan bagi developer yaitu

namanya adalah software requirement

specification kayak gitu ya dan ini akan

menjadi pegangan bagi si developer

kemudian mengembangkan aplikasi

berdasarkan requirement yang sudah dapat

disingkatannya adalah SRS

lalu ini adalah contoh suatu cash tadi

dimana ke studinya adalah

scheduling sistem pada suatu Universitas

ada pengertian singkatnya deskripsi

singkatnya bahwa Buatlah suatu sistem

yang bisa membantu

mengaotomasikan proses pada saat

menjerret jadwal ya jadwal kuliah atau

jadwal mata kuliah seperti itu Nah

sekarang kita lihat stakeholder yang

terlibat di dalam aplikasi ini

stakeholder yang terlibat adalah kalau

dari sisi eksternal itu ada staff ada

lecture ada student tentulah ya pasti di

dalam civitas akademika pasti ada tiga

itu dari sisi internal ada Project

Manager ada developer tim ada bisnis

analis lalu yang baru adalah lihat

posisi yang berada di tengah yaitu

adanya Project ownernya yang Akan

Kemudian nanti bisa

menjadi penghubung diantara internal dan

juga sih eksternal

jadi teman-teman bisa bayangkan bahwa

bahwa ternyata

sebelum kita lebih dalam masuk ke dalam

melakukan recorder kita Tentu juga harus

bisa melihat siapa saja stakeholder yang

terlibat di aplikasi kita gitu ya

kita membutuhkan adanya suatu komunikasi

yang baik diantara dan juga para

ini akan bisa membantu kita dalam

beberapa suatu aplikasi yang bisa

memenuhi segala kebutuhan dari sistem

kode

stakeholder bisa berupa individu grup

organisasi atau siapapun

yang kemudian bisa

berkaitan dengan si segala aktivitas dan

juga keputusan pada project ini

dimana recorder engineering terdiri dari

dua ada repairder developer ada di

qurban Manajemen gitu ya Kemudian pada

saat proses requirement ini terjadi kita

juga kadang membutuhkan banyaknya

informasi dan juga banyaknya dokumen

yang bisa menjadi pegangan kita untuk

kemudian masuk ke tahapan developer

seperti itu

Oke sampai situ untuk pertumbuhan kita

kali ini kita akan ketemu lagi di

pertempur selanjutnya adalah pembahasan

selanjutnya Oke sampai jumpa

[Musik]