2025Year

Second Semester

Software Engineering

Lecture

Software Engineering

Z1900023 Software Engineering

INOKI Mari

2.0Credits

Fri.2Period

Shinjuku Remote

A) A high degree of specialized expertise　100%
B) The skills to use science and technology　0%
C) The ability to conduct research independently, knowledge pertaining to society and occupations, and sense of ethics required of engineers and researchers　0%
D) Creative skills in specific areas of specialization　0%

In software product development, it is extremely important to improve the quality of the requirements definition process, which clarifies what the customer desires.
We will learn requirements elicitation methods so as to gain the ability to elicit and organize diversified requirements from various stakeholders including clients, users and developers productively .

Programming experience, basic knowledge of object-oriented technology and UML

Project Based Learning／Discussion Debate／Group Work／Presentation／Interactive classes using ICT

[Unit 1] Overview of requirements engineering
An outline will be provided regarding issues including the definition of requirements, requirements engineering standards, the requirements engineering body of knowledge, the quality of requirements, requirements elicitation methods, and requirements prioritization methods.
Preparation: Close reading of the explanatory materials distributed in advance.
Review of object-oriented techniques and UML notation.

[Unit 2] Stakeholder analysis, interview method and negotiation method
Preparation: Close reading of the explanatory materials regarding the stakeholder analysis and the requirements elicitation method distributed in advance.

[Unit 3] Development of the requirements specification and use case analysis
Preparation: Close reading of the explanatory materials regarding the requirements specification, use case modeling and functional requirements distributed in advance.

[Unit 4] Specifying functional requirements, use case modeling and its case studies
Preparation: Close reading of the explanatory materials in advance.
Create a use case model with the presented example.

[Unit 5] Scenario analysis and claim analysis
Preparation: Close reading of the explanatory materials in advance.
Create a scenario description with the presented example.

[Unit 6] How to feed back the results of the scenario and claim analysis to the use case model
Preparation: Close reading of the explanatory materials in advance.
Create a draft feedback method for the use case model with the presented example.

[Unit 7] Management, verification and validation of requirements
Preparation: Close reading of the explanatory materials regarding the stakeholder analysis and the requirements elicitation method distributed in advance.
Preparation: Close reading of the explanatory materials in advance.
Create a draft requirements verification method for the requirements specification with the presented example.

[Unit 8] Overview of design thinking-driven requirements engineering
An outline will be provided regarding issues including the design thinking, the entanglement of design thinking and requirements engineering, and design thinking-driven requirements elicitation.
Preparation: Investigate the difference between the conventional and design thinking-driven requirements elicitation methods.

[Unit 9] Design thinking-driven requirements elicitation methods: overview of various modeling methods
Preparation: Close reading of the explanatory materials in advance.
Investigate in advance what kind of design thinking modeling method has been proposed.

[Unit 10] Case study of design thinking-driven requirements elicitation: persona, customer journey map
Preparation: Close reading of the explanatory materials in advance.
Create a draft persona and a customer journey map with the presented example.

[Unit 11] Case study of design thinking-driven requirements elicitation: prototyping and feedback for the use case model
Preparation: Close reading of the explanatory materials in advance.
Create a draft persona and a customer journey map with the presented example.
Create a draft feedback method for the design thinking-driven use case model with the presented example

[Unit 12] Review of requirements elicitation methods
We will once again review the various requirements elicitation techniques, and have discussions regarding how requirements engineering in the new normal era should be.
Preparation: Close reading of the explanatory materials distributed in advance.

[Unit 13] Problem and solution approach for conventional or design thinking-driven requirements elicitation methods
Preparation: Clarify the problems of how to elicit requirements based on conventional or design thinking, and extract the ideas to solve the problems.

[Unit 14] Requirements elicitation and specification: Assignment I, Assignment II
In order to establish and affirm an understanding of the various requirements elicitation and specification techniques, we will work on Assignment I (on eliciting and specifying requirements) and Assignment II (overall review of requirements engineering).
Preparation: Review the explanatory materials distributed so far.

[Unit 15] Assignments I and II review
Preparation: Extraction of any unclear points relating to Assignments I and II.

Grades of 60% and above, based on an evaluation of performance in exercises and the quality of Assignments I and II, will be considered passing grades.

Each assignment presented during a unit will be explained at the beginning of the next unit.
A review of the 14th assignments will be presented to KU-LMS in the 15th unit(on-demand).

No particular textbook will be assigned. Materials will be distributed in advance.

[1] JISA, REBOK WG, REBOK Requirements Engineering Body Of Knowledge, Kindaikagaku-sha, in Japanese, 2011
[2] JISA, REBOK WG, Requirements Engineering Practical Guide: REBOK series2, Kindaikagaku-sha, in Japanese, 2014
[3] Strategic IoT Management,. Minervashobo., in Japanese, 2019

Thursday:16:00~17:00 Sinjuku A-2315 (Software Engineering Laboratory)

Through lectures, case studies and discussion, we will systematically study the various forms of requirements elicitation methods that pertain to software product development.

Applicable

製品ソフトウェア開発の経験がある教員が、開発方法論の開発と管理の技術力を活かし、デジタルトランスフォーメーションの実現を目的としてソフトウェア工学、要求工学について講義する。

Informatics Program