Prototype management system
A prototype management system to provide cross team tools, frameworks, prototype management, and prototype tracking capabilities to improve the overall timeliness and quality of application and web-based product development. In an example, the prototype management system may be configured to cause the prototype to act as a live website that may be accessed by each of the teams and causes each team member to develop operable objects opposed to simulated objects.
1. A prototype management engine comprising:
a communication interface;
one or more processors; and
one or more non-transitory computer-readable storage media storing computer-executable instructions, which when executed by one or more processors, cause the one or more processors to:
receive a request to access a prototype software system from a user device, the prototype software system used to develop software prototypes prior to placing them in service;
determine that the prototype software system is available;
launch the prototype software system as a local prototype in a sandbox environment that is separate from other users;
cause the sandbox environment to use sandbox data to stress test the prototype software system to determine that the prototype software system is capable of at least meeting end user demand thresholds;
cause the local prototype to open in a browser associated with the user device, the local prototype comprising software instructions that are incorporated into at least one of:
a software object associated with a website or application;
a software module associated with a website or application;
a software-implemented feature associated with a website or application;
a software-implemented website; or
a software application;
cause a text editor to open in conjunction with the browser, the text editor to allow software instructions of the local prototype to be modified;
transfer data associated with a plurality of design libraries between a designs library database and the user device, individual ones of the design libraries usable to generate a module associated with the local prototype;
transfer data associated with a plurality of frameworks between a frameworks database and the user device, individual ones of the design libraries usable to edit the local prototype;
store the local prototype as a current version of the local prototype;
provide a dashboard to be displayed on the user device, wherein the dashboard comprises:
a dashboard section comprising:
a first module to allow a user to create a new software prototype;
a second module to allow a user to download data for an existing software prototype; and
a third module to allow a user to browse and select from a plurality of libraries and frameworks; and
a notification section comprising:
a set of accessed software prototypes;
a set of published software prototypes;
a set of new prototypes added to the prototype management engine; and
a set of new design libraries added to the prototype management engine;
receive, by the dashboard, update information associated with the prototype software system, the plurality of design libraries, and the plurality of frameworks;
determine that a second prototype has been modified by second user device to create a modified prototype;
send tracking information associated with the modified prototype to a tracking engine; and
send, by the tracking engine, a notification to the user device indicating that the second prototype has been modified.
2. The prototype management engine as recited in claim 1 , wherein the computer-executable instructions, when executed by the one or more processors, further cause the one or more processors to:
receive, a notification related to a new design library via the communication interface; and
cause the communication interface to send a notification related to the new design library to the user device.
3. The prototype management engine as recited in claim 1 , wherein the computer-executable instructions, when executed by the one or more processors, further cause the one or more processors to:
receive, a notification related to a new framework via the communication interface; and
cause the communication interface to send a notification related to the new framework to the user device.
4. The prototype management engine as recited in claim 1 , wherein the computer-executable instructions, when executed by the one or more processors, further cause the one or more processors to:
receive, a publication request from the user device; and
cause the current version of the local prototype to publish to a server.
5. The prototype management engine as recited in claim 4 , wherein the server is at least one of an internally accessible server or an external accessible server, and wherein each of the designs libraries operates a functioning module when rendered in the browser.
6. The prototype management engine as recited in claim 1 , wherein the computer-executable instructions, when executed by the one or more processors, further cause the one or more processors to:
send tracking data to a tracking engine; and
receive tracking commands that include instructions to store the local prototype as the current version.
7. The prototype management engine as recited in claim 1 , wherein the sandbox data includes web-crawler data and survey data, and wherein stress testing the prototype software system includes stress testing the sandbox environment.
8. A system comprising:
one or more processors;
one or more non-transitory computer-readable storage media to store instructions that are executable by the one or more processors, the instructions comprising:
a prototype management engine to manage development of a prototype comprising software instructions used to create a prototype website;
a design library database to store a plurality of design libraries and frameworks accessible to a local device via a browser, each of the plurality of design libraries and frameworks operable as a function object within the browser;
a sandbox to host a local version of the prototype website associated with the local device, the sandbox using sandbox data to stress test the system to determine that the prototype management engine is capable of at least meeting end user demand thresholds;
a publication server to:
host a published version of the prototype website; and
publish, based on receiving a publish command, the prototype website to at least one of an internal server, an external server, a code management server, a development server, or a production server;
a tracking engine to:
manage version control of the prototype website;
manage the published version of the prototype website;
update version information associated the prototype website;
determine that the prototype website has been modified; and
send a notification to the local device indicating that the prototype website has been modified; and
a dashboard, wherein the dashboard comprises:
a dashboard section comprising:
a first module to allow a user to create a new software prototype;
a second module to allow a user to download data for an existing software prototype; and
a third module to allow a user to browse and select from a plurality of libraries and frameworks; and
a notification section comprising:
a set of accessed software prototypes;
a set of published software prototypes;
a set of new prototypes added to the system; and
a set of new design libraries added to the system.
9. The system as recited in claim 8 , wherein the sandbox data includes web-crawler data, wherein the sandbox hosts a second local version of the prototype website that is accessible to a second local device and inaccessible to other local devices, and wherein stress testing the system includes stress testing the sandbox.
10. The system as recited in claim 8 , wherein the dashboard allows a user to receive update information associated with the prototype website and the plurality of design libraries and frameworks.
11. The system as recited in claim 8 , wherein the prototype management engine provides a prototype page to the local device, the prototype page to allow a user to open the prototype website within the browser.
12. A non-transitory computer-readable storage media storing instructions, that when executed by one or more processors, cause the one or more processors to:
receive a request to access a prototype from a user device, the prototype hosted by a prototype software system used to develop software prototypes;
launch the prototype as a local prototype in a sandbox environment;
cause the sandbox environment to use sandbox data to stress test the prototype software system to determine that the prototype software system is capable of at least meeting end user demand thresholds;
cause the local prototype to open in a browser associated with the user device, the local prototype comprising software instructions that are incorporated into at least one of:
a software object associated with a website or application;
a software module associated with a website or application;
a software-implemented feature associated with a website or application;
a software-implemented website; or
a software application;
cause a text editor to open in conjunction with the browser, the text editor to allow software instructions of the local prototype to be modified;
transfer data associated with a plurality of design libraries between a designs library database the user device, individual ones of the design libraries usable to generate a module associated with the local prototype;
transfer data associated with a plurality of frameworks between a frameworks database and the user device, individual ones of the design libraries usable to edit the local prototype;
store the local prototype as a current version of the prototype to create a current prototype;
provide a dashboard to be displayed on the user device, the dashboard to receive update information associated with the prototype software system, the plurality of design libraries, and the plurality of frameworks, wherein the dashboard comprises:
a dashboard section comprising:
a first module to allow a user to create a new software prototype;
a second module to allow a user to download data for an existing software prototype; and
a third module to allow a user to browse and select from a plurality of libraries and frameworks; and
a notification section comprising:
a set of accessed software prototypes;
a set of published software prototypes;
a set of new prototypes added to the prototype software system; and
a set of new design libraries added to the prototype software system;
determine that the current prototype has been modified to create a modified prototype; and
send a notification of the modified prototype to the user device.
13. The non-transitory computer-readable storage media as recited in claim 12 , wherein the instructions, when executed by the one or more processors, further cause the processors to:
receive, tracking data from a tracking engine indicating the prototype is unlocked and available for editing.
14. The non-transitory computer-readable storage media as recited in claim 12 , wherein the instructions, when executed by the one or more processors, further cause the processors to:
receive, a publication request from the user device; and
cause the current version of the prototype to publish to a server.
15. The non-transitory computer-readable storage media as recited in claim 12 , wherein the instructions, when executed by the one or more processors, further cause the processors to:
send tracking data to a tracking engine; and
receive tracking commands that include instructions to store a local version as a current version.
16. The non-transitory computer-readable storage media as recited in claim 12 , wherein the instructions, when executed by the one or more processors, further cause the processors to:
receive, a notification related to a new framework via a communication interface; and
cause the communication interface to send a notification related to the new framework to the user device.
17. The non-transitory computer-readable storage media as recited in claim 12 , wherein the instructions, when executed by the one or more processors, further cause the processors to:
receive, a notification related to a new design library via a communication interface; and
cause the communication interface to send a notification related to the new design library to the user device.
18. The non-transitory computer-readable storage media as recited in claim 12 , wherein each of the plurality of frameworks operates a functioning code when rendered in the browser.
19. The non-transitory computer-readable storage media as recited in claim 12 , wherein each of the designs libraries operates a functioning module when rendered in the browser.
20. The prototype management engine as recited in claim 4 , wherein the sandbox data includes corpus data, web crawler data, test data, training data, and sample use cases, and wherein stress testing the prototype software system includes stress testing the server.
21. The prototype management engine as recited in claim 1 , wherein the computer-executable instructions, when executed by the one or more processors, further cause the one or more processors to:
cause the sandbox data, after the stress test, to be tracked by the user device so that the user device is able to remove bugs associated with the local prototype.