Software Terms Flashcards
Failure
Deviation identified by end-user while using system.
Failure
Deviation identified by end-user while using system.
Defect
Deviation from the expected behavior to the actual behavior.
SOP
Standard Operating Prodcedure
Defect
Deviation from the expected behavior to the actual behavior.
Error
Any incorrect human action that produces a problem in the system
Products (VS Project)
Developed for multiple customer requirements (vs just one)
Project (VS Product)
Developed for a specific customer requirement (vs multiple customer requirements)
API’s
Application programming interface.
This allows services and products to communicate with each other and leverage each other’s data and functionality through a documented interface.
Deployment Manager Process
- Backup
- Automate
- Test
Enterprise Release Process
- Priority Gate
- Planning
- Phases
- Build Gate
- Integrations Testing
- Build Gate 2
- Goes to Deployment Manager
- Prod Gate to Users!
Environment Manager
Manage Dev, SIT, UAT, Stage
SIT
System Integrations Testing
UAT
User Acceptance Training
STUBS
A program which acts as a dummy module for top down testing
Clusters
Bottom-most modules or units that are being merged and tested. If the main module is not available, a Driver (program) is used instead.
Techniques used in SIT Testing
Top-Down approach (main functionality or module is tested followed by sub modules in order) Bottom-Up approach (Lower modules are integrated first and higher modules are integrated and tested) Big Bang approach (connect everything at once and test all)
Levels of Testing Hierarchy
Unit Testing Component Testing System Testing System Integration Testing User Acceptance Testing Production
What questions must be answered before taking the first steps toward creating your API?
What is the company trying to achieve with the API?
How will the business position and sponsor it?
What are the terms and conditions of the API usage?
What are the risks and liabilities to the company in case of the API misuse?
How will the company protect itself from intellectual property infringement?
What business functions will be made available, and at what level of granularity?
What is the rationalization of the API?
How will the API be discovered?
Why is API interface design so important?
To spot a great API, the design must be a first-order consideration. The API user experience is a primary & critical feature because an optimal design is what will enable application developers to easily understand the purpose and functionality of an API for them to effectively interact with it. This feature will also allow your organization to get the API design right before investing in back-end implementation, which is time-consuming and expensive to undo if design issues aren’t identified until after implementation.
What are some qualities of a well designed API?
Informed decision making for customers: Customer journeys with the API should be simple & intuitive and information must be easily assimilated in order to ensure informed customer decision making.
Simple and easy navigation: There must be no unnecessary steps, delay or friction in the customer journey.
Parity of Experience: The experience availed to a customer when authenticating a process with the API should involve no more steps, delay or friction than the equivalent experience they have when interacting directly with the company.
Familiarity and trust: The customer must only need to use the login credential accorded where necessary. Simple sandbox can allow developers to play with your demo product without any potential harm to live product.
Why is API documentation so important?
’Its no argument; simple API documentation without examples is equal to an undocumented API, and is outrightly disgusting. You’ve simply got to get this right, the importance of API documentation is as essential as the API itself. In fact, the provision of a good, extensive documentation for an API is something that should be understood by developers & vendors by default – you shouldn’t have to point that out.
API features: What is the API is designed to achieve in a form that the consumers can easily digest?
Structures: A schematic description of the API, including data structures & security.
Capabilities: What is the peak load the API can handle (both projected and actual) and the performance pinch points.
Sensitivities: Does the API consume or expose any data that may be subject to regulatory or privacy constraint, such as payment card data, personally identifiable data, and so on.
What is OAuth?
OAuth is an open-standard approval convention or system that describes how inconsequential servers and services can securely enable authenticated access to their assets without really sharing the underlying, related, single login accreditation. OAuth acts as an intermediary on behalf of the end-user, providing services with an access token that authorizes specific account information to be shared.
OAuth is a great property/feature for an API as it provides superior usability for the application developers and other users. Courtesy of the OAuth application users like Xero users are able to interface one application to another via some integration services through authenticating themselves and expressly granting service access to an application.
Why is JSON/REST support important?
Although it is not a must for an API to be RESTful in order to be viewed as great, most new APIs are REST APIs that by default support JSON, and there are many valid justifications for this. For one, REST APIs are stateless, which is one factor that makes many APIs want to incorporate this feature, especially in cases of applications that require a lot of forward and backward informing, e.g. mobile applications.
For example, on the off chance that data transfer to a mobile application is hindered because of, say, reception loss, REST APIs make it extremely simple to recompose & retry the procedure. Moreover, REST APIs are lightweight and perform very well with the web as they utilize basic URIs for correspondence. REST APIs bolster a variety of arrangements, with JSON being just one of them. They also support others like TXT, CSV, and XML formats.
Why is API scalability important?
A good API must encompass the capability to greatly increase in capacity with relative ease – literally because the amount of information accessible to entrepreneurs is continually changing and developing. Quality APIs should thus be able to convey all essential data rapidly, without stoppages, standard slowdowns or other disappointments. It’s critical and of paramount importance to evaluate the reliability and quality of an API through target/goal/objective measures. This can be done through measurements like:
How rapidly can the API relay data?
What amount of data will it be able to relay at a given time?
How regularly has it flopped in the previous years?
These sorts of inquiries help to evaluate whether the API offers the scale and unwavering quality essential for your business or not. They will equally help you assess the possibility of the API presenting that indispensable scalability and reliability necessary for your business’s optimal performance.
Why is mobile API optimization important?
Making information open to mobile applications has developed significantly. Although principally all APIs ought to be platform agnostic, in practice, it’s imperative to consider the mobile readiness & integration capabilities of your API. This is primarily because mobile poses unique integration challenges, and hence having a mobile amicable API will present a more pleasant, flexible, and versatile offer in your business and for the consumers.
Why is API Modification timestamps/ Search by criteria important?
A Quality API should permit to seek information by a specific criterion, and above all by its date.
Why is API Paging important?
A decent API must have the capacity to confine the measure of information that can be received at one go as well as the recurrence of solicitations for information. It ought to likewise have the capacity to tell about the number of “pages” of the information left to be cleared out.
SSO
Single Sign-On
What’s WACG 2.1 AA Compliance?
Accessibility compliance. RainFocus works with a company called “Accessibility” to audit the platform.
What’s GraphQL API’s?
Query language - SQL for integrations.
Hot Fix
Software patch to temporarily fix a bug in a product
Caching
Computing component that transparently stores data so that future requests for that data can be served faster
Build VS Push to Prod
Build is adding it to the queue and pushing to prod is making the changes live. As Rich calls it, “flip the switch”
