ITC548 System Analysis PG Assessment Item 3: Requirements Report

Desklib provides solved assignments and past papers to help students succeed.

ITC548 - SYSTEM ANALYSIS PG
ASSESSMENT ITEM 3 REQUIREMENTS
REPORT

Contents
Introduction...........................................................................................................................................3
Non-functional requirements.................................................................................................................4
Review of cloud based.........................................................................................................................10
SDLC approach...................................................................................................................................14
Conclusion...........................................................................................................................................17
References...........................................................................................................................................18

List of figures
Figure 1: Non-functional requirement...................................................................................................5
Figure 2: FURPS+.................................................................................................................................9
Figure 3: cloud based solution.............................................................................................................10
Figure 4: SaaS.....................................................................................................................................11
Figure 5: SDLC......................................................................................................................................14
List of tables
Table 1: Qualities of system table..........................................................................................................4
Table 2: Interface of system table..........................................................................................................5
Table 3: requirements table...................................................................................................................6
Table 4: Constraint of system table.......................................................................................................7
Table 5: FURPS+ table............................................................................................................................8
Table 6: Strength & weakness table.....................................................................................................11
Table 7: pros & cons of the predictive model......................................................................................14
Table 8: pros & cons of adaptive model table......................................................................................16

Introduction
An organization named Headspace has NewAccess that provide the peoples mental health
from the age of 17-25; this provides the people's relief mentally. The problems that are
coming up are peoples telling their problems related stories repeating so; the purpose of the
Headspace is to eliminate the miscommunication. This assignment includes the requirements
that are non-functional like user interface, system interface system quality, & system
constraint & the FURPS+ that include the performance, reliability, security, & usability.
Then overview the cloud that is SaaS, PaaS & IaaS & selects the desired one with their
strength and weaknesses & deploys in Headspace, & lastly Choose the SDLC approach
(Predictive & adaptive model) with pros and cons & select the one which is best for
Headspace.

Non-functional requirements
System qualities
It is an organized attempt that will manage the Headspace, how they will supply the services
& items. The primary goal of Headspace is to act accountable & have the structure of
organization, process, procedure & resource for improvement to keep it safe.
Table 1: Qualities of system table
Qualities of the system Description
Testability This quality will permit the Headspace to
execute test & as per the already defined
criteria.
Serviceability It is ease through which the deployed
Headspace will be preserve.
Security It is the complex composition of the factor
that will relate the coherence of the system&
its customer. It will include authorization &
authentication of customers, & securely
access to the deployed Headspace.
Latent capacity The ability of Headspace to manage the loads
of peaks that are unusual without resources
those are additional.
Availability It measures how usually the Headspace
services & resources are accessible to the end
customer, usually expressed as Headspace
uptime.
Performance The computation of throughput & response
time with respect to the customer's load
condition.
Scalability The potential to add the capacity & customer
to the deployed Headspace with time.
Scalability will involve the adding of
resources to Headspace without altering the

architecture of the deployment.
Modification It demonstrates how many alterations need to
make the alteration in Headspace for the
individual artefact.
Reusability The capacity to utilize the Headspace & its
components for the other component &
Headspace with few alterations or not.
Interoperability The capacity of the Headspace or the
software to interchange & make the
utilization of information.
Maintainability The potential of the Headspace to board
changes (Meehan, Loose, Bell, Partridge,
Nelson, & Goates, 2016, pp 217-223).
Figure 1: Non-functional requirement
(Source: Meehan, Loose, Bell, Partridge, Nelson, & Goates, 2016, pp 217-223).
System interface
Table 2: Interface of system table
 The interface of Headspace must be appraised with time & will make the alteration as
per the assessment.
 The enumeration of the interface of Headspace will alter as per the implementation of
the design.
 It must be pronounced that above prescribe the interface of Headspace forward in the

design operation.
 The section of the precision is identical for making the resolution & the resolution of
design need to be sensible (Knouse, & Gupta, 2015).
Requirements of user interface
Table 3: requirements table
Liability
The payment of the third party is medicated
than the person at this time has liability
describe to right function of the interface of a
user in the Headspace. These persons & party
establish it necessary to get a balanced
presentation of the offered document.
Security The sensitive data of the user is secure &
preserve in Headspace. Although in most
authorities the use of the confidential data is
forbidden. On the internet, the structure for
the communication will maximize the ethical
conventional in Headspace.
Adjustability & Compatibility For preserving the adjustability in
Headspace, it must produce the operation is
to fulfill the large requirements instead of
providing a particular solution for the
accounted problem. The compatibility
focuses on the rules & regulation of payment
that will upgrade the browser of the
Headspace automatically.
Efficiency The interface of the Headspace is productive
for the customer or user for speed & in user
interaction. Unwanted interaction among
users must be eliminating. The not required
communication will have the capacity of late

& collapse in Headspace.
Authorization Because of the payment in Headspace need to
secure the approved information like debit
card number as this shield may be needed in
the movement must be protected equally by
the Headspace application. The data must be
requested by the interface of the user from
several networks relate association (Blanco,
Lessard, Mortimer, Crumrine, Nair, &
Inglis, 2016, pp.964).
System constraint
Table 4: Constraint of system table
Smashed data Smashed data should be averting in
Headspace that is flow & no confirmation is
received from the Headspace.
Clumsy command & small screen Due to the small screen & commands is
complex to utilize by the users. So, the user
will confront strain & enough to remove. The
UX emphasis on overthrow the conflict in
Headspace.
Space The most possible constraint that the
customer doesn’t have space, as the
information of the application resides on the
customer side as compared to the server.
Upgrade When upgrading or updating the Headspace
application there will be some operation that
is not available for customers as the
downtime. So, reduce the downtime at the
time of upgrading the Headspace application.
Operating system The Headspace design & layout will be
similar for the different operating system as a

platform independent.
The non-functionality of ‘FURP S+’
Some of the requirements of the ‘FURP S+’ are functional & non-functional that may
segregate data specific time as some requirements may classify the independent technology &
other technologies that are not dependent. This permit to think differently for the
requirements in Headspace, the method of FURPS+ will validate the prioritize needs after
knowing the importance & wants of the customer. The acronym is FURPS that is
functionality, usability, reliability, performance & supportability respectively, with the time it
will upgrade the result to watch from an expanded dimension that produces the FURPS+.
This procedure more focuses on the several non-functional requirements to understand.
Table 5: FURPS+ table
Functionality
F is known as
functionality has
the feature that
is most similar
with Headspace
domain for the
result that is
created. It is can
be technically
oriented & the
requirements of
non-functional
have the
management of
Headspace
capabilities of
Headspace,
security, mail, &
review of
Headspace.
Usability
It has non-
functional like
the
documentation,
stability, &
human factor of
Headspace. It
will include the
level of
expertise
accused,
prepared
documentation
& degree of UI.
Reliability
It has the speed,
efficiency,
performance,
time of
response,
throughput &
consumption. It
includes the
number of
synchronous
customer
support, counts
the
transaction/sec.
& response time.
Security
It has non-
functional
requirements
like scalability,
maintainability,
reliability,
portability &
testability.
“+”
It will permit the
physical,
interface,
implementation
& design
constraint. The
physical
constraint
includes the
influence the
hardware that
utilizes for the
Headspace like
weight, shape &
size. The
interface
constraint is
needed to
communicate
with an external
entity, the

design constraint
will provide a
limitation on the
design, &
implementation
involves limits
or restriction on
the construction
or the coding
that is platform
& standards
(Barrer, &
Nichols, 2017).
Figure 2: FURPS+
(Source: Barrer, & Nichols, 2017)

Review of cloud based
The SaaS is known as Software as a service, there are various development has permitted the
SaaS to have the mainstream. The important factors involve the evolution of the tools &
virtualization in the big data. This will easy to provide to manage & scale the infrastructure of
the Headspace & will produce the SaaS as a result. The SaaS is utilized for most for many
parts of the business that involve the management of document, human resource, accounting,
management of service desk, collaboration & management of content. It is a precious part of
cloud computing. It is related to ASP that is application service provider & conveys the
model of the software (Griebel, Prokosch, Köpcke, Toddenroth, Christoph, Leb, &
Sedlmayr, 2015, pp.17).
Figure 3: cloud based solution
(Source :Griebel, Prokosch, Köpcke, Toddenroth, Christoph, Leb, & Sedlmayr, 2015, pp.17)
Why Headspace deploy SaaS?
The will no initially big investment as it will function on the pay & go for the model having
no fees of upfront. As the subscription will pay as annually & monthly for the utilization of
the CRM, this is the reason why the SaaS is mostly favored by Headspace companies who
more emphasis on the budgets that are required to invest as it will consider as the critical
business. Second, plus point is it saves the cost that will attract the Headspace towards SaaS.
When the cost of the CRM SaaS is compared with purchasing software feels expensive. But
in some time it knows that this includes the cost of hardware, managing peoples & hiring will
make the cost more than the approach of SaaS. By utilizing the Software as the service will

serve to forget the spending cost on hardware. The model of SaaS will permit access to the
database of CRM from anywhere, from several devices & at different time. The uptime is
99% require the web browser & the connection of internet. That will host on cloud & will
access above the internet, the CRM of SaaS is best for the Headspace to access the service for
mediation. No trouble in information technology, as the free from hassle will be great from
the point of selling the CRM SaaS. The method for subscription-based pricing will entail
virtually the fee for maintenance of Headspace like security, updates & back-ups. No
requirement for the customer to update & install the local server & hardware that will require
the maintenance cost. The CRM of SaaS is hosted by a provider of SaaS to installation,
maintenance & upgrades & link new customers with the Headspace. The vendor of the SaaS
has the responsibility to convey on promise & make sure it functions according to IT. The
SaaS will integrate & expand as the Headspace want to expand. It explains that the customer
may carry by utilizing the software like the email clients & ERP system & Headspace that
will integrate easily with SaaS (Chris Kraft, & PMP, 2018, pp. 26- 31).
Figure 4: SaaS
(Source :Chris Kraft, & PMP, 2018, pp. 26- 31).
Table 6: Strength & weakness table
Strengths
 Reduction in cost: The benefits of
cost are the precious & obvious plus
point of utilizing the SaaS for the
Headspace. The expense for installing
& buying the whole IT & software
Weakness
 Data security is insufficient: The
concern for the Headspace to opt the
SaaS model. The problem like
management access & identify
required to confront when trusting on