posted 7 years ago
Seems like you have a number of things that are not quite right.
"... trying to design a sequence diagram..." - No, you don't design a sequence diagram. As with any other diagram of this nature, a sequence diagram is a communication tool. As such, it communicates your ideas of how certain aspects of a system are meant to work, i.e. the design. In other words, a diagram like this is meant to communicate aspects of the system's design.
A sequence diagram illustrates the sequence of method calls that are involved in performing a task to produce something useful for the actor(s) involved. Your diagram doesn't do this. The lifelines, which are the parallel vertical lines, represent different objects in the system that interact with each other. The horizontal arrows depict messages, i.e. method calls, that are sent from one object to another so that each object can perform its part in completing the task. Your diagram doesn't depict this either. Instead, it looks like you are trying to use a sequence diagram (an object-oriented diagram) to depict some kind of hybrid data/logic flow chart (procedural).
I think it's best that you go back to your book/notes and figure out the purpose and proper use of a sequence diagram first.