iDateBabes
  • 💟iDateBabes Whitepaper 1.0.0
  • Introduction
    • Purpose
    • Document Conventions
    • Intended Audience and Reading Suggestions
    • Product Scope
    • References
  • Overall Description
    • Product Perspective
    • Product Functions
    • User Classes and Characteristics
    • Operating Environment
    • Design and Implementation Constraints
    • User Documentation
    • Assumptions and Dependencies
  • External Interface Requirements
    • User Interfaces
    • Hardware Interfaces
    • Software Interfaces
    • Communications Interfaces
  • System Features
    • Overview
  • Other Nonfunctional Requirements
    • Performance Requirements
    • Safety Requirements
    • Security Requirements
    • Software Quality Attributes
    • Business Rules
  • Additionally
    • Roadmap
    • Built on Ethereum
    • Conclusion
    • Disclaimer
    • FAQs
  • Appendix A: Glossary
    • Glossary
  • Appendix B: Analysis Models
    • Analysis Models
  • Appendix C: To Be Determined List
    • To Be Determined List
Powered by GitBook
On this page
  1. Introduction

Document Conventions

This whitepaper document was written in a sequential order from higher-level requirements priority, which are assumed to be inherited by detailed requirements. Here we have broken down the big problem into sub-sections to make it easier to understand and build.

The standards used for typographical conventions that were followed when writing this SRS are as follows:

  • Something important to keep in mind, or a name has been bolded.

  • Components in which the order matters, are written as an ordered (numerical) list.

  • Components in which the order doesn't matter, are written as an unordered (bullet-point) list.

PreviousPurposeNextIntended Audience and Reading Suggestions

Last updated 2 years ago