Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • There's an object, called "Application", it's properties can only be changed if its "State" is "INITIAL". This is not a big workflow, like documents flowing from one department to another. What I fail to do is, to reflect this behavior in an object oriented sense. Commented Dec 25, 2015 at 13:14
  • @Reek Application should expose read/write interface, and iteraction logic should take place in higher level. Both applicant and HR uses the same object, but have different privileges - application object shouldn't be concerned about it. Inner exceptions might be used to protect system integration, but I woudn't go to defensive (editing contact information might be neccessary even for approved applications - just need higher access level). Commented Dec 28, 2015 at 20:54