Changes between Initial Version and Version 1 of Adding user

Timestamp:

11/01/17 21:37:52 (6 years ago)

Author:

Dajana Stojchevska

Comment:

--

Adding user

@@ +1 @@
+== Use Case Scenario: Adding user ==
+
+=== 1. Guidance ===
+
+This section provides a description of each section in the use case template.
+
+=== 2. Use Case Identification ===
+
+'''2.1. Use Case ID''': 1.0
+
+'''2.2. Use Case Name''': Adding user
+
+'''2.3. Use Case History'''
+* '''Created by''': ...
+* '''Date created''': ...
+* '''Last updated by''': ...
+* '''Date last updated''': ...
+
+=== Use Case Definition ===
+
+'''3.1. Actors '''
+
+An actor is a person or other entity external to the software system being specified who interacts with the system and performs use cases to accomplish tasks. Different actors often correspond to different user classes, or roles, identified from the customer community that will use the product. Name the actor that will be initiating this use case and any other actors who will participate in completing the use case.
+
+'''3.2. Trigger'''
+Identify the event that initiates the use case. This could be an external business event or system event that causes the use case to begin, or it could be the first step in the normal flow.
+
+'''3.3. Description'''
+Provide a brief description of the reason for and outcome of this use case, or a high-level description of the sequence of actions and the outcome of executing the use case.
+
+'''3.4. Preconditions'''
+List any activities that must take place, or any conditions that must be true, before the use case can be started. Number each precondition. Examples:
+1. User's identity has been authenticated.
+2. User's computer has sufficient free memory available to launch task.
+
+'''3.5. Postconditions'''
+Describe the state of the system at the conclusion of the use case execution. Number each postcondition. Examples:
+1. Document contains only valid SGML tags.
+2. Price of item in database has been updated with new value.
+
+'''3.6. Normal Flow'''
+Provide a detailed description of the user actions and system responses that will take place during execution of the use case under normal, expected conditions. This dialog sequence will ultimately lead to accomplishing the goal stated in the use case name and description. This description may be written as an answer to the hypothetical question, “How do I <accomplish the task stated in the use case name>?” This is best done as a numbered list of actions performed by the actor, alternating with responses provided by the system. The normal flow is numbered “X.0”, where “X” is the Use Case ID.
+
+'''3.7. Alternative Flows'''
+Document other, legitimate usage scenarios that can take place within this use case separately in this section. State the alternative flow, and describe any differences in the sequence of steps that take place. Number each alternative flow in the form “X.Y”, where “X” is the Use Case ID and Y is a sequence number for the alternative flow. For example, “5.3” would indicate the third alternative flow for use case number 5.
+
+
+