Changes between Version 3 and Version 4 of Adding user


Ignore:
Timestamp:
11/01/17 22:33:31 (7 years ago)
Author:
135012
Comment:

Почетна верзија на ова сценарио во понатамошниот развој на проектот кје има измени.

Legend:

Unmodified
Added
Removed
Modified

  • Adding user

    v3 v4  
    1717* '''Date last updated''': ...
    1818
    19 === 3. Use Case Definition ===
     19=== Use Case Definition ===
    2020
    2121'''3.1. Actors '''
    22 
    23 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.
     22System Administrator,Doctor,Receptionist
    2423
    2524'''3.2. Trigger'''
    26 
    27 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.
     25A new user for HMS is identified who needs to be added to the system
    2826
    2927'''3.3. Description'''
    30 
    31 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.
     28 1.  Administrator add new Doctor, Receptionist, Nurse or Patient.
     29 2. Doctor add new Patient.
     30 3. Receptionist add new Patient.
    3231
    3332'''3.4. Preconditions'''
    34 
    35 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:
    36 1. User's identity has been authenticated.
    37 2. User's computer has sufficient free memory available to launch task.
     33 Да се се имаат податоци за корисникот(име, презиме, матичен број, пол, специјалност).
    3834
    3935'''3.5. Postconditions'''
    40 
    4136Describe the state of the system at the conclusion of the use case execution. Number each postcondition. Examples:
    42 1. Document contains only valid SGML tags.
    43 2. Price of item in database has been updated with new value.
     371. Администраторот на системот да може да ги креира докторите, медицинските сестри и шалтерските работници, а пациентите да може да ги гледаат истите
     382. Докторот да може да додаде пациент, а администраторот да може да го одобри и да биде креирана корисничка сметка и потоа пациентот да може да ја користи истата исто така медицинските сестри  и шалтерските работници да може да ги гледаат додадените пациенти.
    4439
    4540'''3.6. Normal Flow'''
    46 
    47 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.
     411. Администраторот се најавува на системот оди во соодветните модули за додавање на Доктори,медицински лица,шалтерски работници и креира нови корисници во соодветните модули.
     422.Докторот се најавува на системот оди во модулот за додавање на пациенти и креира нов пациент.
     433.Шалтрскиот работник се најавува на системот оди во модулот за додавање на пациенти и креира нов пациент
    4844
    4945'''3.7. Alternative Flows'''
    5046
    51 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.
    5247
    53 '''3.8. Exceptions'''
    5448
    55 Describe any anticipated error conditions that could occur during execution of the use case, and define how the system is to respond to those conditions. Also, describe how the system is to respond if the use case execution fails for some unanticipated reason. If the use case results in a durable state change in a database or the outside world, state whether the change is rolled back, completed correctly, partially completed with a known state, or left in an undetermined state as a result of the exception. Number each alternative flow in the form “X.Y.E.Z”, where “X” is the Use Case ID, Y indicates the normal (0) or alternative (>0) flow during which this exception could take place, “E” indicates an exception, and “Z” is a sequence number for the exceptions. For example “5.0.E.2” would indicate the second exception for the normal flow for use case number 5.
    5649
    57 '''3.9. Includes'''
    58 
    59 List any other use cases that are included (“called”) by this use case. Common functionality that appears in multiple use cases can be split out into a separate use case that is included by the ones that need that common functionality.
    60 
    61 '''3.10. Priority'''
    62 
    63 Indicate the relative priority of implementing the functionality required to allow this use case to be executed. The priority scheme used must be the same as that used in the software requirements specification.
    64 
    65 '''3.11. Frequency of Use'''
    66 
    67 Estimate the number of times this use case will be performed by the actors per some appropriate unit of time.
    68 
    69 '''3.12. Business Rules'''
    70 
    71 List any business rules that influence this use case.
    72 
    73 '''3.13. Special Requirements'''
    74 
    75 Identify any additional requirements, such as nonfunctional requirements, for the use case that may need to be addressed during design or implementation. These may include performance requirements or other quality attributes.
    76 
    77 '''3.14. Assumptions'''
    78 
    79 List any assumptions that were made in the analysis that led to accepting this use case into the product description and writing the use case description.
    80 
    81 '''3.15. Notes and Issues'''
    82 
    83 List any additional comments about this use case or any remaining open issues or TBDs (To Be Determineds) that must be resolved. Identify who will resolve each issue, the due date, and what the resolution ultimately is.
    84 
    85 === 4. Use Case List ===
    86 
    87 Primary Actor
    88 * Use Case 1
    89 * Use Case 2
    90 
    91 Primary Actor
    92 * Use Case 1
    93 * Use Case 2