Do Request , View and Processor need to display in Class diagram?
Joined: Aug 25, 2005
I am starting my diagram and meet the following issue.
Do we need to display the following class in the class diagram?
1. Requests (class transfered from presentation layer to business logic, it has value object and screen information ) 2. Views (class transfered from business logic to presentation layer, it also has value object and screen information ) 3. business logic (such as facade and bunsiness processor )
In addition, do we only need to care about the mention four use case: prepare itinerary, change itinerary, price itinerary and pay itinerary?
do other use case such as login need to display in class diagram and component diagram?
Joined: Mar 28, 2005
Hi, this is where the SCEA gets a lot of people. The class diagram that SCEA wants to see from you are not those classes that you will show when you are actually coding. Instead, you put your domain objects there. Remember that business domain object diagram? You suppose to expend on that and put that in your class diagram. It should also be technology independent.
You can place all those thing that you mentioned in the component diagram. [ August 30, 2005: Message edited by: Jeremy Hsu ]