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
  • Admin role
  • Responsibilities and characteristics
  • Staff role
  • Responsibilities and characteristics
  • Girlfriend role
  • Responsibilities and characteristics
  • Boyfriend role
  • Responsibilities and characteristics
  1. Overall Description

User Classes and Characteristics

There will be four types of users. Each one will have different attributes, roles and permissions in the system.

Admin role

Admin is the founder of iDateBabes system. There can only be 1 admin in the system that can do everything all users can do, as well as additional administrative permissions.

Responsibilities and characteristics

  • Ability to view all content and pages at all times.

  • Ability to change (or upgrade) roles of all users.

  • Ability to edit own account information.

  • Ability to commit logical and physical ban of any user's account from the system.

    • Logical (soft) ban – preserves the user account and data related to it. Does not delete the account, but the user cannot log in anymore.

    • Physical (hard) ban – completely deletes the user account and data related to it. The user cannot log in anymore nor restore their account.

Staff role

Staff team is an essential part of iDateBabes. There can be multiple staff in the system, each one dedicated to monitoring different part of the system, or the same part concurrently.

Responsibilities and characteristics

  • User moderation of the content being posted on the website and mobile app.

  • Approvals of the Girlfriend role application.

  • Giving the accounts a strike as a form of punishment for breaking terms of service. Three strikes will get the account temporarily suspended for X period of time. When this happens the reports automatically get forwarded to administrator who decides what will further happen to that account.

Girlfriend role

Girlfriend is the content creator (seller) in the system. There can be multiple girlfriends in the system.

Responsibilities and characteristics

  • Create content by posting pictures, videos or text in timeline of their profile.

  • Reply as fast as possible to her boyfriend's text messages and chat with her boyfriend whenever he wants to.

Boyfriend role

Boyfriend is the buyer within the system. There can be multiple boyfriends registered in the system.

Responsibilities and characteristics

  • Browse and choose the girl they want to be in a relationship with.

  • Pay for her subscription, as in form of "renting" to be his girlfriend.

  • Request whatever he wants from his girlfriend, as long as it's a mutual agreement.

  • Give "allowance money" as in form of tips to his girlfriend.

  • Upgrade relationship status to "engaged" or "wife" package, that gives the boyfriend extra benefits defined by the girl.

PreviousProduct FunctionsNextOperating Environment

Last updated 2 years ago