WINDEV Concepts

124 Part 4: Advanced concept A component diagram includes the following elements: • module : represents the different physical elements that make up a software application. For example: a file, a library, etc. A module can be represented: • by a specification that shows the module interface. This specification can be generic for classes that can be configured. • by its body that presents the module implementation. • task : represents a component that has its own control flow (thread). • main programs of the software application. • subprograms : groups the procedures and functions that do not belong to any class. 2.5 Activity diagram An activity diagram represents the behavior of a method or the flow of a use case. For example, the following diagram presents the flow of a dam: An activity diagram includes the following elements: • activity : represents a specific step in a workflow. For example: "Print an estimate", "Open the window", etc. • synchronization bar : synchronizes different activities: • by indicating the activities that must be performed before a given activity. For example: "Press clutch" and "Change gear" before "Release clutch". • by indicating the activities that will happen in parallel. • object : relates activities to the object that performs them. For example, the "Order" and "Pay" activities are related to the "Customer" object; the "Teach" and "Evaluate" activities are related to the "Teacher" object. • send signal : represents a signal sent to an object. • accept event : represents the acceptance of an event coming from an object. • transition : represents the transition from one completed activity to another. For example: "Too much water", "Enough money", etc. 2.6 Sequence diagram A sequence diagram represents the chronological order of messages sent and received by a set of objects. For example, the following diagram represents the beginning of a phone call: A sequence diagram includes the following elements: • object : represents the different objects used. Each object is represented by a square at the top of a dotted line. This line represents the object lifespan. For example: "Caller", "Callee", etc. • activation period of an object : activation periods can be inserted into the object lifeline. These periods indicate when the object is active. • message : represents, via horizontal arrows, the message exchanged between the different objects. These arrows are oriented from the sender to the recipient. The order in which the messages are sent is given by the position of the arrows on the vertical axis. For example: "Picks up", "Ring", etc.