From the course: Software Design: From Requirements to Release
Unlock the full course today
Join today to access over 24,600 courses taught by industry experts.
Requirement validation
From the course: Software Design: From Requirements to Release
Requirement validation
- [Instructor] Requirement analysis needs system functionalities specified in some form. Either use cases or user stories. Analyzing user stories, helps identify conditions of satisfaction or acceptance criteria for the functionality, and analyzing use case specifications helps us identify domain classes, their attributes and associations. This gives us domain diagrams that are structural representation of our system in terms of, key entities and their attributes. These entities most often translate into, design classes and database tables. From the use case diagrams that we created, let me pick one which I will use just as an example here. One of the simplest ones here is the search food products use case. Let us look at its user story first. Following the standard user story format, we can write it as, as a user, I want to search for a food product by name, so that I can see its nutritional value. What this…
Contents
-
-
-
Define problem and vision statements4m 58s
-
(Locked)
Elicit and specify requirements5m 51s
-
(Locked)
Requirement validation6m 31s
-
(Locked)
Technology validation7m 45s
-
(Locked)
Proof of concept (POC) setup5m 28s
-
(Locked)
POC implementation8m 29s
-
(Locked)
POC deployment7m 16s
-
(Locked)
Challenge: From dev to deploy31s
-
(Locked)
Solution: From dev to deploy2m 4s
-
-
-
-