In systems engineering and requirements engineering, a non-functional requirement is a requirement that specifies criteria that can be used to judge

the operation of a system, rather than specific behaviors. This should be contrasted with functional requirements that define specific behavior or functions. The plan for implementing functional requirements is detailed in the system design. The plan for implementing non-functional requirements is detailed in the system architecture. A product requirements document (PRD) is a document written by a company that defines a product they are making, or the requirements for one or more new features for an existing product. A PRD is often created after a marketing requirements document (MRD) has been written and been given approval by management, and is usually written before (or at least concurrently with) a technical requirements document. It is designed to allow people within a company to understand what a product should do and how it should work. PRDs are most frequently written for software products, but can be used for any type of product. Such a document is typically the result of a requirements analysis.
en.wikipedia.org/wiki/Non-functional_requirement

https://www.dot.ny.gov/programs/trns-mainttrain/peakperf/pdf_files/pw_ch_2.pdf

An efficiency requirement is a useroriented quality requirement that specifies a required amount of efficiency, which is a quality factor that is defined as follows: Efficiency the degree to which something effectively uses (i.e., minimizes its consumption of) its computing and personnel resources. Objectives The typical objectives of a efficiency requirement are to: Minimize its need for computing resources: o o o o Processors. Memory. Mass storage. Communication networks (e.g., bandwidth).

Reliability requirements adequately specify the reliability and maintainability requirements derived from the overall availability needs. Setting only availability targets is not appropriate. Reliability requirements address the system itself, including test and assessment requirements, and associated tasks and documentation. Reliability requirements are included in the appropriate system or subsystem requirements specifications, test plans and contract statements. Provision of quantitative minimum targets (e.g. MTBF / Failure rate) is not sufficient, reliability requirements should drive a (system or part) design to incorporate features that prevent failures from occurring or limit consequences from failure. A design requirement should be precise enough so that a designer can "design to" it and can also prove through testing that the requirement has been achieved within a stated confidence. To derive these requirements in an effective manner, a systems engineering based risk assessment and mitigation logic should be used. The requirements may be part of the output from functional or other failure analysis. The maintainability requirements address the costs of repairs as well as repair time. Testability requirements provide the link between reliability and maintainability and should address detectability of failure modes (on a particular system level), isolation levels and the creation of diagnostics (procedures).
en.wikipedia.org/wiki/Reliability_engineering

Minimize its need for personnel resources: o o o Measurements Efficiency requirements are typically specified in terms of the following measurements: TBD. Examples The following are typical examples of efficiency requirements: The client part of the application shall not require more than the following computing resources: o A Pentium II processor (or the equivalent). o 64 meg of RAM. o 80 meg of hard drive. o A 56K modem.
http://www.opfro.org/index.html?Components/WorkProd ucts/RequirementsSet/Requirements/EfficiencyRequire ments.html~Contents

Operations organization. User support organization.

Portability Requirement Portability in high-level computer programming is the usability of the same software in different environments. The prerequirement for portability is the generalized abstraction between the application logic and system interfaces. When software with the same functionality is produced for several computing platforms, portability is the key issue for development cost reduction. Software portability may involve: Transferring installed program files to another computer of basically the same architecture. Reinstalling a program from distribution files on another computer of basically the same architecture. Building executable programs for different platforms from source code; this is what is usually understood by "porting".

Ethical Requirement Principles that when followed, promote values such as trust, good behavior, fairness, and/or kindness. There is not one consistent set of standards that all companies follow, but each company has the right to develop the standards that are meaningful for their organization. Ethical standards are not always easily enforceable, as they are frequently vaguely defined and somewhat open to interpretation ("Men and women should be treated equally, " or "Treat the customer with respect and kindness."). Others can be more specific, such as "Do not share the customer's private information wi th anyone outside of the company."
http://www.businessdictionary.com/definition/ethicalstandards.html

Usability Requirements Usability is the ease of use and learnability of a human-made object. The object of use can be a software application, website, book, tool, machine, process, or anything a human interacts with. A usability study may be conducted as a primary job function by a usability analyst or as a secondary job function by designers, technical writers, marketing personnel, and others. It is widely used in consumer electronics, communication, and knowledge transfer objects (such as a cookbook, a document or online help) and mechanical objects such as a door handle or a hammer. Usability includes methods of measuring usability, such as needs [1] analysis and the study of the principles behind an object's perceived efficiency or elegance. In human-computer interaction and computer science, usability studies the elegance and clarity with which the interaction with a computer program or a web site (web usability) is designed. Usability differs from user satisfaction and user experience because usability also considers usefulness.
en.wikipedia.org/wiki/Usability

en.wikipedia.org/wiki/Software_portability

Interoperability Requirement Interoperability is the ability of making systems and organizations to work together (inter-operate). While the term was initially defined for information technology or systems engineering services to allow for information [1] exchange, a more broad definition takes into account social, political, and organizational factors that impact system to system performance. With respect to software, the term interoperability is used to describe the capability of different programs to exchange data via a common set of exchange formats, to read and write the same file formats, and to use the same protocols. (The ability to execute the same binary code on different processor platforms is 'not' contemplated by the definition of interoperability.) The lack of interoperability can be a consequence of a lack of attention to standardization during the design of a program. Indeed, interoperability is not taken for granted in the non-standards-based portion of the computing world.
en.wikipedia.org/wiki/Interoperability

Legal Requirements delivery requirements The stipulation that requires that an item of materiel must be delivered in the total quantity required by the date required.
www.thefreedictionary.com/delivery+requirements

Implementation is the realization of an application, or execution of a plan, idea, model, design, specification, standard, al gorithm, or policy. In the IT Industry, implementation refers to post-sales process of guiding a client from purchase to use of the software or hardware that was purchased. This includes requirements analysis, scope analysis, customizations, systems integrations, user policies, user training and delivery. These steps are often overseen by a project manager using project management methodologies. Software Implementations involve several professionals that are relatively new to the knowledge based economy such as business analysts, technical analysts, solutions architects, and project managers. To implement a system successfully, a large number of inter-related tasks need to be carried out in an appropriate sequence. Utilising a well-proven implementation methodology and enlisting professional advice can help but often it is the number of tasks, poor planning and inadequate resourcing that causes problems with an implementation project, rather than any of the tasks being particularly difficult. Similarly with the cultural issues it is often the lack of adequate consultation and two-way communication that inhibits achievement of the desired results.
http://en.wikipedia.org/wiki/Implementation

Legal requirements for any software depends on the industry and type of business that particular software is engaged in. There is no one rule that fits all software. This article will cover general legal requirements applicable to most software on the web. You should consult a specialist to get a better understanding of your software legal requirements. Piracy Control Your software cannot be designed to promote piracy of other software and/or websites on the Internet. You may face legal actions by various law enforcement agencies, for-profit companies and not-for-profit organizations if your software is found to promote piracy. Patent Infringement and Copyright laws You software cannot infringe on existing patents and violate copyright laws without written consent of all involved parties. Patent and copyright laws are different in each country, and if your software will be sold/used globally, you will have to adhere to all local patent and copyright laws. Privacy Laws If your software at any time records private information about your users, you have to let the users know what you plan do with that information. Some software companies do not share that information with third parties and they let users know about this to build more trust. Basically, your software cannot sell or use your users' information without their permission. Safety Instructions You must let the users know of any known issues about your software that may be harmful for the users' computers or for users themselves. Failure to do so may result in lawsuits and complaints from users and other consumer protection agencies. You should also detail instructions to safely use your software.
http://www.ehow.com/list_7198220_software-legalrequirements.html

Performance Requirements The extent to which a mission or function must be executed; generally measured in terms of quantity, quality, coverage, timeliness or readiness. During requirements analysis, performance (how well does it have to be done) requirements will be interactively developed across all identified functions based on system life cycle factors; and characterized in terms of the degree of certainty in their estimate, the degree of criticality to system success, and their relationship to other requirements
Systems Engineering Fundamentals Defense Acquisition University Press, 2001

Privacy Requirements In software Engineering, privacy concerns can arise due to security problems or questions about why certain information is gathered by a website or application. Privacy issues for users of all levels must also be addressed as early in development as the requirements phase, with an emphasis on whom has access to certain information and what will be done with the information. A system should be created that only stores the minimal amount of personal information about a person required to complete a given function.
http://www.hhs.gov/ocio/eplc/EPLC%20Archive%20Docu ments/21%20%20Requirements%20Definition/eplc_requir ements_definition_template.doc

Software system safety In software engineering, software system safety optimizes system safety in the design, development, use, and maintenance of software systems and their integration with safety-critical hardware systems in an operational environment.
http://en.wikipedia.org/wiki/Software_system_safety