Select from the dropdown lists to complete the text.
Example stakeholder groups. Fill in the ASR categories they fall into.
- Students and teaching staff will be concerned with core functionality,
usability, availability and performance – ( core features, security - quality attribute, constraints, application environment, quality attributes ) and ( quality attributes, core features, constraints ).
- The examinations section will be particularly concerned with ( security – quality attributes, constraints, application environment ).
- The finance department will be concerned with the cost – ( constraints, application environment, security - quality attributes ).
- Management will be concerned with the cost, when the system will be
delivered and its effectiveness – ( constraints, quality attributes, application environment ), ( core features, quality attributes, security - quality attributes ).
- Designers will be concerned with how the system can be partitioned, what
the run-time elements will be and where they will be deployed – the
( application environment, constraints, core features, quality attributes ).
- Programmers will be concerned with the core functionality represented in
the design, how easily the design can be implemented in code and what
language(s) will be used – ( core features, application environment ), ( quality attributes, application environment, security - quality attributes ), ( constraints, quality attributes, core features, application environment ).
- Testers will be concerned with whether the system is easy to test – ( quality attributes, core features, application environment ).
. The IT department will be concerned with the operating environment and
how easy the system is to run – ( application environment, security - quality attributes, quality attributes, core features ).
- Developers responsible for maintaining the system will be concerned with
how easy the system is to modify – ( quality attributes, core features, application environment ).