Oh well from a design aspect theres structural/functional design Why? Using the UML Class diagrams can sometimes be particuarly abstract, showing the set of classes each with their own attributes/operations. You don't really get a clear idea of what classes rely on other classes from a functional point of view...like say an operation in class x uses something from class y etc...functional design clearly shows it whereas object wise you dont see it quite as clearly because the system is broken down, funnily enough, by its functions. If you take a functional viewpoint, you look at the actual functionality of the system, structually IMO it's easier to see the concept of the actual use of a system better than you can with UML, you get a clear picture of what the system does, and how. Clear illustrations of calls to modules, data passing etc. Personally i much prefer structured & functional design to object oriented methods, easier to envisage & implement.....and actually DO for that matter, saves the fannying on drawing UML diagrams. Thats my 2 pence anyway
going by that description u could also add that with a structural design being easier to see how the system will work then it would be a lot more useful to the prospective company/client that it will be used for, as they will be able to understand the functionality and work process of the system much easier.
Exactly Genearally i think object oriented analysis/design is a load of bollocks and a waste of my time
