Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Identify requirements functional / non-functional
Previous Previous
 
Next Next
New Post 2/13/2019 10:17 AM
Informative
User is offline Lara 02
1 posts
No Ranking


Identify requirements functional / non-functional  
Modified By Chris Adams  on 2/13/2019 1:59:57 PM)
Need help to identify requirements functional / non-functional :

1

Supports fast page loading.

2

Has a clear homepage layout (to make it easy to find information).

3

Provides menus that facilitate finding information quickly.

4

Displays pictures of section events.

5

Supports concisely communicating valuable information.

6

Includes information about section events (i.e., monthly meetings, refresher classes)

7

Facilitates access from mobile/tablet platforms

8

Homepage contains direct/quick links to important information (i.e., event registration)

9

Serves as an information repository for members to access

10

Provides ability to cancel registration for monthly meetings, refresher classes, etc

11

Has efficient search engines to support finding information quickly.

12

Supports the resolution of technical issues.

13

Supports easy access for members to update their contact information/profile.

14

Supports generating reports (i.e., event registration lists, etc.).

15

Facilitates generating invoices for online payments (i.e., for event/meeting registration, etc.).

16

Supports customizing the template for promotion/registration for special events

17

Supports easily posting monthly meeting information.

18

Supports capturing/storing walk-in information/registration at events

 

 1 Reports
New Post 2/16/2019 2:03 AM
User is offline rajesh 01
2 posts
No Ranking


Re: Identify requirements functional / non-functional  
Modified By Chris Adams  on 2/19/2019 11:54:18 AM)

 

Functional and non-functional requirements need to be carefully selected in order to ensure that they make sense in the context of the final outcome of the project and conveyed to all the team members working on it.

Missing out on a requirement or misapplying one could spell disaster for a project.

Requirements generally fall into two types: functional and non-functional.

The difference between them is fairly straightforward, nevertheless, in the this article well define the two types of requirements and provide examples of each to point out more concretely the fundamental difference between them.

Functional requirements

The definition of a functional requirement is:

Any requirement which specifies what the system should do.

In other words, a functional requirement will describe a particular behaviour of function of the system when certain conditions are met, for example: Send email when a new customer signs up” or “Open a new account”.

A functional requirement for an everyday object like a cup would be: ability to contain tea or coffee without leaking”.

Typical functional requirements include:

  • Business Rules
  • Transaction corrections, adjustments and cancellations
  • Administrative functions
  • Authentication
  • Authorization levels
  • Audit Tracking
  • External Interfaces
  • Certification Requirements
  • Reporting Requirements
  • Historical Data
  • Legal or Regulatory Requirements

Non-functional requirements

The definition of a non-functional requirement is:

Any requirement which specifies how the system performs a certain function.

In other words, a non-functional requirement will describe how a system should behave and what limits there are on its functionality.

Non-functional requirements generally specify the systems quality attributes or characteristics, for example: Modified data in a database should be updated for all users accessing it within 2 seconds.

A non-functional requirement for the cup mentioned previously would be: contain hot liquid without heating up to more than 45 °C”.

Typical non-functional requirements include:

  • Performance – for example: response time, throughput, utilization, static volumetric
  • Scalability
  • Capacity
  • Availability
  • Reliability
  • Recoverability
  • Maintainability
  • Serviceability
  • Security
  • Regulatory
  • Manageability
  • Environmental
  • Data Integrity
  • Usability
  • Interoperability

It is important to correctly state non-functional requirements since theyll affect your users’ experience when interacting with the system.

 

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Identify requirements functional / non-functional




Latest Articles

Domain Expertise and the Business Analyst: How Vital Is It?
Sep 15, 2019
0 Comments
The question of how essential domain expertise is to a business analyst is a recurring debate in the BA community. One school of thought maintains tha...
Copyright 2006-2019 by Modern Analyst Media LLC