Студопедия
Случайная страница | ТОМ-1 | ТОМ-2 | ТОМ-3
АрхитектураБиологияГеографияДругоеИностранные языки
ИнформатикаИсторияКультураЛитератураМатематика
МедицинаМеханикаОбразованиеОхрана трудаПедагогика
ПолитикаПравоПрограммированиеПсихологияРелигия
СоциологияСпортСтроительствоФизикаФилософия
ФинансыХимияЭкологияЭкономикаЭлектроника

Definitions

Hardware and System Software Architecture and Computer Communication and Networking Architecture | Application Software Architecture | Federation Architecture | Integration Architecture | Security and Privacy Requirements | Performance Requirements | Packaging Requirements | Acceptance Requirements |


Читайте также:
  1. Before you read the article below, match these words to their definitions.
  2. Match the definitions below to words in the text. Then use the words in sentences of your own.
  3. Match the terminology expressions given in English with their definitions or explanation given in Russian.
  4. Match the terminology expressions given in English with their definitions or explanation given in Russian.
  5. Match the terms on the right to their corresponding definitions on the left.
  6. Match the terms on the right to their corresponding definitions on the left.

This topic contains definitions for a variety of terms that arise in this and related documents.

UML Specific Definitions:

· Actor — someone or something outside the system or business that interacts with the system or business.

· Use case — a use case defines a set of use-case instances, where each instance is a sequence of actions performed by the system that yields an observable result of value to a particular actor. A use-case class contains main as well as alternate flows of events related to producing the 'observable result of value'

· Use-case diagram — a diagram that shows the relationships among actors and use cases within a system.

· Use-case instance — a sequence of actions performed by a system that yields an observable result of value to a particular actor.

· Use-case model — a model that describes a system’s functional requirements in terms of use-cases.

 

Domain Specific Definitions:

· Inventory – is a physical piece of metal (or pack of grain or coins) that is atomic (thus cannot be divided), measured in EA (each) and is stored within a Warehouse

· Warehouse – is a physical storage or a Vault that is a specially equipped premises that is used to store Inventory. Throughout this document the terms Warehouse, Vault and Site are used as synonyms.


Дата добавления: 2015-08-27; просмотров: 69 | Нарушение авторских прав


<== предыдущая страница | следующая страница ==>
Purpose of the Software Requirements Document| Overview

mybiblioteka.su - 2015-2024 год. (0.005 сек.)