Software Engineering Exercise 3 – Functional & Non Functional Requirements

Software Engineering Exercise 3 – Functional & Non Functional Requirements

This exercise is meant as class work only and there is no need to submit.

Part A
Divide into groups and choose an organization for which you will build a computerized system.
For this system write:

• 
  At least 10 functional requirements.
  
• 
  At least 10 non-functional requirements.
  

Each requirement should be classified according to the type of requirement.
Part B

1. 
   A customer of a software system wants to define the system requirements himself, but the system analyst requires performing the process together with the customer. What reasoning justifies the requirement of the systems analyst?
   

1. 
   The client knows what his pain points are, but he does not have the professional tools to analyse the problem
   
2. 
   The customer has interests that could harm the system
   
3. 
   The customer is not as smart as the system analyst
   
4. 
   The customer does not know how to program
   

2. 
   Consider the following requirement: "A movie ticket can be purchased through the system with any mobile device available to the buyer." How can it be classified?
   

1. 
   This is a Supportability requirement
   
2. 
   This is a Reliability requirement
   
3. 
   This is a Performance requirement
   
4. 
   This is a Usability requirement
   

3. 
   Consider the following requirement: "The system will be user-friendly". What is the problem of such a requirement?
   
   1. 
      It is irrefutable.
      
   2. 
      It does not describe how the system will be user-friendly.
      
   3. 
      There is no correct answer
      
   4. 
      As software engineers we cannot be responsible for system friendliness.
      

4. 
   In the software system for selling tickets to events at the stadium, the following requirement was defined: "The identification of visitors who purchased tickets for a show at the stadium will be done by identifying the fingerprint of the visitors at the entrance gates." How can it be classified?
   

1. 
   This is a Supportability requirement
   
2. 
   This is a Usability requirement
   
3. 
   This is a Reliability requirement
   
4. 
   This is a Performance requirement
   

5. 
   Consider the following requirement: "The system will run on operating systems Windows 8 and higher." How can it be classified?
   
   1. 
      This is a Performance requirement
      
   2. 
      This is a Supportability requirement
      
   3. 
      This is a Reliability requirement
      
   4. 
      This is a Usability requirement
      

6. 
   In the requirements document of the moodle college system, the following requirement was defined in the chapter on non-functional requirements: The system will allow several students to work in parallel. What is the problem with defining this requirement?
   
   1. 
      This is a requirement for the structure of the entities in the system and therefore it should appear in the department chart (the student entity will be linked in a many to one relationship to the system entity)
      
   2. 
      The number of students who can connect to the system in parallel must be defined in a measurable manner
      
   3. 
      This is an illegitimate requirement because no technology can really guarantee that during system load you can serve multiple users simultaneously
      
   4. 
      There is no correct answer
      

7. 
   Consider the following requirement: When a user changes a password, the system must keep it encrypted. How should this requirement be classified?
   
   1. 
      Reliability Requirement
      
   2. 
      Functional Requirement
      
   3. 
      Usability Requirement
      
   4. 
      Performance Requirement
      

8. 
   Should students who set up the system give up analyzing the system and start programming it immediately?
   

1. 
   No, system analysis ensures that the customer will be satisfied with the end result
   
2. 
   No, the system must be analyzed to ensure that there is no change in requirements during development
   
3. 
   No, system analysis makes it easy to correct design errors without having to rewrite code
   
4. 
   No, the system must be analyzed before application, so that there is good documentation to accompany it
   

9. 
   What characterizes the requirement that every action in the system be performed within a maximum of one second?
   

a. This is a Reliability Requirement
b. This is a functional requirement
c. This is a Performance Requirement
d. This is a Usability Requirement

10. 
    Since the restaurant employs many French-speaking waiters, it was decided to add a requirement to develop a user interface for the system in this language. What kind of requirement is this?
    

a. This is a Performance Requirement
b. This is a Usability Requirement
c. This is a Supportability Requirement
d. This is a functional requirement