3rd-Party Software Development Platform

From GM-RKB
(Redirected from toolkit for building)
Jump to navigation Jump to search

A 3rd-Party Software Development Platform is a software platform that facilitates software development (of software systems).



References

2024

  1. 3rd-Party Software Development Platforms
    1. 3rd-Party Integrated Development Environment (IDE)s
      1. 3rd-Party Desktop IDEs (e.g., Visual Studio, IntelliJ IDEA)
      2. 3rd-Party Cloud-based IDEs (e.g., AWS Cloud9, GitHub Codespaces)
    2. 3rd-Party Low-Code Development Platforms
      1. 3rd-Party Enterprise Low-Code Development Platforms (e.g., OutSystems, Mendix)
      2. 3rd-Party Citizen Developer Low-Code Development Platforms (e.g., Microsoft Power Apps)
    3. 3rd-Party No-Code Development Platforms
      1. 3rd-Party Web Application Builders (e.g., Webflow, Wix)
      2. 3rd-Party Mobile App Builders (e.g., Adalo, Thunkable)
    4. 3rd-Party Game Development Platforms
      1. 3rd-Party Multi-purpose Game Engines (e.g., Unity, Unreal Engine)
      2. 3rd-Party Specialized Game Platforms (e.g., Roblox Studio)
    5. 3rd-Party Enterprise Application Development Platforms
      1. 3rd-Party CRM Platforms (e.g., Salesforce Lightning)
      2. 3rd-Party ERP Platforms (e.g., SAP Business Technology Platform)
  1. 3rd-Party Software Development Frameworks
    1. 3rd-Party Web Application Frameworks
      1. 3rd-Party Frontend Frameworks (e.g., React, Angular)
      2. 3rd-Party Backend Frameworks (e.g., Django, Ruby on Rails)
      3. 3rd-Party Full-stack Frameworks (e.g., Meteor)
    2. 3rd-Party Mobile Development Frameworks
      1. 3rd-Party Cross-platform Frameworks (e.g., React Native, Flutter)
      2. 3rd-Party Native Frameworks (e.g., SwiftUI for iOS, Jetpack Compose for Android)
    3. 3rd-Party Data Processing Frameworks
      1. 3rd-Party Big Data Frameworks (e.g., Apache Hadoop, Apache Spark)
      2. 3rd-Party Stream Processing Frameworks (e.g., Apache Kafka, Apache Flink)
    4. 3rd-Party Machine Learning Frameworks
      1. 3rd-Party General-purpose ML Frameworks (e.g., TensorFlow, PyTorch)
      2. 3rd-Party Specialized ML Frameworks (e.g., Scikit-learn, Keras)
    5. 3rd-Party Testing and Automation Frameworks
      1. 3rd-Party Unit Testing Frameworks (e.g., JUnit, pytest)
      2. 3rd-Party UI Testing Frameworks (e.g., Selenium, Cypress)
    6. 3rd-Party IoT Development Frameworks
      1. 3rd-Party Edge Computing Frameworks (e.g., Azure IoT Edge)
      2. 3rd-Party IoT Protocol Frameworks (e.g., MQTT, CoAP)
  1. 3rd-Party Development Tools and Services
    1. 3rd-Party Version Control Systems
      1. 3rd-Party Centralized Version Control Systems (e.g., Subversion)
      2. 3rd-Party Distributed Version Control Systems (e.g., Git, Mercurial)
    2. 3rd-Party CI/CD Tools
      1. 3rd-Party Continuous Integration Tools (e.g., Jenkins, CircleCI)
      2. 3rd-Party Continuous Deployment Tools (e.g., Spinnaker, ArgoCD)
    3. 3rd-Party Project Management Tools
      1. 3rd-Party Agile Project Management Tools (e.g., Jira, Trello)
      2. 3rd-Party Developer-focused Project Management Tools (e.g., GitHub Projects, GitLab Boards)
    4. 3rd-Party Code Quality and Analysis Tools
      1. 3rd-Party Static Analysis Tools (e.g., SonarQube, ESLint)
      2. 3rd-Party Dynamic Analysis Tools (e.g., Valgrind)
    5. 3rd-Party Collaboration and Communication Tools
      1. 3rd-Party Team Collaboration Platforms (e.g., Slack, Microsoft Teams)
      2. 3rd-Party Code Review Tools (e.g., Gerrit, Reviewable)
  1. 3rd-Party Cloud and Infrastructure Platforms
    1. 3rd-Party Infrastructure as a Service (IaaS) Platforms
      1. 3rd-Party Public Cloud Providers (e.g., AWS EC2, Google Compute Engine)
      2. 3rd-Party Private Cloud Platforms (e.g., OpenStack)
    2. 3rd-Party Platform as a Service (PaaS) Platforms
      1. 3rd-Party Application Platform as a Service Platforms (e.g., Heroku, Google App Engine)
      2. 3rd-Party Container Platform as a Service Platforms (e.g., Red Hat OpenShift)
    3. 3rd-Party Serverless Platforms
      1. 3rd-Party Function as a Service (FaaS) Platforms (e.g., AWS Lambda, Azure Functions)
      2. 3rd-Party Backend as a Service (BaaS) Platforms (e.g., Firebase, Supabase)
  1. 3rd-Party DevOps and SRE Tools
    1. 3rd-Party Configuration Management Tools
      1. 3rd-Party Infrastructure as Code Tools (e.g., Terraform, Ansible)
      2. 3rd-Party Configuration Orchestration Tools (e.g., Puppet, Chef)
    2. 3rd-Party Monitoring and Observability Tools
      1. 3rd-Party Application Performance Monitoring Tools (e.g., New Relic, Datadog)
      2. 3rd-Party Log Management Tools (e.g., ELK Stack, Splunk)
    3. 3rd-Party Container Orchestration Platforms
      1. 3rd-Party Kubernetes Platforms and Distributions
      2. 3rd-Party Container Orchestration Alternatives (e.g., Docker Swarm)
  1. 3rd-Party Specialized Development Environments
    1. 3rd-Party Data Science and Analytics Platforms
      1. 3rd-Party Notebook Environments (e.g., Jupyter, Google Colab)
      2. 3rd-Party Data Analytics Platforms (e.g., Apache Zeppelin, RStudio)
    2. 3rd-Party Blockchain Development Platforms
      1. 3rd-Party Smart Contract Platforms (e.g., Ethereum, Solana)
      2. 3rd-Party Enterprise Blockchain Platforms (e.g., Hyperledger Fabric)
    3. 3rd-Party AR/VR Development Platforms
      1. 3rd-Party AR Development Kits (e.g., ARKit, ARCore)
      2. 3rd-Party VR Development Platforms (e.g., SteamVR, Oculus SDK)

2024

2022

  • (Wikipedia, 2022) ⇒ https://en.wikipedia.org/wiki/software_framework Retrieved:2022-11-1.
    • In computer programming, a software framework is an abstraction in which software, providing generic functionality, can be selectively changed by additional user-written code, thus providing application-specific software. It provides a standard way to build and deploy applications and is a universal, reusable software environment that provides particular functionality as part of a larger software platform to facilitate the development of software applications, products and solutions. Software frameworks may include support programs, compilers, code libraries, toolsets, and application programming interfaces (APIs) that bring together all the different components to enable development of a project or system.

      Frameworks have key distinguishing features that separate them from normal libraries:

      • inversion of control: In a framework, unlike in libraries or in standard user applications, the overall program's flow of control is not dictated by the caller, but by the framework. This is usually achieved with the Template Method Pattern.
      • default behaviour: This can be provided with the invariant methods of the Template Method Pattern in an abstract class which is provided by the framework.
      • extensibility: A user can extend the framework – usually by selective overriding – or programmers can add specialized user code to provide specific functionality. This is usually achieved by a hook method in a subclass that overrides a template method in the superclass.
      • non-modifiable framework code: The framework code, in general, is not supposed to be modified, while accepting user-implemented extensions. In other words, users can extend the framework, but cannot modify its code.


2013