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.
Main Topics
Browse All TopicsHey 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
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: MilanKMPosted on 2006-04-17 at 06:24:52ID: 16468834
OBJECT ORIENTED ANLYSIS & DESIGNING ---------- ---------- --
----------
--------------------------
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
--------------------------
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
MilanKM