Chapter 9 will focus on scenario bases modeling. Throughout analysis modeling, your focus should be on what, not how. While everything may not be known, we can approach this in an iterative method refining the model until everything is uncovered. The requirements model should have 3 primary objectives: Elements of an analysis modeling: Requirements Analysis…
Each requirement, when modeled, should be examined for: inconsistency, omissions, and ambiguity. You also need to check for: Requirements negotiation is often used to help ensure that requirements are reasonable, and can be met in a reasonable amount of time. You should look to a win-win situation, not a winner takes all contest. Validating Requirements…
The first step is developing a use case is defining a set of actors. While it will normally be a “user”, it might also be “an automated/scheduled system”, “an administrator”, etc. There will likely be different actors in the system, or different roles that the same person might play. When building the use case you…
Ideally everyone from stakeholders to developers would work on the same team and be of the same mind, but that isn’t always the case. In fact, that is rarely the case. Defining the Stakeholders The “Anyone who directly or indirectly benefits from the system being built” is a little too vague in my opinion. Instead,…
