Functional And Non-functional Requirement For WSWT 1

Functional and Non-functional Requirement for WSWT 1

Functional and Non-functional Requirement for Western Sydney Wellness Trust

Name

Course

Professor

Institution of learning

State/City

Date

Functional and Non-functional Requirement for WSWT 2

Functional and Non-functional Requirement for Western Sydney Wellness Trust

(WSWT)

Functional requirements

The WSWT need to select nonfunctional and functional requirements carefully to ensure

sufficient output in their operations. Functional requirements illustrate the particular functional

behavior of a software system after achieving certain conditions. For instance, a firm operating in

goods and services may send an email notification after a new client has signed up to their

website or account. The functional requirements include regulatory or legal requirements, audit

requirement or trial, and administrative functions (Koay, Kataria, & Juric 2010, p. 469).

1. Regulatory requirements

Functional requirements of the WSWT may require the application of software systems

which operates within the legal regulation of the state. The recent laws such as Sarbanes-Oxley

(SOX) and Health Insurance Portability and Accountability Act (HIPAA) which influence

operations of software systems (Koay, Kataria, & Juric 2010, p. 469).

2. Audit requirement or trial

Organizational audit requirement provides sets of account or records, safety-relevant

chronology records, source and information destination to offer documentary proofs of

subsequent events which operations of a firm (Koay, Kataria, & Juric 2010, p. 469). Audit

requirement may assist in ensuring effectiveness in scientific research, financial transactions, and

healthcare data transactions in the WSWT. The software system privilege mode and role-based

safety model plays a significant role in accessing and supervising organizational database table.

3. Administrative functions

Functional and Non-functional Requirement for WSWT 3

The software system contains administration section which offers and maintain

healthcare information. The section requires an administrator to log in using password and

username before performing an administrative task in the system (Koay, Kataria, & Juric 2010,

p. 469).

Nonfunctional requirements

Nonfunctional necessities or requirements play a significant role in ensuring the success

of an organizational software. The element assists an organization in enhancing the satisfaction

of customers, developers, and users. Additionally, nonfunctional requirement prevents budget

overrun, encourages active schedule and rectification of software established without proper

nonfunctional requirements (Slankas & Williams 2013, p.14). Consequently, nonfunctional

requirement ensures active operations of a software system in an organization.

Even though formulation of nonfunctional requirements depends on users’ concerns, the

concerns may act as constrain to numerous elements which are nonfunctional requirement

characteristics. Therefore, application of a user-oriented strategy requires comprehension of the

users in the WSWT. Moreover, practical understanding of software users may assist in selecting

the type of applicable nonfunctional requirement in the WSWT. Based on efficient operations,

the firm may apply nonfunctional requirements which ensures organizational integrity,

efficiency, and confidentiality.

1. Integrity

Firstly, the integrity of an organizational software illustrates the ability of the software in

maintaining data and information in the system. The maintenance of information and data in a

software system may help the WSWT to enhance ethnicity and accuracy in their operations

(Slankas & Williams 2013, p.14). Furthermore, the integrity of nonfunctional requirement has a

Functional and Non-functional Requirement for WSWT 4

direct contribution in preventing corrupt practices in the firm. Therefore, confidentiality

enhancement through restricting access of data to authorized personnel plays a vital role in

protecting sensitive information and data of the WSWT.

2. Efficiency

Secondly, the ability of software system describes the capacity effectiveness of the

system in time response and output. The WSWT may achieve their ultimate goals and objectives

through adopting nonfunctional requirements which promotes the operational efficiency of the

firm.

3. Reliability

Lastly, nonfunctional requirements which ensure the safety of a software system depends

on the ability of the system to perform specified roles consistently without failures (Slankas &

Williams 2013, p.14). Additionally, reliable software system provides consistent functionality

and active recovery during system failures.

Functional and Non-functional Requirement for WSWT 5

References

Koay, N., Kataria, P. and Juric, R., 2010. Semantic management of nonfunctional requirements

in an e-health system. Telemedicine and e-Health, 16(4), pp.461-471.

Slankas, J. and Williams, L., 2013, May. Automated extraction of non-functional requirements in

available documentation. In Natural Language Analysis in Software Engineering

(NaturaLiSE), 2013 1st International Workshop on (pp. 9-16). IEEE.

Place new order. It's free, fast and safe

Paper type

Deadline

Page count

550 words

Total price: $ 15.00

Our customers say

Jeff Curtis

USA, Student

"I'm fully satisfied with the essay I've just received. When I read it, I felt like it was exactly what I wanted to say, but couldn’t find the necessary words. Thank you!"

Ian McGregor

UK, Student

"I don’t know what I would do without your assistance! With your help, I met my deadline just in time and the work was very professional. I will be back in several days with another assignment!"

Shannon Williams

Canada, Student

"It was the perfect experience! I enjoyed working with my writer, he delivered my work on time and followed all the guidelines about the referencing and contents."