In this assignment you will create a use case model, detailed use case steps for one of the use cases following the Use Case Template, and a sequence diagram for

profileadelen
 (Not rated)
 (Not rated)
Chat

In this assignment you will create a use case model, detailed use case steps for one of the use cases following the Use Case Template, and a sequence diagram for the detailed use case. See the Readings and Resources for Lesson 3 for additional examples and resources.

Directions

1. Identify, list, and define, and describe all actors and all use cases for the School Board problem statement in the Week 1 Assignment.
2. Develop a use case diagram.
3. Choose one of the use cases and develop detailed use case steps using the Use Case Template. See the Medical Calculator SRS Excerpts for an example of a use case.Make certain that you use the Use Case Template. Also review Developing Use Cases with Detailed Steps and Sequence Diagrams for an example of developing a sequence diagram for the detailed use case steps.
4. Using the detailed use case you just developed, create a detailed sequence diagram that shows all objects and messages needed in the sequence diagram to implement the detailed use case.
5. Use your CASE tool to create the use case model and sequence diagrams. Add text that includes your name and course number directly on both the use case diagram and the sequence diagram.
6. In a Word document, include the following:
6.1. Your name and course number at the top of the document.
6.2. List of the actors with their definitions.
6.3. List of the use cases with descriptions/scenarios for each use case.
6.4. Include a snapshot/graphic image of your use case diagram
6.5. Include the detailed use case steps for your selected use case and a discussion of your detailed use case model.
6.6. Include a snapshot/graphic image of your sequence diagram.
6.7. Include a description of your sequence diagram.
7. When you submit your Word file, use your name as part of the file name, e.g., ENTD321Assignment3_FirstNameLastName

============

Use Case Detailed Template with Description of Contents

 

A.  Use Case Template Description

 

The following is a description of the fields in the Use Case Detailed Template at the end of this document.

 

1.   Use Case and History

1.1.             Use Case ID

Give each use case a unique integer sequence number identifier like UCxxx. Alternatively, use a hierarchical form: UCxxx.yyy. Related use cases can be grouped in the hierarchy.

1.2.             Use Case Name

State a concise, results-oriented name for the use case. These reflect the tasks the user needs to be able to accomplish using the system. Include an action verb and a noun. Some examples:

·        Search for a course.

·        Enter weight.

·        Place an order for a CD.

1.3.             Created By

Supply the name of the person who initially documented this use case.

1.4.             Date Created

Enter the date on which the use case was initially documented.

1.5.             Last Updated By

Supply the name of the person who performed the most recent update to the use case description.

1.6.             Date Last Updated

Enter the date on which the use case was most recently updated.

 

 

2.   Actors, Description, Preconditions, Postconditions

2.1.             Actor

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(s) that will be performing this use case.  Some examples include Student, Nurse, and Customer.

2.2.             Description

Provide a brief description of the goal of the use case, 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.

2.3.             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.

2.4.             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.   Normal Course

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 numbered responses provided by the system.

 

 

4.   Alternative Courses

Document other, legitimate usage scenarios that can take place within this use case separately in this section. State the alternative course, and describe any differences in the sequence of steps that take place.

 

 

5.   Use Case Related System Issues

5.1.             Exceptions

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.

5.2.             Includes

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.

5.3.             Priority

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.

5.4.             Frequency of Use

Estimate the number of times this use case will be performed by the actors per some appropriate unit of time.

5.5.             Business Rules

List any business rules that influence this use case.

5.6.             Special Requirements

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.

5.7.             Assumptions

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.

5.8.             Notes and Issues

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.


B.  Use Case Detailed Template

 

 

Use Case and History

Use Case ID:

 

Use Case Name:

Created By:

 

Date Created:

 

Last Updated By:

 

Date Last Updated:

 

     

 

 

Actors, Description, Preconditions, Postconditions

Actors:

 

 

Description:

 

 

Preconditions:

 

 

Postconditions:

 

 

 

 

Normal Path

User Action

System Action

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Alternative Path

User Action

System Action

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Use Case Related System Issues

Exceptions:

 

 

Includes:

 

 

Priority:

 

 

Frequency of Use:

 

 

Business Rules:

 

 

Special Requirements:

 

 

Assumptions:

 

 

Notes and Issues:

 

 

 

 ==

Medical Calculator SRS Excerpts

Screen Mockups, Requirements, Use Cases

 

Note:  Excerpts from an SRS (Software Requirement Specification) are included to provide a simplistic example of using screen mockups, requirements, use case diagrams, and detailed use case specification.  This app was developed for an Android device for illustration purposes.

 

 

1Purpose

TheMedicalCalculatorisanAndroidapplicationdesignedtobeusedbynursesto converttheweightofapatientfrompoundstokilogramsorviceversa.Thisisthe firstreleaseofthisnewapplication.Therearenoothercomponentsofthissystemat thistime.

 

 

2. Overall Description

ThenewMedicalCalculatorapplicationprovidesnursesamobilewaytoconvertthe weightofapatientfrompoundstokilogramsandkilogramstopounds.Mosthospital scalesdisplayweightinpounds,buttheprescribedmedicationisoftenbasedonthe weightofapatientinkilograms.Forsafetyreasons,theexactweightofthepatient mustbecorrectlyconvertedbetweenpoundsandkilograms.Thenurseentersthe weightofthepatienceandselectsaradiobuttonto determinewhetherpoundsare beingconvertedtokilogramsorkilogramsarebeingconvertedtopounds.Themobile applicationthencomputestheconvertedweightbasedontheconversionformulasand displaystheresultonthescreen.

 

 

3. User Interfaces

Thisapplicationwillbeusedbynursesinamobileenvironment.Theywill entertheweightofapatient,selectaconversionsoptionandpressa buttontoconverttheweighttotheselectedmetric.Thefollowingare samplescreensfortheuserinterface.Figure1showstheinitialdisplay whentheappisinvoked.Figure2showsthekeypadusedbythenurseto entertheweight.Figure3showstheresultsoftheconversion.


 

 

 

Figure1.InitialDisplay

 

 

 

Figure2.Keyboardforenteringweight

 

 

Figure3.Resultsdisplay

 

 


 

4. Functional Requirements

The following section lists the general, error message, and use case requirements for the app.  It also includes the use case diagram and detailed use case specification.

 

GeneralRequirements

 

GEN-1:   Theapplicationshallallowtheusertoentertheweightofa patient.

GEN-2:Theapplicationshallallowtheusertoselectanoptiontoconvert poundsto kilogramsorconvertkilogramstopounds.

GEN-3:Thesystemshallallowtheusertoconverttheweight.

GEN-4:Thesystemshalldisplaytheconvertedweightincludingunits.

 

ErrorMessageRequirements

 

ERR-1:   Iftheifpounds >=500, then system displays error message “Pounds must be less than 500”.

ERR-2:   ifkilos > 225, the system displays errormessage “Kilos must be less than 225”.

 

 

UseCaseRequirements

 

UseCase-1:TheapplicationshallimplementtheConvertWeightuse case.

 

 

Use Case Diagram

 

 

 

 

 

 

 

UseCaseDiagram

 

Thefollowingusecasediagramillustratestheuserinteractionwiththe system.ANurseactorusestheConvertWeightusecase.

 

 

 

 

 


 

Use Case Detailed Specification

 

Use Case: UC1 Convert Weight

 

Standard Path(normalsequence ofoperations)

 

Use Case: UC1 Convert weight

Pre conditions

The user must have activated the application.

Post conditions

The system will have successfully convertedthe weight.

Actor(Nurse)

System

1.This use case is initiated bythe user starting the application on theirAndroid device

2.App displays the opening screen

3.Nurse clicks in the

Weight displaybox

4.The appdisplays the panelfor entering the weight.

4.The Nurse enters the weight and presses the Done button

6.The appdisplays the weight entered

7.Nurse selects conversion option

8.The appdisplays the highlighted conversion option.

9.Nurse requests conversion

10.Ifpounds tokilograms is selected, then kilograms = pounds *2.2

 

11. Ifkilograms to pounds isselected, then pounds = kilograms/2.2

 

12. App displays result

 

Alternative Path(error orspecial situations)

 

Actor(Nurse)

System

 

1.In #10 above, ifpounds >=500, then system displays errormessage “Pounds must be less than 500”.

 

2.In # 11 above, ifkilos > 225, the system displays errormessage “Kilos must be less than 225”.

 

 

    • 6 years ago
    the answer 100 % correct
    NOT RATED

    Purchase the answer to view it

    blurred-text
    • attachment
      entd321assignment3_firstnamelastname.docx