- 18 Jul 2024
- 3 Minutes to read
- Print
- DarkLight
- PDF
FAQ
- Updated on 18 Jul 2024
- 3 Minutes to read
- Print
- DarkLight
- PDF
PRD-AI
What is PRD-AI?
PRD-AI is our enhanced-AI-powered tool that generates comprehensive Product Requirements Document (PRD) for your software applications. Provide a brief description of your app and your business and PRD-AI generates a detailed outline, including features, user roles, acceptance criteria, and so much more.
What are Context Settings?
Context provides relevant details about your business and your preferred technologies to help PRD-AI customize your PRD to your organization’s development environment.
Context Settings are how you provide that context data within the Crowdbotics platform.
What is Module Matching?
What are Non-Functional Requirements (NFRs)?
As part of the initial PRD creation, PRD-AI generates Non-Functional Requirements (NFRs) to identify and capture areas (such as scalability, compatibility, and maintainability) that need to be considered during app development.
NFRs are provided in their own category called Non-Functional Requirements at the bottom of Phase 1 on the Phases & Features tab. Each NFR area (or type) looks and functions just as any other feature.
What are Technical Recommendations?
What are Data Models?
Reliability
Is Crowdbotics SOC2 certified?
Yes. Crowdbotics is SOC2 Type 2 certified. This reinforces our promise to prioritize security and reliability in everything we do. |
How can I trust the quality and accuracy of the code generated by Crowdbotics?
Most code provisioned by AI on Crowdbotics is selected from code already written and generated by an organization, where the quality, accuracy, and IP rights have already been reviewed by the organization’s own standards. We always recommend that code created by a generative AI solution should be reviewed by a human.
How does Crowdbotics handle code vulnerabilities that are discovered in supporting catalogs and modules?
Crowdbotics uses Dependabot and other continuous vulnerability trackers to ensure that all packages and dependencies are kept up to date. Within an enterprise, we plug into an organization’s own vulnerability and update trackers to post updates to modules.
Ownership
In general, who owns the code generated by the Crowdbotics platform?
The Crowdbotics platform hosts a centralized, shareable private catalog of code modules and related data for our customers. However, all code modules within a customer's private catalog are exclusively owned by and for the use of that customer and any agents they provide access to.
During the application development process, the Crowdbotics platform injects applicable pre-certified modules into configured code repositories of their choice. Customer administrators have full access to all modules, at all times through their Git repository.
Should a customer decide to part ways with Crowdbotics, all customer modules can be exported to a code repository of their choice, and we will work with the customer to determine the export format for related data. However, any module updates would not be available without a license.
Do I own the apps I build using the Crowdbotics platform?
Absolutely. You own the apps you build on the Crowdbotics platform.
Crowdbotics assigns ownership of inventions created during app development to you.
Crowdbotics grants you a license to use its pre-existing materials in your app.
Who owns the modules in the Crowdbotics platform?
Private Catalog
All modules in your private catalog are exclusively owned by, and for the use of, your company and any agents to whom the you provides access.
Public Catalog
Open-source components used in Crowdbotics projects are licensed under their respective open-source licenses. Link to Reusable Modules section
Modules
Can I view the Crowdbotics Public catalog?
Yes, of course.
You can also view the public catalog in the Crowdbotics GitHub.
On the Crowdbotics dashboard, click Module Catalog in the Grow your Reuse Asset card. Choose the public catalog.
Why should a write a module?
If you’re working on multiple software projects, writing a module lets you to save time and development costs by reusing module content across those projects. If you have to write a feature you know you’ll need to use again in future projects, that should probably be a module.
Where are modules stored?
Modules are stored in a GitHub repository in Public and Private catalogs.