To move beyond "vibe coding" and develop a proper system, you must first accurately analyze the requirements. Furthermore, you need to create scenarios so that these requirements are connected and executable. This covers how to analyze requirements and write scenarios.
Requirements analysis implementation methods
How to succeed in system development
How to define requirements as scenarios
Discover practical requirements analysis and implementation methods
containing the know-how of a developer with 40 years of experience! 📚
To develop a system, you must first accurately analyze the requirements. Additionally, you need to create scenarios so that these requirements are connected and executed. This course covers the specific methods for analyzing requirements and writing scenarios. It does not focus on theoretical analysis methods, but rather on practical, concrete ways to develop a system.
Requirements Analysis, why should you learn it through this course?なぜこの講義で学ぶべきなのでしょうか？
Strategic Approach
To succeed in system (software, project) development, you need strategies and methods. Good programming skills alone do not guarantee the success of system development. However, since system development involving many stakeholders must succeed, it must be developed through strategies and methods. This course covers strategies and methods for successful system development.
How to write a successful scenario
In system development, there must be scenarios that clearly define the requirements. By following these scenarios during program development, you can build systems conveniently and safely. This course covers how to define and write requirements as scenarios. You can learn requirement analysis and implementation methods that lead to successful system development.を扱います。システム開発を成功に導くための要件分析の実装方法を学ぶことができます。
The instructor has been involved in software contract development for over 35 years, including 12 years of running a software development company. Software contract development always involves deadlines, costs, quality, and inspections.
A development environment governed by deadlines, costs, quality, and inspections forced the instructor to develop methods and strategies for successful system development. An environment where project stakeholders inspect the code I wrote turned the instructor into a professional developer.
The key to successful system development is requirements analysis. Contract-based development presents a different environment where development must be completed in a short period. To address this, requirements analysis and system design are integrated. An approach is needed that shortens the development period while conducting a more complete requirements analysis through the integration of development stages.
Know-how perfected through experience
The image shows the book 'Event Process Modeling for Requirements Analysis.' At that time, I was in my 26th year of development. Even after publishing the book, I continued to evolve the requirements analysis methodology by incorporating further practical experience. I have refined those experiences and insights to create this course. This is not just a theoretical lecture; it is a practical course built on over 40 years of experience. The book is now out of print, and this course serves as the final, definitive version.
Analysts who analyze and
define requirements
Project Planner
System Architects
Developers looking to
jump into an analyst role
A course specialized for practical application
This course covers requirements analysis implementation methods for successful system development. It provides practical methods that can be applied to system development requirements analysis right away. This is the only course that covers how to implement requirements analysis.
System Design Included
To ensure a more complete requirements analysis, some content related to system design has been included. This can shorten the system design period, and allows you to proceed directly to program development once the requirements analysis is complete.
To clearly define and analyze requirements, requirements analysis is performed in 5 stages. We approach it by creating the roots, trunk, branches, and leaves of the requirements analysis. Finally, we finalize the requirements to landscape the analysis and create a forest. Previews for the concepts of each stage are provided.
Traveling from Seoul to Busan via Daejeon and Daegu is a single connection and a flow. The results of the requirements analysis must also take the form of a connected flow.要求分析の結果も、繋がった流れの形式である必要があります。
Requirements analysis in the Event Process Modeling method is based on Events, Processes, and Scenarios. When an actor takes an action, an event (the cause, reason, or purpose for executing the next process) occurs. The subsequent process is executed by receiving the event (cause, reason, purpose) generated by the preceding process. Processes are connected to one another through events. Processes are logically connected with a clear basis.
A structure where processes are connected to create a flow like this is called a scenario. If each process is not logically connected, it becomes a scenario lacking a solid basis, which means the requirements analysis was done incorrectly. In this lecture, we will cover how to perform requirements analysis based on logic.
Requirements analysis involves writing scenarios so that requirements can be implemented into a program. The written scenarios are finalized after being reviewed and confirmed by project stakeholders. Program development can then proceed by following these scenarios, which are the result of the requirements analysis. In other words, requirements are solved through scenarios, not through program code.
✔️ You can be reborn as a full-stack developer who develops software creatively.
✔️ You will learn strategies and methods to prevent requirement changes.
✔️ By learning how to define requirements as scenario processes, you will be able to naturally resolve refactoring and clean code issues.
Who is this course right for?
An analyst who analyzes and defines requirements
Software Developer (regardless of programming language)
Vibe Coding
A designer who designs systems
Need to know before starting?
It is not necessary. However, an understanding of programming concepts is required.
9,737
Learners
407
Reviews
337
Answers
4.8
Rating
13
Courses
I am a developer who loves software development.
Email: tonextday@gmail.com
Videos: 11
Rust Build-up: Building a Solid Foundation
Cleanup JavaScript: Jump-up
Cleanup JavaScript: Base Build-up
JavaScript Beginner
JavaScript Intermediate/Advanced
Modern JavaScript (ES6+) Basics
Modern JavaScript (ES6+) Advanced
DOM Basics
DOM Interaction
React Beginner, Complete React
Requirements Analysis Implementation Methods
JavaScript Machine Learning TensorFlow.js
Books: 9 Volumes
Immersion! JavaScript
ECMAScript 6
HTML5
DOM Scripting
JavaScript Regular Expressions
Event Process Modeling for Requirements Analysis
Machine Learning TensorFlow.js,
Ajax Utilization, Complete Analysis of prototype.js
I am the first domestic author for 8 out of these 9 books.
In particular, there were no books related to "Machine Learning TensorFlow.js" on amazon.com at the time of its publication.
Among the 9 books I've authored, including "x Utilization" and "Complete Analysis of prototype.js," 8 are the first of their kind by a domestic author. In particular, when "Machine Learning TensorFlow.js" was published, there were no related books available on amazon.com.
Among the 9 books I have authored, including "x Utilization" and "Complete Analysis of prototype.js," 8 were the first of their kind by a domestic author. In particular, when "Machine Learning TensorFlow.js" was published, there were no related books available on amazon.com.
All
84 lectures ∙ (8hr 52min)
Course Materials:
All
3 reviews
4.7
3 reviews
Reviews 1
∙
Average Rating 5.0
5
This seems like a really good class for supplementing the inadequate aspects of design that occur in actual work.
Thank you.
Reviews 7
∙
Average Rating 5.0
5
I listened to it once quickly, and from the second time on, I read it carefully. Even the teacher, who has a meticulous personality, had typos, and it felt human :) At first, I didn't even know what requirement analysis was, and I listened to everything the teacher taught without thinking because I wanted to see everything, but as I worked, I did a rough requirement analysis of my boss's request and made a rough screen design document (because I didn't learn how to do it properly, I kept working like that and didn't worry), and the work style of just talking here was so difficult (because all the situations mentioned in the lecture happened...), so I watched the second time really understanding one by one with the intention of doing requirement analysis and design. It was fun and I was looking forward to the next video. I watched it all and enjoyed it. I want to apply it one by one to my work in the future and watch the video again and again. I'm struggling with the development work that's just talk and such incompetence, but thanks to you, I'm working thinking that I've learned and gained skills. Thank you for making the video so hard.
Thank you. It feels like you have entered the world of professionals. Congratulations. If you develop your current thoughts, you will develop the belief that if you leave it to that person, the job will be done successfully. I support the beautiful world of professionals.
Reviews 2
∙
Average Rating 4.0
$77.00
Check out other courses by the instructor!
