Examples of Final Exam Questions

Slides:



Advertisements
Similar presentations
Chapter 4: Requirements Engineering
Advertisements

Software Testing and Quality Assurance
Testing dan Implementasi Sistem materi 4
Chapter 14 Requirements and Specifications. Copyright © 2005 Pearson Addison-Wesley. All rights reserved Software Engineering The implementation.
SE 555 Software Requirements & Specification Requirements Management.
Fundamentals of Information Systems, Second Edition
IS550: Software requirements engineering Dr. Azeddine Chikh 4. Validation and management.
Gregor v. Bochmann, University of Ottawa Based on Powerpoint slides by Gunter Mussbacher (2009) with material from: IEEE Standard, Daniel Amyot.
Chapter 4 Capturing the Requirements 4th Edition Shari L. Pfleeger
The Software Development Life Cycle: An Overview
RUP Requirements RUP Artifacts and Deliverables
Dynamic Black-Box Testing Part 2
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Chapter 6 Requirements Engineering Process.
1 REQUIREMENT ENGINEERING Chapter 7. 2 REQUIREMENT ENGINEERING Definition Establishing what the customer requires from a software system. OR It helps.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
Software Life Cycle Requirements and problem analysis. –What exactly is this system supposed to do? Design –How will the system solve the problem? Coding.
UML-1 3. Capturing Requirements and Use Case Model.
Systems Analysis and Design in a Changing World, 6th Edition
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
 Dr. Syed Noman Hasany.  Review of known methodologies  Analysis of software requirements  Real-time software  Software cost, quality, testing and.
Week 3: Requirement Analysis & specification
Essentials of OVID Using UML based notation to capture system requirements and design.
Software Requirements Specification Document (SRS)
Requirements engineering The process of establishing the services that the customer requires from a system and the constraints under which it operates.
HNDIT23082 Lecture 09:Software Testing. Validations and Verification Validation and verification ( V & V ) is the name given to the checking and analysis.
Daniel Amyot, University of Ottawa Based on Powerpoint slides by Gunter Mussbacher (2009) with material from: Jo Atlee, Dan Berry (both University of Waterloo);
Miguel Garzón, University of Ottawa Based on Powerpoint slides by Gunter Mussbacher (2009) with material from: Jo Atlee, Dan Berry (both University of.
The Quality Gateway Chapter 11. The Quality Gateway.
Emdeon Office Batch Management Services This document provides detailed information on Batch Import Services and other Batch features.
I-9 Express Overview What is I-9 Express? The service includes two Web sites that will help you eliminate paper, reduce costs, and maintain compliance.
1 Requirements Management - II Lecture # Recap of Last Lecture We talked about requirements management and why is it necessary to manage requirements.
Daniel Amyot, University of Ottawa Based on slides by Gunter Mussbacher (2009) and Stéphane Somé (2008) with material from these standards: IEEE ,
Testing dan Implementasi Sistem materi 4
Investigating System Requirements
CompSci 280 S Introduction to Software Development
Systems Analysis and Design in a Changing World, Fourth Edition
CSE 219 Final exam review.
Inspecting Software Requirement Document
PREPARED BY G.VIJAYA KUMAR ASST.PROFESSOR
Presentation on Software Requirements Submitted by
CSC 480 Software Engineering
Requirements Analysis Scenes
Chapter 8 – Software Testing
Objectives State the reasons for the complexity involved in the development of software Define the following terms Objects Classes Messages Methods Explain.
Business Models Modeling.
GROUP BOOKINGS.
EKT 421 SOFTWARE ENGINEERING
Requirements Analysis and Specification
System Modeling Chapter 4
Daniel Amyot and Jun Biao Yan
How does a Requirements Package Vary from Project to Project?
Introduction to Software Engineering
CS 790M Project preparation (I)
Chapter 3: The Requirements Workflow
Object-Oriented Analysis
UML State machine diagram
Lecture 09:Software Testing
Requirements Analysis
Verification and Validation Unit Testing
Examples of Final Exam Questions
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
System Construction and Implementation
Engineering Quality Software
Applied Software Project Management
Software Testing Lifecycle Practice
Subject Name: SOFTWARE ENGINEERING Subject Code:10IS51
CS 426 CS 791z Topics on Software Engineering
QUICK GUIDE TO CIRCULATION IN ALMA
CS 426 CS 791z Topics on Software Engineering
Presentation transcript:

Examples of Final Exam Questions SEG3101 Examples of Final Exam Questions Daniel Amyot, University of Ottawa Based on material from: S. Somé 2008, D. Amyot 2008, G. Mussbacher 2009, G.v. Bochmann 2010

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.

UCM Modeling You are asked to model the following business process using a single UCM diagram. Pay attention to the syntax, the use of the right components, and the right allocation of responsibilities to components. A summary of the UCM notation is available at the end of the exam. The Metasearch Engine for Systematic Literature Reviews (MESLiR) is a system that allows a student to do complex queries on three search engines (Google, Springer and Xplore) and to obtain the combined results. When a search query has been prepared by a student, MESLiR validates the query and returns an error message to the student if the query is syntactically invalid. If it is valid, the query is simultaneously executed on the three search engines. MESLiR then combines the obtained results. Finally, MESLiR presents the results to the student while at the same time keeping a local copy of the results in its database.

Requirements Prioritization A simple costs/values 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 costs/values 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

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

Requirements Negotiation During this term, you worked on defining requirements for a Metasearch Engine for Systematic Literature Reviews. Provide responses 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.

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 all the stakeholders to understand the essential requirements from the point of view of the others stakeholders.

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)?

Requirements Management A requirement may have different status (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).

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

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

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:

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.

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?