Answers |Actual Complete Exam| Already Graded A+
1. The agile concept of minimizing requirements
Barely suflcient require-
docu- mentation in favor of focusing on
ments
creating working software.
2. Creating detailed, non-functional
requirements be- fore software Big design up-front
construction starts. (BDUF)
3. How well you understand (or can understand) the cur- Clarity
rent and future state of the business and
correspond- ing software requirements.
4. The degree to which a system needs to serve a variety Client team
size and diver-
of clients, in different roles and in different 9. The
locations, supporting numerous variations in degree
business require- ments. to which
software
5. The degree to which software features features
involve com- plex data and calculations or depend
involve numerous varia- tions. on each
other
6. The degree to which a system faces high
and so
costs for poor reliability, security, safety,
must be
or auditability.
built or
7. A model that defines different sets of project designe
charac- teristics, indicating where agile and d in a
plan-driven ap- proaches are most appropriate particul
and likely to succeed. ar order.
8. The degree to which a system needs to
interoperate or exchange data with other
systems.
1/
27
, IS 321 Final Exam with all Correct & 100% Verified
Answers |Actual Complete Exam| Already Graded A+
sity
Complexity of features
Criticality
Home Grounds Model
Integration
Interdependence
2/
27
, IS 321 Final Exam with all Correct & 100% Verified
Answers |Actual Complete Exam| Already Graded A+
10. The various locations where the information technolo- IT
team locations gy development team members are
located. They can encompass multiple time zones,
native languages,
cultures, and organizations.
11. The need to increase the number, diversity, and matu- IT team new
skills needed
rity of skills in an IT team to match project
character- istics.
12. The number of team members in the IT team size
information technology development team.
13. The number of different software features that Number of features
need to be delivered in a project. Often
expressed as the number of user stories.
14. The amount of work a system must perform in Performance (chapter 10
terms
of volumes of users or transactions. Typically includes definition)
speed and reliability metrics.
15. A type of graph in which a series of measurements are Radar
chart
plotted on axes surrounding a central point.
16. 18. The degree to
which software
requirements
17.
remain the
same over
time.
3/
27