On Wednesday, 26 March 2014 8:49 PM, Dileepa Jayakody
<[email protected]> wrote:
> Hi Dan, David and all,
> Above class diagram only contains the domain entities. Perhaps David's
> question on the domain requirements could be clarified if domain service
> classes are also included in the diagram. Shall I do so?
No. Please don't do that. Stick to the domain object model (leave out any view
objects also). Key attributes and methods will aid in understanding it.
So .. you are saying that the reputation analysis/scoring is not part of the
domain for the application but is a separate component? In that case I am
correct in saying it is an external service (whether it runs in the same
processor space or accessed via a web-service is irrelevant - the fact is that
it is not part of the domain of the ISIS based application).
I must say that this is an ambitious project with a lot of integration - what
is the overall objective? Just to prove that ISIS is a rapid prototyping tool?
In which case I would "stub" out all the integration points and have some fake
random reputation scoring code sitting behind the service otherwise all your
effort will go into writing the SI layer and the reputation analysis/scoring
and ISIS does not help you one jot with that.
Regards,
David.
