Hi Shaquille, > Let me know what you think or if you have any further > questions/concerns.
I do understand the model. However I still have some questions. The first question is that you have modelled this in the logical view. I would think it is something for the use case view, to clarify a usecase. I wouldn't use the swimlanes for client and server side during requirements. I don't know anything about client and server application in that stage of development. However, I have attached the model I had in mind: My idea is that the 'check password data' activity in the diagram is clarified in the documentation of the activity. I don't think the diagram would be clear if you would model each of the following checks seperately: 'length > 6', 'new password == new confirm password', 'old password is correct password' etc, but you do have to define what the system will do in these cases and what error message should be show. I think this is done best using the documentation, but I was wondering if anyone had any other ideas about that? Or do you have comments on this model? Greetings, Arno Leenders ----------------------------------------------------------------- ATTENTION: No legal consequences can be derived from the content of this e-mail and/or its attachments. Neither is sender committed to these. The content of this e-mail is exclusively intended for addressee(s) and information purposes. Should you receive this message by mistake, you are hereby notified that any disclosure, reproduction, distribution or use of this message is strictly prohibited. Sender accepts no liability for any damage resulting from the use and/or acceptation of the content of this e-mail. Always scan attachments for viruses before opening them. -----------------------------------------------------------------
datacheck.zip
Description: Binary data
