Created
April 3, 2013 13:36
-
-
Save JefClaes/5301262 to your computer and use it in GitHub Desktop.
Four eyes principle applied with commands
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 1. When the user adds an accountnumber, a command gets sent which isn't handled yet. | |
| 2. When a supervisor logs on, he gets a list of commands to approve or decline, including the AddAccountNumber. | |
| 3. When the supervisor approves the AddAccountNumber command, it will be handled. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The problem IMO is that the modeled commands don't capture the language. There are two commands here: one is a request for approval, the other is the actual work to be done once it is approved. Digg deeper into what the supervisor and end user want. What's the message flow upon decline? Chances are you'll need to notify that end user (indirectly using a list or a status on his original request). Maybe you'll uncover that a request is a separate thing in your model the end user wants to interact with (i.e. the request he wants to follow up on). The hardest part is giving these things a name.