Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Architecture Paper #7
Instructions for Reviewers: First of all, thanks so much for doing this! I’m really proud of this paper and want it to be my best work yet. This means that I’m approaching this from all angles. I’d appreciate your feedback on these things specifically:
Sections not implemented yet:
A use case, I'd argue, has a user/business goal.
It seems like sentences like:
have a particular thing in mind which is not inherent to a use case. I think there's some mingling of the idea of a use case (which describes a system) and some object inside of a system. A Context object in a DCI architecture has the job of encapsulating the interactions among the roles of a system. Often this is confused with a service object.
I agree that this should have more about the domain which would be relevant to the roles and their goals in a use case.
This reads sort of like you are describing a Context object from DCI. In both use case terminology (from Cockburn) and DCI terminology there isn't required input, but a user action which triggers the use case or interaction of objects. But the "required input" makes me think this is something else (unless you mean trigger).