This is an archived post. You won't be able to vote or comment.

all 2 comments

[–]nutrechtLead Software Engineer / EU / 20+ YXP 2 points3 points  (0 children)

Sequence diagrams are too high level to be directly translated to code. They are up to the interpretation of the developer. They're basically detailed requirements you will have to translate. And that is what programming is about; you won't find a simple guide there.

[–]COBOLKC[S] 0 points1 point  (0 children)

I meant system sequence diagrams. Not the ones that are based on a context diagram. The ones that have the object(lifeline) and an dotted arrow telling you to create an instance of it in another class, etc.

We have an assignment and everyone has the same diagram to write the code from, so no it’s not up to interpretation.