We have been asked to produce a logical application and infrastructure diagram for an existing system which is in the process of been transferred to a different server. After some searching on Google we have not found any guidance on what this sort of diagram should containing, does anyone have any links or suggestions?
Probably what you need is to create UML diagrams, you can use CASE Applications like MS VISIO, Enterprise Architect (EA), StarUML for generating such diagrams.
Component Diagram
Logical Deployment Diagram
For reading more about UML see:
http://www.tutorialspoint.com/uml/uml_deployment_diagram.htm
Related
I currently work on a rather large system that consists of a WinForms app that uses WCF services and a database at the bottom. If you think about a use case or a requirement, what a developer needs is a quick overview of the implementation of that particular use case (or requirement). A person who knows the systems could very quickly verbally explain that these two views (or subviews) are used in the UI, they are data-bound to this controller, which uses this WCF service to get this DTO. The service uses this business class, which uses this data adapter, and the data is in these tables in the database.
I think in most cases it would be possible to convey all this information in a single diagram. However, it would be a kind of a hybrid between component and activity diagrams as it shows both workflow and the components that are involved. UML obviously doesn't have such a diagram, but I was wondering if anyone has done anything on these lines and what tools you have used.
I dont think activity diagram is appropriate here. Activity diagrams, as far as i believe are intended for somebody to understand how the module/system works without getting into the technical part. But then if you can express all that what you said in an activity digram and if your team and your audience are able to decipher things, then sure. Getting back to your scenario, i have done this before and a UML sequence diagram has helped me here. A sequence diagram depicts sequential object interactions. You might wanna check it out
I'm using enterprise architect and I want to know if there's a way to convert a sequence diagram into a communication diagram.
Any ideas?
Currently there is no automated process built into Enterprise Architect to achieve this but I believe it is penciled in for a future release?
However here are a couple of workarounds:
The first, depending on what elements you have used to create your sequence diagram (use objects not lifelines), is to reuse the same elements. Create a new collaboration diagram and drag the sequence elements from the Project Browser onto it. These will be exactly the same elements in both diagrams (so any name or attribute changes to one will be reflected in the other.
The second is to use Enterprise Architects Automation Interface or scripting engine to write a quick script that will do it for you. I remember one of this being available in the past, but you had to contact support#sparxsystems.com to get them to send you a copy.
I hope this helps!
RSA IBM and Omondo EclipseUML have this feature.
I am attempting to draw a UML diagram for the our web service dependencies. I need to break down how all the projects in our solution interact with different web services.
My initial thought what to use Communication Diagram but that did't seem like the right choice when I looked at some examples. Does anyone have any suggestions? Is there an industry standard? I did seethis question here as well but I am asking what TYPE of diagram do I choose.
Looks like according to this I should be using a Package Diagram
When it comes to systems integration, how do you model integration requirements? Do you use UML or BPMN or some other techniques?
What limitiations you see in existing approaches and what would be an ideal modeling approach to system integration requirements in your opinion?
This question is really broad and could be refined (e.g. what level of system?) if you desire a better answer. The approaches below have worked in my experience and were adopted broadly within a company. This may not work for your organization, but our is very application/data integration oriented and these methods help us track integration at high/flow/data entity levels. The key to success is not the ideal model, but a practical one with good training and examples/cheat sheets.
One UML model view that seems to work will for system integration at the component/interface level is a component diagram with components and then interface realizations and interface usages drawn out.
Also using the concept of information flow either UML or just lines with a definition. Then just pick your level of abstraction. Example: PeopleSoft --- (Person Details via File) -----> Active Directory --- (Groups via LDAP) ----> Training Tool.
BPMN is for business process really and though I really think it is great this is not where it should be used.
OMG has tried to answer to your question with the requirement diagram integrated in the sysml modeling langage. SysML tools providers try to solve your problem. For instance check out rational rhapsody solution.
I have to develop an integration concept to integrate my software as a subsystem into an enterprise information system which communicates with other information systems in other institutions.
I want to show a diagram which explains how the several subsystems are connected and which data is communicated between the subsystems. My problem is that I'm not sure if there is in the UML language a diagram-type that supports modeling of complete information systems.
I thought about the deployment diagram, but I am not sure if it is the right. I don't want to start an then recognize that it is the wrong way.
Is there any advice which diagram should be used, or if there is an alternative modeling language for complex information systems?
A component diagram is what you want - see chapter 25 of "The Unified Modeling Language User Guide".
I want to show a diagram which explains how the several subsystems work together and which data is communicated between the subsystems.
I'd probably start with a conceptual sequence diagram.
So, for example, you could have your lifelines represent the various components that you're integrating with, and your interactions could be any of the messages that need to transfer to and from those components.