Requirements

Imagine you're building a platform inspired by Terribly Tiny Tales (TTT), where users can create and share very short stories (text and optionally images). This isn't just about storing strings; we need a robust and extensible system that allows for various story formats, content moderation, user interaction, and potentially even monetization in the future. We want to simulate the creation, display and management of short stories with optional images, focusing on the core domain and how it translates to clean, maintainable code. # Requirements ## Functional Requirements 1. **Story Creation:** * Users should be able to create a story with a title and content (text). * Users should be able to optionally add an image to the story. * The system must enforce a maximum character limit for the story content (e.g., 280 characters, similar to Twitter). * The system must support different content types beyond plain text later on (e.g., Markdown). * Each story must be associated with an author (user). * Stories should have a unique ID. * The system should store the creation timestamp of each story. 2. **Story Retrieval:** * Users should be able to retrieve a story by its ID. * Users should be able to retrieve all stories created by a specific author. * The system must efficiently support retrieving stories sorted by creation date (newest first, oldest first). * Implement pagination for story retrieval (e.g., retrieve 10 stories at a time). 3. **User Management (Simplified):** * Assume a simplified user model with only a user ID and a username. * The system should be able to create and retrieve user objects. (Basic CRUD operations) 4. **Content Moderation:** * Implement a basic content moderation system. * Stories can be flagged as inappropriate by other users. * Moderators can review flagged stories and either approve or reject them. * Rejected stories are not visible to regular users. * Implement a strategy for flagging stories that could be extended in future for sentiment analysis. 5. **Image Handling (Simplified):** * Assume images are stored as URLs (no actual image processing or storage is required for this problem). * The system needs to validate that the provided URL is a valid image URL (basic format check). ## Non-Functional Requirements 1. **Extensibility:** * The system should be designed to easily support new content types (e.g., Markdown, video snippets) without requiring major code changes. * The content moderation system should be easily extensible to support different moderation rules and automated content analysis. * The storage mechanism for stories and users should be easily replaceable (e.g., in-memory, file-based, database). 2. **Modularity:** * The system should be divided into well-defined modules with clear responsibilities. * Dependencies between modules should be minimized. 3. **Testability:** * The code should be designed to be easily testable using unit tests and integration tests. 4. **Thread Safety:** * If the in-memory data structures are accessed concurrently (e.g., by multiple threads simulating user requests), the code must be thread-safe. Consider scenarios where multiple users are creating stories or flagging stories simultaneously. 5. **SOLID Principles:** * The code should adhere to the SOLID principles of object-oriented design. ## Core Entities 1. **Story:** Represents a short story with a title, content, author, optional image URL, creation timestamp, and moderation status. 2. **User:** Represents a user with a user ID and username. 3. **Content:** An abstraction for different content types (TextContent, ImageContent, etc.). The Story will aggregate this. 4. **Author:** The user that creates the story. 5. **Moderation:** Represents the moderation status of a story (approved, rejected, flagged). 6. **ModerationService:** An interface/class responsible for handling content moderation, including flagging, reviewing, and approving/rejecting stories. 7. **ContentValidator**: Interface for validating if a content item is valid. 8. **StoryService:** Interface/Class responsible for story creation, retrieval, and management. 9. **UserService:** Interface/Class responsible for user creation, retrieval, and management.

Design Short Story Telling (Text/Images) platform like Terribly Tiny Tales.

Requirements

Interview Simulation

Functional Requirements

💡 Interview Tip

Non-Functional Requirements

Core Entity Identification

Premium Content