OOAD Concepts

Hey guys

I've been reading a few books and web sites on OOAD, OMT & OOSE and am a bit lost. I understand that Use-case diagrams came from OOSE but I don't know what specific concepts came from OMT and OOAD. I've had a long look around the internet but am at a lost. I think that class diagrams and object diagrams come from OOAD but can't seem to verify this anywhere.

So basically.
1) What concepts are unique to OOAD or were essential parts of OOAD
2) The same question but for OMT.

Cheers folks
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Object Oriented Analysis & Designing or OOAD concept stands upon the software life cycle that Analysis -> Design -> Implementaion.

Analysis:~ Analysis builds a model of the real-world situation showing its important properties. The analyst must work with the requestor to understand the problem because problem statements are rarely complete or correct.

Design:~ This phase has 2 levels, System Design & Object Design. The system designer makes high-level decisions about the overall architecture. During system design the target system is organized into subsystems based on both the analysis structure and proposed architecture.

Where as the object designer builds a design model based on the analysis model but containing implementation details. The designer adds details to the design model in accordance with the strategy established during system design.

Implementaion:~ The object classes and relationships developed during object design are finally translated into a particular programming language, database or hardware implementaion. Programming should be a relatively minor and mechanical part of the development cycle.

Object Modeling Technique or OMT is the methodology that combines 3 views of modeling systems - Object, Dynamic and Functional Model. Object model represents the static, structural, data aspects of a system. The dynamic model represents the temporal, behavioral control aspects of a system. And the functional model represents the transformational function aspects of a system. A typical software procedure incorporates all these three aspects. It uses data structures(object model), it sequences operations in time (dynamic model) and it transforms values (functional model). Each model contains references to entities in other models. For example. operations are attached to objects in the object model but more fully expanded in the functional model.

Hope this helps

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
levyukAuthor Commented:
Dude that's some good information. Pity it wasn't easy to come across online.

I'll keep this open for a bit incase I have some more questions or somebody else has something to add.
>> "Pity it wasn't easy to come across online" may I ask what u try to say by this?

levyukAuthor Commented:
The information you gave me. I wish it was easy to find online.
Anyways best of luck, hope someone may help u soon

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Programming Theory

From novice to tech pro — start learning today.