Software feature
A software feature is "a prominent or distinctive user-visible aspect, quality, or characteristic of a software system or systems", as defined by Kang et al.[1] At the implementation level, "it is a structure that extends and modifies the structure of a given software in order to satisfy a stakeholder’s requirement, to implement and encapsulate a design decision, and to offer a configuration option", as defined by Apel et al.[2]
Context
The term feature means the same for software as it does for any kind of system. For example, the British Royal Navy's HMS Dreadnought (1906) was considered an important milestone in naval technology because of its advanced features that did not exist in pre-dreadnought battleships.[3]
Feature also applies to computer hardware. In the early history of computers, devices such as Digital Equipment Corporation's PDP-7 minicomputer (created in 1964) was noted for having a wealth of features, such as being the first version of the PDP minicomputer series to use wire wrap, as well as being the first to use the proprietary DEC Flip-Chip module which was invented in the same year.[4][5]
Feature also applies to concepts such as a programming language. The Python programming language is well-known for its feature of using whitespace characters (spaces and tabs) instead of curly braces to indicate different blocks of code.[6]
Another similar high-level, object oriented programming language, Ruby, is noteworthy for using the symbols "@" and "$" to highlight different variable scopes, which the developers claim improves code readability. Its developers also claim that one of its important features is a high amount of flexibility.[7]
The Institute of Electrical and Electronics Engineers (IEEE) defines feature in the (obsolete) standard for software test documentation IEEE 829 as a "distinguishing characteristic of a software item (e.g., performance, portability, or functionality)".[8]
Although feature is typically used for a positive aspect of a software system, a software bug is also a feature but with negative value.
Examples
The terminal emulator xterm has many notable features, including compatibility with the X Window System, the ability to emulate a VT220 and VT320[9] terminal with ANSI color, and the ability to input escape sequences using a computer mouse or other similar device, and the ability to run on multiple different Unix-like operating systems (e.g. Linux, AIX, BSD, and HP-UX).[10]
Feature-rich and feature creep
Feature-rich describes a software system as having many options and capabilities.
One mechanism for introducing feature-rich software to the user is the concept of progressive disclosure, a technique where features are introduced gradually as they become required, to reduce the potential confusion caused by displaying a wealth of features at once.[11]
Sometimes, feature-rich is considered a negative attribute. The terms feature creep, software bloat, and featuritis refer to software that is overly feature-rich.[12] This type of excessive inclusion of features is in some cases a result of design by committee.[13]
To counteract the tendency of software developers to add additional, unnecessary features, the Unix philosophy was developed in the 1970s by Bell Labs employees working on the Unix operating system such as Ken Thompson and Dennis Ritchie. The philosophy can be summarized as: software programs should generally only complete one primary task and that "small is beautiful".[14][15]
See also
- Feature-oriented programming
- Product family engineering
- Software design
- Software testing
- Application lifecycle management
- Feature creep
- Scope creep
- Overengineering
References
Page Template:Reflist/styles.css has no content.
- ^ Page Module:Citation/CS1/styles.css has no content."Feature-Oriented Domain Analysis (FODA) Feasibility Study". insights.sei.cmu.edu. 1990-10-31. Retrieved 2025-02-18.
- ^ Page Module:Citation/CS1/styles.css has no content.Apel, Sven; Kästner, Christian (August 2009). "An Overview of Feature-Oriented Software Development". The Journal of Object Technology. 8 (5): 49–84. doi:10.5381/jot.2009.8.5.c5. S2CID 417250.
- ^ Page Module:Citation/CS1/styles.css has no content."How the Dreadnought sparked the 20th Century's first arms race".
- ^ Page Module:Citation/CS1/styles.css has no content."PDP-7". reference.com Computing Dictionary. Archived from the original on June 16, 2013.
- ^ Page Module:Citation/CS1/styles.css has no content.Tore Sinding Bekkedal (2009). "Digital Equipment Corporation PDP-7". soemtron.org.
- ^ Page Module:Citation/CS1/styles.css has no content."PEP 8 – Style Guide for Python Code".
- ^ Page Module:Citation/CS1/styles.css has no content."About Ruby".
- ^ IEEE Std. 829-1998
- ^ Page Module:Citation/CS1/styles.css has no content."XTERM - Change Log - Patch #24 - 1996/8/11 - XFree86 3.1.2Ee". Archived from the original on 2001-12-22.
- ^ Page Module:Citation/CS1/styles.css has no content.Thomas E. Dickey. "XTerm – Frequently Asked Questions (FAQ), Who wrote XTerm?". Archived from the original on 2018-06-24. Retrieved 2018-06-04.
- ^ Page Module:Citation/CS1/styles.css has no content.User centered system design: new perspectives on human-computer interaction. Norman, Donald A., Draper, Stephen W. Hillsdale, N.J.: L. Erlbaum Associates. 1986. ISBN 0-89859-781-1. OCLC 12665902.
{{cite book}}: CS1 maint: others (link) - ^ Page Module:Citation/CS1/styles.css has no content."Featuritis (or creeping featurism)".
- ^ Page Module:Citation/CS1/styles.css has no content.Krystallis, Ilias; Locatelli, Giorgio (2022-09-01). "Normalizing White-Collar Wrongdoing in Professional Service Firms". Journal of Management in Engineering. 38 (5): 04022049. doi:10.1061/(ASCE)ME.1943-5479.0001079. hdl:11311/1228318. ISSN 1943-5479. S2CID 250326876.
- ^ Page Module:Citation/CS1/styles.css has no content.Doug McIlroy; E. N. Pinson; B. A. Tague (8 July 1978). "Unix Time-Sharing System: Foreword". The Bell System Technical Journal. Bell Laboratories: 1902–1903.
- ^ Page Module:Citation/CS1/styles.css has no content."The Unix Philosophy".
