Below is a list of general terms and definitions that will be referred to throughout Discovery. For more information pertaining to CaseComplete Items, please refer to the CaseComplete Definitions Section. Related article: PM Glossary of Terms
| Term | Definition |
|---|---|
| API | API stands for application programming interface, a set of functions and procedures allowing the creation of applications that access the features or data of an operating system, application, or other service. API's use something called an endpoint to connect and transmit data. There are restful endpoints and active endpoints. |
| Basecamp | Basecamp is a 3rd party communication system, primarily use for client interactions. This is accomplished through various features like message threads, tracking to-do(s), documents and files, and more. |
| Connect | Clarity Connect: a customizable integration platform (middleware) that enables the client to move data between two or more systems such as ERPs, CRMs, eCommerce, etc. |
| CEF | Acronym; Stands for Clarity eCommerce Framework which is the platform that is used as a template to build customer eCommerce platforms. |
| Deliverable | The term “deliverable” is a project management term that is traditionally used to describe the quantifiable good or service that must be provided upon the completion of a project. Deliverables can be tangible or intangible in nature. For example, in a project focusing on upgrading a firm's hardware, a deliverable may refer to the acquisition of a dozen new computers. Conversely, for a software project, a deliverable might allude to the implementation of a computer program aimed at improving a company's accounts receivable computational efficiency. |
| Deployment | Development is the act of engineering a piece of software or a solution. |
| Environment | An environment describes the hardware specifications, the operating system installed, and the networking appliances available to house a website or application. |
| ERP | Acronym for Enterprise Resource Planning - The integrated management of main business processes, often in real time and mediated by software and technology. |
| Estimation | Estimates are not guaranteed. We provide estimations to the client about how many hours we think their specific tasks are going to take to complete. Based on the hours we can also estimate cost. |
| FSD | Functional Specifications Document; A functional specification is a formal document used to describe a product's intended capabilities, appearance, and interactions with users in detail for software developers. The functional specification is a kind of guideline and continuing reference point as the developers write the programming code. This document title is taking the place of IIW in all projects going forward as of 1/1/22 |
| Hours on Hand | The remaining billable hours a project has. |
| IIW | Acronym; Stands for Integration, Implementation, and Workflows; Represents the document that will be an output of the Discovery Process. This document defines the project’s full scope using Use Cases, Test Scenarios, User Stories, and Requirements. This document term is being sunsetted as of 1/1/22. |
| Integration | The action or process of integrating. Commonly used for integration of data between two or more systems. May refer to the total integration process or individual job syncs. |
| RDP | Remote Desktop Configurator (RDP). The Microsoft Remote Desktop Protocol (RDP) provides remote display and input capabilities over network connections for Windows-based applications running on a server.” (MSDN) Essentially, RDP allows users to control their remote Windows machine as if they were working on it locally (well, almost). |
| Requirement | A condition or capability needed by a user to solve a problem or achieve an objective. Clarity will be using Requirements to document all data that will be required to develop a feature, as well as to define the Requirements for each workflow mockup (screenshot). |
| SaaS | A method of software delivery and licensing in which software is accessed online via a subscription, rather than bought and installed on individual computers. Setting up a new client in [Connect SAAS] Azure |
| Sprint | A period of time that a set amount of work is planned to be completed. Resources (developer hours) are allocated to the set amount of work across all active and support projects. At Clarity, we operate on a 2-week sprint cadence starting on every other Wednesday. |
| Sync | A sync is can be an internal or external meeting that gets Meeting Roster on the same page. It can consist of something as detailed as how we're going to buildout a specific task, to a workflow, and even as broad as an external client meeting where we provide the client with an update on the three constraints - Timeline (Gantt Chart), Scope (Current Sprint Allocation, Demo, etc.), and Budget (PSR). |
| Test Scenario | A test scenario is a single path through a Use Case that describes the user inputs and expected results associated with each step of the workflow. Additional test scenario information can include test descriptions, testing setups, testing configurations, and status of the test. |
| Use Case | A Use Case is a list of actions or event steps typically defining the interactions between a role and a system to achieve a goal. The Actor can be a human or other external system. |
| User Story | A User Story is an informal, natural language description of one or more features of a software system. User stories are often written from the perspective of an end-user or user of a system. |
| VPN | VPN stands for “virtual private network” — a service that protects your internet connection and privacy online. VPN Instructions |
Additional needs: