Project Organization
I have been having a discussion with a colleague about the best way to organize a (C#)project after he reorganized a project I had been working on from something that looked like this:
How to divide OO project into packages?
I’m a hobbyist programmer working on my own projects. I use Java.
How to divide OO project into packages?
I’m a hobbyist programmer working on my own projects. I use Java.
How to divide OO project into packages?
I’m a hobbyist programmer working on my own projects. I use Java.
How to organize repository branches? [closed]
Closed 9 years ago.
Why do we use non-descriptive internal codenames? [closed]
Closed 9 years ago.
What do you call classes that do arbitrary work in your project? [closed]
Closed 9 years ago.
What do you call classes that do arbitrary work in your project? [closed]
Closed 9 years ago.
Enterprise application object oriented modeling for user and role
Generally in the Enterprise Applications like ERP or ERM, CRM, BP etc. we see two things a lot, one of them is Role and the other one is User. What happens is that in the real world we have some persons as the Audiences of the Organization and also we have some roles that each person do his duty as that role. Actually each person has his own information in his file, dependent on the role that he has. Notice that one person can has more than one role.
What to do with user stories that depend on horizontal integrations?
How do you handle a user story when it depends on horizontal integrations in an application?