sgithehu
asked on
UML: Which Diagrams to Use?
In the middle of requirements definition for a large web application. Will also design and develop the same. The following are key information:-
1. Constraint: Must use UML
2. Constraint: Must use Java, Oracle and Linux at the back end. Shall be 3-tier.
3. More information: Will entail integration with external business partners - exchange of xml-based data most likely via web services. There will be different documents exchanges, some real-time, others at agreed frequencies.
4. Additional Information: Once documents are received from external party, they shall go through a number of internal processes like reconciliation with and validation against other documents, amendments etc.
5. Additional Information: There shall be many internal (in the organization) and external users (outside the organization)
There are numerous diagrams in UML. Clearly, it is not feasible to use all of then. I want to use the best selection given the nature of my application (web-based java application, exchanging time-relevant xml documents with external systems).
Kindly advice what to use for the following (include rational)
a) Requirements gathering
b) Analysis
c) Design
d) Any Other
1. Constraint: Must use UML
2. Constraint: Must use Java, Oracle and Linux at the back end. Shall be 3-tier.
3. More information: Will entail integration with external business partners - exchange of xml-based data most likely via web services. There will be different documents exchanges, some real-time, others at agreed frequencies.
4. Additional Information: Once documents are received from external party, they shall go through a number of internal processes like reconciliation with and validation against other documents, amendments etc.
5. Additional Information: There shall be many internal (in the organization) and external users (outside the organization)
There are numerous diagrams in UML. Clearly, it is not feasible to use all of then. I want to use the best selection given the nature of my application (web-based java application, exchanging time-relevant xml documents with external systems).
Kindly advice what to use for the following (include rational)
a) Requirements gathering
b) Analysis
c) Design
d) Any Other
CEHJ
It's impossible to be prescriptive for this, as b and c depend on a. You won't be using *any* UML in a, and probably none in d. The kind of diagrams you use will depend on a
Hi,
UML stands for Unified Modeling Language. This object-oriented system of notation has evolved from the work of Grady Booch, James Rumbaugh, Ivar Jacobson, and the Rational Software Corporation. These renowned computer scientists fused their respective technologies into a single, standardized model. Today, UML is accepted by the Object Management Group (OMG) as the standard for modeling object oriented programs.
Types of UML Diagrams
UML defines nine types of diagrams: class (package), object, use case, sequence, collaboration, state chart, activity, component, and deployment.
The diagram which you choose is mainly depends on the type of the project and the work what you do.
Package diagrams organize the elements of a system into related groups to minimize dependencies among them. So, may be for your project this would be enough.
UML stands for Unified Modeling Language. This object-oriented system of notation has evolved from the work of Grady Booch, James Rumbaugh, Ivar Jacobson, and the Rational Software Corporation. These renowned computer scientists fused their respective technologies into a single, standardized model. Today, UML is accepted by the Object Management Group (OMG) as the standard for modeling object oriented programs.
Types of UML Diagrams
UML defines nine types of diagrams: class (package), object, use case, sequence, collaboration, state chart, activity, component, and deployment.
The diagram which you choose is mainly depends on the type of the project and the work what you do.
Package diagrams organize the elements of a system into related groups to minimize dependencies among them. So, may be for your project this would be enough.
ASKER
@CEHJ
So are you saying there are no certain types of diagrams most suitable for web applications; that i can use any?
So are you saying there are no certain types of diagrams most suitable for web applications; that i can use any?
Basically we don't use any UML diagram during requirement phase. We can have the Use case diagrams during the analysis phase to get the over view of which components we are going to update. In design phase we can use the class diagrams, sequence diagrams to explain the flow of the application.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
@markolorenz
Thanks for your insight. This is pointing me to the right direction. What do you use for Design? And are the package diagrams in any way related to the packages in languages such as java?
Thanks for your insight. This is pointing me to the right direction. What do you use for Design? And are the package diagrams in any way related to the packages in languages such as java?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If you are not familiar with making UML diagrams I'd suggest starting out with paper and pencil first. You want to just get a good feel for the diagrams and their purposes without getting distracted by learning new software....save that till later.