1. Examples of Final Exam Questions
SEG3101
Examples of Final Exam Questions

3. Geneviève Bergeron, 21, was a second year scholarship student in civil engineering.
Hélène Colgan, 23, was in her final year of mechanical engineering and planned to take her Master’s degree.
Nathalie Croteau, 23, was in her final year of mechanical engineering.
Barbara Daigneault, 22, was in her final year of mechanical engineering and held a teaching assistantship.
Anne-Marie Edward, 21, was a first year student in chemical engineering.
Maud Haviernick, 29, was a second year student in engineering materials, a branch of metallurgy, and a graduate in environmental design.
Barbara Maria Klucznik, 31, was a second year nursing student.
Maryse Laganière, 25, worked in the budget department of the Polytechnique.
Maryse Leclair, 23, was a fourth year student in engineering materials.
Anne-Marie Lemay, 27, was a fourth year student in mechanical engineering.
Sonia Pelletier, 28, was to graduate the next day in mechanical engineering. She was awarded a degree posthumously.
Michèle Richard, 21, was a second year student in engineering materials.
Annie St-Arneault, 23, was a mechanical engineering student.
Annie Turcotte, 20, was a materials engineering student.

4. Requirements Writing and Quality Measurement
The following requirements about a library system are non- functional requirements stated in an unverifiable way. For each, indicate the quality attribute considered and rewrite it so that it is verifiable (make up some suitable details).
The System shall respond to users in a timely manner.
The System shall provide a good throughput.
The System shall be easy to learn to use.

5. Requirements Writing, Quality Measures and Management Tools
You were hired as a requirements analyst by a software tool development company to write requirements for a new Wiki- like collaboration feature for IBM Rational DOORS. It has been decided not to integrate an existing Wiki to DOORS. Based on your knowledge of requirements management tools and of Wikis, provide answers to the following questions. Your answers must be realistic in the context of requirements management tools and follow “good requirements writing guidelines”.
Give two functional requirements for this Wiki-like feature for DOORS.
Give two non-functional requirements (of different types) for this Wiki-like feature for DOORS.

6. Domain Models and Class Diagrams (1/2)
UML class diagrams are often used to model domains. The following diagram describes a very simplified and incomplete domain model of a tool intended to create and analyze Use Case Maps (UCM).

7. Domain Models and Class Diagrams (2/2)
Using your knowledge of the UCM language, add to this model (class with attributes as well as associations / compositions with roles and multiplicities directly on the above diagram) the concept of Component, which is an integral part of a Map. A component is of type CompKind and can include sub-components. Path elements (e.g., start/end points, responsibilities, etc.) can also optionally be bound to a component
UML class diagrams are often too imprecise to describe in detail a domain and all of its subtleties. Describe precisely (in English or in French) two constraints required for a better specification of the UCM domain model shown in the above class diagram (including the new Component class). At least one constraint must involves navigating through an association.

8. UCM Modeling For your project’s UCM model (with 3 Boolean variables):
Give 3 scenario definitions that ensure full segment coverage.
Modify the model and relevant scenario definitions to handle a timeout in case a Query is not provided in a timely fashion.

9. Requirements Prioritization
A simple cost/value approach for requirements prioritizing is not sufficient in practice for various reasons. Which of the following suggestions is not a possible improvement of a simple cost/value approach?
Adding criteria for the ease of use at the organizational level and ease of implementation at the technical level
Using pairwise comparisons and clustering requirements as services/features
Adding estimates for benefits, penalties, implementation costs and technical risks
Not considering requirement interdependencies
Adding criteria for value as seen by customers and value as seen by the business

10. Requirements Prioritization
In the Analytic Hierarchy Process (AHP) requirements prioritization approach, it is suggested to apply pairwise comparisons to clusters of connected requirements such as features rather than to individual requirements. Briefly explain why.

11. Requirements Negotiation
During this term, you worked on defining requirements for a [insert this year’s project!]. Provide answers to the following questions in the context of this project.
Give two examples of stakeholders with conflicting requirements. For each example, briefly explain the potential conflict.
Describe how you would handle negotiation to resolve conflicting requirements.

12. Requirements Negotiation
Circle which of the following assertions (about the responsibilities of requirements analysts) does not apply to requirements negotiation:
You must arrive at an agreement on a set of coherent requirements which satisfies all stakeholders as much as possible.
You must detect when user requirements are inconsistent.
You must avoid involving managers in the negotiations.
You must evaluate the importance of inconsistent requirements for each involved stakeholder.
You must convince each stakeholder involved in the negotiation to understand the essential requirements from the point of view of the others stakeholders.

13. Requirements Validation and Verification
Inspection is an effective technique for requirements verification and validation. Briefly explain the importance of checklists for requirements inspection.
Which type of analysis would you use with DOORS to discover which tests (in a test module) need to be re- examined following a requirement modification (in a requirements module)?

14. Requirements Management
A requirement may have different statuses (states) in a Requirements Management System. Complete the following simple state machine (there are no events or actions on transitions) describing the lifecycle of a requirement in a Requirements Management System. You must have at least 6 statuses (states).

15. Traceability
It is advised to define several types of links in order to establish precise traceability relations in a Requirements Management System. Supplement the following table by defining 4 types of links and indicating the types of source and target objects (user requirement, system requirement, test, a part of a UML/URN model, etc.) of these links.
Link Type
Source Object Type
Target Object Type

16. Features Interactions
Suppose a UCM model where a dynamic stub contains 3 features described as plug-ins: A, B, and C. A Default plug-in is also included.
As in assignment #2, it is possible to subscribe to each of these features. This is represented using Boolean variables subA, subB and subC. An attempt was made to solve an interaction problem between the features by giving the user the possibility to state preferences using two Boolean variables Pref1 and Pref2. Show (with a counter-example) that the following situation is incorrect.
Selection Policy:
(!subA && !subB && !subC)  Select Default
subA && ( (!subB && !subC) || (Pref1 && Pref2) )  Select A
subB && ( (!subA && !subC) || (!Pref1 && Pref2) )  Select B
subC && ( (!subB && !subA) || (Pref1 && !Pref2) )  Select C
!subA, subB, subC, Pref1, Pref2  nothing selected

17. Requirements Modeling
URN includes two types of diagrams (GRL and UCM) for various modeling tasks. Briefly describe what each of the following URN diagrams could be used for in the context of requirements specification.
GRL Diagrams:
UCM Diagrams:

18. UML State Machine
The Ebooking System is an automated check-in system to be used in airports to speed-up passenger check-in with little assistance from agents.
A passenger willing to check-in for a flight must enter a reservation number. If there is a reservation with the given number, the booked flight is displayed to the passenger on a touch screen and the passenger is presented with a button to CONFIRM and a button to request a CHANGE. If the reservation can not be found, an error message is displayed and the passenger is asked to enter another reservation number.
If the passenger chooses to confirm by pressing the CONFIRM button, the system asks whether or not the passenger has any baggage to check, and if the customer presses NO, then the system prints and ejects a boarding pass which the customer can then take to the departure gate.
If the passenger pressed YES (has baggage to be checked in), the system asks for the number of baggage pieces. After the passenger has indicated the number of pieces, the system prints and ejects a boarding pass, as well as the required number of luggage slips. The system also displays a message asking the passenger to proceed immediately to a check-in agent who will handle the baggage.
If the passenger wishes to make a change to the reservation, he or she presses the CHANGE button on the screen, the system displays the reservation details and the details for the next available flight to the same destination and asks if the customer wishes to change to the following flight. The customer again has the option of CONFIRMing or CHANGing to the next flight. In either case, the same procedure as before applies once more.
Whenever a boarding pass or luggage slips have been printed and the customer has not taken them from the machine within 15 seconds, the machine sounds an alarm until the documents are taken by the customer.
A CANCEL button is displayed all the time after the check-in process has started. The passenger can choose to cancel checking-in by pressing this button. In that case, the system should return to asking for a reservation number.

20. SPLs and Feature Models
Typical questions:
Is the following configuration valid?
Does this model contain dead features? If so, what are they?
Does this model contain core features? If so, what are they?
Combining this FM with a GRL model, what would be the best valid configuration?

21. RE in Different Software Development Processes
Rational Unified Process (RUP) and eXtreme Programming (XP) promote two different approaches for requirements engineering.
What are two main differences between RUP and XP regarding requirements engineering?
What are two advantages of RUP over XP regarding requirements engineering?
What are two advantages of XP over RUP regarding requirements engineering?

22. RE in Different Software Development Processes
What have you learned this year?
How to use this in practice, realistically, in your capstone project?
What are the requirements specific to mobile applications that need to be elicited?
How can you improve RE practices a given agile or RUP process in a specific (e.g., where you had your last internship)?