Modern requirements gathering is all based on the work that our users perform in the domain. The focus is on value to the user, not technical considerations. This video introduces you to the essential concepts.
- Now that we've learned something … about both the job and the big picture, … let's look at the actual work. … How do you create an architecture? … Every architect has his or her own approach. … I'll describe my approach in this chapter, … but there are others. … There are three main phases: defining the problem, … developing the user stories, defining the structure. … Note that I'm just skimming the surface of this process. … It can take days to really cover this stuff in depth. … I wanted to give you the big picture, though. … Also, I'm presenting this as a linear process, … but in practice, … all three of these steps often happen in parallel. … That being said, let's start at the beginning. … The first thing I usually do … is write out a so-called problem statement. … I say so-called because a problem statement does two things. … First of all, it describes the end user's problem. … And if there isn't an end user problem to solve, … why are you even writing the software? … It also describes the solution to the problem, however. …
- What is software architecture?
- The architect's day-to-day job
- Architectural theories and concepts
- Gathering requirements
- Identifying bounded contexts and entities
- Categories of architecture
- Architectural patterns