In addition, there are probably other things the user might Similar issue for a the success of the DB store. IOW, the user needs toĪcknowledge the message before the application can close. Simply close before the User reads the message. For exceptions it seems to shut down after displaying a I also believe you need to think about how to indicate the applicationĬompletes. Manifested in error messages to the WebAPI as they are detected and the Aren't thoseĮxceptions already handled by the previous processing? IOW, they are I don't really understand what the 'or' clause is about. Message with the updated record as an argument going back User. If it is a person, wouldn't that justīe a display via WebAPI? If it is other software, then you need a > DTO), or an exception (either from the business logic layer, EF or the If commit succeeds the user gets the updated record (mapped back to I would like some guidelines on how I might proceed to show the validation steps above in the sequence diagram. If commit succeeds the user gets the updated record (mapped back to DTO), or an exception (either from the business logic layer, EF or the database). The db might throw an exception if the commit failed, or success if the commit succeeds.Ĩ. If validation succeeds, EF tries to commit the changes to the db.ħ. If validation fails, an exception is thrown. Before actually committing, Entity Framework performs another validation of the model. If validation succeeds, the model is passed to the Save method of the Data Access Layer, which uses Entity Framework to commit the model to the db.Ħ. If the validate method fails, an exception is thrown back to app (through the Web Api layer).ĥ. The Save method in turn calls a Validate method which validates the model according to business logic. This model is then pass to the Save method of the service layer.Ĥ. This layer simply convert the DTO received from the client and maps it to a domain model. If all mandatory fields are not empty, the app makes a Post request to the Web Api layer. If the method fails, a message is shown save is ended.ģ. The Save method calls CheckAndShowMessage which validates empty mandatory fields. We have an existing application and I would like to draw a sequence diagram which shows what happens when the user wants to save a record in the db.Ģ. I'm new to UML so I'm still learning about the different diagrams and elements.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |