Architectural Designs

software architectural design & object-oriented design?

what are the differences between software architectural design & object-oriented design? can provide me some examples?

Public Comments

1. Well Object-oriented design is about breaking down a problem into units (objects) that can then be developed. Software architectural design i suppose would be a step above that. It would be the major design decisions such as what platform, how to organize modules etc. The overall plan & layout of the problem if you get me. Object-oriented design would be the process of deciding on the actual logical objects within the program itself.
2. These are not different types of design. Software architecture refers to the plan as it emerges from the specification, showing the details of the objects, types, and the relationship between the objects. "Object oriented design" is just a new name for State Driven Programming and refers to the structuring of programs about arrays instead of about subroutines. The phases involved in project development are: a) Conceptualisation b) Work breakdown c) Specification d) Programming e) Testing & debugging f) Publication Unlike state driven/object oriented approaches, software architecture (as opposed to operating system architecture)has nothing to do with the programming itself. Software architecture refers to the style or method of program specification that occurs long before any code is written for a large project. "Software architectural design" could be used in some circles to refer to spaghetti code while trying to pretend to sound educated at the same time? A great deal of jargon evolves for no other reason than to confuse the audience and thereby make the speaker appear more knowledgeable than s/he really is. The word "paradigm" has only one correct use - as a reference to the complete list of tenses for a verb. All too often it is misused when more sensible words such as, "model" are actually more meaningful. The only people in my experience to ever "smash a paradigm" were Microsoft when they defied linguistic convention to make the verb (method) part of the noun (object) in their visual programming languages instead of treating the verb as an independent element. This incidently, lies at the heart of object oriented programming. Unfortunately for object oriented fans, independent subroutines are nearly always faster than the subordinate method. It is also possible that "software architectural design" may refer to the more linguistically conventional design model that treats arrays and subroutines as equal components or at the other extreme the later approach of treating subroutines exclusively as components with arrays subordinate to or otherwise contained by the subroutines. I hope this helps...