Requirements

Let's craft a system resembling Google Forms or SurveyMonkey. Imagine a scenario where users can create surveys composed of various question types (e.g., multiple choice, text input, rating scales). Other users can then respond to these surveys. The system must be robust, extensible, and handle concurrent access gracefully. We need to think about how new question types can be easily added, and how responses can be efficiently stored and retrieved. Consider the need to potentially add reporting features later. The focus is on the core domain model and object-oriented design, not building a full-fledged web application. # Requirements ## Functional Requirements * **Survey Creation:** * A user should be able to create a new survey. * A user should be able to add questions to a survey. * Support the following question types: * Multiple Choice (single selection) * Text Input (short answer) * Rating Scale (e.g., 1-5 stars) * Checkbox (multiple selections) * Date * A user should be able to specify whether a question is mandatory. * A user should be able to reorder questions within a survey. * A user should be able to delete questions from a survey. * A user should be able to set the title and description of a survey. * **Survey Taking (Response Submission):** * A user should be able to answer a survey. * The system should validate that mandatory questions are answered before submission. * The system should store the responses associated with a survey. * The system should be able to retrieve all responses for a given survey. * **Survey Management:** * A user should be able to view a list of surveys they have created. * A user should be able to retrieve a specific survey and its questions. * A user should be able to close a survey to prevent further responses. * **Question Management:** * Each Question should have a unique identifier. * Each Question should have a type (e.g., Multiple Choice, Text Input). * Each Question should have text. * Each Question can have optional help text. * Each Question can be marked as mandatory. * Question types may have question-type-specific configurations (e.g., multiple choice options). ## Non-Functional Requirements * **Extensibility:** The system should be designed to easily support new question types without requiring significant code changes. We will evaluate how easily a new question type like "File Upload" could be added. * **Modularity:** The system should be composed of loosely coupled modules, each responsible for a specific aspect of the survey creation or response process. * **Testability:** The code should be written in a way that makes it easy to write unit tests for individual components. This includes using interfaces to abstract dependencies. * **Thread Safety:** The system should handle concurrent requests from multiple users without data corruption or unexpected behavior. Pay attention to how survey creation and response submission are handled concurrently. Focus on data structures and synchronization. * **Maintainability:** The code should be well-structured and easy to understand, following SOLID principles to reduce technical debt. * **Object-Oriented Design:** The solution should demonstrate strong object-oriented principles, including encapsulation, abstraction, inheritance (where appropriate), and polymorphism. ## Core Entities * **Survey:** Represents a survey, containing metadata like title, description, creation date, and a list of questions. * **Question:** An abstract class or interface representing a question in the survey. It should have common properties like question text, mandatory flag, and potentially help text. * **QuestionType:** An enum or class hierarchy representing the different types of questions (e.g., MultipleChoice, TextInput). This is closely tied to the chosen design pattern for extensibility (likely Strategy or Factory). * **MultipleChoiceQuestion:** A concrete Question type that allows the user to select one option from a list of predefined options. * **TextInputQuestion:** A concrete Question type that allows the user to enter free-form text. * **RatingScaleQuestion:** A concrete Question type that allows the user to select a rating from a predefined scale (e.g., 1-5). * **CheckboxQuestion:** A concrete Question type that allows the user to select one or more options from a list of predefined options. * **Response:** Represents a user's answer to a specific question in a survey. * **SurveyResponse:** Represents a complete set of responses for a single survey. * **User:** Represents a user of the system, either creating or responding to surveys. Can be simplified for this exercise.

Design Survey similar to Google Forms / SurveyMonkey.

Requirements

Interview Simulation

Functional Requirements

💡 Interview Tip

Non-Functional Requirements

Core Entity Identification

Premium Content