use case modeling

User Generated

txneninqv

Business Finance

Description

The assignment is u have to describe about use case text, use case diagram, vision document, glossary document and supplementary specification document using famous articles or software projects as described in the 'use case assignment docs'. U can search any articles available online or any IT company article about the above five things. You can find one article or five different articles. But please make sure u write in your words do not copy paste please at the end please give reference. If you have any doubts let me know immediately

Unformatted Attachment Preview

Assignment #3 1. • • • • • SYST 1034 - Use Case Modeling Search online and find examples of the following artifacts: Use Case Text Use Case Diagram Glossary Document Vision Document Supplementary Specification Document Each artifact you find should come from a reputable website (e.g., an IT company, an IT professional’s personal website, a government website etc). Also, each artifact should come from a real software development project, and not a made-up example. Your artifact, therefore, should come in a document format (i.e., MS Word or PDF) and not text from a website. Be sure to cite your references in APA format. For each artifact, do the following: • • Summarize the contents of each artifact in 5-10 sentences and in your own words. Explain in 2-3 sentences why you think your reference is reputable. Submission guidelines: Please create 1 MS Word document with all this information and include YOUR name in the file name (ie: jimmy.docx) Please hand in as a professional document with a title page, TOC, etc... Submit to Brigthspace folder Individual Assignment 3 by the due date noted on the dropbox folder. Page 1 of 1
Purchase answer to see full attachment
User generated content is uploaded by users for the purposes of learning and should be used following Studypool's honor code & terms of service.

Explanation & Answer

Attached.

Use Case Modeling

1

Use case modeling
Insert name of the Institution
Insert your name
Insert professor name
March 2018

Use Case Modeling

2
Table of Contents

USE CASE MODELING ................................................................................. ERROR! BOOKMARK NOT DEFINED.
1.

USE CASE TEXT .............................................................................................................................................. 3

2.

USE CASE DIAGRAM ...................................................................................................................................... 4

3.

GLOSSARY DOCUMENT.................................................................................................................................. 5

4.

VISION DOCUMENT ....................................................................................................................................... 6

6.

REFERENCES ................................................................................................................................................ 10

Use Case Modeling

3
Use of Case Modeling

1. Use Case Text
Article: Information Systems Modeling with Use Cases
The term “use case” refers to the sequence of all events in the system as understood from the
perspective of the user. In other words, the use of the case represents actions related to the "use"
of the actor to the system. Use cases have become an important part of object analysis methods.
Modeling use cases in Unified Modeling Language (UML) are popular text tools for system
analysis and design. Use cases can use or not use backup case graphs. Use cases define the
sequence of operations, including variant sequences and error sequences that a system,
subsystem, or class can perform when interacting with external participants. Cases are presented
using UML usage charts in formal or informal text or advanced graphical views. We often use
the use case diagram to start modeling. The use case diagram shows three aspects of the system:
roles, use cases, and boundary systems.
In UML 2, the boundary system is called the theme. The subject is defined by the person or
system (ie, the participant) he/she uses and the specific benefits the system provides for these
participants (eg, use cases). The theme is drawn into a box, the actor is shown outside the box
and the case is used inside the box. Participants represent the role of some external entities
(people, other systems or devices) communicating with specific use cases in the system. The
actor is portrayed as a simple character or stereotyped as an "actor" class. Use cases describe the
behavior of the system to one or more entities. A good way to find use cases is to ask the
following questions: "How does each character use the system?" And "What does the system do
for each actor?" However, use cases must be specified in text form. The document specifying the

Use Case Modeling

4

use case is called the use case specification. There are many types of use case specifications. The
template for this description should be known in every organization or project.
The simple template for a use case specification generally contains:
1. a use case name
2. Unique identifier
3. Brief description
4. Participants (some key entities trigger use cases, and the secondary entity interacts with
the use case after activation)
5. Prerequisites (System Limits Affecting Use Case Implementation)
6. Release Terms (system restrictions caused by use cases)
7. Mainstream (a series of declarative steps in time when used)
8. Alternative process (a list of alternatives to the main process that we can present in our
use case or as a separate use case)

2. Use Case Diagram
In the context of the Unified Modeling Language, use case diagrams are often the starting point
for many software projects. However, questions about use-case diagrams still exist in the minds
of many business analysts. Implement use case diagrams in this area. This study was completed
by the author with the full support of the Image Management Group (OMG). The author created
an online questionnaire containing 38 questions for querying UML usage, including use case
diagrams. A total of 284 relevant survey responses were collected and analyzed. The first
important conclusion from this study was that 182 respondents used UML, and 102 respondents
gave reasons why they did not use UML. The average doctor has 15.1 years of experience but
has only 4.7 years of experience in UML.

Use Case Modeling

5

It is worth noting that UML has existed for more than 12 years, but many experienced people are
still using UML for projects. It is not yet clear why the level of experience is so low because the
data does not show the correlation between the amount of experience and the use of UML
diagrams. UML diagrams are used for non-trivial projects. It should be noted that the average
number of use cases per project is 88. This is a large amount of information to be sent, and it is
useful to provide a use case template containing a case graph. In addition, current tools can map
traceability between use cases and classes to ensure that the provided solution meets the end
user's goals.
When demand changes (because it happens frequently), how many categories are
affected by changes in usage can provide valuable information directly related to costs, scope,
and project ...


Anonymous
Awesome! Perfect study aid.

Studypool
4.7
Trustpilot
4.5
Sitejabber
4.4

Related Tags