1

Information Security

Topic: AES and DES.

Assignment no: 2

Name: Muhammad Abdullah Akram

Registration no.: 1220100908

Class: BS(SE)

Semester: 3rd

Submitted to: Miss IQRA QAYYUM

Submission Date: 23-Dec-2023

International Institute of Science, Arts and Technology

2

Table of Contents
Functional Requirements .................................................................................................... 2

Non-functional Requirements............................................................................................. 3

Difference Between Functional and Non-Functional Requirements .......................... 4

How Are Functional and Non-Functional Requirements Written ................................. 5

What Are Some of the Best Practices ................................................................................ 6

Difference between Functional and Non-functional Requirements ..............................7

Real life examples of functional and Non-functional requirements ..............................8

-:-----------------------------------------------------:-

Functional Requirements:
Functional requirements form the behavior of the system. If someone is giving you
functional requirements for a project, they're giving you information on how the project's
product is going to work.

These requirements describe the interactions between a system and its environment.

Let's say that you already have a product that's out on the market, called Product 1.0.
Now, your project is to work on Product 2.0.

The new features of the Product 2.0 would be functional requirements. The bugs that you
will be fixing from Product 1.0 are also your functional requirements.

The new behavior you're building in the product is also a functional requirement.
 3

Non-Functional Requirements

Non-functional requirements, also known as quality attributes, describe the general

software characteristics.

The list of primary non-functional requirements includes:

• Usability: the ability of a user to easily interact with a product

• Reliability: the product should be secure enough to handle users' sensitive information
• Performance: how a product reacts to user's actions
• Error handling: how the product handles errors
4

Difference Between Functional and Non-Functional Requirements:

The major difference between functional and non-functional requirements in
software engineering is that functional requirements explain What the system does, while
non-functional requirements explain How the system works.
Functional requirements:
• User stories: Instagram users want to upload image and video content, write
captions, and publish the update. They also want to react to content published by
other accounts.

• Use cases: when a user opens their Instagram, the first page is the feed. Here,
the user can interact with the content, leaving likes and comments.

• Additional functionality: push notifications, automated location tagging,

automated expiration of user stories, photo filters, search bars, etc.

Non-functional requirements:
5

• Performance: content loading is a priority as users spend more time viewing

content than uploading content.
• Usability: users should be able to intuitively navigate between profiles and their
subscriptions.
• Reliability and scalability: the system should work well in low-latency conditions,
showing media content with the smallest delay possible.
• Safety: Instagram has detailed authentication protocols, photo upload, API
integration, photo embedding, and encryption of direct messages.

Now you know what are functional and non-functional requirements and how to
differentiate between functional and non-functional requirements.

How Are Functional and Non-Functional Requirements Written:

There are a few different ways to write functional or non-functional requirements. Here
are the most common:

1. Requirements Specification Document

This document is one way to formalize functional and nonfunctional requirements in

software engineering. It describes the functions and capabilities the product must provide.
It can also contain constraints and assumptions.

A requirements specification document generally contains the following elements:

• Purpose (definitions, system overview, and background)

• Overall description (assumptions, constraints, business rules, and product vision)
• Specific requirements (system attributes, functional requirements, database
requirements)
6

2. Use Cases

Use case document is a document that describes the interactions between the system
and the external users in a generalized, impartial way. It's a written description of how
users will perform tasks in the system.

3. User Stories

User stories describe the functionality from the perspective of the end-user. They include
what exactly the end-user wants the system to do. Agile teams organize user stories in a
backlog, which is an ordered list of product functions.

For example, a user story may be the following:

As Jane, I want to invite my friends to join the app to experience it together.

4. Functional Decomposition

Functional decomposition is a document in which complex functionality is broken down

into structural parts.

For example,

Reserve a room -> Log in -> Select hotel and date -> Confirm reservation

What Are Some of the Best Practices?

1. Requirements should be clear and easy to understand.

Let's explain functional and non-functional requirements' best practices. Whether it's a
use case or a functional decomposition, requirements should be written in a way that is
clear and easy to understand. Keep in mind that some stakeholders won't be well-versed
in the technological language, making the document as easy to understand as possible.
Always choose the active voice over the passive and keep your sentences short.
7

2. Requirements should be written accurately.

Make sure your requirements document is written accurately, using consistent

terminology and format. Avoid giving irrelevant information that may just confuse the
reader.

3. Use requirement imperatives correctly.

Many requirements documents contain imperatives such as "shall," "will," and "should."
Some people will say that "shall" is a requirement, while others that "should" and "must"
is a requirement. Your company should outline what each of these means and how to use
them correctly when writing requirements.

4. Don’t use weak phrases and subjective words.

For instance, if you write "something bad happened to the system," "something bad" can
mean different things to different people. It's critical not to use these words. If you use
them, make sure they're going to be interpreted in the same way by everyone.

Difference between Functional and Non-functional Requirements.

Now we discuss the Functional and Non-functional Requirements;

Functional Requirement Non-functional Requirements

Functional requirements form the behavior Non-functional requirements describe the

of the product. general software characteristics.

They explain “What the system does.” They explain “How the system works.”
8

Helps you verify the functionality of the Helps you verify the performance of the
software. software.

They are captured in use cases. They are captured as a quality attribute.

Easy to define. Difficult to define.

Focus on user requirement. Focus on the user's expectation and

experience.

Examples(Netflix): Examples(Netflix):
Users should be able to play any video The interface should be desktop and
by pushing the play button. The platform’s mobile friendly. Every user should fill a
search bar should allow users to filter form with personal details and provide
results by genres. The platform frequently financial data for paid subscriptions. The
updates the suggestions list by using data platform should comply with copyright
analytics laws.

Real life examples of functional and Non-functional requirements:

Functional requirements

First example online banking system:

• User Authentication:
• Account Management:
• Transaction Processing:
9

• Bill Payments:
• Transaction History:
• Alerts and Notifications:
• Account Closure:
• Currency Exchange:
• Accessibility:
• Security:

Second example hospital management system:

• Patient Registration:
• Appointment Scheduling:
• Electronic Health Records (EHR):
• Prescription Management:
• Billing and Invoicing:
• Inventory Management:
• Laboratory and Test Management:
• Ward and Bed Management:
• Appointment Reminders:
• Emergency Response:
• Staff Management:

Non-functional requirements

First example online banking system:

• Performance:
• Reliability:
• Scalability:
• Security:
• Usability:
10

• Availability:
• Compatibility:
• Maintainability:
• Compliance:
• Performance Efficiency:

Second example hospital management system:

• Performance:
• Reliability:
• Scalability:
• Security:
• Usability:
• Availability:
• Compatibility:
• Maintainability:
• Compliance:
• Performance Efficiency:
11