Win a copy of Kubernetes in Action this week in the Cloud/Virtualization forum!

Alex Pavlishin

Greenhorn
+ Follow
since Aug 17, 2008
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
(keep public parts private until JForum day)
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt
Moderation Tools

Recent posts by Alex Pavlishin

Hi,

How many classes and components do you guys have in you class and component diagrams. I have 12 classes and 16 components.

Thanks.
How do we add tagged values to a deployment diagram in StarUML. If I right-click on the Node and select Tagged Values, the Tagged Definition Set in the resulting pop-up is empty.

Any help on this will be appreciated. Thanks!
I have another question regarding the business domain model. The model has a relationship between the DestinationMarket, CarModel and the different parts.

However, I feel that the DestinationMarket and CarModel have no meaning to the system. To me every different car part would be one more element in an Enumeration. As we add more parts, we add more elements to the enumeration. Every new Request for Parts would relate to any one part type in the PartTypes enumeration.

I don't want to tie a part type to a particular car model or a destination market since that seems too restrictive. It is possible that one part type could be used in multiple car models.

So, how are you guys addressing this? And thoughts would be appreciated.

Thanks.
I think you can just mention that you will use WS-AtomicTransactions to handle the update of the request to 'scheduled' and updating the Stock Inventory system in one transaction.

Here is a good high-level read on the topic of WS-Transactions.

HTH
* I don't see anything wrong with using the classes provided in the business domain model and stereotyping them with Entity stereotype. For you Orchestra Director stateless session bean, you can use the Model Facade pattern. It is described very well in the Java EE blueprints at https://blueprints.dev.java.net/bpcatalog/ee5/persistence/ejbfacade.html


* The BusinessDelegate is meant to separate presentation tier logic from business logic. Also, you can handle container specific exceptions in your Business Delegate classes and only pass application specific exceptions to the business tier. And if your project requirements are such that you might need multiple presentation tiers in the future, having a common entry point with a Business Delegate can be very helpful.

However, since the Business Delegate is a POJO, you will not be able to use dependency injection to look up your Session Facade classes. You will have to use a Service Locator design pattern to do that.
Abhinav,

How did you add components to the deployment diagram in StarUML. I just started evaluating StarUML and it seems like it only lets me add predefined components, and those appear as 'text' instead of the usual component icon within the node.

Any advice is much appreciated. Thanks.
In the BDM, there is a one-to-many relationship between Request and PurchaseOrder. Based on my understanding of the assignment, one Request will result in only one PurchaseOrder. So the BDM, in my opinion, is incorrect. Anyone else working on this assignment who feels the same way.

Also, can I indicate in my assignment that I think the model is incorrect and proceed with the solution based on my assumptions.

Any thoughts on this will be appreciated.

Thanks.
Yes. Based on the use case and the assignment description, I think the system should check with the Inventory System for its validation.
Is anyone else working on this assignment for Part II. Seems like I'm the only one with this assignment.