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.
