Here is our dictionary of terms to help define all the terms used within this documentation. Let the help desk know if you don't find what you are looking for.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z | |||
A | Affiliate scheme | ||
Many of our customers recommend RequirementONE to other people using our affiliate scheme - by doing this they earn a percentage of the subscription income from people who become customers as well as helping their colleagues get hold of great software.
|
|||
Agile | |||
Agile is a set of software development principles in which requirements and solutions evolve through team collaboration. It promotes adaptive planning, evolutionary development, early delivery, and continuous improvement, and it encourages rapid and flexible response to change.
|
|||
B | Business Software Implementation solution |
||
A solution used to implement or replace any business software, such as a CRM, ERP, HR and Finance system.
|
|||
C | COBIT5 | ||
Control Objectives for Information and Related Technology (COBIT) is a framework for IT management and IT governance. It's based on five main principles and seven enablers.
|
|||
Compliance solution |
|||
A solution that assists with conforming to laws, standards, regulations, and other requirements.
|
|||
CRM | |||
A strategy for managing all your company’s relationships and interactions with your customers and potential customers.
|
|||
Custom fields | |||
100% customizable attributes, used to manage your records for progress, and status. Typical attributes include priority, status, person responsible, and version.
|
|||
D | DMAIC | ||
A data-driven quality strategy used to improve processes. DMAIC is the acronym for the five phases that make up the process: Define the problem, improvement activity, opportunity for improvement, the project goals, and customer (internal and external) requirements. Measure process performance. Analyze the process to determine root causes of variation, poor performance (defects). Improve process performance by addressing and eliminating the root causes. Control the improved process and future process performance.
|
|||
E | ECM | ||
Enterprise content management - a way of storing and organizing documents.
|
|||
I | IEEE | ||
Institute of Electrical and Electronics Engineers, a professional association that develops, defines, and reviews electronics and computer science standards.
|
|||
Integrations | |||
An Integration is a feature that allows your users to access information quickly about projects using external applications. Whenever the trigger event occurs, RequirementONE automatically completes all searches or actions for you. Triggers, searches and actions are simply events you can use to build an integration.
|
|||
ISO27001 | |||
A specification for an information security management system (ISMS). An ISMS is a framework of policies and procedures that includes all legal, physical and technical controls involved in an organisation's information risk management processes.
|
|||
Issue | |||
A present problem or concern which happens when a requirement has not been implemented correctly.
|
|||
ITIL | |||
Information Technology Infrastructure Library - a set of practices for IT service management (ITSM) that focuses on aligning IT services with the needs of business.
|
|||
L | Level | ||
The level of detail and complexity given in a solution template
|
|||
P | Product Development Solution | ||
A solution used to develop a new product using various methodologies, including agile and waterfall. This solution spans planning, requirement specification, issue tracking and gathering stakeholder feedback.
|
|||
R | Read | ||
Permission that allows a user to see records, tasks etc within the project.
|
|||
ReadWrite | |||
Permission that allows a user to edit a record, task etc within the project.
|
|||
ReadWriteAdmin | |||
Permission that allows a user full access rights - users can modify records and delete them.
|
|||
Records | |||
Business requirements, functional requirements, use cases and test cases.
|
|||
Requirements | |||
Business requirements define the goals and objectives that solutions have to support
|
|||
Review | |||
A list of issues
|
|||
S | Specification | ||
Data records organised into documents
|
|||
Sprints | |||
Set periods of time during which specific work has to be completed and made ready for review
|
|||
Surveys | |||
Groups used to organize your stakeholder feedback questionnaires
|
|||
T | Task | ||
A detailed deliverable within your project
|
|||
Traceability matrix | |||
A document, usually in the form of a table that correlates any two baselined documents that require a many-to-many relationship to determine the completeness of the relationship.
|
|||
W | Waterfall | ||
A waterfall model is a sequential design process, used in software development, in which the phases of conception, initiation, analysis, design, construction, testing, production/implementation and maintenance are seen as flowing steadily downwards (like a waterfall).
|
|||
Comments
0 comments
Please sign in to leave a comment.