Use Cardano-native token to solve software development and usability problems

[GENERAL] Name and Surname of Main Applicant

Jay Imerman

[GENERAL] Email address of Main Applicant

jay@theparallelrevolution.com

Additional Applicants

Jay Imerman - jay@theparallelrevolution.com - over 30 years as a computing professional developing and implementing solutions for businesses of all sizes; two years as a Cardano SPO

 

Daniel Kuchciak - dan@theparallelrevolution.com - over 30 years as a computing professional developing and deploying business, database, and Web-based solutions since the Web’s inception; one year as a Cardano SPO; ADA owner since the beginning; Cryptocurrency enthusiast for 5 years; 2 years as Cardano SPO

 

Dr. Peter Trzos, MD - pete@theparallelrevolution.com - Over 10 years experience in political advocacy, canvassing, and marketing; ADA owner and Cryptocurrency enthusiast for several years

 

Alex Mazurek, Lead Cyber Security Engineer - alex@theparallelrevolution.com - Over 12 years experience in database & software development, automation across Aerospace, Banking & Retail

[GENERAL] Please specify how many months you expect your project to last (from 2-12 months)

12

[GENERAL] Please indicate if your proposal has been auto-translated into English from another language.

No

[GENERAL] Does your project have any dependencies on other organizations, technical or otherwise?

No

[GENERAL] If YES, please describe what the dependency is and why you believe it is essential for your project’s delivery. If NO, please write “No dependencies.” in this field.

No dependencies

[GENERAL] Will your project outputs be fully Open Source?

No

[GENERAL] If NO, please describe which outputs are not going to be open source. If YES, please write “Project will be fully open source.” in this field.

Back-end server apps will not be open source. All public and Cardano-integrating code is and will be open source.

[METADATA] Category of Proposal

Dev Tools, API or Library

[METADATA] SDG rating

SDG Goals:

1. Conduct research to identify Best Practices related to ICEM, and define solutions to support these -> ISO Working Groups? University research?
2. Promote sustained explosive growth in adoption of industry-recognized ICEM standards, practices and education
3. Help Software Developers focus on accuracy of error reporting, and using that to help direct quality improvement
4. Make Cryptocurrencies mainstream for everyone, and inspire other projects to integrate with Crypto
5. Make error research, and leverage of existing knowledge, easy, fast, and rewarding
6. Take User Experience with software use to the next level, with zero overhead

[IMPACT] Please describe your proposed solution.

CodaEA is a Centralized Error Management System (CEMS). It is part of an online ecosystem that enables a wholly new approach in Computer Science! That is the discipline of ICEMS, or Integrated CEMS - an Error-Centric approach to managing issues with software. For example, in the case of application server operation, it completes Operational Monitoring by providing a much-needed service and functionality that will help server operators keep an eye on issues and handle them proactively.

At The Parallel Revolution LLC, we realized that after decades of technology experience, it was time to take a stand:

No more error messages unless you also give us solutions, and let us contribute our knowledge to help others.

And CodaEA was born - the Error Centric ecosystem that enables you not only to get the description of the problem, but to get it in an understandable way, with actionable solutions, and the ability to participate in the community.

CodaEA is an Error Analysis ecosystem designed to link communities around networks (or applications) for mutual support - and around specific error codes that represent the actual issues faced as users in the Community. Network Operators typically have the job of running server software, which emit execution logs. Often, the error messages are cryptic or otherwise difficult to determine a) whether they are significant or not, and b) what you should do to fix it - especially if you are new to operating that software.

CodaEA is the solution. It provides a public REST API to report the errors, and operations for the community to analyzed and establish the appropriate meaning and severity of the error, and query those results. It facilitates discussion and troubleshooting. But more importantly, it provides visibility into the backend operations of server software - visibility to the operators for monitoring and issue alerts, and visibility to the software developers for in-field quality assessments and operational performance.

If that isn't great enough, CodaEA collects metrics on the errors that are reported. Software Developers can access those metrics, to find out what errors their customers are facing in the field. And, they can use those metrics to measure the effectiveness of their QA efforts, or maybe even to drive their QA focus to resolving specific issues that are of bigger impact.

As a Network Operator or Software Developer, you can join the CodaEA Community by creating an Account. Community Members earn reputation for their participation, and that reputation will soon be tied to the CodaCOIN Token cryptocurrency, which will be awarded to the Members' Cardano wallet by the end of every epoch.

We also propose to add Smart Contracts and Web3 integration to our Website to allow bounties to incentivize solutions using Cardano native token.

[IMPACT] How does your proposed solution address the challenge and what benefits will this bring to the Cardano ecosystem?

For Developers, this will make:

• Coding easier and more robust, helping leverage community-driven solutions to recurring coding problems
• Reduce Learning curve, helping make it easier to ramp up development skills in Cardano ecosystem

For Users, this will make software easier to use, because messages not only offer a message, but a list of solutions derived from a live community feed, and inclusion of the user in the community providing answers.

[IMPACT] How do you intend to measure the success of your project?

In the Short-Term:

●    Coverage of CodaEA in blogs, podcasts, and news articles

●    Positive Word of Mouth recommendations

●    Achieve all Phase 1/Phase 2 objectives

●    Number of accounts with Cardano wallet addresses registered

In the Long-Term:

●    Grow CodaEA and general ICEM principles to become an indispensable part of computing landscape

[IMPACT] Please describe your plans to share the outputs and results of your project?

We will have weekly posts on our Discord, including:

• Metric (KPI) stat reporting
• List of active projects
• Status of projects
• Assessment per milestones

[CAPABILITY/ FEASIBILITY] What is your capability to deliver your project with high levels of trust and accountability?

We currently have 4 full-time committed professionals with multiple decades of experience each. We have a communication system in place on social media, and software already developed and being used. We can therefore keep public announcements going, development, and interactions with other groups as it moves forward.

[CAPABILITY/ FEASIBILITY] What are the main goals for the project and how will you validate if your approach is feasible?

Our main goals are to:

1. Make all software easier to use by creating and including communities to help each other solve problems
2. Incentivize people to join cryptocurrency by incorporating a monetized incentive system
3. Aid developers in consistently applying better development practices incorporating ICEM in their user messaging

We have already validated our approach with testing on processing Cardano CNODE logs over the past year, and including other software analysis in our ecosystem. We will continue to validate feasibility based on the indicated metrics we will measure as it moves forward (see KPIs / measurements of success in other areas of this proposal).

[CAPABILITY/ FEASIBILITY] Please provide a detailed breakdown of your project’s milestones and each of the main tasks or activities to reach the milestone plus the expected timeline for the delivery.

Project Milestones

• Phase 1 Launch
• Phase 2
• Token Issuance
• Liquidity Pool Allocation
• UX Definition
• UI Definition
• Software Development
• Beta 1 Testing
• Beta 2 Testing
• Phase 2 Launch
• Public Release

Usage Milestones / KPIs

• Number of User Accounts
• Number of Developer Accounts
• Number of registered Networks/Apps
• Numbers of reported Errors per Network/App
• Numbers of solutions to Errors, Numbers of errors without solutions
• Number of bounties issued, collected, abandoned
• Number of non-bounty contributions

Public Reporting

• Weekly public reporting of metrics via Discord announcement at https://discord.gg/ecaz5C4mCv

[CAPABILITY/ FEASIBILITY] Please describe the deliverables, outputs and intended outcomes of each milestone.

Phase 1: Launch

Deliverables:

• Identification of projects involved in, where CodaEA will be used to improve
• Status reports

Outputs & Documentation:

• Public list of active projects engaging/utilizing CodaEA

Phase 2: Development Integration

Deliverables:

• KPI Metrics from projects quantifying delivered value

Outputs & Documentation:

• Updated list of projects

[RESOURCES & VALUE FOR MONEY] Please provide a detailed budget breakdown of the proposed work and resources.

Operational Costs: $50,000 (Operation of server environments, software licensing, cloud infrastructure hosting, backups)

Developers: $300,000 (Pay salaries of existing developers, Hire additional developers, Smart Contract writers, UX Experts, Graphics Experts - for 1 year)

Liquidity Pool: $150,000 to incentivize use of CodaCoin token with CodaEA, purchases and exchanges with other currencies

[RESOURCES & VALUE FOR MONEY] How does the cost of the project represent value for money for the Cardano ecosystem?

Our project represents a leap forward in software capabilities around error and message management. We will be helping developers, making it easier to develop software and ramp up skillsets. We will also help them to gather usage statistics of their code to help focus QA efforts on continuous improvement.

We also help make it easier to support and use the software, by providing instant references to the messages, and allowing all people to contribute to the knowledge base.

[IMPORTANT NOTE] The Applicant agreed to Fund10 rules and also that data in the Submission Form and other data provided by the project team during the course of the project will be publicly available.

I Accept