REQUIREMENT AND

ANALYSIS
Project Name: My Unique Story
Client: Mr. Lee Mallon

ICT302- IT PROFESSIONAL PRACTICE PROJECT

Supervisor
Ms. Noor Alkhateeb
Team
Lucid Inc.
Team Members
Abdul Rahman El Sayed
Bhavin Desai
Samra Ahmed
Ashraf Ben El Haj
Kevin Richard Correya
Document Date
14 February, 2024
Document Version
1
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

Table of Contents
1. Executive summary .................................................................................................................................................. 3
2. Introduction .............................................................................................................................................................. 4
2.1. Project Purpose ............................................................................................................................................... 4
2.2. Client Organization Background................................................................................................................... 4
2.3. Problems and Opportunities .......................................................................................................................... 4
2.3.1. Problems ...................................................................................................................................................... 4
2.3.2. Opportunities .............................................................................................................................................. 5
2.4. Goals and Objectives ...................................................................................................................................... 5
2.4.1. Goals ............................................................................................................................................................ 5
2.4.2. Objectives .................................................................................................................................................... 5
2.5. Methodology .................................................................................................................................................... 6
3. Outline of the solution proposed to solve the problem(s) ...................................................................................... 7
3.1. Scope ................................................................................................................................................................ 7
3.2. Proposed Solution ........................................................................................................................................... 8
3.2.1. Front-End Development: ........................................................................................................................... 8
3.2.2. User Interface Design and User Experience: ............................................................................................ 8
3.2.3. Back-End Processing: ................................................................................................................................. 8
3.2.4. Content Generation and Compilation: ..................................................................................................... 8
3.2.5. User Experience and Output: .................................................................................................................... 9
3.3. Content Enhancement .................................................................................................................................... 9
3.4. Scalability and Future Enhancements........................................................................................................... 9
4. Functional Requirements ........................................................................................................................................10
4.1. Mandatory Functional Requirements (MFR) .............................................................................................10
4.2. Optional Functional Requirements (OFR) ..................................................................................................15
5. Non-functional Requirements ................................................................................................................................17
5.1. Mandatory Non-Functional Requirements (MNFR) ..................................................................................17
5.2. Optional Non-Functional Requirements (ONFR) .......................................................................................20
6. Diagrammatic representation of the requirements ..............................................................................................23
6.1. Use Case Diagram ..........................................................................................................................................23
6.2. System Architecture Diagram .......................................................................................................................27
6.3. Component Diagram......................................................................................................................................28
6.4. Sequence Diagram .........................................................................................................................................30
6.5. Activity Diagram ............................................................................................................................................32
6.6. Dataflow Diagram ..........................................................................................................................................34

1
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

7. Conclusion ................................................................................................................................................................36
8. Appendices ...............................................................................................................................................................37
Appendix A - Deliverable Task Breakdown Statement............................................................................................37
Appendix B - Copies of client documents ..................................................................................................................38
Appendix C – Glossary ...............................................................................................................................................43

2
 Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

1. Executive summary
This document presents the requirements analysis for Lucid Inc.'s "My Unique Story" project, being
initiated for the client Mr. Lee Mallon. The goal is to develop an AI-powered platform that
generates hyper-personalized children's storybooks tailored to each child's preferences and
developmental needs.
The proposed solution (Section 3) will leverage cutting-edge generative AI models to create unique
stories and illustrations adapted to inputs like age, language, genre, artwork style etc. The text and
images will be compiled into interactive paginated HTML storybooks for an engaging reading
experience.
The functional requirements (Section 4) outline core features ranging from user registration,
intuitive interfaces for inputting personalization parameters, robust back-end logic to integrate AI,
stringent content moderation mechanisms and basic accessibility options. Non-functional
requirements (Section 5) define system attributes such as high performance, reliability, security,
usability, and maintainability along with scalability to support increasing users.
Additionally, non-mandatory requirements are also analyzed including advanced accessibility,
multilingual support, cross-platform compatibility, external services integration, and offline access
with regular data backups.
A multidimensional understanding of the platform is enabled through detailed behavior models
(Section 6), with diagrams depicting use cases, system architecture, components, sequences, data
flows and interactions.
In summary, this report provides a comprehensive blueprint for the development of a pioneering
personalized children’s reading platform powered by artificial intelligence to transform literacy
experiences for young audiences globally. The vision is brought to life through a methodical
analysis of strategic and technical requirements mapped to the solution outline.

3
 Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

2. Introduction
2.1. Project Purpose
In the evolving landscape of children’s literature, the integration of Artificial Intelligence (AI)
presents an opportunity to redesign how stories are created and hyper-personalized. ‘My Unique
Story’ is an ambitious project aimed at harnessing AI’s potential to craft personalized stories for
children’s books. This initiative seeks to merge technology with creativity offering unique tailor-
made reading experiences that cater to individual preferences and developmental needs of young
readers across the globe.

2.2. Client Organization Background

Our client, led by Mr. Mallon, is a forward-thinking technologist deeply invested in the exploration
and practical application of AI across various domains. Through his work, including the voice
preservation project voiceOK and the imaginative MRLEE hotel collection, he delves into the human-
AI interaction, emphasizing technology's role in enhancing creativity and human connection. His
insightful blogs critique the hype around AI, urging for a balanced understanding and integration of
AI in business and everyday life. Mallon champions AI's potential to transform industries, advocating
for enterprises to embrace and adapt to AI's evolving landscape.

2.3. Problems and Opportunities

2.3.1. Problems
• Generic Children’s Content – The looming/prevailing lack or shortage of truly
personalized content highlights a critical issue of something that is not currently present
in the market heavily where in generic stories fall to resonate with individual preferences.
• Accessibility Gaps – Children with diverse needs would encounter challenges in
accessing suitable content, as existing solutions do not address the varied accessibility
requirements. This issue could be faced by adults i.e., parents even when accessing the
system. For Example – Taking raw CSV files and dropping it in ChatGPT and messing
around with prompts; and exporting images and copying them to Canva – which is all too
many steps.
• Ethical Concerns – As AI generated content becomes prevalent and ever growing
recently there comes a need to address ethical concerns related to age-appropriate content
and system accountability.
• AI Content Bias/Algorithmic Bias – The AI Algorithms may unintentionally incorporate
biases, thereby impacting the content generation. While generating stories especially for
children between the ages of 6-10, it should be kept in mind that they are at the age of
growing up both mentally and physically quickly and it's the age of learning things

4
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

quickly, so striving for fairness and inclusivity is crucial to avoid perpetuating stereotypes
or unintentionally favoring certain demographics.
2.3.2. Opportunities
• Innovation in Children’s literature - The project will provide an opportunity to
innovate and redefine the landscape of children's literature by introducing AI-driven
hyper-personalization of curating stories.
• Inclusivity – Addressing accessibility needs would help in ensuring that the tool or
system is inclusive, catering to a wide range of children and even adults i.e., parents
accessing the content for children, including those with visual impairments or language
learning difficulties.
• Market Competition – By combining and blending the advanced AI capabilities with a
specific focus on curating quality stories or storytelling, the client organization will
garner the potential to establish itself as a leader in the personalized children’s content
market.
• Collaboration with Educational Institutions – Partnering with schools and institutions
can provide a platform to integrate the tool or system into a formal educational setting,
expanding its reach and overall impact.

2.4. Goals and Objectives

2.4.1. Goals
• Development of AI-Powered Tool: Create a robust AI algorithm capable of generating
hyper-personalized children's books based on user-input data.
• User-Friendly Interface: Design an intuitive UI that facilitates easy input of
personalization parameters for parents, guardians, or educators.
• Multilingual Support: Developing the tool to generate stories/books in multiple
languages based on the option chosen by the user, enhancing its global appeal.
• Accessibility: Implement features such language options, text to speech for visually
impaired readers to ensure the tool caters to diverse accessibility needs
• User Testing and Feedback: Conduct comprehensive user testing sessions with a diverse
group of children and caregivers i.e., parents to gather feedback and make necessary
adjustments.
2.4.2. Objectives
• Integrating with external AI for Story Generation: Integrating external AI for creating
and curating stories based on the user’s preferences and input.
• Integrating with external AI for Image Generation: Integrating external AI for creating
visually compelling images that complement the generated stories.
• Quality Assurance: Ensure that the generated stories align with the client's emphasis on
quality, embodying age-appropriate, culturally sensitive narratives.

5
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

• Front-end: Develop a front-end system that would help in account management i.e.,
saving account details and managing them, preferences, language preferences,
• Backend Dashboard and Security Features: Develop a robust backend system with
features such as user login, logout, integrating with external AI APIs.
• Ethical Security Measures: Prioritize ethical security by implementing backend
diagnostics to monitor user activities and promptly address any concerns or complaints.

2.5. Methodology
To create a comprehensive methodology for Lucid Inc.'s "My Unique Story" project, combining
both project and development methodologies, we consider the following approach:
Agile methodology is an approach to software development and project management that prioritizes
adaptability, client involvement, and rapid delivery of value via iterative work cycles known as
iterations. It encourages flexible and responsive response to changes by supporting early delivery,
progressive growth, adaptive planning, and continuous improvement. Cross-functional teams
working closely together on different project components are a feature of the agile methodology.
Regular thoughts on how to improve efficiency led to process adaptation and evolution over time.
• Initiation and Planning - The first step is to outline the goals, potential risks, and extent of
employing AI to create tailored children's storybooks. Project managers, AI developers,
secretary, security coordinators, communications officer and user experience designers
should all be on the cross-functional team.
• Iterative Development - Using an Agile approach to create, test, and improve features in
iterative cycles. Iterative inspections and regular stand-ups provide alignment and flexibility
in the face of change.
• AI Model Development: Create and develop AI models for generating images and stories.
Utilize machine learning algorithms to customize according to user preferences and inputs.
• Security and Privacy: Implement best practices for data security and privacy into practice.
These include secure APIs, encryption, and adherence to data protection laws.
This approach builds a strong foundation for the project's success and future expansion by merging
the efficiency and automation of a agile development approach with the flexibility and stakeholder
engagement of Agile project management.

6
 Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

3. Outline of the solution proposed to solve the problem(s)

The objective of "My Unique Story: Crafting Personalised Tales for Every Child" is to leverage
generative artificial intelligence to create hyper-personalized children's books that cater to the
individual preferences and needs of young readers aged between 6 to 10 years old. The proposed
solution encompasses a multi-faceted approach to address the challenges of personalization,
accessibility, and engagement in children's literature. Below is a detailed outline of the proposed
solution.

3.1. Scope
The project, "My Unique Story: Crafting Personalized Tales for Every Child," encompasses the
development and deployment of a comprehensive system for generating hyper-personalized
children's books. This system will leverage AI technologies for content creation and offer an
interactive platform for users (parents, guardians, or educators) to customize storybooks according
to specific preferences and needs. The scope of this project includes several key components and
delineates the responsibilities of the development team as follows:
Within Scope:

UI/UX Design: Comprehensive UI/UX design and implementation efforts will be undertaken to
ensure intuitive, engaging, and accessible interfaces for both end-users (creators) and
administrators, enhancing the overall experience of creating and managing personalized storybooks.
Front-End Development: Development and implementation of two distinct interfaces: one for the
end-users (creators) to input personalization parameters and view/download their personalized
storybooks, and another for administrators for user management and content moderation.
Back-End Algorithm Development: Development of algorithms that process user inputs, manage
the integration with AI APIs for story and image generation, and compile the outputs into a
cohesive, paginated storybook format as an HTML file with pagination, features.
API Integration: Establishing and maintaining connections with external AI services (eg. OpenAI,
Gemini Pro, Dall-E, Stable Diffusion, etc.) for text and image generation, ensuring reliable and
efficient content creation.
Compilation and Delivery: Development of algorithms to compile text and images into a
storybook format (HTML), making it available for users to view or download from their dashboard.
Storage Solution: Implementing a storage solution for saving the generated storybooks and their
associated images, ensuring data persistence and easy retrieval.
Database Management: Developing a database system to track user inputs, generated content, and
user interactions, including flagging content for review.
Content Flagging: Providing users with the ability to flag content as inappropriate, triggering a
review process by the administrative team.
7
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

3.2. Proposed Solution

3.2.1. Front-End Development:
User Input Interface: Design a user-friendly interface where users (children, parents,
guardians, or educators) can input personalization parameters. This interface will include
fields for child age, story genre (e.g., adventure, fantasy), preferred artwork style (e.g.,
cartoonish, realistic), story prompts (to guide the storyline), and language selection.
Account Management: Implement a secure system for users to create and manage their
accounts, enabling them to save their preferences, view their history of created stories,
and access their personalized books.
3.2.2. User Interface Design and User Experience:
Design Philosophy: The design will embody a playful, colourful, and engaging aesthetic
that appeals directly to children in the 6 to 10 age group. It will incorporate elements that
are familiar and enjoyable to the demographic, such as bright colours, large buttons,
simple shapes, and interactive elements that provide immediate feedback.
User Experience Considerations: Special attention will be paid to making the interface
intuitive and engaging for users, children and/or adults, while ensuring that visual
elements can captivate children's interest. This may include interactive previews of the
storybooks, and visual cues that help guide the creation process.
Consistency and Branding: Across both interfaces, the design will maintain
consistency in terms of color schemes, typography, and layout principles, aligning with
the project's branding and thematic elements. This consistency reinforces the platform's
identity and enhances user trust and engagement.
3.2.3. Back-End Processing:
Input Processing: The back-end system will parse the inputs received from the front
end and prepare a structured prompt for the AI story generation algorithm.
Security Measures: Ensure the system incorporates robust security protocols to protect
user data and privacy, adhering to international standards and regulations.
3.2.4. Content Generation and Compilation:
Story Generation: The structured prompt is sent to the text-generative AI, which crafts
a unique story based on the specified parameters. The AI utilizes natural language
processing (NLP) techniques to ensure the story is coherent, engaging, and age
appropriate.
Image Generation: Alongside the story, the AI generates image prompts related to key
moments or elements in the narrative. These prompts are then sent to an image-
generative AI, which produces illustrations consistent with the requested artwork style.

8
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

Compilation into a ‘Story Book’: The generated story text and corresponding images
are compiled into an HTML page, structured to mimic the layout of a physical book.
This process involves paginating the content and matching text with relevant
illustrations.
3.2.5. User Experience and Output:
Dynamic Story List Update: Once the personalized book is compiled, it is
automatically added to the user's "view story list" on the front end. This ensures that
users can immediately access new content.
Interactive Book Viewing: Users can open their personalized book through the front
end, browsing through pages to read the story and view illustrations, enhancing the
reading experience with an interactive, digital book format. The user will also be able to
download the book in a pdf format, for offline access.

3.3. Content Enhancement

Moderation and Quality Control: Implement a dual system of automated filters (eg.
Profanity filter to validate input before parsing) and manual review to monitor and maintain
the appropriateness and quality of the generated content i.e. users can flag if any content of
the book is found to be inappropriate.

3.4. Scalability and Future Enhancements

Cloud-Based Architecture: Utilize cloud computing solutions to ensure the infrastructure
is scalable, supporting an increasing load of simultaneous story generations and user
interactions without degradation in performance.
Continuous Improvement: Plan for iterative enhancements, including the finetuning and/or
training of the AI models for text and image generation, expanding language options, and
incorporating new features based on user feedback and technological advancements.
This detailed approach ensures that the solution not only meets the immediate goals of
creating personalized children's books but also establishes a framework for future growth,
innovation, and user satisfaction.

9
 Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

4. Functional Requirements
The following list presents a detailed breakdown of the functional requirements essential for the
system's operation. These requirements are organized into two distinct categories: Mandatory,
which are essential for the system's basic functionality and cannot be compromised, and Optional,
which are desirable features that enhance system performance and user experience but are not
critical for the system's core operations. This approach ensures a clear understanding of the system's
necessities and additional features that could provide added value.

4.1. Mandatory Functional Requirements (MFR)

MFR-01 Name of Requirement: Register and Authenticate Users

Criticality: High I/O: User input for registration; System output as user profile
creation and login confirmation.
Priority: 6/10

Description: The system must provide a secure registration form for new users and a login
mechanism for returning users. It should feature encryption for password storage and verification
processes to prevent unauthorized access.
Dependencies: Secure authentication service/library and user database integration
Cost: None
Schedule: 2 days
Technical Issues: Ensuring compatibility between our database and the secure authentication
service/library.

10
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

MFR-02 Name of Requirement: Provide Story Creation Interface

Criticality: High I/O: User input for story criteria

Priority: 8/10
Description: An interface must be provided for users to select age, language, genre, artwork
style, and input a story prompt.

Dependencies: N/A
Cost: None
Schedule: 1 day
Technical Issues: NONE

MFR-03 Name of Requirement: Process and Validate Inputs

Criticality: High I/O: User inputs; System output as validated parameters for story
generation
Priority: 8/10
Description: The system must accurately process and validate user inputs, ensuring they are in
the correct format for the AI algorithms to interpret and use for story generation. The system also
should run the text input (story prompt) against a profanity filter. It should prompt users to
correct any invalid or incomplete inputs.
Dependencies: Robust backend validation logic; Profanity filter dictionary/list/library. MFR-02
Cost: None
Schedule: 1 day
Technical Issues: Options to be selected should be limited to drop downs, excluding the NLP
prompt.

11
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

MFR-04 Name of Requirement: Generate Stories via AI

Criticality: High I/O: Structured data from user inputs; System output as a
complete, unique story
Priority: 10/10
Description: The AI must generate a story based on structured input, crafting a narrative that is
coherent and engaging. The story should reflect the user's preferences and input while
maintaining age-appropriate content.
Dependencies: Generative AI’s APIs.
Cost: High
Schedule: 2 days
Technical Issues: Aligning the AI output with user expectations

MFR-05 Name of Requirement: Generate Images via AI

Criticality: High I/O: Image prompts from story generation; System output as
relevant and cohesive images.
Priority: 10/10
Description: Upon receiving image prompts from the AI-generated story, the system must
generate corresponding images that match the narrative and style requested by the user, ensuring
visual harmony with the story content.
Dependencies: AI image generation service; MFR-04
Cost: Very High
Schedule: 2 days
Technical Issues: Ensuring image relevance and appropriateness. Cost is very high for testing.

12
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

MFR-06 Name of Requirement: Support Multilingual Story Generation

Criticality: Medium I/O: Language selection; System output as a story in the selected
language.
Priority: 9/10
Description: The system must be capable of generating stories in multiple languages, allowing
users to select their preferred language. It should ensure linguistic accuracy and cultural relevance
in all supported languages.
Dependencies: Multilingual AI models and language databases.
Cost: High
Schedule: 1 day
Technical Issues: Ensuring the accuracy of language models and cultural nuances.

MFR-07 Name of Requirement: Assemble and Store Content

Criticality: High I/O: Generated story text and images; System output as a
compiled HTML file.
Priority: 9/10
Description: The system must compile the generated story text and images into a paginated
HTML file format that can be readily viewed in a web browser. It should then store this HTML
file and associated images in a designated server or cloud storage space.
Dependencies: Local Storage OR Reliable storage solution with backup and retrieval capabilities
Cost: Low
Schedule: 1 week
Technical Issues: Managing storage scaling as user base grows.

13
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

MFR-08 Name of Requirement: Facilitate User Interaction with Content

Criticality: High I/O: Generated HTML content; System output as an interactive

book viewable in the browser.
Priority: 8/10
Description: Once a story is generated, the user should be redirected to view their book in an
interactive format within the web browser, with functionalities such as page turning and text size
adjustments for enhanced readability.
Dependencies: Web development frameworks and libraries for interactivity.
Cost: Low
Schedule: 1 week
Technical Issues: Ensuring cross-platform compatibility and responsive design.

MFR-09 Name of Requirement: Basic Accessibility Features

Criticality: Medium I/O: Accessibility preferences; Adjusted content display output.

Priority: 7/10
Description: Implement accessibility features, such as increasing/decreasing font size or
changing the font style.

Dependencies: N/A
Cost: None
Schedule: 2 days
Technical Issues: Integrating features without compromising existing functionality.

14
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

4.2. Optional Functional Requirements (OFR)

OFR-01 Name of Requirement: Content Flagging

Criticality: Medium I/O: Review and Flag Content

Priority: 6/10
Description: Users should be able to flag any generated content they find inappropriate. The
system should log this event, notify administrators, and initiate a review process.

Dependencies: N/A
Cost: None
Schedule: N/A
Technical Issues:

OFR-02 Name of Requirement: Content Moderation by Admin

Criticality: Medium I/O: Admin commands; System output as actions on content and
user data.
Priority: 6/10
Description: Admins should be able to manage, search, and filter all books created, view detailed
information, and delete any content or user accounts if needed. This functionality must be secure
and auditable.

Dependencies: Admin dashboard interface, secure access controls.

Cost: None
Schedule: [TBD]
Technical Issues: Implementing comprehensive admin controls without affecting system
availability and integrity.

15
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

OFR-03 Name of Requirement: Enhance Accessibility Features

Criticality: Low I/O: Accessibility preferences; Adjusted content display output.

Priority: 4/10
Description: Implement and progressively improve accessibility features, such as high-contrast
modes, and text-to-speech. The system must meet international accessibility standards and be
user-friendly.
Dependencies: Accessibility libraries and compliance standards; TTS engine or SaaS; MFR-04
Cost: High
Schedule: N/A
Technical Issues: Integrating features without compromising existing functionality.

OFR-04 Name of Requirement: Download Story Books as PDFs

Criticality: Low I/O: User clicks the button to download; System output as a PDF
file of the storybook.
Priority: 4/10
Description: The system shall provide users the functionality to download their personalized
storybooks in PDF format. This feature will convert the HTML storybook into a downloadable
PDF, preserving the layout, images, and text as presented online.
Dependencies: PDF generation library, file conversion service integration.
Cost: Low
Schedule: N/A
Technical Issues: Ensuring high fidelity in the conversion from HTML to PDF, maintaining
interactive elements and accessibility features in the PDF format.

16
 Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

5. Non-functional Requirements
The tables below provide a comprehensive overview of the non-functional requirements (NFRs)
that are crucial for the development and operation of the system. These requirements are divided
into two categories: Mandatory Non-Functional Requirements (MNFRs) and Optional Non-
Functional Requirements (ONFRs). MNFRs cover vital aspects such as performance, system
reliability, data protection, user interface design, maintainability, and accessibility. These
requirements are essential for the system's functionality and user experience. On the other hand,
ONFRs are optional but offer additional enhancements, which include cross-platform support,
offline access to generated books, integration with external services, and regular backup procedures.
Each requirement is clearly defined with its corresponding description and level of importance to
effectively guide the development process.

5.1. Mandatory Non-Functional Requirements (MNFR)

MNFR-1 Name of Requirement: Performance

Criticality: High I/O: Performance metrics, resource optimization, fast response time,
resource efficient processing
Priority: 8/10
Description: The system should generate appropriate hyper-personalized books within a
reasonable timeframe, ensuring users do not experience significant delays.
Dependencies: MNFR-5
Cost: Low
Schedule: 2-3 weeks
Technical issues: Slow response time which could impact user experience negatively

17
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

MNFR-2 Name of Requirement: System reliability and stability

Criticality: I/O: Error handling, fault tolerance, graceful failure recovery, real-time
High monitoring
Priority: 10/10
Description: In case of unexpected errors, the system should be able to recover gracefully and
operate reliably without crashing frequently or experiencing heavy downtime.
Dependencies: MNFR 1/MNFR 5
Cost: Low
Schedule: 3 weeks
Technical issues: Lack of fault tolerance resulting in service disruptions, insufficient system
monitoring which could lead to lateness in detection and resolution of issues.

MNFR-3 Name of Requirement: Protection of user data and integrity

Criticality: I/O: Access control policies, user authentication mechanisms
High
Priority: 7/10
Description: The system should follow best practices for access control, and secure
communication protocols for storing and protecting user data, including personalization
parameters.
Dependencies: MNFR-4
Cost: Low
Schedule: N/A
Technical issues: Vulnerability in authentication mechanisms could lead to unauthorized access
to sensitive data. Weak access control mechanisms can allow lesser privileged users to tamper
with the data and resources of the system.

18
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

MNFR-4 Name of Requirement: Well-designed user interface

Criticality: I/O: UI design, accessibility features, user guidance, user feedback
High mechanisms
Priority: 9/10
Description: To ensure a positive user experience for both parents/guardians and children, the
user interface should be friendly and intuitive. The system should provide clear instructions and
feedback throughout the personalization process so that users with varying levels of technical
expertise can use it.
Dependencies: N/A
Cost: Low
Schedule: 3 weeks
Technical issues: Poor UI could lead to user being confused, insufficient user guidance could
hinder user interaction with the system, complexity in user hyper-personalization could lead to
user dissatisfaction.

MNFR-5 Name of Requirement: Maintainability of the system

Criticality: High I/O: Version control, testing, documentation, error logging
Priority: 7/10
Description: Set up coding standards and use version control systems such as Git to ensure
consistency in collaboration and code review. Validate system functionality and ensure stability
during development and deployment using standardized testing practices.
Dependencies: N/A
Cost: High
Schedule: 2/3weeks
Technical issues: Codebase complexities, inconsistent coding standards, limited testing coverage
which could lead to difficulty in identifying and fixing bugs.

19
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

MNFR-6 Name of Requirement: Accessibility

Criticality: I/O: Accessibility guidelines, color contrast, keyboard navigation
Medium
Priority: 6/10
Description: To make the system usable by individuals with disabilities, the Text-to-Speech
function should be made available for those who are visually impaired. The UI should have
sufficient color contrast between text and background to improve readability for users. The UI
should also be able to support keyboard navigation.
Dependencies: MNFR-5
Cost: N/A
Schedule: N/A
Technical issues: As a result of a lack of accessibility testing, a less diverse audience may be
attracted to the system since users may have difficulty using it if it was not designed with them in
mind.

5.2. Optional Non-Functional Requirements (ONFR)

ONFR-1 Name of Requirement: Cross-platform support of the system

Criticality: I/O: Cross-platform support, responsive design, feature parity
Medium
Priority: 5/10
Description: The system supports all devices as it uses responsive design which caters to all
users being able to have the same experience with the system whether they use a laptop, phone or
tablet.
Dependencies: MNFR-5
Cost: High
Schedule: N/A
Technical issues: Ensuring that the responsive design adapts to all different screen sizes and
resolutions to warrant a consistent and user-friendly experience.

20
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

ONFR-2 Name of Requirement: Offline Access of generated books

Criticality: low I/O: Local storage, offline functionality
Priority: 4/10
Description: Create an option for users to download generated books for offline viewing so that
children can read them even without an internet connection, these books can be downloaded in
acceptable formats like pdf.
Dependencies: N/A
Cost: low
Schedule: N/A
Technical issues: Designing the option to download the book in a pdf format which will then go
to the downloads folder on any device.

ONFR-3 Name of Requirement: Integration with external online services

Criticality: low I/O: External services API, data formats, integration code, reliability
measures
Priority: 2/10
Description: Integrate other external services into the system, such as social media platforms or
educational content providers, to enhance the reading experience. Enable the sharing of
personalized books through social media platforms.
Dependencies: N/A
Cost: high
Schedule: N/A
Technical issues: Different external services may use different protocols or data formats which
makes the compatibility challenging leading to difficult integration. Integrating with different
services could also introduce new security vulnerabilities to the system.

21
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

ONFR-4 Name of Requirement: Regular backup procedures

Criticality: I/O: Backup schedule, data storage locations, backup files, data restoration
medium procedures
Priority: 5/10
Description: Creating copies of system data and storing them securely is part of regular backup
procedures, which help prevent data loss in case of system failures, hardware malfunctions, or
human errors. All critical system components, databases, and user-generated content should be
backed up regularly according to a predefined schedule.
Dependencies: N/A
Cost: high
Schedule: N/A
Technical issues: To maintain correct data protection, the frequency of backups needs to be
balanced with the performance and resource utilization of the system.

22
 Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

6. Diagrammatic representation of the requirements

6.1. Use Case Diagram
The use case diagram represents the requirements graphically and provides a user-centric view. The
use case list with use case description is provided for a better understanding and overview of
requirements below Table 6.1.1. Use case list, followed by the use case diagram Figure 6.1.1.
Use case Use Case Description Actor
No
1. Register User The users can register for the My Unique User
Story system using their email address and
other details. The system creates an account
for the user using their email address.
2. Select Preference The user selects the preferences from the list User
of preferences given to the user by the system.
This list includes age categories 6-10 years,
story genre, artwork style and language. The
system provides a list of preferences for users
to select desired options.
3. Submit Preference The user submits their selected preference User
with the story prompt (storyline) to the system
to generate the story for them. The system
allows the user to submit all the inputs and
preferences for story generation.
4. Generate Stories As the user submits the preferences and the User
prompt, the system generates the story by
examining it and aligning it with the
preferences. The stories generated are
according to users' input and are hyper-
personalized.
5. Prompt Error The system examines the prompt and the
preference given by the user and reports the

23
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

error if occurred while getting input or invalid

inputs.
6. Generate Image The system generates images related to the
storyline and inputs given by the user. This
provides images and graphics to the
storybook.
7. Produce The system supports multilingual story
Multilingual Story generation according to the user’s preferred
language.
8. Download Stories The system allows users to download stories User
generated by the system in PDF form
according to their preferences.
9. View Story Book The user reviews the storybook and can access User
it inside their account anytime. The system
provides users with the option to view their
previously generated stories.
10. Flag Content The users can flag inappropriate or displeasing User
content while viewing the storybook.
11. Review Flagged The admin reviews the flagged content Admin
Content provided by the users and any additional
comments provided by users. The system
should allow the admin to view the flagged
content with complete information about the
user’s prompt.
12. Moderate Flagged The admin moderates the flagged content after Admin
Content reviewing it and checks about the valid reason
reported by the user. If the flagged content is
inappropriate, the admin deletes the content
from the database entirely. The system allows
the admin to moderate and delete the content.
Table 6.1.1. Use Case List

24
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

Figure 6.1.1. Use Case Diagram

25
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

Figure 6.1.2. Use Case Diagram Legend

26
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

6.2. System Architecture Diagram

The system architecture diagram Figure 6.2.1 depicts the high-level components and under lying
technological architecture of the complete system being proposed.

Figure 6.2.1. System Architecture Diagram

Figure 6.2.2. System Architecture Diagram Legend

27
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

6.3. Component Diagram

The component diagram Figure 6.3.1 shows the various modules/components and their logical
inter-relationships and interactions within the proposed system.

Figure 6.3.1. Component Diagram

28
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

Figure 6.3.2. Component Diagram Legend

29
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

6.4. Sequence Diagram

The sequence diagram Figure 6.4.1 shows the flow and the sequence of events between the
different system components according to the proposed system’s function.

Figure 6.4.1. Sequence Diagram

30
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

Figure 6.4.2. Sequence Diagram Legend

31
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

6.5. Activity Diagram

The activity diagram illustrates the step-by-step workflow within the system, showing the activities,
transitions and decisions and end points. For this document, we are considering two typical
activities, one each by the user (creator) Figure 6.5.1 and the other by the admin Figure 6.5.2.

Figure 6.5.1. User Activity Diagram

32
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

Figure 6.5.2. Admin Activity Diagram Figure 6.5.3. Activity Diagram Legend

33
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

6.6. Dataflow Diagram

The context 0-level Dataflow diagram Figure 6.6.1 is a high-level overview of the system and its
interaction with external entities. The diagram provides an understanding about the scope and the
boundaries of the system to stakeholders.

Figure 6.6.1. Content 0- Level Data Flow Diagram

34
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

Figure 6.6.2. Content 0- Level Data Flow Diagram

35
 Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

7. Conclusion
The document specifically outlines the project’s core objective: to use advanced artificial
intelligence to tailor children’s storybooks, creating a unique, engaging, and educational experience
for each child. This initiative is not merely about personalization; it represents a massive shift in
how children interact with literature, making reading an immersive, interactive journey that caters to
the individual interests and learning curves of young readers.
The document further explores the technical intricacies and challenges overcome in developing
such a sophisticated platform. It emphasizes the integration of generative AI for content creation,
image generation, ensuring stories are not only personalized but also diverse and inclusive.
It also includes the use case diagrams such as system sequence diagrams, component, system
architecture diagram, data flow diagram etc. It also highlights the functional and non-functional
diagrams and how high on the priority list they are.
The strategic development of an intuitive front end, alongside a sophisticated AI algorithm,
underscores our dedication to creating a user-friendly and accessible platform. The inclusion of
multilingual support and ethical security measures further exemplifies our commitment to
accessibility and responsible innovation.
As we conclude the R&A phase, we stand on the threshold of turning this vision into reality. The
collaborative efforts of our team, guided by the insights and objectives detailed in this document,
have laid a solid foundation for the successful development and implementation of the project. With
a focus on quality, inclusivity, and innovation, "My Unique Story" is set to open new horizons in
educational technology and storytelling, making every child's reading journey as unique as they are.

36
 Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

8. Appendices

Appendix A - Deliverable Task Breakdown Statement

Project Team Name
LUCID INC.

Team Member Deliverable Date Signature

Names Percentage
Completed
Bhavin Desai 20% 9th February 2023

Achraf Ben Haj 20% 9th February 2023

Abdul Rahman 20% 9th February 2023

Samra Ahmed 20% 9th February 2023

Kevin Richard 20% 9th February 2023

37
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

Appendix B - Copies of client documents

38
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

39
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

40
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

41
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

42
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

Appendix C – Glossary

Word Definition
The area of computer science focused on creating intelligent
Artificial Intelligence (AI) systems that can perform tasks requiring human-like
intelligence.
Guidelines and requirements that aim to make digital
Accessibility Standards content and technology accessible to individuals with
disabilities.
A set of instructions or rules that guide a computer program
Algorithm
in solving a problem or completing a task.
An API is an interface that enables two software
API (Application Programming applications to communicate with each other by exposing
Interface) data and functionality for external use, without exposing its
core systems, thus avoiding security risks.
The behind-the-scenes part of a software system that
Backend handles data processing, storage, and security, is not directly
visible to users.
Protocols and practices for creating and storing copies of
Backup Procedures
data to prevent loss in case of system failures or disasters.
Systematic errors or inaccuracies in data or algorithms that
Bias
lead to unfair treatment of individuals or groups.
Computing infrastructure where resources and services are
Cloud-Based Architecture delivered over the internet, providing scalability and
accessibility.
Compatibility with multiple operating systems, devices, or
Cross-Platform Support platforms, enabling users to access and use a system in
different environments.
A plain text file format is used to store tabular data, like
CSV (Comma-Separated Values) spreadsheets, where each line represents a row and values
are separated by commas.

43
Lucid Inc. Requirement and Analysis_LI_MUS_1 My Unique Story

A visual interface that provides users with access to various

Dashboard
tools, features, and data in one central location.
Moral and fairness issues related to the use of technology or
Ethical Concerns
specific practices.
The part of a software application that users directly interact
Frontend
with, usually through a graphical interface or web interface.
AI systems capable of creating new content, such as text or
Generative Artificial Intelligence
images, based on patterns and inputs.
The process of combining or incorporating different
Integration systems, services, or components to work together
seamlessly.
A set of principles, practices, and procedures used to guide
Methodology
processes and decision-making in a particular field.

Multilingual Ability to operate in or produce content in multiple

languages.
The branch of AI that focuses on computers' ability to
NLP (Natural Language Processing)
understand, interpret, and generate human language.
Organized into sections or pages, especially in digital or
Paginated
printed materials.

Profanity Filter Software or tool designed to identify and remove offensive

or inappropriate language in text content.
Web design approach that ensures websites and applications
Responsive Design
adapt to different devices and screen sizes.
Measures implemented to protect data, systems, and users
Security Features
from unauthorized access or malicious activities.

Text-to-Speech (TTS) Tool that converts written text into spoken words, enabling
computers to speak textual content.
UI (User Interface) The interface between a user and a computer program,
including graphical elements like buttons and menus.
The overall experience a user has while interacting with a
UX (User Experience) product or system, including factors like usability and
satisfaction.

44