UML idea for objects with similar characteristics.

![enter image description here][1] [1]: Events, jobs, self and contact are nothing but DTO objects where each objects can be added, edited and deleted from database. I am not so familiar with use case diagrams so I wanted to know if this is correct or can be improved. Is there something to be generalised here? add edit and delete methods in implementations are handled by one class. but the call are handled separately for each object. Is this ok?

以上就是UML idea for objects with similar characteristics.的详细内容,更多请关注web前端其它相关文章!

赞(0) 打赏
未经允许不得转载:web前端首页 » JavaScript 答疑

评论 抢沙发

  • 昵称 (必填)
  • 邮箱 (必填)
  • 网址

前端开发相关广告投放 更专业 更精准