diagrams show the object classes in the system and the associations between these classes Sequence

Use case

Class

Activity

.......... perspective, where you model the dynamic behavior of the system and how it responds to events An interaction

An external

A structural

A behavioral

.............. diagrams show the activities involved in a process or in data processing Sequence

Use case

Class

Activity

..................diagrams show how the system reacts to internal and external events Sequence

Use case

Class

Activity

Number of help frames is a metric of the Usability

Robustness

Portability

Reliability

................. diagrams show interactions between actors and the system and between system components Sequence

Use case

Class

Activity

The section in the structure of a requirements document that present a high-level overview of the anticipated system

Introduction Glossary Preface Appendices

Time to restart after failure is a metric of the.......... Speed

Robustness

Portability

Reliability

Screen refresh time is a metric of Speed

Robustness

Portability

Reliability

Probability of data corruption on a failure is a metric of the Speed

Robustness

Portability

Reliability

Mbytes is a metric of the ........... Size

Robustness

Portability

Reliability

Number of target system is a metric of the....... Speed

Robustness

Portability

Reliability

The software requirements document is the official statement of what is required of the system developers

True False

Software engineering is the processing of establishing the services that the customer requires from the system and the constraints under which it operates and is developed

True False

Closed interviews where various issues are explored with stakeholder True

False

The non-factional requirements are constraints and properties of the system services True

False

A system boundaries are established to defined what is inside and what is outside the system True

False

A model is an abstract view of a system that ignore system details True

False

Graphic models facilitate discussion about an exciting or proposed system True

False

Complementary system models can be developed to show the systems context, interactions, structures and behavior

True False

Use cases describe interactions between a system and internal actors True

False

The goad is a general intention of the user such as ease of use True

False

Ambiguous requirements may be interpreted in different ways by developers and users True

False

Verifiable non-fictional requirements is a statement using some measure that can be objectively tested True

False

Consistency means that should be no conflicts and contradictions in the descriptions of the system facilities

True False

Understandability and implicitness are some domain requirements problem True

False

Verifiable non-fictional requirement is a general intention of the user such as ease of use True

False

Generalization is implemented using the class inheritance mechanism built into the language True

False

Using case diagram and sequence diagrams are used to describe the interactions between users and system in the system being designed

True False

Requirements document is always up to date in agile model True

False

System modeling is the process of developing abstract models of a system True

False

An aggregation model shows how classes are inherited of other classes True

False

An aggregation model shows how classes that are collections are composed of other classes True

False

Generalization is implemented using the polymorphism mechanisms built into the language True

False

Context models are used to show what lies outside the system boundaries True

False

In a generalization, the attributes and operations associated with higher-level classes are also associated with the ''lower-level classes"

True False

The stimuli in Behavioral models can be data or events> True

False

The functional requirements are the system services and constraints True

False

Domain requirements may be new functional requirements, constraints on existing requirements or define specific computations"

True False

Requirements engineering is the process of establishing the services that the customer requires from a system and the constraints under which it operates and is developed

True False

Requirements specification is the process of writing down the user and system requirements in a requirements document

True False

Completeness means that requirements should include descriptions of all facilities required True

False

The functional requirements are the system services True

False

Requirements should include descriptions of all facilities required True

False

Non-functional requirements may affect the overall architecture of a system rather than the individual components

True False

The Verifiable non-functional requirement is a general intention of the user such as ease of use True

False

Requirements document is always out of date in agile methods True

False

Activity diagram are used to define the static structure of classes in a system and their associations. True

False

Class diagram show interactions between system objective

T

F