Search results for query: *

I think Mike has some good ideas here. Fundamentally, you need to consider minimising your coupling between your main domain layer and the driver layer. If you do this correctly, you can swap your driver layer for another (you would need to implement some classes for the new layer), and your...

However...eh hm...taxonomically, a rectangle and a square could be a shape, but depending on how you work with your classes, rectangle being a square or vice versa wouldnt work. If you decide a square is a type of rectangle you run into problems. If you decide a rectangle is a square, you run...

Interjecting... Since this is the OO group, why not consider building an OO solution to the problem? Nick.

Requirements Determination is also known as Requirements Analysis, or Requirements Gathering. In OO/UML you will probably use Use Cases, Scenarios, Activity Diagrams and possibly state diagrams depending on what you are doing. Nick.

To add my two pence... In system design, the concept of <<interface>> doesnt necessarily mean Ixxxx, be it in C++/COM, VB, Delphi or whatever. It is a conceptual term to refer to something abstract. Earlier in design something could be demarked as <<interface>>, but later turn into a class...