Tag Info

New answers tagged

3

Personally being a Sr. Software Configuration Manager for many years (10+) I hear the terms mismatched in a variety of real life situations. It is not uncommon for non technical personnel due to the relative nature of the positions. They both have specific roles, needs and requirements that are similar but yet can be clearly divided in my opinion. I ...


0

Firstly, congratulations on recognising that inheritance is a poor choice in this situation. You are 100% correct. Changing the type of an entity at run-time is definitely code smell! @Doc Brown's answer is getting to the heart of the matter, especially the comment about using Person rather than User, and allowing a 1:many between Person and roles. What is ...


1

What you have sounds like what is known as an Epic. This is basically a user story that is too large to be implemented, tested and accepted in a single sprint. This should typically be the starting point to go back to the customer and try to derive more details and specifics around what they want. You should be doing this as a regular part of your backlog ...


1

A user story is actually some text of your customer. You should split that story into valuable backlogs. If it's hard for you to write them, because they take too much time to be reasonable valued you have to consider a story split. That means you talk to your stakeholder and recompose the user story in more smaller user stories. The thing is, that scrum is ...


0

One way is that we have an Inheritance Hierarchy of Users which each one has his own data and his own behaviors (for example in one clinic we have doctor, patient and Secretary that all of them are derived of the user.) That's IMHO not a good approach. You have persons (IMHO a better term than "users"), and "doctor", "patient", and "secretary" are ...


1

Why don't you separate the concepts? Have one bounded context to handle the user identity. This BC will have all data related to the person itself. This should answer "Who is that user?" Have another BC to control the roles which each user have. This BC will be responsible for answering "Is this user allowed to do that?" And a 3rd BC for the operations ...



Top 50 recent answers are included