cs4473B/cs9551B
INDIVIDUAL TEMPLATE
Reading Summary and Questions and Answers
Rules – please note these carefully:
● Submission filename MUST be: “Last-name First-name” “Group”<id>_”Chapter” (or reading) <id>
(e.g., Blogs Joe_Group 3_Chapter 2)
● This template must be used for ONLY ONE chapter (or reading) at a time. For the second item of
reading, if any, please use another copy of this template.
● PLEASE compress multiple files (one file/chapter) using standard (e.g., Windows) compression
that can be uncompressed on a Windows machine with simple clicks. Please do not use
unusual/fancy compression tool; your template won’t be graded and you will be penalised.
● Submission to be done on OWL as per the deadline set.
● EMAIL SUBMISSION WILL NOT BE ACCEPTED AND WILL INCUR PENALTY.
● Use of template is mandatory: submission of text made outside the template will result in a zero
mark.
● Altering this template (meta-items) will incur a penalty.
● Submission format is MS WORD only (not PDF). PDF files will incur a penalty.
● The source of the answer captured from the chapter must be accurate or closest to the context
(e.g., Chapter #, Section or sub-section #, page number, etc.).
● The question must be properly and fully specified, and easily understandable. Cryptic text or
grammatical errors will be penalised – no appeals accepted.
● The question must not be so general or non-specific to apply to non-specific answers.
● The answer (text identified from chapter) must be an important point, not something trivial or
highly specific to a context.
● Answer from the book must be copied “as-is” from the text (reference to chart/table/figure/etc.,
in the reading is permitted and encouraged). Cryptic text or grammatical errors will be penalised –
no appeals accepted.
o If in doubt about the quality or acceptability of your text, you will have one chance to have
it reviewed by the instructor for “live” feedback. No emails please.
● Assessment of your submitted template will be done sometime before the end of the term. Please
do not expect marks of your submission every week!
● There will be no “remake” of the summaries (e.g., for improving the mark). It is a one-time
submission and assessment. Late submissions will not be accepted.
Part 1: Summary
Group member’s name: _______________________ Group No: ___________
Please write the full reference of the reading in the WHITE box below.
o Chapter #, Chapter title (or article title if appropriate).
o Book title
o Author(s)
o Publisher
o Book edition, Year of publication
(Example shown below; overwrite on that space.)
Chapter 30
Please write in the WHITE box below an abstract of the reading in 50-75 words.
Estelle struggles with managing requirements in a document-based
system, facing issues like version control, tracking changes, and
organizing requirements for different releases. Requirements
development (RD) and requirements management (RM) tools address
these limitations by improving collaboration, traceability, and
automation. RD tools assist in eliciting and refining requirements, while
RM tools help store, track, and manage them efficiently. However,
selecting and implementing these tools requires careful planning,
training, and cultural adaptation. While tools enhance efficiency, they
cannot replace a well-defined requirements process. Proper user
adoption and disciplined usage are key to maximizing their benefits and
avoiding ineffective implementation.
Part 2: Questions, Answers and Comments
Please create THREE important Question-Answer-Comment sets from the given reading:
● State your question succinctly. Add more lines as needed.
● State <LOCATION of answer in the book (e.g., section #>: <as-is answer EXACTLY from the book>
; please indicate whether a hardcopy or ebook ‘cause the page numbers are not the same.
● State your Comment related to the answer; this is mandatory.
NOTE: The following will be penalised: a cryptic question; inaccurate copying of the answer; a trivial
point; “too specific or small detail”; missing or trivial comment; etc.. Informative, insightful, or key
concept/idea, question, answer, and comment are expected.
o Actual chart/table/figure/etc. must NOT be given in the text below, but you may site its
location in the reading by giving precise specification.
For staff use only:
__________________________________________________________________________________
__________________________________________________________________________________
(1)
QUESTION: what is Elicitation tools
ANSWER: <Select one: ebook><209>
Elicitation tools include those used for recording notes during elicitation sessions.
These enable the
BA to quickly organize ideas and to annotate follow-up questions, action items,
core terms, and
the like. Mind-mapping tools facilitate brainstorming as well as organizing the
information
produced. Audio pens and other recording tools allow playback of conversations
or provide
visual reminders of what happened during an elicitation session. Some recording
devices also tie
the audio directly to the text that was written at the same time, enabling you to
hear specific
portions of the audio conversation as needed. Tools that support quality checks,
such as scanning
a requirements document for vague and ambiguous words, help a BA write
clearer requirements.
Some elicitation tools convert requirements from text to auto-generated
diagrams. Certain tools
also enable collaborative voting to help a team prioritize requirements.
.COMMENT (also include where possible: an *example*, citation, justification, etc. -- to support
your comment).
The answer provides a concise definition of elicitation tools and highlights their role
in capturing, organizing, and refining requirements during elicitation sessions. However,
the response could be improved by adding specific examples, justification, and the significance of
these tools in the broader requirements engineering process.
For staff use only:
__________________________________________________________________________________
__________________________________________________________________________________
(2)
QUESTION: what is Prototyping tools
ANSWER: < ebook><107>
Prototyping tools facilitate the creation of work products that range from
electronic mock-ups to
full application simulations. Simple prototyping tools come with basic shapes and
designs to create
low-fidelity wireframes ([ref080]). Common applications such as Microsoft
PowerPoint can be
used to quickly mock up screens and the navigations between them or to
annotate existing screen
shots.
COMMENT (also include where possible: an *example*, citation, justification, etc. -- to support your
comment):
The provided answer correctly defines prototyping tools as tools used to
create mock-ups and simulations of applications. However, it could be enhanced
with examples, justification, and a deeper explanation of their importance in software development .
For staff use only:
__________________________________________________________________________________
__________________________________________________________________________________
3)
QUESTION: how to manage Manage versions and changes
ANSWER: ebook<107>
Your project should define one or more requirements baselines,
each identifying a specific collection of requirements allocated to a particular
release or iteration.
Some RM tools provide baselining functions. The tools also maintain a history of
the changes
made to each requirement. You can record the rationale behind each change
decision and revert
to a previous version of a requirement if necessary. Some tools contain a change-
proposal system
that links change requests directly to the affected requirements
COMMENT (also include where possible: an *example*, citation, justification, etc. -- to support
your comment):
The provided answer correctly outlines the importance of managing versions
and changes in requirements management. However, it could be enhanced with
concrete examples, justification, and references to best practices for effective version
control.