Application Design – Use Cases and Database Access Scenarios – SQL Views

Actors

Admin

• Can moderate content for appropriateness
• Has a read-write permisions to the whole system
• Can add or remove existing users
• Can view platform analytics and user activity
• Can manage and resolve reported content

Writer

• Has a read-write permissions to own content
• Can add new stories and chapters, edit own stories and chapters
• Has own reading list
• Can collaborate with other writers through a permission-based system
• Can view analytics on their stories
• Can receive and accept/reject AI-generated writing suggestions
• Can set stories as draft, published, or archived
• Can manage mature content settings on their stories

Regular User

• Has a read-only permision of all stories and chapters
• Can leave comments and likes to the stories
• Can add stories to their reading list
• Can report inappropriate stories or comments

Guest User (Unauthenticated User)

• Has a read-only permision of all public stories and chapters
• Browse by categories or other filters
• Cannot manage data in the system before registration or login

Scenarios

WriterRegistration
RegularUserRegistration
ExistingAdmin
WrittersCollaboration
RegularUserLikesStory
RegularUserCommentsOnStory
UserCreatesReadingList
UserRemovesStoryFromReadingList
WriterViewsStoryCollaborationDetails
UserViewsPublicReadingLists
UserBrowsesStoriesByGenre
UserViewsStoryDetailsAndChapters
UserReadsAChapter
WriterEditsAnExistingChapter
WriterArchivesAStory
AdminRemovesAStory

Most Important Scenarios

WriterRegistration
WriterCreatesStory
WriterPublishesStory
WriterAddsChapterToStory
WriterReceivesAISuggestions
UserAddsStoryToReadingList
AdminManagesGenres