Any idea how I express 'implements' in UML?
I'm trying to write some actionscript classes in starUML with the help of this handy little template tool:
http://blog.flashmech.net/2008/09/generate-actionscript-3-with-staruml/
I want the tool to generate 'implements Iblah' in the classes but am not sure what connector to use, Aggregation? Dependecy?
Any help much appreciated.
Inheritance and implementations are represented as Class Level Relationships in U.M.L. class diagram.
Depending on the type of relation you should choose between these two.
I suggest you take a look at this:
http://en.wikipedia.org/wiki/Class_diagram#Class_Level_Relationships
Here is a starUML tutorial that should help - http://cnx.org/content/m15092/latest/
Related
I exported a json file from my firebase but I can't seem to find a tool that can generate a class diagram or UML from a json file. Can anyone help me? It'll be a great help.
I don't think this is possible.
An instance of a JSON document describes what values are attached to what key's. UML class diagram is meant to show structure. A UML diagram could use a class to represent a JSON object. Using the JSON keys as attributes (with nested information as a class that it has an instance of). However Going this way would still make it impossible to define the type of the information the attribute holds. For example you might have a key X that holds the number 5. Without knowing this is a number no tool can auto generate a UML diagram for you. As the tool would need to know the type of the data in advance.
I'm working on a description of a scenario by using sequence diagram. and i would like to define the metamodel without having all the uml element for the SD. Kind of creation of my own SD. the problem is i don't know the steps to follow. does anybody know how i should start?
Have you checked the documentation found at: https://www.eclipse.org/sirius/doc/specifier/sequences/Sequence%20Diagrams.html
Does anyone know how to have dependency injection work with linq2sql. Heres my situation..
I will explain it as best i can here.
I have a base class which has a DBML (linq2sql) and classes etc .. This DBML is COMMON to more than 1 project.. Well each project has its own DBML but has all the tables etc that is in the common dbml i am using in the base class - does that make sense?!
Each of my projects creates a new class by inheriting the base class and extending it... but of course i need to REINJECT my dbml because the dbml that i use specifically in my project has all the functionality that was in COMMON and then some
I am a little lost here.. Anyone know how to achieve this.. I do hope i explained it well enough :-)
I was hoping to use unity or something similar, the classes that are created by linq2sql don't seem to implement interfaces... is this going to be a issues with DI?
Thanks
It sounds like you probably don't need a DBML in every project. I would recommend having one project "MyCoolApp.Entities" that contains your Linq to SQL entities, and then reference that project in your other projects. Those other projects can extend your base entities as needed.
As for Dependency Injection, Unity can definitely resolve dependencies that don't implement interfaces so that shouldn't be a problem.
We're using Linq-To-SQL in one of our projects, and I like to modify the template the code generate uses to add some Code Analysis suppression attributes. Anyone know how I can do this?
Have a look here (by Damien Guard), it provides a good rundown on using T4 Templates for this purpose.
Also, looks like he's since posted the whole thing on CodePlex: LINQ to SQL templates for T4
Many of the Linq-To-SQL classes are implemented as partial classes. If you implement your own partial class (http://msdn.microsoft.com/en-us/library/wa80x488%28VS.80%29.aspx) you could added the attributes to it. By using the partial class you avoid the risk of your attributes being removed the next time the Ling-To-SQL classes are generated.
In a class diagram, is there a way of specifying that a class is an internal class of another class ?
Or is it considered as a pure implementation choice ?
Consider using a nesting relationship (a line with a '+' in a circle at the parent end).
Since UML isn't supposed to be directly implementation specific, I'd use a naming convention, such as:
OuterClass vs OuterClass::InnerClass
I would imagine if you're hoping to reverse-engineer or code-generate to/from UML that different tools would us different techniques (if they support it at all).
A quick test of some reverse engineering using Enterprise Architect (EA v7) confirms that they use the above InnerClass::OuterClass syntax when processing some C# with a public inner class.
For this kind of thing you have separate Diagrams showing the internal structure or processing of a class.
usually, those extra diagrams are activity diagrams to show processing. Sometimes one per method. You might also have an internal sequence diagram showing the API interactions.
No reason you can't have an additional class diagram to show internal structure of a class.
Or you can show the inner class fully enclosed by the outer class, one rectangle inside another.