Arvind Tiwari

Greenhorn
+ Follow
since Jun 23, 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
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Arvind Tiwari

Hi All,

Passed part II & III.

Thanks for all the help and support.

Arvind
Hi All,

Passed part II & III.

Thanks for all the help and support.

Arvind
Hi Gurus,

Are you guys are planning to apply any core design pattern?
Please share your ideas.

Thanks,
Arvind
Hi Gurus,

Are you guys are planning to apply any core design pattern?
Please share your ideas.

Thanks,
Arvind
Hi Gurus,

Are you guys are planning to apply any core design pattern?
Please share your ideas.

Thanks,
Arvind
Hi Guys,

First of all thanks for responding to my queries.


I am totally with Scott regarding first Use case and PO relationship and following is my view.

A request can have more than one item (sub request) of same part which has same specification for different procurement date. In this case multiple PO will be issued to the winner.


Christian:
Could you please put more light in following statement, how you can use a generalized class to represent all the part types. As per OOD you have to go with specialized classes if the behavior changes, in our case there could be 1000 for part type in future and all may have different algorithms to generate the specification.
(Specification: Complete part specification which will be given in the auction request for supplier)

I use generalization for represent all the type of parts, because the design has to be extensible.



I would like to discuss more on extensibility because that look biggest challenge to me.

Thanks
Arvind
Thanks Ronald for the prompt response, I will assure that we will discuss the project within the rule. Feel free to point me if I violate the rules.

I also have done something (class diagram, component diagram and sequence diagram) but got some confusion as following, please share your views.

1. How to show (class diagram/component diagram) that my design is extensible?

The BDOM is showing three classes (Brake Pad, Brake Discs, suspension) but we need to make the design extensible." with additional part types coming in later phases."

In my opinion, if there is one more part them there will be one more class added in the class diagram and there will one more master table (i.e. headlight master) in the database.
(Sorry I am thinking the implementation)

As per following comment to address extensibility but that violates the OO design, you should have specialized classes for specialized part.

"Pratik Das: I have replaced the three parts with a single class part type but I have not used the enumeration. Using enumeration will entail changing the class model each time we add a new part type."

2. Why we need to initialize all the part type object, all we need is the part specification in the request object and quantity?

3. For the 1st use case, are we going to have multiple part types in single request o?
Then only we can justify 1-* relation between request and PO but if the request will have single item then it is in correct.
Hi Ronald,

Are you still working on this project?

If yes lets start working on it.

Thanks,
Arvind
Dear All,

I am also working on the same assignment, I have following three questions.

1. How to show (class diagram/component diagram) that my design is extensible?

The BDOM is showing three classes (Brake Pad, Brake Discs, suspension) but we need to make the design extensible." with additional part types coming in later phases."

In my opinion, if there is one more part them there will be one more class added in the class diagram and there will one more master table (i.e. headlight master) in the database.
(Sorry I am thinking the implementation)

As per following comment to address extensibility but that violates the OO design, you should have specialized classes for specialized part.

"Pratik Das: I have replaced the three parts with a single class part type but I have not used the enumeration. Using enumeration will entail changing the class model each time we add a new part type."

2. Why we need to initialize all the part type object, All we need is the part specification in the request object and quantity?

3. For the 1st use case, are we going to have multiple part types in single request? Then only we can justify 1-* relation between request and PO but if the request will have single item then it is in correct.

Please give your thoughts

Thanks in advance.
Arvind Tiwari
Hi All,

I am stuck in one place, please help.

I wanted to show the validation and current bids (to support open auction) to bidders and would like to use AJAX.
Don�t know how to show it in sequence diagram and even in the component diagram, let me know if you guys have any idea.

Thanks,
Arvind
9 years ago
Hi All,

I am almost done, but stuck in one place

I wanted to show the validation and current bids (to support open auction) to bidders and would like to use AJAX.
Don�t know how to show it in sequence diagram and even in the component diagram, let me know if you guys have any idea.

Thanks,
Arvind
Thanks Ashish, for all the suggestions and help.
9 years ago
Hi Ashish,

Thanks for the prompt response and suggestions.

The confusing part is even Mark Cade mentioned session bean classes while extending his BDOM in the class diagram.

Regards,
Arvind
9 years ago
Hi Ashish,

*Congratulations for the excellent score*

This is Arvind and I am working part II assignment and really got confused, following are my queries.

1. What extra classes after from given BDOM should I show in the class diagram (i.e session bean, application server, singleton class, JSF managed bean)

2. I have to implement a MDB, will it go to the class diagram?

3. I am using JSF for the presentation layer should I show there JSF classes in class diagram?

4. I have mainly 5 JSF screen as per the use case, is it recommended to have only one component diagram and show all the use case flow in one?

5. Do I need to show all the 5 JSF in one component diagram?

6. As per my design, transaction is going to be the important factor should it be shown in the sequence diagram?

7. In some of my use case I have to update inventory and as per the assignment the inventory system will be accessible through a web service. Transaction is important here to update the inventory and web service does not support transaction. Since transaction is important here what do you recommend should I assume there is a Java interface (i.e. SLSB) to inventory and create my design based on that?

Thanks in advance.
Arvind
9 years ago
Hi Alex,

I am stuck at one place.

Since the inventory is only accessible through the web service it means for inventory update (use case 5,5) will be handled by this web service.

If that is the case then how to handle the transaction, I dont think there is a way to handle transaction with web service call to update the inventory.

Please let me know your thoughts.

Thanks,
Arvind