1

I have a web application that reads from a file. My application is represented as a node and file as an artifact. Can I use dashed arrow to represent their relationship ?

enter image description here

qwerty_so
  • 35,448
  • 8
  • 62
  • 86
Lorenzo
  • 31
  • 6

2 Answers2

1

I never used artifacts as you want but it seems legal.

Artifact (p654) : An Artifact represents some (usually reifiable) item of information that is used or produced by a software development process or by operation of a system. Examples of Artifacts include model files, source files, scripts, executable files, database tables, development deliverables, word-processing documents, and mail messages.

A log file is produced by an operation of the system, I guess. Guys, what do you think ?

And there a stereotype in the standard profile: «Create» : A usage dependency denoting that the client classifier creates instances of the supplier classifier. (p 678)

So if you want to model that your wbe server creates an instance of LogFile, the following schema should do the job.

enter image description here

More remarks:

  • the web server is an execution environment deployed on a node.

  • your web application is an artifact running on the execution environment.

granier
  • 1,739
  • 13
  • 25
  • Thanks for your answer granier. I don't need to model that my server writes log file. I want to model my web application that reads my log file. – Lorenzo Nov 15 '17 at 15:12
  • your application reads the log file ? Is it a monitoring application ? Otherwise I can not figure why an application would read a log file. But even if this is for read, the stereotype is Create ... not Read ... :) If you want to model the read, a use dependency as you said is more suitable and you can add a note to precise the meaning of the use dependency. – granier Nov 15 '17 at 15:14
  • Yes it's a monitoring application. It localizes every request received by my server. Could the stereotype <> be right? I cannot find no article that explains if this kind of relationship between a node and artifact is right! – Lorenzo Nov 15 '17 at 15:19
  • @Lorenzo, See https://stackoverflow.com/questions/47181038/why-is-it-possible-to-model-a-use-dependency-between-an-actor-and-a-use-case#comment81318672_47181038 to have some information about <>. It can be used between almost all UML meta-classes. – granier Nov 15 '17 at 15:24
0

That's perfectly ok. You could optionally stereotype the dependency with <<create>>.

qwerty_so
  • 35,448
  • 8
  • 62
  • 86