Home.... | log in.... | Pub my question! | Sign-up....

Java-index >> Other Topics >> Patterns & OO Design

OOAD steps

Can someone explain the different steps we follow while designing a project using OOAD and UML.Thanks to all of you.Satya

[142 byte] By [tsatyawali] at [2007-9-27 21:23:03]

«« what is wrong here, jsp
»» disk space

# 1

> Can someone explain the different steps we follow

> while designing a project using OOAD and UML.

> Thanks to all of you.

> Satya

Hello,

UML doesn't describe any procedure or sequence of steps.

OOAD uses UML notation.

In OOAD you follow the following steps:

1) Initial analisys

2) Analisys of System Objects and Classes

3) Dynamic Modeling

4) Object Model Design

5) Dynamic Design

6) System Design

Tipically, in every step you use more UML diagrams.

Regards

Paolo

pvercesi at 2007-7-7 3:17:51 >

top of Java-index,Other Topics,Patterns & OO Design...

# 2

Paolo,Thanks for the response. Can you please tell me small desc. of all these steps or if you have any idea from wehere I can get these details.It would really helpful if there is any case study available on the net.Thanks again for the reponseSatya//

tsatyawali at 2007-7-7 3:17:51 >

# 3

The following are the steps I use for OOAD using UML.

1)Identifying users, Actors and then write the usecases.

2)Drawing sequence/collaboration diagram

3)Drawing activity diagram

4)Identifying objects/Classes/interfaces. Then draw the class diagram of the system.

Sachin.

sparandker at 2007-7-7 3:17:51 >

# 4

Hi All,I have recently started with the OOAD designing with UML.Any specific doc. or case study link will highly appreciated?RegardsSatya

tsatyawali at 2007-7-7 3:17:51 >

# 5

Hi. For a good overview of using UML, try UML Distilled.For a brief introduction to OO analysis and design, try Bruce Eckel's Thinking in Java chapter 1 section on "Analysis and Design." (Thinking in Java is available at www.bruceeckel.com as a pdf)-y

ybakos at 2007-7-7 3:17:51 >

# 6

> The following are the steps I use for OOAD using UML.

> 1)Identifying users, Actors and then write the

> usecases.

> 2)Drawing sequence/collaboration diagram

> 3)Drawing activity diagram

> 4)Identifying objects/Classes/interfaces. Then draw

> the class diagram of the system.

> Sachin.

I guess I would add a little bit here the sequence of these steps is very important and is of a crucial nature in the design itself so the steps would be as follows : -

1) Activity diagrams

2) Use cases

3) Sequence diagrams

4) Collaboration diagrams

5) Class diagrams

6) state diagrams

7) Component diagrams

8) Deployment diagrams

Though I would say you could live without the last three. and still reach a sound design making a choice between the Collaboration and the Class diagrams. I would personally prefer class diagrams.

nome02 at 2007-7-7 3:17:51 >

# 7

There's one thing I feel is very important and do

after writing use cases and before drawing interaction diagrams.

DOMAIN MODELING, I've found it invaluable.

GRASP patterns are invaluable in improving the quality of your designs.

A quick search on the web should lead you to the GRASP patterns, by Craig Larman.

rennu at 2007-7-7 3:17:51 >

# 8

I have gone through the GRASP patterns, by Craig Larman. How could I decide about the specific pattern to use. It has a no. of patters mentioned. I am confused .....Satya

tsatyawali at 2007-7-7 3:17:51 >

# 9

< www.omg.org/uml >

The_Vulcan at 2007-7-7 3:17:51 >

# 10

I have an question to sparandker's post, how could we create sequence diagram before we define objects and classes? As I think sequence diagrams are based on objects interactions? What object should we present in then sequence diagrams?

hciuts at 2007-7-7 3:17:51 >

# 11

> 1) Activity diagrams

> 2) Use cases

> 3) Sequence diagrams

> 4) Collaboration diagrams

> 5) Class diagrams

> 6) state diagrams

> 7) Component diagrams

> 8) Deployment diagrams

I would comment on the list. I suggest step 5 (class diagrams) goes alongside the 1st step (if not before it, but it depends). Thus you are first performing analysis, and seq/coll diagrams belong somewhere in between analysis & design (depending on the details level)

mr_dronski at 2007-7-7 3:17:51 >

# 12

Here is an approach that has helped me:

1. From the requirements write use cases

2. From the use cases identify subsystems and components.

(see http://www.theserverside.com/patterns/thread.jsp?thread_id=17595

for an example)

3. Develop component diagram

4. Develop "domain" class diagram

5. Adopt/develop a framework (say Struts) to accomplish use case goals

6. Develop "framework" class diagram

6. Develop sequence diagrams

7. Develop deployment diagram

Nalla

nsenthil at 2007-7-7 3:17:51 >

# 13

What r the steps of writing use cases in an OO Application Design ?

Dama at 2007-7-7 3:17:51 >

Java programming resources: FAQs, tutorials, compiler and browser download sites, documentation, books lists, IDEs, etc.

OOAD steps

Other Topics New Topic

Other Topics Hot Topic

Other Topics

All Classified