SecurEth Guidelines
PlanningDevelopmentAuditRelease
Search…
v0.2.1
Introduction
Getting Started
Examples
Project Planning
System Description
Development Plan
Architecture
Preliminary Audit
Development
Software Requirements
Testing
Traceability
Managing Changes
Peer Reviews
Security Audit
Preparing for an Audit
Audit Prep Report
Test Results
Audit Revisions
Final Report
Network Release
Maintaining Your Project
Deployment Plan
Mitigation Plan
Incident Response
Tools
Tools for Secure Design
Creating Tools
Qualifying Tools
Tool Reports
Existing Tools
Access Controls
Access Controls Section
Contributing
Guideline Revision Process
Powered By GitBook
Development Plan
A Development Plan says from a development perspective, how you are going to develop, test, audit and deploy your smart contracts. It is a very top level document that shows you have thought through the whole development process.

Why do a Development Plan?

The Development Plan says what you want to do before you do it. You can present this plan with the System Description to an auditor or for a Preliminary Audit. The idea is to get critical feedback before the main work begins..

What is included in a Development Plan?

  1. 1.
    Describe the team and their expertise
  2. 2.
    Define the language (Solidity/Viper/Flint etc.), libraries, tools
  3. 3.
    How will you structure the contracts?
  4. 4.
    How much on chain, how much off?
  5. 5.
    What is your test plan?
  6. 6.
    How long do you expect the development to last?
  7. 7.
    Deployment Phases (Truffle, Rinkeby, MainNet Beta, Final MainNet Release)
  8. 8.
    Audit Phases (How many audits and in when?)

Examples

Check here for a description of the examples used below.

Got a comment? Check out our Gitter Channel!
Copyright and related rights waived via CC0​
​
Project Planning - Previous
System Description
Next - Project Planning
Architecture
Last modified 3yr ago
Copy link
Contents
Why do a Development Plan?
What is included in a Development Plan?
Examples