Scribd
Upload
61 views6 pages

SC2006 Tutorial 1 Slideshow

NTU SC2006 Tutorial 1 Solutions

Uploaded by

matthewtanyh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
61 views6 pages

SC2006 Tutorial 1 Slideshow

NTU SC2006 Tutorial 1 Solutions

Uploaded by

matthewtanyh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

Tutorial 1: Requirements Elicitation –

Functional/Non-Functional Requirements
Question 1: Atomize the requirements for an Inventory and
Asset Tracking System.
Check that the atomized requirements are also verifiable.
The System may be queried. A query may contain a user number or a serial number. If
the query contains a user number, all equipment assigned to that user is reported. If the
query contains a serial number, the assignment for that computer is reported. All query
results show the name, office and user number of a user, followed by the serial numbers
and types of all computers assigned to that user, and the date of each assignment. If a
user is not assigned a computer or a computer not assigned to a user, this is reported.

Question 2: List several non-functional requirements for the


above Inventory and Asset Tracking System
Question 1: Atomize the requirements

This tutorial is an exercise in splitting (atomizing) requirements statements and


organizing them in a logical hierarchy. There should also be consideration for how
the requirements can be verified.

Requirements specification heuristics:


• Write complete, simple sentences in the active voice.
• Define terms clearly and use them consistently.
• Group related material into sections.
• Express all requirements using the words “must” or “shall”.
• Write verifiable requirements.
• Write atomized requirements.
Question 2: Non-functional requirements
Nonfunctional Requirements (NFRs) define system attributes such as
security, reliability, performance, maintainability, scalability, and usability.
They serve as constraints or restrictions on the design of the system

Security: Authentication

Reliability: Consistency, accuracy

Performance: Response time

Maintainability: Easy to restart / recover

Scalability: Up capacity easily

Usability: Friendliness

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy