|
Software Requirements
Software requirements for a system are the description of what the system should do, the service or services that it provides and the constraints on its operation. The IEEE Standard Glossary of Software Engineering Terminology defines a requirement as: # ''A condition or capability needed by a user to solve a problem or achieve an objective.'' # A condition or capability that must be met or possessed by a system or system component to satisfy a contract, standard, specification, or other formally imposed document. # A documented representation of a condition or capability as in 1 or 2. The activities related to working with software requirements can broadly be broken down into elicitation, analysis, specification, and management. Note that the wording ''Software requirements'' is additionally used in software release notes to explain, which depending software packages are required for a certain software to be built/installed/used. Elicitation Elicitation is the gathering and di ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Requirement
In product development and process optimization, a requirement is a singular documented physical or functional need that a particular design, product or process aims to satisfy. It is commonly used in a formal sense in engineering design, including for example in systems engineering, software engineering, or enterprise engineering. It is a broad concept that could speak to any necessary (or sometimes desired) function, attribute, capability, characteristic, or quality of a system for it to have value and utility to a customer, organization, internal user, or other stakeholder. Requirements can come with different levels of specificity; for example, a requirement specification or requirement "spec" (often imprecisely referred to as "the" spec/specs, but there are actually different sorts of specifications) refers to an explicit, highly objective/clear (and often quantitative) requirement (or sometimes, ''set'' of requirements) to be satisfied by a material, design, product, or se ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Role-playing
Role-playing or roleplaying is the changing of one's behaviour to assume a role, either unconsciously to fill a social role, or consciously to act out an adopted role. While the ''Oxford English Dictionary'' offers a definition of role-playing as "the changing of one's behaviour to fulfill a social role", in the field of psychology, the term is used more loosely in four senses: * To refer to the playing of roles generally such as in a theatre, or educational setting; * To refer to taking a role of a character or person and acting it out with a partner taking someone else's role, often involving different genres of practice; * To refer to a wide range of games including role-playing video game (RPG), play-by-mail games and more; * To refer specifically to role-playing games. Amusement Many children participate in a form of role-playing known as make believe, wherein they adopt certain roles such as doctor and act out those roles in character. Sometimes make believe adopts an o ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Application Lifecycle Management
Application lifecycle management (ALM) is the product lifecycle management (governance, development, and maintenance) of computer programs. It encompasses requirements management, software architecture, computer programming, software testing, software maintenance, change management, continuous integration, project management, and release management. ALM vs. Software Development Life Cycle ALM is a broader perspective than the Software Development Life Cycle (SDLC), which is limited to the phases of software development such as requirements, design, coding, testing, configuration, project management, and change management. ALM continues after development until the application is no longer used, and may span many SDLCs. Integrated ALM Modern software development processes are not restricted to the discrete ALM/ SDLC steps managed by different teams using multiple tools from different locations. Real-time collaboration, access to the centralized data repository, cross- ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Unified Modeling Language
The Unified Modeling Language (UML) is a general-purpose, developmental modeling language in the field of software engineering that is intended to provide a standard way to visualize the design of a system. The creation of UML was originally motivated by the desire to standardize the disparate notational systems and approaches to software design. It was developed at Rational Software in 1994–1995, with further development led by them through 1996. In 1997, UML was adopted as a standard by the Object Management Group (OMG), and has been managed by this organization ever since. In 2005, UML was also published by the International Organization for Standardization (ISO) as an approved ISO standard. Since then the standard has been periodically revised to cover the latest revision of UML. In software engineering, most practitioners do not use UML, but instead produce informal hand drawn diagrams; these diagrams, however, often include elements from UML. History Before UML ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Systems Modeling Language
The Systems Modeling Language (SysML) is a general-purpose modeling language for systems engineering applications. It supports the specification, analysis, design, verification and validation of a broad range of systems and systems-of-systems. SysML was originally developed by an open source specification project, and includes an open source license for distribution and use. SysML is defined as an extension of a subset of the Unified Modeling Language (UML) using UML's profile mechanism. The language's extensions were designed to support systems engineering activities. Contrast with UML SysML offers several systems engineering specific improvements over UML, which has been developed as a software modeling language. These improvements include the following: * SysML's diagrams express system engineering concepts better due to the removal UML's software-centric restrictions and adds two new diagram types, requirement and parametric diagrams. The former can be used for requiremen ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Requirements Interchange Format
In product development and process optimization, a requirement is a singular documented physical or functional need that a particular design, product or process aims to satisfy. It is commonly used in a formal sense in engineering design, including for example in systems engineering, software engineering, or enterprise engineering. It is a broad concept that could speak to any necessary (or sometimes desired) function, attribute, capability, characteristic, or quality of a system for it to have value and utility to a customer, organization, internal user, or other stakeholder. Requirements can come with different levels of specificity; for example, a requirement specification or requirement "spec" (often imprecisely referred to as "the" spec/specs, but there are actually different sorts of specifications) refers to an explicit, highly objective/clear (and often quantitative) requirement (or sometimes, ''set'' of requirements) to be satisfied by a material, design, product, or ser ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Trello
Trello is a web-based, kanban-style, list-making application and is developed by Trello Enterprise, a subsidiary of Atlassian. Created in 2011 by Glitch, it was spun out to form the basis of a separate company in New York City in 2014 and sold to Atlassian in January 2017. History The name Trello is derived from the word "trellis" which had been a code name for the project at its early stages. Trello was released at a TechCrunch event by Fog Creek founder Joel Spolsky. In September 2011 ''Wired'' magazine named the application one of "The 7 Coolest Startups You Haven't Heard of Yet". Lifehacker said "it makes project collaboration simple and kind of enjoyable". In 2014, it raised US$10.3 million in funding from Index Ventures and Spark Capital. Prior to its acquisition, Trello had sold 22% of its shares to investors, with the remaining shares held by founders Michael Pryor and Joel Spolsky. In May 2016, Trello claimed it had more than 1.1 million daily active use ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Collaboration Tool
A collaboration tool helps people to collaborate. The purpose of a collaboration tool is to support a group of two or more individuals to accomplish a common goal or objective. Collaboration tools can be either of a non-technological nature such as paper, flipcharts, post-it notes or whiteboards. They can also include software tools and applications such as collaborative software. Collaboration tools before Web 2.0 The first idea to use computers in order to work with each other was formed in 1945 when Vannevar Bush shared his thoughts on a system he named"memex" in his article "As We May Think". A system that stores books, records and communications of an individual and makes them available at any time. At this stage he called it "''an enlarged supplement to his memory"''. Computerized office automation In 1968 computer systems were brought in connection with communication and the potential way of working together when not at the same place by Dr. J. C. R. Licklider, he ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Wiki
A wiki ( ) is an online hypertext publication collaboratively edited and managed by its own audience, using a web browser. A typical wiki contains multiple pages for the subjects or scope of the project, and could be either open to the public or limited to use within an organization for maintaining its internal knowledge base. Wikis are enabled by wiki software, otherwise known as wiki engines. A wiki engine, being a form of a content management system, differs from other web-based systems such as blog software, in that the content is created without any defined owner or leader, and wikis have little inherent structure, allowing structure to emerge according to the needs of the users. Wiki engines usually allow content to be written using a simplified markup language and sometimes edited with the help of a rich-text editor. There are dozens of different wiki engines in use, both standalone and part of other software, such as bug tracking systems. Some wiki engines are o ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Concordion
Concordion is a specification by example framework originally developed by David Peterson, and now maintained by a team of contributors, led by Nigel Charman. Inspired by the Fit Framework, David states the following aims were behind Concordion: * Improved readability of documents * More "opinionated" (scripting is actively discouraged) * Easier to use How it works Concordion specifications are written in Markdown, HTML or Excel and then instrumented with special links, attributes or comments respectively. When the corresponding test fixture class is run, Concordion interprets the instrumentation to execute the test. Rather than forcing product owners to specify requirements in a specially structured language, Concordion lets you write them in normal language using paragraphs, tables and proper punctuation. This makes the specifications much more natural to read and write, and helps everyone to understand and agree about what a feature is supposed to do. The Markdown, HTML o ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Specification By Example
Specification by example (SBE) is a collaborative approach to defining requirements and business-oriented functional tests for software products based on capturing and illustrating requirements using realistic examples instead of abstract statements. It is applied in the context of agile software development methods, in particular behavior-driven development. This approach is particularly successful for managing requirements and functional tests on large-scale projects of significant domain and organisational complexity. Specification by example is also known as example-driven development, executable requirements, acceptance test–driven development (ATDD or A-TDD), Agile Acceptance Testing, Test-Driven Requirements (TDR). Advantages Highly abstract or novel new concepts can be difficult to understand without concrete examples. Specification by example is intended to construct an accurate understanding, and significantly reduces feedback loops in software development, leading ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
