why do u say the OOAD Process is confusing? Its true that there is no fixed set of steps to be followed in any OOAD Process of Software Development. But I look at it as finding the objects, their collaborations, interfaces, packages as some visible outcomes of teh process. So if you know what are you looking at while following the process, i believe it can't be confusing. UML Distilled is the best. tnx.
You are right. There is no standardlized process for the ooad development. Basically, some people like use case driving and other people like responsibility driving. No single process meets the demands of all possible reality problems. By confusing I mean the development management process. To me this is a field even more confusing than that of object development. My question is how do you make judgement on a matter which is not clearly defined. We face exactly the problem in the OOAD/UML test. Can you recommend any resources on this topic? Thanks.
We noticed he had no friends. So we gave him this tiny ad: