Home > Articles > Software Development & Management

Like this article? We recommend

Nonfunctional Requirements

This section outlines a number of additional topics that are of importance in the design of desktop (and other) architectures and that are collectively referred to as nonfunctional requirements.


A wide-ranging discussion on security topics is outside the scope of this article. For more information about this subject, see the selection of Sun BluePrints articles under the Security heading at:


There are, however, a number of security issues that are particularly relevant to desktop environments.

Virus Infection

Virus infection is an issue that has had (and probably will continue to have) an impact on every IT user. At present, most viruses are targeted at a specific operating environment (Microsoft Windows), associated email client, and browser. Although in fairness, it should be pointed out that this tendency is most likely due to a combination of the wide availability and usage of these products. There are also potential architectural weaknesses in the design and implementation of some software products that make them easier to attack than others. In any event, organizations need to take comprehensive precautions against viruses. A program of defense should include:

  • User education

  • Hardening of server systems by removal of unnecessary subsystems, services, and accounts

  • Lock down or restriction of the capabilities of client devices

  • Implementation of virus scanning and spam filtering software on mail servers and/or mail relays

  • Implementation of antivirus software on vulnerable operating system platforms (for example, Windows servers and clients)

  • Some of these measures are more effective and/or more easily implemented in a thin-client environment. This can reasonably be viewed as an argument in favor of thin-client solutions in terms of both vulnerability and TCO.

Federated Identity

The topic of user authentication was covered in "Services and Servers" on page 21. There is an additional architectural debate that some organizations need to follow and make a decision on, which is the selection of standards and products for the support of federated identity. This topic is important to organizations that are seeking to build communities of external users (for example, customers and suppliers), but it is also important to organizations that are building portals to support a mobile workforce. The main protagonists in this debate are the Liberty Alliance (http://www.projectliberty.org) and Microsoft with their Passport product.

User Identification

A number of current and forthcoming software and hardware products are targeted at increasing security against spam (bulk unsolicited email) and at preventing unauthorized access to applications and resources, along with the authentication services described in "Services and Servers" on page 21.

Some examples are:

  • Smart cards, such as those based on the Java Card technology

  • Smart cards can be used with readers to provide another security leg. Users need to present a valid smart card in conjunction with the correct user name and password to gain access to the system(s).

  • One-time password or token generators, such as SecureID and SafeWord

  • Token generators can be used in conjunction with a memorized PIN to generate a one-time key that is the correct response to a challenge issued by server software (provided by the company that manufactures the token card). This mechanism is often used to provide authentication for remote users who want to gain access to an internal network by using a dial-up connection or a VPN.

  • Biometric devices

  • These are relatively expensive solutions that aim to provide authentication based on unique personal identifiers such as a thumbprint or a retinal pattern. Initially used for enhanced physical security (for example, access to buildings and data centers), they are now being used to extend to include controlled access to secure systems such as the defense and financial networks.

Single Sign-On

Single sign-on is a facility whereby the user is able to pass through one authentication gateway and be granted automatic access to all of the applications to which they have been given access rights. This facility can be provided today by a combination of authentication services with scripting and configuration set-up in a portal server or integration software layer.

Eventually, most applications and services will be integrated with an authentication server and undertake their own look-up with the server, eliminating the need for below the covers scripting solutions.

Data Security

Data security, as an aspect of the desktop architecture, should not be overlooked. A full discussion of this topic is outside the scope of this article, but a couple of key points need to be remembered during system design:

  • Security of data storage devices

  • Consider the deployment of resilient storage devices such as RAID 1 or RAID 5 disk arrays.

  • Backup and recovery of data

  • Consider the addition of backup devices (for example, tape libraries) in conjunction with appropriate software and backup regimes.


Manageability is another topic that is covered well by many other documents, but it also constitutes a vital component of any desktop solution. Some considerations that are specific to the desktop environment include:

  • Sun Ray ultra-thin client administration

  • The facilities provided by the Sun Ray ultra-thin client server software to manage the clients generally needs to be augmented by user-written scripts that provide additional features, such as printer management and session management.

  • Sun Ray ultra-thin client and Solaris OS servers (for example, directory, file, print, and messaging servers)

  • These servers can be administered by using the Sun™ Management Center software. Generally, the designer needs to provide a separate management LAN and also consider the automation of frequent management tasks and integration with manager-of-manager tools, such as HP OpenView, Unicenter TNG, and Tivoli.

Availability and Reliability

Some aspects of resilience have particular relevance to desktop systems design (for instance, Sun Ray ultra-thin client server resilience). The Sun Ray ultra-thin client server software provides failover between two or more servers in a logical cluster (that is, a user session on a failed server is lost, but it can be re-established on a second server, if available). The software also provides for load balancing between servers so that user logins are distributed on a least heavily loaded basis when multiple servers are available.

Tarantella and Citrix provide similar failover and load balancing facilities in their integration software. In combination with Sun Ray ultra-thin client server software, users with failed sessions can reattach to their existing Citrix or Tarantella session after they have reconnected to an operational server.

Other service types also have their own means of ensuring that availability goals are met. Authentication services such as LDAP or AD generally support the concept of backup servers that can hold active or nonactive copies of user identification and attribute data.

File and print services can be based on cluster solutions such as the Sun™ Cluster 3.0 software, which ensures that service can be re-established following a server failure. Storage continuity also needs to be provided to ensure complete continuity.

Messaging and calendar software products are generally designed with a built-in concept of horizontal scaling (for example, user mailboxes can be held on a single mail server or spread across several servers). In this environment, failure of a single server causes partial loss of overall service, but complete loss for some users. Designers might want to consider a cluster solution if a higher level of availability is required.

Vertical and Horizontal Scalability

Most of the services discussed in this article can be loosely (that is, logically) clustered. Therefore, designers can add capacity relatively simply to desktop server infrastructures by adding more purpose-built servers (for example, Tarantella servers or directory servers) to the existing infrastructure.

Although this gives the architect a straightforward solution for scaling the design, it is worth considering the trade-off between horizontal and vertical scaling. As the number of physical servers and operating system instances increase, so too does the requirement for system administrators, space, and power. Most UNIX-based services also scale vertically. For example, directory services and mail services achieve near linear performance improvements as more processors, memory, and I/O capacity are added to the system.

Network Design

Consider network bandwidth, latency, and resilience when determining the type and location of client devices, printers, and servers. It is important to recognize that some client devices (for example, the Sun Ray ultra-thin client devices) have fairly large bandwidth requirements (around 1 megabit per second) and need to be located at least on the same campus as their associated servers, if not on the same LAN segment, unless the organization has a particularly fat WAN and an aversion to distributed servers.

Other clients like those using Tarantella or Citrix have more limited network needs and can be successfully located at the end of a low-bandwidth pipe. Printers constitute an intermediate case. Low-volume printers require limited network capacity, but fast printers with high-resolution graphics can create significant network traffic.

Usability and Environmental Factors

There is considerable variation in the size of screen and display resolution between the smallest mobile phone and a high-resolution engineering workstation. You should consider how users will use the device (for example, the applications required and the frequency and duration of access).

The Sun Ray ultra-thin client and some other thin clients (for example, Windows-based terminals) have no moving parts; therefore, they generate almost no noise in operation. This feature can be particularly useful in crowded environments such as call centers and training rooms. In addition, Sun Ray ultra-thin clients require less than 20 watts (typically, 11 watts) to operate, as compared with conventional desktops that require 200 to 300 watts (excluding display devices in both cases). This can lead to a significant reduction in electricity costs, even when the Sun Ray ultra-thin client server power budgets are factored into the equation.

Given the lower power consumption of the Sun Ray ultra-thin client, it necessarily follows that the heat output, and therefore the cooling requirements, for these clients are also significantly lower than the heat output of fully functional PCs or workstations.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020