#Software #Engineering - Lecture 4: Requirements Engineering, Specification, Validation & Management

#SoftwareEngineering #Course #HowToProgram #HowToCode #HowToBeEngineer
Hello everyone. My name is Furkan Gözükara, and I am a Computer Engineer Ph.D. Assistant Professor at the Software Engineering department.

In this course, we will learn what is the true meaning of being a Software Engineer rather than being a web developer / freelancer developer / software developer / developer / coder / programmer, etc.

This course does not require you to have any knowledge about programming in any programming language.

However, if you want to start learning programming or develop your other Software Engineering related skills you can watch our below full courses:

Lecture 4 : Requirements Engineering
* Functional and non-functional requirements
* The software requirements document
* Requirements specification
* Requirements engineering processes
* Requirements elicitation and analysis
* Requirements validation
* Requirements management

All of the Sub-Topics of Lecture 4:

* Requirements engineering
* What is a requirement?
* Requirements abstraction (Davis)
* Types of requirement
* User and system requirements
* Readers of different types of requirements specification
* Functional and non-functional requirements
* Functional requirements
* Functional requirements for the MHC-PMS
* Requirements imprecision
* Requirements completeness and consistency
* Non-functional requirements
* Types of nonfunctional requirement
* Non-functional requirements implementation
* Non-functional classifications
* Examples of nonfunctional requirements in the MHC-PMS
* Goals and requirements
* Usability requirements
* Metrics for specifying nonfunctional requirements
* Domain requirements
* Train protection system
* Domain requirements problems
* Key points
* The software requirements document
* Agile methods and requirements
* Users of a requirements document
* Requirements document variability
* The structure of a requirements document
* Requirements specification
* Ways of writing a system requirements specification
* Requirements and design
* Natural language specification
* Guidelines for writing requirements
* Problems with natural language
* Example requirements for the insulin pump software system
* Structured specifications
* Form-based specifications
* A structured specification of a requirement for an insulin pump
* Tabular specification
* Tabular specification of computation for an insulin pump
* Requirements engineering processes
* A spiral view of the requirements engineering process
* Requirements elicitation and analysis
* Problems of requirements analysis
* Requirements elicitation and analysis
* The requirements elicitation and analysis process
* Process activities
* Problems of requirements elicitation
* Requirements discovery
* Stakeholders in the MHC-PMS
* Interviewing
* Interviews in practice
* Scenarios
* Scenario for collecting medical history in MHC-PMS
* Use cases
* Use cases for the MHC-PMS
* Ethnography
* Scope of ethnography
* Focused ethnography
* Ethnography and prototyping for requirements analysis
* Requirements validation
* Requirements checking
* Requirements validation techniques
* Requirements reviews
* Review checks
* Requirements management
* Changing requirements
* Requirements evolution
* Requirements management planning

Auto timed subtitle : success

[yunusemrebitkay]

I learned in this lecture

• What is Requirements Engineering?
* It is the process of establishing the constraints of the process by which the requirements that customers need from the software run and are developed.
• What is a Requirement?
• What is Requirements Abstraction?
* If the client wishes to contract for a software project, the client should define the software's requirements as abstractly as possible.
• What are Types of the Software?
• What would be an example of user and system requirements for MHC-PMS Software?
• What are functional and non-functional requirements?
* Functional Requirements - A description of the services the software must provide to the customer, how the software should respond based on the data entered, and how the software should behave in certain circumstances.
* Non-functional Requirements - Timing constraints are constraints on the services provided by the software, such as restrictions on the software development process.
• What Would Be the Functional Requirements for MHC-PMS Software?
• What is a Requirements Imprecision Problem?
• What is Completeness and Consistency of Requirements?
• What are the Types of Non-functional Requirements and How are Requirements Implemented?
• What are Non-functional Classifications?
• What Could Be Non-Functional Requirements in MHC-PMS Software
• What are the Usability Requirements in MHC-PMS Software?
• What are Domain Requirements?
* What is Train Protection System Example and How Does It Work?
* What Could Be Problems With Domain Requirements?


• What is a Software Requirements Document?
* The software requirements document is the official description of what software developers need. We can say that it is the document that explains how to set which tasks the software should do.
* Who are the Users of the Requirements Document?
* What is Requirements Document Variability?
-> The information in the requirements document depends on the software type and development method used. Incremental systems will have less details in the requirements document.
* What is the Structure of the Requirements Document?

• What are Agile Methods and Requirements?
• What Are the Specification of the Requirement?
• What are the Ways to Write a Software Requirements Specification?
• What Should the Requirements and Design Be Like?
* The requirements should specify what the software should do and describe how the design does it.
• What is Natural Language Specification?
* What Could Be Problems With Natural Language?
• What Are the Guidelines for Software Requirements?
• Insulin Pump Software System
* What are the Sample Requirements for the Insulin Pump Software System?
* What Is a Structural Example Feature of an Insulin Pump Requirement?
• What is Structured Specifications?
• What are Form-Based Specifications?
• Requirements Analysis
* What are the Requirements Engineering Processes?
* What is Requirements Determination and Analysis?
* What are Requirements Analysis Problems?
* What are the Requirements Analysis Process Activities?

• What is Requirements Discovery?
* It is the process of collecting data about required and available software and purifying user and system requirements with this data.
• Who are the Stakeholders in MHC-PMS?
• What are the interviews for software?
• What are Software Scenarios?
* Scenarios are real-life examples of how to use software.
* What is an example scenario for MHC-PMS?
• What are the Use Cases?
* What are the Use Cases for MHC-PMS?
• What is Ethnography?
* What are the Scope of Ethnography?
* What is Focused Ethnography and how does it work?
* How does the Ethnography and prototyping process for requirements analysis go?
• What is Requirements Validation?
* How to Check the Requirements?
* What are Requirements Validation Techniques?
* How to Conduct Requirements Reviews?
* How are Requirements Controls Reviewed?
* How should Requirements Management be done?
• What are the Changing Requirements?
• How should Requirements Management Planning be done?
• How should Requirements Change Management be done?

195050019
Yunus Emre Bitkay
Thank You For Lesson :)

[ahmetvidin]

in this lecture i learned,
Requirements engineering, What is a requirement?, Requirements abstraction (Davis), Types of requirement, User and system requirements, Readers of different types of requirements specification, Functional and non-functional requirements and for the MHC-PMS, Requirements imprecision, Requirements completeness and consistency, Non-functional requirements, Types of nonfunctional requirement, Non-functional requirements implementation and classifications, Examples of nonfunctional requirements in the MHC-PMS, Goals and requirements, Usability requirements, Metrics for specifying nonfunctional requirements, Domain requirements, Train protection system, Domain requirements problems, The software requirements document, Agile methods and requirements, Users of a requirements document, Requirements document variability, The structure of a requirements document, Requirements specification, Ways of writing a system requirements specification, Requirements and design, Natural language specification, Guidelines for writing requirements, Problems with natural language, Example requirements for the insulin pump software system, Structured specifications, Form-based specifications, A structured specification of a requirement for an insulin pump, Tabular specification, Tabular specification of computation for an insulin pump, Requirements engineering processes, A spiral view of the requirements engineering process, Requirements elicitation and analysis, Problems of requirements analysis, Requirements elicitation and analysis, The requirements elicitation and analysis process, Process activities, Problems of requirements elicitation, Requirements discovery, Stakeholders in the MHC-PMS, Interviewing, Interviews in practice, Scenarios, Scenario for collecting medical history in MHC-PMS, Use cases, Use cases for the MHC-PMS, Ethnography, Scope of ethnography, Focused ethnography, Ethnography and prototyping for requirements analysis, (Requirements validation, reviews, reviews and validation techniques), Review checks, Requirements management, Changing requirements, Requirements evolution, Requirements management planning

195050803
AHMET MUSTAFA VİDİN

[muhtesemkaansengul]

In this lesson i learned
Functional requirements
and Non-functional requirements implementation,
Goals and requirements
,
Metrics,
Users of a requirements document,
Requirements specification
,
Natural language specification,
Form-based specifications,
Tabular specification,
Problems of requirements analysis,
Requirements elicitation and analysis,
Key points,
Stakeholders in the MHC-PMS
,
Use cases for the MHC-PM,
Requirements checking
175050001

[cantutar]

In this lesson, I learned;

+Information about Functional requirements,
+Information about Non-functional requirements,
+Information about Goals and requirements,
+Information about Metrics,
+Information about Users of a requirements document,
+Information about Requirements specification,
+Information about Natural language specification,
+Information about Form-based specifications,
+Information about Problems of requirements analysis,

+Information about Requirements elicitation and analysis,
+Information about Key points,
+Information about Stakeholders in the MHC-PMS,
+Information about Use cases for the MHC-PM,
+Information about Requirements checking.

175050004

[sidodiko]

This lecture are covering requirements Engineering, functional and non-functional requirements, The software requirements document, Requirements specification, Requirements engineering processes, Requirements elicitation and analysis, Requirements validation and Requirements management .Frist of all, we define Requirements Engineering with example about (software company ), we continue with Requirements abstraction (Davis), types of requirement (user requirements and system requirements) and Readers of different types of requirements specification. Second, we describe with examples for each of items Readers of different types of requirements specification, Functional and non-functional requirements, Functional requirements, Functional requirements for the MHC-PMS, Requirements imprecision, Requirements completeness and consistency, Non-functional requirements, Types of nonfunctional requirement, Non-functional requirements implementation and Non-functional classification. Next we continue to define subjects and examples, Examples of nonfunctional requirements in the MHC-PMS, Goals and requirements, Usability requirements, Metrics for specifying nonfunctional requirements, Domain requirements, Train protection system, Domain requirements problems, Key points, The software requirements document, Agile methods and requirements, Users of a requirements document, Requirements document variability, The structure of a requirements document, Requirements specification, Ways of writing a system requirements specification, Requirements and design, Natural language specification, Guidelines for writing requirements, Problems with natural language, Example requirements for the insulin pump software system, Structured specifications, Form-based specifications, A structured specification of a requirement for an insulin pump, Tabular specification, Tabular specification of computation for an insulin pump, Requirements engineering processes, a spiral view of the requirements engineering process, Requirements elicitation and analysis, Problems of requirements analysis, Requirements elicitation and analysis, The requirements elicitation and analysis process, Process activities, Problems of requirements elicitation, Requirements discovery, Stakeholders in the MHC-PMS, Interviewing, Interviews in practice, Scenarios, Scenario for collecting medical history in MHC-PMS, Use cases, Use cases for the MHC-PMS, Ethnography, Scope of ethnography, Focused ethnography, Ethnography and prototyping for requirements analysis, Requirements validation, Requirements checking, Requirements validation techniques, Requirements reviews, Review checks, Requirements management, Changing requirements, Requirements evolution and Requirements management planning. Eventually, The goal of requirement engineering is to develop and maintain sophisticated and descriptive .175050901

[kadirdurmaz]

In this lecture I learned;

*Requirements engineering and what's a requirement?
*Requirements abstraction(Davis), types of requirement(user and system)
*Requirements specification
*Functional and non-functional requirements
*Types of nonfunctional requirement, implementation, classifications, examples and goals
*Usability requirements (goal, testable non-functional requirement)
*Metrics for nonfunctional requirements
*Domain requirements, problems(understandability, implicitness)
*Software requirements document, (not a design document)
*Agile methods and requirements
*The structure of a requirements
*Natural language and problems (lack of clarity, requirements)
*Form-based specifications
*Tabular specification (natural lang is used)
*Requirements elicitation and analysis processes, problems
*Stakeholders, interviewing
*Use cases
*Definition of ethnography and its scope, focused ethnography
*Requirements checking, validation techniques, review checks
*Changing requirements and evolutions, management

Abdulkadir Durmaz
175050008

[eblaekerdiker]

In this lesson i learned the topics below;

-What is a requirement?
-User and system requirements
-Functional and non-functional requirements
-Usability requirements
-Domain requirements
-Train protection system
-Domain requirements problems
-Agile methods and requirements
-Users of a requirements document
-The structure of a requirements document
-Requirements specification
-Ways of writing a system requirements
specification
-Requirements and design
-Natural language specification
-Problems with natural language
-Structured specifications
-Form-based specifications
-Tabular specification
-Requirements engineering processes
-Requirements elicitation and analysis
-Problems of requirements analysis
-Requirements elicitation and analysis and process of it
-Process activities
-Stakeholders in the MHC-PMS
-Interviewing
-Interviews in practice
-Scenarios
-Use cases
-Ethnography
-Review checks
-Requirements management

Ebla Ekerdiker
185050010

[ekremsahin]

165050012
I learned in this video
-Domain requirements
-Train Protection System
-What is a requirement?
-Non-functional requirements,
-Guidelines for writing requirements
-Goals and requirements,
-The structure of a requirements
-Metrics
-Requirements and design
-Natural language specification
-Problems with natural language
-Requirements engineering processes
-Requirements elicitation and analysis
-Stakeholders
-Problems of requirements analysis
-UML
-Changing requirements
-Requirements change management

Thank you for lesson.

[zeynepbaykal]

In this lesson, I learned

-What is a requirement?
- Types of requirements
- Functional requirement
- Use cases
-Stakeholders in the MHC-PMS

185050004

[burakpaker]

In this video covers
-requirements engineering
-Requirements abstraction
-Types of requirements
+User, System, Functional, Non-Fonktional, Domain
-Requirements imprecition
--Usability requirements
-Domain requirements
-Train Protection System
-Domain requirements
+Understandability, implicitness
-Agile Methods
-Users of a Requirements Document
-The Structure of a Requirements Document
-Requirements Specification
-Requirements and Design
-Structured Specifications
-Form-based Specifications
-Tabular Specification
--Requirements Engineering Processes
-Requirements Elicitation and Analysis
-Problems of Requirements Analysis
--Stakeholders in the MHC-PMS
-Sccenarios
-Ethnography
-Requirements management

175050012
M.BURAK PAKER

[alikursun]

In this video, I have learned those in below;

-Functional and non-functional requirements
-Types of non-functional requirements
-Domain requirements
-Train Protection System
-Doman requirements problems
-Agile methods and requirements
-Guidelines for writing requirements
-Form based specifications
-Requirements engineering process
-The requirements elicitation and analysis process
-Requirements validation
-Requirements validation techniques
-Changing requirements
-Requirements change management

165050011

[yagmur]

175050010

In this lesson;
- Information was given about the non-functional requirements and their types.
- What are the metrics for specifying non-functional requirements
- Information was given about the requirements engineering processes.
- Provided information about the requirement features and methods
- How are requirements uncovered and analyzed?
- What are non-functional classifications and examples of requirements are given.

From this course;
Metrics for specifying non-functional requirements; speed, size, ease of use, portability, robustness and reliability.
If domain requirements are not satisfied, the system may be unworkable.
Domain requirements issues are understandability and implicit.
The structure of the requirements document should be listed as preface, introduction, glossary, user requirements definition and system architecture.

[ahmetyusufdiktepe]

In this video i learned that;

Requirements engineering,
What is requirement?
User and system requirement,
Functional, non-functional and domain requirements,
requirements should be consistent and complete,
types of nonfunctional requirement, non-functional requirements implementation, classifications,
usability requirements,
some problems in domain requirements,
agile methods and requirements,
structure of a requirements document,
requirements and design,
natural language specification,
guidelines for writing requirements,
some problems in natural language,
structured specifications,
form-based specifications,
requirements engineering processes,
some problems of requirements analysis,
requirements validation,
changing requirements,

Ahmet Yusuf Diktepe
175050013

[ceydaszr]

I learned,
-what requirement is,
-about user and system requirements,
-about functional, non-functional and domain requirements,
-about requirements completeness and consistency,
-about what are non-functional classifications,
-problems about domain requirements,
-agile methods and requirements,
-about specification of requirements,
-ways of writing a system requirements specification,
-about design and requirements,
-about the process of requirements engineering,
-about requirements elicitation and analysis and problems of requirements analysis.
175050003
Ceyda Süzer.

[freonsp]

Why aren't there real people in these comments????

[simayseyrek]

Requirements engineering,
What is requirement?
User and system requirement,
Functional, non-functional and domain requirements,
requirements should be consistent and complete,
types of nonfunctional requirement, non-functional requirements implementation, classifications,
usability requirements,
some problems in domain requirements,
agile methods and requirements,
structure of a requirements document,
requirements and design,
natural language specification,
guidelines for writing requirements
Simay Seyrek, 195050001

[mrmrdefmr]

O aksanla ve hatalarla nasıl United States diye belirttin videoda. Bir de tüm arkadaşlarını ya da botları örgütleyip yorum yaptırmış. İNANILMAZ BİR UĞRAŞ. ama ne gerek vardı ?

[mustafacagrpeker]

İ learned

- what is requirement
- types of requirement
- functional requirement
- unfunctional requirement
- domain requirement
- requirement and design
- tabular spesification
- UML

Mustafa Çağrı Peker
165050008

[samedarc]

In this lesson i learned:
- what is requirements engineering
- what is a requirement
- user requirement and system requirements
- what are functional requirements
- what are non-functonal requirements and types
- product, organisational and external requirements
- what are usability requirements
- what are domain reuqirements
- agile methods and requirements
- what are process activities
- what is unified modeling language
- what is ethnography
- what are requirements validation techniques

Samed Arıcı - 195050005

[burhanyasbay]

From this video we learned
-What is a requirement engineering
-What are the metrics
-What are usability and domain requirements
-What is ethnography
-What are non-functional classifications



Burhan Yaşbay
195050027