it3 Information Systems, Exercises of Information Systems

this is Information Systems and Information Systems examples

Typology: Exercises

2019/2020

Uploaded on 11/08/2020

nnniii8
nnniii8 🇸🇦

5 documents

1 / 11

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Functional and Non-Functional
Requirements
A requirement is a statement of what the
system must do or what characteristics it
needs to have.
Requirements describe
- what the business needs
(business requirements)
-what the users need to do
(user requirements)
- what the software should do
(functional requirements)
- characteristics the system should have
(non-functional requirements), and
-how the system should be built
(system requirements)
pf3
pf4
pf5
pf8
pf9
pfa

Partial preview of the text

Download it3 Information Systems and more Exercises Information Systems in PDF only on Docsity!

Functional and Non-Functional

Requirements

A requirement is a statement of what the system must do or what characteristics it needs to have.

  • (^) Requirements describe
    • what the business needs (business requirements)
    • what the users need to do (user requirements) - what the software should do (functional requirements) - characteristics the system should have (non-functional requirements) , and
    • (^) how the system should be built ( system requirements )

Functional Requirements (1/4)

Functional requirements:

Relates directly to a process the

system has to perform (process-

oriented) or information it needs

to contain (information-oriented).

  1. Information-oriented - Information the system must contain Examples:
  • (^) The system must retain customer order history for three years
  • (^) The system must include real-time inventory levels at all warehouses
  • (^) The system must include budgeted and actual sales and expense amounts for current year and three previous years

Functional Requirements (3/4)

Functional Requirements (4/4)

1. Operational - the physical and technical environments in which the system will operate Examples:

  • (^) The system can run on handheld devices
  • (^) The system should be able to integrate with the existing inventory system
  • (^) The system should be able to work on
Non-Functional Requirements
  1. Performance:
    • the speed, capacity, and reliability of the system Examples:
  • (^) Any interaction between the user and the system should not exceed 2 seconds
  • (^) The system downloads new status parameters within 5 minutes of a change
  • (^) The system should be available for use 24 hours per day 365 days per year
  • (^) The system supports 300 simultaneous users from 9-11AM; 150 simultaneous users at all
Non-Functional Requirements
  1. Cultural and political :
    • cultural and political factors and legal requirements that affect the system Examples:
  • (^) The system should be able to distinguish between U.S. currency and currency from other nations
  • (^) Company policy is to buy computers only from Dell
  • (^) Country managers are permitted to authorize custom user interfaces within their units
  • (^) Personal information is protected in
Non-Functional Requirements
Non-Functional Requirements