Open Source LIMS Development terminology
|
4IR. Fourth Industrial Revolution The fourth major industrial era since the initial Industrial Revolution of the 18th century, a range of new technologies that are fusing the physical, digital and biological worlds, and impacting all disciplines, economies, and industries. In fields such as artificial intelligence, robotics, the Internet of Things, autonomous vehicles, 3D printing, quantum computing and nanotechnology. Acceptance Testing The last phase of software testing. Software users test the software to make sure it was delivered to specifications CD. Continuous delivery A software engineering approach in which teams produce software in short cycles, ensuring that the software can be reliably released at any time. It aims at building, testing, and releasing software with greater speed and frequency to reduce the cost, time, and risk of delivering changes by allowing for more incremental updates to applications in production. Wikipedia.org CR. Change Request Change Requests document the feasibility and common understanding of what is required for the recommended changes to the original specification If in agreement, both Bika and the client signs this document for the changes to be implemented. It also serves as a functional specification for programmers working on the project and quality management tool It is used to estimate development cost and establish a quote for the modification Easter Egg Unintended surprise feature discovered by chance. Intended in disciplines like Game development FLOSS. Free/Libre/Open Source Software Refers to both Free Software and Open Source Software. FLOSS is liberally licensed to grant the right of users to use, study, change, and improve its design through the availability of its source code. This approach gained momentum and acceptance as the potential benefits have been increasingly recognized by both individuals and corporations. Free refers to the freedom to copy and reuse the software, rather than to the price of the software FOSS. Free Open Source Software Refers to the Free Software and Open Source communities as a whole without differentiating between the terms and the matching philosophies. Libervis.com Gap Analysis In LIMS analysis and design, a planning tool to compare the current Bika functionality with the lab's desired requirement The Gap AnalysIt forms the basis for development of customisation plans to address high-priority gaps
|
GPL. General Public License The Open Source GPL guarantees freedom to share and change software and ensures it is free for all users NDA. Non-disclosure Agreement A legal contract between parties describing confidential material, knowledge, or information that they wish to share with one another for certain purposes, but restrict access to by third parties. Commonly signed when two entities are considering project collaboration or partnerships OSS. Open Source Software POC. Proof of Concept Evidence, typically deriving from an experiment or pilot project, which demonstrates that a design concept, business proposal, etc. is feasible. Lexico.com POSS. Professional Open Source Software The POSS model combines traditional OSS projects run by a community of software enthusiasts, with a professional company and fee paying client sponsors Customers benefit from the increased quality of the software, best of breed design, and increased traction enabled by the product's community The model is powerful because the customers, partners, engineers, and open source communities are all self-motivated to behave in ways that are beneficial to themselves and, as a side effect, to all
Pick any two of Fast, Good and Cheap. If you want Fast, it cannot be Cheap. Never sacrifice quality. With Open Source, strive to do as much possible inhouse with assistance on community forums. Not fast, but free RERO. Release early, release often Popularised by Eric S. Raymond in his 1997 essay The Cathedral and the Bazaar, "Release early. Release often. And listen to your customers" A software development philosophy that emphasises the importance of early and frequent releases in creating a tight feedback loop between developers and testers or users, contrary to a feature-based release strategy. This allows the software development to progress faster, enables the user to help define what the software will become, better conforms to the users' requirements for the software, and ultimately results in higher quality software. The development philosophy attempts to eliminate the risk of creating software that no one will use. Wikipedia.org
|
REST. REpresentational State Transfer An interoperability architecture popular for its simplicity, using existing Internet HTTP features to connect systems. REST compliant web services allow access and manipulation of resources IDentified by their URLs in a standardised set of stateless operations. Initially used for documents, REST is now used for any object that can be identified, named, addressed or handled on the web. REST therefore is fast, reliable, scalable and kept freshly up to date Requests to a resource's URL prompts a response in say XML, HTML or JSON format, to confirm modifications, and possible links to related resources GET, POST, PUT, DELETE, and other predefined methods are available in for HTTP ROI. Return on Investment Sanity Testing Sanity Testing as a test execution which is done to touch each implementation and its impact but not thoroughly or in-depth, it may include functional, UI, version, etc. testing. The goal is to determine that the proposed functionality works roughly as expected Smoke Testing Smoke Testing is not exhaustive testing but it is a group of tests that are executed to verify if the basic functionalities are working fine as expected or not. It covers the most important functionality of a module or system TCO. Total Cost of Ownership UAT. User Acceptance Testing The last phase of software testing. Software users test the software to make sure it was delivered to specification UI. User Interface The system by which people interact with a computer e.g. a set of commands or menus in a program. Graphical user interfaces, GUIs, use windows, icons, and pop-up menus URS. User Requirement Specification A non-technical description of a lab's LIMS requirements, in layman language but unambiguous with enough details for coding specifications and cost calculations to be based on UX. User Experience User experience encompasses all aspects of the end-user’s interaction with the software. It refers to the feeling users experience when using an application or system. It covers anything from how well the user can navigate the product, how easy it is to use, how relevant the content displayed is etc.
|
Project Management Triangle
