Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

Software Modeling > Vocabulary > Flashcards

Vocabulary Flashcards

(71 cards)

Start Studying
1
Q

Actors

A

Classes that define roles that objects external to a system may play

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Use Case

A

Classes that define a sequence of interactions (units of functionality) between the actor and the system.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Class

A

A set of objects with the same characteristics or a common implementation.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Object

A

Well-defined representational constructs of concrete or conceptual entities that provide an understanding of the real world

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Attribute

A

A data value, or structural characteristic, held by an object in a cass

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Operation

A

The specification of a function performed by an object; a behavioral characteristic of an object

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Use Case modeling

A

An approach for describing the functional requirements of a system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Software Requirements

A

Describe the functionality that the system must provide for the users.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Requirements Specification

A

The document that needs to be agreed on by the requirements analysis and the users.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Functional requirement

A

Describes the functionality a system must be capable of providing in order to fulfill the purpose of the system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Nonfunctional requirement

A

a.k.a Quality Attribute: refers to a quality of service goal that the system must fufill

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Three examples of nonfunctional requirements:

A

performance requirement, availability requirement, security requirement

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Quality Attributes of Software Requirements Specification (SRS)

A
  1. Correct
  2. Complete
  3. Unambiguous
  4. Consistent
  5. Verifiable
  6. Understandable by a non-computer specialist
  7. Modifiable
  8. Traceable
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Use Case Model

A

Describes the functional requirements of the system in terms of actors and use cases. The system is a black box. It only matters what the system does not how the system does it.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Actors that are not human include:

A

external systems, I/O devices, timers

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Primary Actor

A

The actor that initiates the use case, usually the actor that gains value from the use case

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Secondary Actor

A

An actor other than the primary actor that participates in the use case.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Five Types of Actors

A
  1. Human
  2. External System Actor
  3. Input Device Actor
  4. Input/Output Device Actor (typically a sensor)
  5. Timer Actor
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Senario

A

Each complete sequence through the use case

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Main Sequence

A

The most common sequence of interactions between the actor and the system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Use Case Description Sections

A 
Use Case Name
Summary
Dependency
Actors
Preconditions
Description of the Main Sequence
Description of alternative Sequences
Nonfunctional requirements
Postcondition
Outstanding Questions
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Alternative Sequence

A

Other situations that occur less frequently

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Inclusion Use Case

A

Functionality that is common to more than one use case, usually cannot be executed on its own. The inclusion use case is reusable.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

The include relationship

A

The relationship between the base use case and the inclusion use case. The included use case is pointed to from the base use case by a dotted line and denoted as a relationship with the > notation.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
The extend Relationship
Used to model alternative paths that a use case may take; used to show a conditional part of the vase use case that is executed only under certain circumstances; used to model complex or alternative paths.
26
Extension points
Used to specify the precise location in a base case where extensions can be added. (is given a name) contains a condition to select the extension use case. Only one condition can be true (Mutually exclusive)
27
Use Case Package
Group of related use cases that represent high-level requirements that address major subsets of the functionality of the system
28
Activity Diagram
Diagram that depicts the flow of control and sequence of activities, decision nodes, loops and concurrent activities; ;represents the sequential steps of a use case
29
Activity node
depicts one or more steps in the use case description
30
Decision Node
Depicts a situation in which, based on the decision, an alternative sequence could branch off of the main sequence.
31
Static Model
defines the classes in the system, the attributes of the classes and the relationships between the classes
32
Static Modeling
Refers to the modeling process and the UML class diagram notation that is used to depict the static model
33
Three types of relationships between classes
1. Aggregation/Composition (whole/part) 2. Association 3. Generalization/specialization (inheritance)
34
Association
A static structural relationship between classes. Usually a verb. Associations are inherently bidirectional.
35
Multiplicity of Associations
specifies how many instances of one class relate to a single instance of another class.
36
Associations (UML book)
Descriptions of a set of links with common structural features, behavioral features, relationships and semantics. They are used to model a set of relationships that relate to concepts where relationships have common characteristics.
37
Association Class
a class that models an association between two or more classes. Most often occurs in a many to many relationship.
38
Compositions
Are used to model parts that exist or live and die with their associated owner; a relationship among instances.
39
A composite class often involves...
a physical relationship between the whole and the parts
40
Rank composition, aggregation and associations by strength of relationship
Composition, aggregation, association
41
Aggregation
Part instances can be added and removed from the aggregate whole: likely to model conceptual classes rather than physical classes.
42
Generalization/Specialization
Common attributes are abstracted into generalized class
43
`Is a` relationship
Generalization
44
`Is part of` relationship
Composition/Aggregation
45
software system context diagram
a diagram that explicitly shows the boundry between the software system and the external environment
46
«external input device»__________ «software system»
Inputs to
47
«software system» _______ «external output device»
Outputs to
48
«external user» ___________ «software system»
Interacts with
49
«external system» _______________ «software system»
Communicates with
50
«external timer» _________ «software system»
Signals
51
Four main object and class structuring models
1. Entity Object 2. Boundary Object 3. Control Object 4. Application Logic Object
52
Entity Object
A software object which encapsulates information (business model) including rules, relationships, data and persistence behavior.
53
Boundary Object
Objects that interact with the external environment.
54
The types of Boundary Objects
1. User Interaction Object 2. Proxy Object 3. Device I/O Object
55
User Interaction Object
Software object that interacts with an communicates with a human user
56
Proxy Object
Object that interfaces to and communicates with an external system or subsystem
57
Device I/O Boundary Object
Object that receives input from and/or outputs to a hardware I/O Device
58
Control Object
Object that provides the overall coordination for a collection of objects.
59
Control Object Types
Coordinator objects, state-dependent, timer
60
Application logic object
Object that contains the details of the application logic
61
Types of application logic objects
Business logic, algorithm objects, service objects
62
Software system context class diagram
shows all external classes that interface to and communicate with the system
63
Entity Object
object that stores information. Typically persistent
64
Control Object
provides the overall coordination of the objects that realized a use case
65
Coordinator object
decision making object that determines the overall sequencing for a collection of related objects. NOT state dependent
66
State-dependent control objects
an object whose behavior varies in each of its states.
67
Timer object
a control object that is activated by an external timer, performs some action itself or activates another object to perform the desired action
68
Business logic object
defines the business specific application for processing a client request. goal to separate logic from entities. Prime responsibility is to encapsulate and execute the business rules
69
Algorithm Object
Encapsulate and execute the algorithm
70
Service Object
Provides a service for other objects, never initiates a request. Might encapsulate the data it needs to service client requests or access another entity object.
71
Dynamic Modeling
A view of the system in which control and sequencing are considered within or between objects

Software Modeling (3 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions