software Requirment Engineering, Assignments of Requirements Engineering

it cover a Assigment of software Riquirment engineering

Typology: Assignments

2020/2021

Uploaded on 07/07/2021

muzamil-channa
muzamil-channa 🇵🇰

5

(1)

8 documents

1 / 11

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Activity 1 –
1) Users must be able to browse for events by name or date or venue
ANSWER Functional Requirement (FR)
2) searching for events by keywords should also be possible
ANSWER Functional Requirement (FR)
3) User will select ticket price from those offered and also specify the number of
tickets they require
ANSWER Functional Requirement (FR)
4) The system should display availability of the tickets within five seconds
ANSWER The system should display availability of the ticket is a Functional
Requirement FR and within five second is a Non Functional Requirement
(NFR – performance).
5) Users must be able to choose their seats and purchase tickets 24/7
ANSWER user must be able to choose their seats and purchase tickets is
Functional Requirement FR and 24/7 Non Functional Requirement
(NFR– availability).
6) Only registered customers can buy tickets
ANSWER Only registered customers is Non Functional Requirement (NFR
– access) and can buy tickets is Functional Requirement (FR).
7) Daily reports of ticket sales must be generated. These must be retained for
two years.
ANSWER Daily Non Functional Requirement (NFR – availability) reports
of ticket sales must be generated Functional Requirement (FR). These must
be retained for two years Non Functional Requirement (NFR – archiving &
retention).
8) All data is to be backed up nightly
ANSWER All data is to be backed up nightly Non Functional Requirement
(NFR – backup).
pf3
pf4
pf5
pf8
pf9
pfa

Partial preview of the text

Download software Requirment Engineering and more Assignments Requirements Engineering in PDF only on Docsity!

Activity 1 –

  1. Users must be able to browse for events by name or date or venue ANSWER Functional Requirement (FR)
  2. searching for events by keywords should also be possible ANSWER Functional Requirement (FR)
  3. User will select ticket price from those offered and also specify the number of tickets they require ANSWER Functional Requirement (FR)
  4. The system should display availability of the tickets within five seconds ANSWER The system should display availability of the ticket is a Functional Requirement FR and within five second is a Non Functional Requirement (NFR – performance).
  5. Users must be able to choose their seats and purchase tickets 24/ ANSWER user must be able to choose their seats and purchase tickets is Functional Requirement FR and 24/7 Non Functional Requirement (NFR– availability).
  6. Only registered customers can buy tickets ANSWER Only registered customers is Non Functional Requirement (NFR

- access) and can buy tickets is Functional Requirement (FR).

  1. Daily reports of ticket sales must be generated. These must be retained for two years. ANSWER Daily Non Functional Requirement (NFR – availability) reports of ticket sales must be generated Functional Requirement (FR). These must be retained for two years Non Functional Requirement (NFR – archiving & retention).
  2. All data is to be backed up nightly ANSWER All data is to be backed up nightly Non Functional Requirement (NFR – backup).

9) It should not be possible to double-book tickets (i.e. buy a ticket that has already been sold) ANSWER Non Functional Requirement (NFR - robustness).

  1. Ad hoc reporting will be required, showing ticket sales over a week. It should be possible to vary that time span and look at any duration up to six months ANSWER Ad hoc Non Functional Requirement (NFR – availability) reporting will be required, showing ticket sales over a week Functional Requirement (FR). It should be possible to vary that time span and look at any duration up to six months Functional Requirement (FR)

Activity 2 – Document Management System

PART 1 ANSWER

 Anyone can able to browse the catalogue

Include

  • Whenever a user want to upload or download a record they need to submit information about their membership.
    • Downloading and uploading Document members, including membership authentication

Extend:

 If the data input do not match current members, they will have a registration chance  The usage case Authenticate Member will be extended by Register Member provided the user is not registered.

Activity 3 – At the Vet

QUESTION NO 1 (ANSWER)

1. “This facility is to be usable in a noisy and dirty workshop environment” (usability) or 2. “This must be possible on all shifts, including overtime” (availability).

Two Solution

1. “The time and materials used data is to be captured on touch screens next to the machines on the factory floor”. 2. “The sales manager has asked for secure remote access via VPN using a laptop to the historic data on the system when working away from the office”.

Two Ambiguous

1. “The system is to provide management with a data mining type function to drill down on historic data.” 2. Different people may have different ideas of ‘a data mining type function’ would include, or what ‘drilling down’ means, or how far back historic data goes, etc.

Two Conflicting

1. “The system is to log the craftsperson, start and finish time and materials used for each manufacturing job” and “The system is to provide a “time spent” analysis (time to set up, time per step, rework time, etc.) report of the work done by each craftsperson” – 2. The system cannot provide the required analysis if it only logs start and finish times. QUESTION 2 ANSWER Stakeholder: MD (the project sponsor) Elicitation Technique: Interview Justification: The Terms of Reference need to be clarified, a report must be prepared, and any 'politics' identified; confidential concerns may also need to be examined. We also need to examine the "data mining function" of the MD.

Stakeholder: Management Team Elicitation Technique: Workshop Justification: To explore the company goals and/or reporting. Enabling control levels of commitment to guarantee ownership of the objectives/ needs detect differences of opinion. Require remote access by Clarify Sales Manager. Stakeholder: Craftspeople Elicitation Technique: Prototyping Justification: User interface prototyping to develop usability requirements. They presumably don't think about concepts and we don't seem to have a computer system, thus a mockup might minimise costly errors. QUESTION 3 ANSWER 1 MUST There would be no system unless we begin to record the data! It is tied directly to the core goal (better costing information for future jobs). 2 Do not classify the first part as not a solution as a requirement until rewritten. the second part is (no- functional).SHOULD or COULD The second portion offers a manual workaround. The priority is based on the first portion assigned. 3 Must That's the entire system point. There is no use in collecting the data if it is unable to do so. 4 Could It is not clear that the main goal (cost information) is directed directly because it's about analysing the time spent. Without this reporting, the system would still fulfil its fundamental goal. 5 Either decline to classify until it is Without remote access the system would

The scenario shows whatever the materials in each job are used, but the class model claims that each job use just one material

  • Requirement 1 states that we must record the start-up and end times for each job, but no characteristics for each job are available.
  • The class model indicates that more than one Craftsperson can work on each job, but only 1 is required.
    • No data are available to allow the system to compute overall costs to fulfil requirement 3 or quantity of material used to compute material costs.