Block I: Requirements

Given the following text representing a requirement: "The system will meet the requirements of the ASIL level according to the standard ISO 26262 on physical security"
a. Represents a functional requirement
b.Represents a non-functional requirement
c.represents a class
d. Represents a use case

b

Given a requirement that must contain a condition...
a) It is convenient to specify the condition adequately in terms of quantity,
units of measure and tolerance.
b) It is convenient that the condition is automatically inferred from the context.
c) Conditions should not be specified in functional requirements.
d) Conditions should not be specified in non-functional requirements.

a

A requirements specification is...
a) Complete if it describes all relevant needs for stakeholders.
b) Correct if it describes the relevant needs of the stakeholders.
c) Complete if everything is relevant and contains no errors.
d) Correct if everything is relevant, but contains errors.

a

What kind of consistency matrices are used as a method to organize requirements?
a) Matrix to show conflicts.
b) Matrix to show couplings.
c) Matrix to show redundancy.
d) They are all types of consistency matrices for organizing requirements.

d

Regarding the requirements life cycle...
a) The implementation serves to reject requirements.
b) The implementation serves to detect requirements.
c) The implementation serves to verify requirements.
d) The implementation serves to validate requirements.

c

Can diagrams be used to represent requirements?
a) Yes, but care must be taken not to fall into design.
b) Yes, but only activity diagrams.
c) Yes, but only to represent the information provided by a person.
d) Yes, but only in agile development processes.

a

What does it mean for a requirement to be "traceable"?
a) That its structure and style can be changed.
b) That its existence can be verified in finite time.
c) That its origin is clear and it exists for a reason.
d) That it can be done, it is realistic.

c

If quantities are specified in a requirement...
a) It is advisable to define the possible range of values.
b) It is advisable to define tolerance or operating limits.
c) It is recommended to explicitly define temporary dependencies if they exist.
d) All of the above are correct.

d

An attribute is...
a) Equivalent to a bidirectional association.
b) Equivalent to a unidirectional association.
c) Equivalent to a reflexive association.
d) None of the above is correct.

b

Which of the following requirements specifications is incorrect?
a) Complete.
b) Consistent.
c) Scalable.
d) Traceable.

c

Which of the following qualities corresponds to a well-specified requirement?
a) Correct and over-specified.
b) Verifiable and noisy.
c) Clear and consistent.
d) Contradictory, but not ambiguous.

c

What is the work plan followed to obtain and describe requirements?
a) Identify, review, write and interview.
b) Interview, identify, write and review.
c) Identify, write, review and interview.
d) Identify, interview, write and review.

d

We have an application, which below there is a database where the information is stored.
information. This database is controlled by maintenance personnel from a
database manager program external to this application. If we have to do a
requirements document, Do we have to have both the administrator and the normal user in
account when making the document?:
a) Both must be taken into account, and their corresponding classes must appear in the
document diagrams.
b) The user should appear, but the administrator should not, since the user is an actor of
the application, and the administrator when using an external program does not.
c) The user should not appear, but the administrator should, since the latter has more
weight that the user performs the necessary operations so that the application
works.
d) Neither of them should appear.

b

Which statement about redundancy is correct?
a) Group reviews do not allow it to be detected.
b) Provides consistency to the text.
c) Its appearance may cause it to be necessary to repeat the work.
d) None of the above.

c

What types of requirements exist?
a) Capacity and functional.
b) Non-functional.
c) Capacity and restriction.
d) None of the above.

c

Which of the following characteristics does not belong in the requirements specification?
a) Complete.
b) Consistent.
c) Not modifiable.
d) Verifiable.

c

An interface offers a consistent service if:
a) Contains the implementation of the operations.
b) It has attributes.
c) It has navigable associations.
d) You cannot have direct instances.

d

Select the type of diagram that does not correspond to the obtainment diagrams and
description of requirements.
a) Data flow diagrams.
b) Activity diagrams.
c) Architectural diagrams.
d) State diagrams.

c

Which of these parameters is not directly related to non-requirements?
functional?
a) Interface Requirements.
b) Error Handling.
c) Execution tests.
d) Yield.

c

What is the classification of software requirements?
a) Negative requirements, functional requirements and non-functional requirements.
b) Functional requirements and non-functional requirements.
c) Positive requirements, non-functional requirements and functional requirements.
d) None of the above.

a

What are the types of software requirements?
a) Functional requirements and non-functional requirements.
b) Capacity requirements, restriction requirements and interface requirements.
c) Inverse requirements, functional requirements and non-functional requirements.
d) User requirements, functional requirements and inverse requirements.

c

What is a possible life cycle of a requirement?
a) Created->Proposed->Cancelled
b) Proposed->Validated->Verified
c) Created->Proposed->Validated->Implemented->Verified
d) Proposed->Validated->Implemented.

c

In which two levels are the requirements generally classified?
a) Functional requirements and non-functional requirements.
b) User requirements and software requirements.
c) Negative requirements and positive requirements.
d) Information requirements and operation requirements.

b

Which of the following statements regarding requirements is FALSE?
a) The verb must be in the passive voice instead of the active one.
b) The longer the better as it will include more details.
c) The use of pronouns should be avoided.
d) It is not advisable to include pseudocode.

a

Regarding non-functional requirements, it can be stated that:
a) They explain the services that the application must provide.
b) They indicate what the application should not do.
c) They are gradual, negotiable, transversal and operational.
d) Its verification is simpler than that of the functional requirements.

c

How should not be a requirements specification?
a) Complete.
b) Consistent.
c) Spurious.
d) Clear and unambiguous.

c

What is an interface?
a) It is a documented need for the content, form or functionality of a
product or service.
b) A set of operations that offer a consistent service.
c) A set of abstract diagrams that represent the relationship between the
components of a system.
d) None of the above.

b

Find the bogus property of the view attribute definition in class:
a) It is a property shared by members of the same class.
b) Each attribute has a different value for each object.
c) The attributes of the same class always have the same value.
d) Neither is false.

c

How many are the sins of the specifier?
to 5
b) 7
c) 8
d) 6.

b

Which of these definitions does not correspond to the IEEE definition of a requirement?
a) A condition or capability that a user needs.
b) A condition or capability that a system must possess.
c) An argued representation of a characteristic of the system.
d) A documented representation of a condition or capability.

c

Which of the following types of requirements is not correct?
a) Functional requirement.
b) Abstraction requirement.
c) Restriction requirement.
d) Negative requirement.

b

What is an attribute?
a) Property shared by the objects of a class.
b) Distinctive quality of a class.
c) Function that can be applied to the objects of a class.
d) Exclusive ownership of an object of a class.

a

Which of the following are Techniques for eliciting and describing user requirements...
a) Textual, User Interfaces and prototypes and Visuals.
b) Graphic, Textual and Written.
c) Visual, Written and User Interfaces and prototypes.
d) Textual, Graphic and User Interfaces and prototypes.

d

The functional requirements study...
a) The how, that is, the pre-design of the application.
b) The analysis-design duality.
c) The analysis, that is, the descriptive and/or specific model of the system.
d) Design and quality.

c

Mark which of the following statements does NOT correspond to the definition: What is a Requirement according to IEEE?
a) Condition or capacity that a user needs to be able to solve a problem or
achieve a goal.
b) A documented representation of a condition or capability.
c) A methodical study of the information acquired to achieve a true
understanding of what the system should do.
d) Condition or capacity that a system must have to satisfy a contract,
standard, specification, or other formally imposed documentation.

c

Software engineering is:
a) The systematic application of knowledge, methods and scientific experiences and
technology to the design, implementation, testing and documentation of software.
b) It is the systematic development of requirements through an iterative process and
cooperative in which the problem is analyzed.
c) A condition or capability that a user needs.
d) None of the above.

a

The software requirements consistency table allows to represent:
a) Relationship between functional and non-functional software requirements.
b) Conflicts, redundancies, couplings and independences.
c) Traceability of software requirements.
d) Relations between the requirements and the system model.

b

Assume a requirements document for developing a web page from scratch. The client requests that web standards be respected (although it does not specify which ones). Yes in said
document there is a requirement whose description is "The web page must respect the standard
W3C Media Usage", what kind of requirement will this be?
a) Capacity user.
b) Restriction user.
c) Functional software.
d) Non-functional software.

d

The following information must be found in the requirements traceability matrix:
a) It must show the relationship of the requirements with the implementation units.
b) It must explain the conflicts, couplings and redundancies that may exist between the
requirements functionalities.
c) It must show the flow and direction of the information that will be given in our component
software.
d) It must detail the different stages in the progress of the requirements since they are
they began to write until the veruna final espion monitoring the hours employees.

a

In the life cycle of a requirement, in what state or states could it be completely eliminated?
of the project documentation?
a) Proposed.
b) Proposed and Validated.
c) Proposed, Validated and Implemented.
d) Proposed, Validated, Implemented and Verified.

a

A requirements specification is complete if...
a) Describes all relevant needs for stakeholders.
b) There are no conflicts between requirements.
c) It facilitates making changes in a simple, complete and consistent way.
d) It has only one interpretation.

a

A requirement...
a) It is verified and validated by the client.
b) It is validated by the client.
c) It is implemented by the client.
d) None of the above is correct.

b

Indicate which of the following statements about the requirements specification is FALSE.
a) It is possible to detect absolutely all the defects of a requirement if the
proper methods for performing performance tests.
b) Total completeness is an unattainable goal, since completeness is relative
at the time in which the requirements are raised.
c) The requirements can be grouped into thematic packages, as well as subordinated between
they.
d) In the final version there can be no Conflicts or Redundancies, but there can be Couplings.

d

A good requirement is characterized by:
a) Avoid undefined technical terminology, using simple, clear, precise texts and not
ambiguous.
b) Indicate design details and use pseudocodes to improve understanding of the design.
requirement.
c) Group the largest number of user needs to avoid generating a high
number of requirements.
d) Use the conditional mood to indicate optional needs.

a

We have an application, below which there is a database where the information is stored.
information used from the users themselves. This database is controlled by staff
administrator from a database manager program external to this application. There are
to take into account both the administrator and the normal user when carrying out the
conceptual models of the considered application?
a) Both must be taken into account, and their corresponding classes must appear in the
requirements document diagrams.
b) The user must appear, since he is an actor of the application and his data is used,
but the administrator does not, because he uses an external program.
c) The user should not appear, but the administrator should, since the latter has more
weight that the user performs the necessary operations so that the application
works.
d) Neither of them should appear, since they are external agents to the system, and
therefore, they should not appear in the system information model, or model
conceptual.

b

Prototyping allows:
a) Add all the functionalities to the system.
b) Implement a first complete, secure and reliable version of the project.
c) Extract requirements, test solutions and eliminate risky parts.
d) Reduce costs, being a mandatory part of any software project.

c

Investment in requirements engineering...
a) It is always good to invest in it, as much as possible, since the better the
requirements the better the final product will be.
b) It is productive to invest in it up to a certain point, if you invest too much time or
money we end up wasting resources.
c) The investment in requirements is not especially relevant for the project.
d) In general, more or less 35% of the resources must be invested in the specification of
requirements.

b

Use cases:
a) With the same term "use case" an objective or service can be designated
demanded by the user, and also the typical sequence of interactions with the user.
system to achieve this goal.
b) They are essential to achieve a good specification of requirements.
c) They represent system activities connected by arrows indicating the time sequence of execution, so that between all of them a
certain service required by the actor.
d) None of the above.

c

If you are looking for an architecture to facilitate the evolution and change of existing functionalities,
the following non-functional requirement should be considered:
a) Extensibility
b) Modifiability
c) Simplicity
d) Efficiency.

b

An attribute is...
a) Equivalent to a unidirectional association.
b) Equivalent to a bidirectional association.
c) Equivalent to a reflexive association.
d) None of the above is correct.

a

Based on the requirements writing criteria, which statement is INCORRECT?
a) Using several negative words in the same sentence can cause a difficulty to
time to understand it.
b) The optionality of a requirement must be expressed as text within the requirement.
c) The number of syllables per word and words per sentence is a good indicator of the
readability of the requirement.
d) Including a high number of connectors may indicate that more than one need is being included in the
same requirement.

b

What is a stakeholder in a Software Engineering project?
a) Is a representative of the client company who makes decisions about the direction of the
Project.
b) It is any person/entity potentially affected or that affects the system
target software.
c) After the commercial exit, it is a type of user that provides an evaluation of the
software system through opinions, interviews or other methods.
d) They are all the people who work on the project, such as software designers
or project clients.

b

Regarding the traceability of the requirements, mark the CORRECT option:
a) The traceability of a requirement indicates that the requirement is correct.
b) The traceability of a requirement indicates that the requirement is atomic.
c) The traceability of a requirement indicates that the requirement has a clear origin and exists for a reason.
d) The traceability of a requirement indicates that the requirement is unambiguous

c

Select the INCORRECT answer regarding the NON-functional requirements.
a) The measure of satisfaction (or verification) is gradual.
b) They impose restrictions on the developed product or development process.
c) They do not require operationalization, since they are not functional requirements.
d) They cut across the functional requirements.

c

Given the next requirement. "the system shall meet the requirements of the ASIIL level C according to the standard ISO 2830 about safety"
Select one:
a. it is a non-functional requirement
b. it is a functional requirement
c. leave this question blank
d. it is a user requirement
e. it is a business requirement

a

which of the following rules to write requirements will lead us to ambiguity in our specification?
a. use correct punctuation
b. use correct grammar
c. leave this question blank
d. use correct spelling
e. use specification sentences

e

A functional requirement....
a. A software requirement that describes not what the software will do but how the software will do it.
b. a statement that identifies what a product or process must accomplish to produce required behaviour and/or results.
c. a condition or capability needed by a user to solve a problem or achieve an objective.
d. none of the answers is correct
e. leave this question blank.

b

a software requirement specification is correct if:
a. it describes all relevant needs for all stakeholders.
b. when every requirement stand is one that the software shall meet and the specification is partially complete
c. leave this question blank
d. it does not include any conflict
e. every requirement stated therein is one that the software shall meet.

e

what kind of information is represented in a traceability matrix?
a. it shows the development status of requirements from the early stages of development to the end, saying the effort in hours
b. it explains conflicts, overlapping and redundancies among requirements
c. it shows the relationship between the requirements and implementation units
d. it shows the information flow between software components.
e. leave this question blank.

c

Can I use a graphical notation (ex. a diagram) to represent requirements?
a. yes, but carefully to avoid design instead of specification.
b. yes, but only activity diagrams.
c. leave this question blank.
d. yes, but only in agile processes
yes. but only to represent information gathered from a person

a

why should we invest in requirements engineering?
a. it is necessary to invest but just to some extent, if we invest too much time or money, it will be a waste of resources
b. it is always necessary to invest as much as possible because better requirements always imply a better final product
c. it is a kind of investment that is not relevant for a software project
d. leave question blank
e. the investment should be around 35% of the total project.

a

one of the seven sins of the specifier is NOISE. Select the proper definition
a. the presence of an element that defines a feature of the problem in such a way that a candidate solution cannot realistically be validated with respect to the feature.
b. the existence of a feature of the problem that is not covered by any element of the text.
c. the presence in the text of an element that uses features of the problem not defined until later in the text
d. leave question blank
e. the presence in the text of an element does not carry information relevant to any feature of the problem

e

select a rule to ensure that requirements are precise
a. if a quantity is specified, we must ensure that the writing(spelling and grammar) of the requirement is correct.
b. if a quantity is specified, we must ensure that each requirement is specified once and only once.
c. if a quantity is specified, we must use units of measurement and magnitudes with tolerance and limits
d. if a quantity is specified, the use of superfluous infinitives shall be avoided.
e. leave question blank

c

in the context of software and systems development...
a. requirements are validated and verified by the client
b. requirements are validated by the implementation
c. requirements are verified by the implementation
d. requirements are validated by the implementation
e. leave question blank

c

which is a good practice to write requirements statements?
a. avoid the excessive use of pronouns
b. use sentences expressing an opinion.
c. use unambiguous but incomplete sentences
d. include design details in the requirement statement.

a

what kind of information is represented in a cross- reference matrix?
a. it shows the relationship between the requirements and implementation units
b. it shows conflict, overlapping and redundancies among requirements
c. it shows the information flow between software components
d. it shows the development status of requirements from the early stage of development to the end, stating the effort in hours.

b

given a requirement specifying a condition...
a. it is necessary to properly specify the quantity, units of measurement and tolerance
b. the conditions must be automatically inferred by context
c. conditions are not allowed in functional requirements
d. conditions are not allowed in non-functional requirements

a

Prototyping is a kind of technique that allows us:
a. to reduce and save costs being an essential activity in any project.
b. to extract requirements, test potential solutions and remove risky parts.
c. to implement all required functionalities of a system.
d. to implement a first, complete and reliable version of a system.

b

regarding the authoring of requirements, which of the following statements is INCORRECT?
a. the use of several negative words I the same statement can lead us to a misleading requirement statement.
b. the optionally of a requirement must be expressed as part of the requirement statement.
c. the number of syllables and the number of words per statement are good indicators of the requirement quality.
d. a requirement statement with several connectors can indicate that the requirement is stating more than one capability.

b

given a requirement specifying a condition...
a. it is necessary to properly specify the quantity, units of measurement and tolerance.
b. the conditions must be automatically inferred by context
c. conditions are not allowed in functional requirements
d. conditions are not allowed in non-functional requirements

a

what is a stakeholder in the context of software engineering?
a. it is a client representative that makes decisions about ht software system.
b. it is a person or entity that affects or is affected by the target software system.
c. once the software system is in production, it is a kind of end-user that gives us feedback.
d. any person that works in the management or development of the software system.

b

regarding requirement traceability, select the CORRECT statement
a. the traceability of a requirement indicates that the requirement is correct.
b. the traceability of a requirement indicates that the requirement is atomic
c. the traceability of a requirement indicates that the requirement source is clear and exists because a reason
d. the traceability of a requirement indicates that the requirement is not ambiguous.

c

a software requirement specification is COMPLETE iff:
a. it describes all relevant needs for all stakeholders.
b. it does not include any conflict
c. every requirement states therein is one that the software shall meet
d. when it is in a) and partially in b)

a

regarding non-functional requirements, select the INCORRECT answer:
a. the degree of satisfaction (or verification) is incremental
b. the state restrictions on the productor under development or in the development process.
c. they do not require implementation since they are not functional requirements.
d. functional requirements are cut crosswise by non-functional requirements

c

prototyping is a kind of technique that allows us:
a. to implement all required functionalities of a system
b. to implement a first, complete and reliable version of a system
c. to extract requirements test potential solutions and remove risky parts.
d. to reduce and save costs being an essential activity in any project

c

why should we invest in requirements engineering?
a. it is alway necessary to invent as much as possible because better requirements always imply a better final product
b. it is necessary to invest but just to some extent. if we invest too much time or money it will be a waste of resources.
c. it is kind of investment that is not relevant for a software project
d. the investment should be around the 35% of the total project time.

b

use cases:
a. the term 'use cases' may refer to 1) an objective or service required by an user and 2) the set of interactions to get such objective
b. they are a critical factor to get a good requirement specification
c. they represent a kind of a temporal flow diagram in which activities are states connect through arrows to other states defining a temporal workflow to fulfill a users need.
d. none of the aforementioned answers are correct

a

what is a requirement
1. a condition or capability needed by a user to solve a provoke or achieve an objective
b. a condition or capability that must be met or processed by a system or system component to satisfy a contract, standard, specification or other formally imposed document.
c. a documented representation of a condition or capability as in (1) and (2)
d. all of the aforementioned definitions are correct

d

a non-functional requirement....
a. defines a system capability
b. defines a system constraint
c. defines a system functionality
d. none of the aforementioned definitions are correct

b

given the next requirement (The MTBF (Mean Time Between Failures) of the car shall be at least 100 hours"
a. it is a non-functional requirement(reliability)
b. it is a functional requirement(reliability )

a

Let's suppose that we have a requirements specification to develop a web page from scratch. The client requests us that the web shall accomplish the W3C web standards. If we have a requirement such as "the web page shall accomplish with the W3C recommendation for multimedia contents. " We can classify this requirement into the next category:
a. user requirement(functional)
b. user requirement (non-functional)
c. software requirement(functional)
d. software requirement(non-functional)

d

the requirements traceability matrix must:
a. show the relationships between requirements and the implementation units.
b. explain potential conflicts, overlapping and redundancies between the different functionalities specified in the set of requirements
c. show the data workflow of our system
d. show the evolution (changes) of our requirements

a

in which of the following stage(s) a requirement can be completely removed:
a. proposed
b. proposed and validated
c. proposed. validated and implemented
d. proposed. validated implement and verified

a

The requirements engineering process comprises:
a. activities to understand and translate user needs into precise and unambiguous statements.
b. activities to simulate and state system requirements as models.
c. activities that are always mandatory.
d. activities that are executed in a liner way and based on models

a

regarding requirement traceability, select the CORRECT statement
a. the traceability of a requirement indicates that the requirement is correct
b. the traceability of a requirement indicates that the requirement is atomic
c. the traceability of a requirement indicates that the requirement source is clear and exists because a reason.
d. the traceability of a requirement indicates that the requirement is not ambiguous.

c

a software requirements specification is CONSISTENT iff:
a. it describes all relevant needs for all stakeholders
b. it does not include any conflict
c. every requirement states is one that the software shall meet.
d. it is clear without ambiguities.

b

in the requirements elicitation and description process, if there is a NON SATISFIED transition, what it should NOT BE done?
a. restart again the process of identifying requirements
b. make interviews
c. write a new version of the requirement statement.
d. verify the requirement with the client

d

what is a stakeholder in the context of software engineering?
a. it is a person or identity that affects or is affected by the target software system
b. it is a client representative that makes decisions about the software system.
c. once the software system is in production, it is a kind of end-user that gives us feedback
d. any person that works in the management or development of the software system.

a

the problem of over-specification occurs when
a. there is information in the requirement statements that is not relevant for the problem being specified.
b, there are aspects of the problem that are not stated within the requirements.
c. there are elements that do not correspond to the problem but to a potential solution
d. there are future references

c

how can we do to "not omit anything relevant" in a requirement specification?
a. using a requirements management tool to uniquely identify each requirement
b. using one and only writing style
c. making a peer view with experts, clients, etc
d. making an ambiguity checking process

c