CS364
In the Collaborative Writing (CW) article, the author identifies several benefits to CW as
described in the literature. Select all that are mentioned in the article. -
1-Generation of new ideas and better ideas through varying viewpoints and
experiences
2-Bonding between authors
3-Higher quality and more understandable documents
4-Improved learning by the contributors
More accuracy and less errors
Brainstorming -
Sam and Sue are orally discussing several different strategies for their upcoming
term paper.
Converging on brainstorming -
After reviewing all the ideas for their paper, Sue decides on which approach to
follow.
Outlining -
Sam creates a mater-plan for the paper.
Drafting -
Sue sits down and writes the introduction.
Reviewing -
Sue reads the paper aloud looking for awkward wording
Revising -
Sam fixes the mistakes that were previously noted on the draft.
Copyediting -
Sue makes the paper compliant with the IEEE standard
Writer -
One who produces content
Consultant -
One who answers questions and provides data but does not write
Editor -
One who "owns" the document
Reviewer -
1|Page
, One who provides feedback on the document.
Team leader -
One who organizes the writing effort.
Facilitator -
A coach to the writing team.
According to Royce, what is the relationship between documentation and design early in the
software development process? -
Documentation is the design
According to to Faulk, there are two types of requirements: functional and non-functional.
There are also behavioral requirements and developmental quality attributes. Which of the
following best describes the relationship between these concepts? -
Functional requirements is very similar to behavioral requirements. Non-functional
requirements is very similar to developmental quality attributes.
Which of the following best describes the relation between the problem space and the
solution space as it pertains to the SRS and SDD? -
The SRS defines the problem space and the SDD defines the solution space.
In "4.1 Essential Difficulties" and "4.2 Accidental Difficulties", the author makes reference to
Brooks' distinction between things which are hard due to the very nature of the problem
(Essential) or hard because we don't know a better way of doing it (Accidental). Classify each
of the following hindrances to requirements engineering as accidental or essential.
Due to lack of discipline, important steps in the development process are skipped. -
Accidental
In "4.1 Essential Difficulties" and "4.2 Accidental Difficulties", the author makes reference to
Brooks' distinction between things which are hard due to the very nature of the problem
(Essential) or hard because we don't know a better way of doing it (Accidental). Classify each
of the following hindrances to requirements engineering as accidental or essential.
Stakeholders do not know what they want and cannot explain what they do know. -
Essential
In "4.1 Essential Difficulties" and "4.2 Accidental Difficulties", the author makes reference to
Brooks' distinction between things which are hard due to the very nature of the problem
(Essential) or hard because we don't know a better way of doing it (Accidental). Classify each
of the following hindrances to requirements engineering as accidental or essential.
Large and complex systems are difficult or impossible to visualize -
Essential
In "4.1 Essential Difficulties" and "4.2 Accidental Difficulties", the author makes reference to
Brooks' distinction between things which are hard due to the very nature of the problem
(Essential) or hard because we don't know a better way of doing it (Accidental). Classify each
of the following hindrances to requirements engineering as accidental or essential.
2|Page
, It is very difficult to anticipate which requirements will be difficult and which will be easy to
meet. -
Essential
In "4.1 Essential Difficulties" and "4.2 Accidental Difficulties", the author makes reference to
Brooks' distinction between things which are hard due to the very nature of the problem
(Essential) or hard because we don't know a better way of doing it (Accidental). Classify each
of the following hindrances to requirements engineering as accidental or essential.
The requirements document is not written for the purpose of being understandable or a good
reference. -
Accidental
In "4.1 Essential Difficulties" and "4.2 Accidental Difficulties", the author makes reference to
Brooks' distinction between things which are hard due to the very nature of the problem
(Essential) or hard because we don't know a better way of doing it (Accidental). Classify each
of the following hindrances to requirements engineering as accidental or essential.
The wrong tool is used for the job. A document meant to address one issue is used for
another, thereby making it unfit for the purpose it was meant to achieve. -
Accidental
Faulk lists several properties of a "good" SRS. Please match the property name with the
description.
Complete -
If the development team were to provide a system meeting every requirement, then
the system should be satisfactory for the client
Faulk lists several properties of a "good" SRS. Please match the property name with the
description.
Implementation independent -
The SRS should not specify how the system is to be built, but rather what it is to do.
The design team should have the freedom to pursue any design that meets the requirements.
Faulk lists several properties of a "good" SRS. Please match the property name with the
description.
Unambiguous and consistent -
There must be no "wiggle room". Every requirement must have exactly one
interpretation.
Faulk lists several properties of a "good" SRS. Please match the property name with the
description.
Precise -
Only the required behavior should be described as exactly as possible.
3|Page
In the Collaborative Writing (CW) article, the author identifies several benefits to CW as
described in the literature. Select all that are mentioned in the article. -
1-Generation of new ideas and better ideas through varying viewpoints and
experiences
2-Bonding between authors
3-Higher quality and more understandable documents
4-Improved learning by the contributors
More accuracy and less errors
Brainstorming -
Sam and Sue are orally discussing several different strategies for their upcoming
term paper.
Converging on brainstorming -
After reviewing all the ideas for their paper, Sue decides on which approach to
follow.
Outlining -
Sam creates a mater-plan for the paper.
Drafting -
Sue sits down and writes the introduction.
Reviewing -
Sue reads the paper aloud looking for awkward wording
Revising -
Sam fixes the mistakes that were previously noted on the draft.
Copyediting -
Sue makes the paper compliant with the IEEE standard
Writer -
One who produces content
Consultant -
One who answers questions and provides data but does not write
Editor -
One who "owns" the document
Reviewer -
1|Page
, One who provides feedback on the document.
Team leader -
One who organizes the writing effort.
Facilitator -
A coach to the writing team.
According to Royce, what is the relationship between documentation and design early in the
software development process? -
Documentation is the design
According to to Faulk, there are two types of requirements: functional and non-functional.
There are also behavioral requirements and developmental quality attributes. Which of the
following best describes the relationship between these concepts? -
Functional requirements is very similar to behavioral requirements. Non-functional
requirements is very similar to developmental quality attributes.
Which of the following best describes the relation between the problem space and the
solution space as it pertains to the SRS and SDD? -
The SRS defines the problem space and the SDD defines the solution space.
In "4.1 Essential Difficulties" and "4.2 Accidental Difficulties", the author makes reference to
Brooks' distinction between things which are hard due to the very nature of the problem
(Essential) or hard because we don't know a better way of doing it (Accidental). Classify each
of the following hindrances to requirements engineering as accidental or essential.
Due to lack of discipline, important steps in the development process are skipped. -
Accidental
In "4.1 Essential Difficulties" and "4.2 Accidental Difficulties", the author makes reference to
Brooks' distinction between things which are hard due to the very nature of the problem
(Essential) or hard because we don't know a better way of doing it (Accidental). Classify each
of the following hindrances to requirements engineering as accidental or essential.
Stakeholders do not know what they want and cannot explain what they do know. -
Essential
In "4.1 Essential Difficulties" and "4.2 Accidental Difficulties", the author makes reference to
Brooks' distinction between things which are hard due to the very nature of the problem
(Essential) or hard because we don't know a better way of doing it (Accidental). Classify each
of the following hindrances to requirements engineering as accidental or essential.
Large and complex systems are difficult or impossible to visualize -
Essential
In "4.1 Essential Difficulties" and "4.2 Accidental Difficulties", the author makes reference to
Brooks' distinction between things which are hard due to the very nature of the problem
(Essential) or hard because we don't know a better way of doing it (Accidental). Classify each
of the following hindrances to requirements engineering as accidental or essential.
2|Page
, It is very difficult to anticipate which requirements will be difficult and which will be easy to
meet. -
Essential
In "4.1 Essential Difficulties" and "4.2 Accidental Difficulties", the author makes reference to
Brooks' distinction between things which are hard due to the very nature of the problem
(Essential) or hard because we don't know a better way of doing it (Accidental). Classify each
of the following hindrances to requirements engineering as accidental or essential.
The requirements document is not written for the purpose of being understandable or a good
reference. -
Accidental
In "4.1 Essential Difficulties" and "4.2 Accidental Difficulties", the author makes reference to
Brooks' distinction between things which are hard due to the very nature of the problem
(Essential) or hard because we don't know a better way of doing it (Accidental). Classify each
of the following hindrances to requirements engineering as accidental or essential.
The wrong tool is used for the job. A document meant to address one issue is used for
another, thereby making it unfit for the purpose it was meant to achieve. -
Accidental
Faulk lists several properties of a "good" SRS. Please match the property name with the
description.
Complete -
If the development team were to provide a system meeting every requirement, then
the system should be satisfactory for the client
Faulk lists several properties of a "good" SRS. Please match the property name with the
description.
Implementation independent -
The SRS should not specify how the system is to be built, but rather what it is to do.
The design team should have the freedom to pursue any design that meets the requirements.
Faulk lists several properties of a "good" SRS. Please match the property name with the
description.
Unambiguous and consistent -
There must be no "wiggle room". Every requirement must have exactly one
interpretation.
Faulk lists several properties of a "good" SRS. Please match the property name with the
description.
Precise -
Only the required behavior should be described as exactly as possible.
3|Page
