The Stack Overflow podcast is back! Listen to an interview with our new CEO.
3 some grammar and style corrections plus some formatting to make it more clear
source | link

Studying about OOADOOAD I've found a simple workflow based on five steps. I don't work with a team, so what I'm interested in is a workflow that can be used by a developer working alone. The workflow I found is:

  1. Gather requirements for the application
  2. Describe the application with use cases
  3. Based on the use cases identify the main objects
  4. Identify the relationships between the objects found
  5. Write a class diagram

Now, there are two things about this workflow that makes me a little confused: first it seems oversimplified, and second it seems to treat just aboutdeal only with the domain layer, but I'm not sure.

So, my first question is: is this workflow ok, or is it really oversimplified? If that's the case, which more information could be added to it in order to make it clearer the way we proceed from the requirements all the way to the class diagram?So, my questions are:

And my second question is: am I right that this simply is all about the domain model? When we do OOAD we include on the model and on the class diagrams other classes that might be needed to connect the domain model to the technologies? Or on this step we are just concerned with modeling the domain of the application?

  1. Is this workflow ok, or is it oversimplified?
  2. If that's the case, which more information could be added to it in order to make it more clear the way to proceed from the requirements all the way to the class diagram?
  3. Am I right in that this is all about the domain model?
  4. When we do OOAD do we include on the model and on the class diagrams other classes that might be needed to connect the domain model to the technologies? Or on this step we are just concerned with modeling the domain of the application?

Studying about OOAD I've found a simple workflow based on five steps. I don't work with a team, so what I'm interested in is a workflow that can be used by a developer working alone. The workflow I found is:

  1. Gather requirements for the application
  2. Describe the application with use cases
  3. Based on the use cases identify the main objects
  4. Identify the relationships between the objects found
  5. Write a class diagram

Now, there are two things about this workflow that makes me a little confused: first it seems oversimplified, and second it seems to treat just about the domain layer, but I'm not sure.

So, my first question is: is this workflow ok, or is it really oversimplified? If that's the case, which more information could be added to it in order to make it clearer the way we proceed from the requirements all the way to the class diagram?

And my second question is: am I right that this simply is all about the domain model? When we do OOAD we include on the model and on the class diagrams other classes that might be needed to connect the domain model to the technologies? Or on this step we are just concerned with modeling the domain of the application?

Studying about OOAD I've found a simple workflow based on five steps. I don't work with a team, so what I'm interested in is a workflow that can be used by a developer working alone. The workflow I found is:

  1. Gather requirements for the application
  2. Describe the application with use cases
  3. Based on the use cases identify the main objects
  4. Identify the relationships between the objects found
  5. Write a class diagram

Now, there are two things about this workflow that makes me a little confused: first it seems oversimplified, and second it seems to deal only with the domain layer, but I'm not sure.

So, my questions are:

  1. Is this workflow ok, or is it oversimplified?
  2. If that's the case, which more information could be added to it in order to make it more clear the way to proceed from the requirements all the way to the class diagram?
  3. Am I right in that this is all about the domain model?
  4. When we do OOAD do we include on the model and on the class diagrams other classes that might be needed to connect the domain model to the technologies? Or on this step we are just concerned with modeling the domain of the application?
2 added 1 character in body; edited tags
source | link

Studying about OOAD I've found a simple workflow based on five steps. I don't work with a team, so what I'm interested in is a workflow that can be used by a developer working alone. The workflow I found is:

  1. Gather requirements for the application
  2. Describe the application with use cases
  3. Based on the use cases identify the main objects
  4. IdentiyIdentify the relationships between the objects found
  5. Write a class diagram

Now, there are two things about this workflow that makes me a little confused: first it seems oversimplified, and second it seems to treat just about the domain layer, but I'm not sure.

So, my first question is: is this workflow ok, or is it really oversimplified? If that's the case, which more information could be added to it in order to make it clearer the way we proceed from the requirements all the way to the class diagram?

And my second question is: am I right that this simply is all about the domain model? When we do OOAD we include on the model and on the class diagrams other classes that might be needed to connect the domain model to the technologies? Or on this step we are just concerned with modeling the domain of the application?

Studying about OOAD I've found a simple workflow based on five steps. I don't work with a team, so what I'm interested in is a workflow that can be used by a developer working alone. The workflow I found is:

  1. Gather requirements for the application
  2. Describe the application with use cases
  3. Based on the use cases identify the main objects
  4. Identiy the relationships between the objects found
  5. Write a class diagram

Now, there are two things about this workflow that makes me a little confused: first it seems oversimplified, and second it seems to treat just about the domain layer, but I'm not sure.

So, my first question is: is this workflow ok, or is it really oversimplified? If that's the case, which more information could be added to it in order to make it clearer the way we proceed from the requirements all the way to the class diagram?

And my second question is: am I right that this simply is all about the domain model? When we do OOAD we include on the model and on the class diagrams other classes that might be needed to connect the domain model to the technologies? Or on this step we are just concerned with modeling the domain of the application?

Studying about OOAD I've found a simple workflow based on five steps. I don't work with a team, so what I'm interested in is a workflow that can be used by a developer working alone. The workflow I found is:

  1. Gather requirements for the application
  2. Describe the application with use cases
  3. Based on the use cases identify the main objects
  4. Identify the relationships between the objects found
  5. Write a class diagram

Now, there are two things about this workflow that makes me a little confused: first it seems oversimplified, and second it seems to treat just about the domain layer, but I'm not sure.

So, my first question is: is this workflow ok, or is it really oversimplified? If that's the case, which more information could be added to it in order to make it clearer the way we proceed from the requirements all the way to the class diagram?

And my second question is: am I right that this simply is all about the domain model? When we do OOAD we include on the model and on the class diagrams other classes that might be needed to connect the domain model to the technologies? Or on this step we are just concerned with modeling the domain of the application?

1
source | link

Object Oriented Analysis and Design workflow for developer working alone

Studying about OOAD I've found a simple workflow based on five steps. I don't work with a team, so what I'm interested in is a workflow that can be used by a developer working alone. The workflow I found is:

  1. Gather requirements for the application
  2. Describe the application with use cases
  3. Based on the use cases identify the main objects
  4. Identiy the relationships between the objects found
  5. Write a class diagram

Now, there are two things about this workflow that makes me a little confused: first it seems oversimplified, and second it seems to treat just about the domain layer, but I'm not sure.

So, my first question is: is this workflow ok, or is it really oversimplified? If that's the case, which more information could be added to it in order to make it clearer the way we proceed from the requirements all the way to the class diagram?

And my second question is: am I right that this simply is all about the domain model? When we do OOAD we include on the model and on the class diagrams other classes that might be needed to connect the domain model to the technologies? Or on this step we are just concerned with modeling the domain of the application?