TU Wien:Requirements Engineering and Specification VU (Grünbacher)/Practical Test 2021-12-15

Die Prüfung wurde im Rahmen von Distance Learning abgehalten. Tuwel-Test, 60 Minuten.

1) Elicitation.

A company is developing a Bug Tracking application for identifying and tracking bugs in software projects or for systems during operation. The Bug Tracking application can be tailored to different types of customers and market segments. Specifically, administrators can log in to the app and enter the details of projects and staff members, view the complaints of users, assign tasks to the members, track the bug resolution status, and send messages to users. The Staff can log in to the app to view bug complaints assigned to them and start working on them. If a member is unable to resolve a bug issue, they can forward the problem to another member. Users can view the progress status of their bug complaints. Users can also use the ticket number generated during the submission of their compliant and view the solution plan details for the same.

(a) Identify key stakeholders for developing this product line based on Alexander’s Onion Model. (2.5 points)

(b) Describe important Win Conditions, Issues, Options, and Agreements to illustrate the WinWin negotiation model (3.0 points)

(c) Characterize a key user of the system using a persona profile. (2.0 points)

2) Scenarios.

(a) Define a normal course scenario of the "Fix and Resolve Bug" use case of the Bug Tracking application (cf. question 1) using the style guide discussed in class. (4.5 points)

(b) Define one variation scenario and two alternative scenarios for this use case. (3.0 points)

3) Requirements Specification.

(a) Evaluate the following quality requirement regarding the IEEE Std. 830 SRS quality characteristics unambiguous, complete, verifiable. - Provide concise arguments for your evaluation. (3 points)

QR2: The HTML Parser shall produce an HTML markup error report to allow quick resolution of errors by novices.

(b) Discuss and argue which of the two proposals for SRS structures (Volere Template; SRS Outline according ISO/IEC/IEEE 29148) you would recommend for specifying the requirements of the Bug tracking App (cf. question 1). (2 points)

(c) Assuming that influential system stakeholders insist in specifying the Bug Tracking App according ISO/IEC/IEEE 29148: Which approach would you suggest for organizing the 'Specific Requirements' clause and why? (2 points)

4) Architecture Quality Requirements.

(a) Identify three main architectural drivers for the Bug Tracking App (cf. question 1 above). Provide concise arguments for your selection. (1.5 points)

(b) Identify one use case scenario, one growth scenario, and one exploratory scenario for the Bug Tracking App related to the architectural drivers identified under (a). Describe them using the stimulus-context-response format suggested by the 'Quality Attribute Workshop' (QAW). (4.5 points)

(c) Exemplify the QAW template for refining scenarios by applying it to one of the scenarios identified in (b). (2.0 points)