動画検索
関連広告
検索結果
1 | Intro
2 | Solutions Architect's responsibilities
3 | The advantages of clear communication
4 | What are Non-functional requirements (NFRs)
5 | A real example of building NFRs for the video-on-demand platform
6 | Reliability
7 | Portability
8 | Cost
9 | Maintainability
10 | What I think about monolithic applications
11 | Conclusion
Introduction to the episode
What are Non-functional Requirements?
Let's take an example of a Chat Application, what are NFRs?
Paul's experience with Non-Functional Requirements
Who is responsible for gathering NFR's? How should we approach NFRs?
How do we approach estimating cost of having something vs not?
How futuristic should we be when it comes to NFRs? 2 years? 5 years?
Is security a Non-Functional Requirement?
How should we document Non-Functional Requirements?
Where does observability come into the picture?
When Functional Requirements impact NFRs
Top 3 things developers can do to approach NFRs