You would then use subsystems and components (modules is not an UML concept). You can of course replace a single system lifeline with multiple lifelines.So, if you don't take UML too literally and want to use this representation:
The practice of showing actors in sequence diagrams is nevertheless still quite popular. Moreover, if we take the UML specifications by the book,external actors should in principle not appear in a sequence diagram since they are external to the system, and the sequence diagrams is about parts belonging to the internals of the system. or inside the sequence diagram we only mentioned that action of creating a Exam, without giving further details. Is it correct to specify the fields that the actors will submit? for example when a admin create a new exam, he/she need to select the questions, give it an activation data, assign it to an applicant,specify the Category, Duration, and so on. Is it OK, if i deal with the system as separate modules? meaning that i will have different objects representing each of the system modules, rather than having the system as one object?Ĭan i have multiple actors under each other? So now i have the following 4 questions about building a sequence diagram for this system:. who access the system to develop and maintain it with modules including Exam creation, Adding Question/Answers,Reports, and so one. Can add questions/answers under his/her functional area only
Can manage questions/answers under all functional areas. I am working on an online exam management system, which have those main actors:.
0 kommentar(er)
