Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Structured Anal...  Sequence of UML daigram in Design phase
Previous Previous
 
Next Next
New Post 3/19/2008 3:49 AM
User is offline Sam
1 posts
No Ranking


Sequence of UML daigram in Design phase 

Hi all!

To Prosnet the design model UML is used but can anyone tell methe exact sequence of UML diagram I mean the order in which thesediagrams are created......

 
New Post 3/19/2008 5:27 AM
User is offline VN
34 posts
9th Level Poster




Re: Sequence of UML daigram in Design phase 

Sam,

 

First you should identify the use cases and create the use case model for the project.

Then, when you dive into each use case, you do the other diagrams (state, activity…) in any order. Actually what diagrams you’ll use depends on the use case.

For example: The state diagram could be applied to the status changes of hotel rooms for example but not for a use case about report generation.

The idea is to create these diagrams that best describe the use cases you are writing. You are not supposed to use all of them all the time, and you may create several diagrams of each type pre use case if it is too complicated.

-Vessela

 
New Post 3/19/2008 9:01 AM
User is offline kr_BA
34 posts
9th Level Poster


Re: Sequence of UML daigram in Design phase 

Hi SAM!

The Most general approach will be:

Analysis Level Class (Domain Modeling) -->UML Use Case --> Activity and/or State Chart --> Sequence Diagram (Optional)

--> Derived Static Strucre (Class Diagram).

Kumar Rohit

 

 
New Post 4/11/2008 12:19 AM
User is offline Kimbo
454 posts
5th Level Poster


Re: Sequence of UML daigram in Design phase 

Hi Sam,

Hmmm.... don't really like this prescriptive approach to BA work but here goes. I disagree with previous posters. Here's what I do:

Activity diagram to get the process sorted out. Each action on the activity diagram is a use case or a use case package.

During writing up the use cases I start any State Chart diagrams (entity life cycles), Class diagram (business domain model) and use case diagrams that are needed to support my argument.

Never needed to write a sequence diagram yet. As a BA I don't deal in solution. Sequence diagrams are far too technical for an old coder like me.

Kimbo

 
New Post 9/5/2008 6:07 AM
User is offline vinny
66 posts
8th Level Poster


Re: Sequence of UML daigram in Design phase 
Modified By vinny  on 9/5/2008 8:09:11 AM)

I'm with Kimbo on this one for the most part.  Since I was introduced to BPMN a few months back, I've started using it to first document the business process, and then use activity diagrams to model the desired system processes to support the business processes.  Use cases are often used to supplement either the BPMN or activity diagrams so that the stakeholders can understand everyone's role (including the system's) in every process.  I also use DFDs to show data flow for more apt stakeholders and management who desire a bit of detail.

I do use sequence diagrams sometimes.  They've proven invaluable in describing how data is exchanged and processed between us and third party vendors.

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Structured Anal...  Sequence of UML daigram in Design phase

Community Blog - Latest Posts

Salesforce has established itself as one of the most reputable CRM platforms, providing important customer data to assist businesses in effectively managing their operations. Salesforce is the world's best CRM platform that helps businesses to keep up the data in an arranged or structured manner. Salesforce is the world's most popular...
There are big differences between data exploration versus data presentation. And you need to be aware of these differences as you're creating data stories and data presentations. Let’s start by defining our terms: Data exploration means the deep-dive analysis of data in search of new insights. Data presentation means...
Is Agile a reason to avoid documentation? I bet this question shows up again and again while working with product requirements. On one side, we have got long specifications, complicated diagrams, mystical technical design, too many prototypes and pretty obvious for engineers user guides (do we really need so much?). On the other side, can we actual...

 






 

Copyright 2006-2022 by Modern Analyst Media LLC