ASSUMED VIVA QUESTIONS

48. Can you explain the process of handling user-generated content, such as book reviews,
to ensure quality and authenticity? => In managing user-generated content like book
reviews, ensuring quality and authenticity is paramount. We implement various measures
such as content moderation, where reviews undergo a screening process before being
published to the platform. Additionally, we provide reporting features for users to flag
inappropriate or misleading content, enabling community policing. Furthermore, we
encourage user engagement and participation to foster a culture of authenticity and trust
within the community. Regular audits and moderation efforts help maintain the integrity of
user-generated content on BookHaven, ensuring a reliable and trustworthy platform for all
users.
49. Why you created this project/ Why choose to create this? => "I created BookHaven to
fill a gap I saw in the market for an easy-to-use online bookstore that also fosters a sense of
community among readers. While there are other platforms out there, I wanted to innovate
by offering features like multi-language support, AI-powered recommendations, and
augmented reality book previews. Even though these features aren't included yet, I'm open
to adding them in the future. My goal is to combine my passion for technology with my love
for literature to create a valuable resource for book enthusiasts worldwide."
50. What is Augumented reality, bulding a community and AI powered recommendations
mean? => 1. Augmented Reality (AR): You could create a feature where users can use their
smartphones or tablets to scan the cover of a book. Then, using AR technology, they could
see a 3D image or animation related to the book's theme or characters. This would make
the reading experience more interactive and engaging.
2. AI-Powered Recommendations: Implement a recommendation system that uses artificial
intelligence to analyze users' reading habits, preferences, and past purchases. Based on this
data, the system can suggest books that the user is likely to enjoy, helping them discover
new titles and authors.
3. Community Building: Create a community platform within your bookstore where users
can create profiles, connect with other readers, join book clubs, and participate in
discussions. This would foster a sense of belonging among book lovers, making the platform
more than just a place to buy books, but also a vibrant literary community.
51. SDLC of your project? => 1. Planning: During the planning phase, we meticulously
defined the project scope, objectives, and requirements for the BookHaven online
bookstore platform. This involved identifying key features and functionalities, as well as
establishing a clear timeline and resource allocation plan.
2. Analysis: In the analysis stage, we conducted comprehensive research to gather detailed
requirements and insights into user needs and preferences. This included studying user
stories, conducting market research, and analyzing competitor platforms to inform our
decision-making process.
3. Design: The design phase focused on creating a robust architectural and technical
blueprint for the BookHaven platform. We developed detailed design specifications for the
frontend and backend components, including database schema, user interface layouts, and
system integration points.
4. Development: With the design in place, we proceeded to the development phase, where
we implemented the BookHaven platform according to the design specifications. This
involved coding and programming using a variety of languages and technologies, including
HTML, CSS, JavaScript, PHP, and MySQL.
5. Testing: Following development, rigorous testing procedures were conducted to ensure
the quality and functionality of the BookHaven platform. This encompassed various testing
methodologies, including unit testing, integration testing, system testing, and user
acceptance testing (UAT), to identify and resolve any issues or defects.
6. Deployment: Upon successful testing, the BookHaven platform was deployed to a
production environment for public access. This involved configuring servers, setting up
databases, and deploying application code in a secure and efficient manner, ensuring a
smooth transition to the operational phase.
7. Maintenance: Post-deployment, ongoing maintenance and support activities were
undertaken to ensure the continued performance and reliability of the BookHaven platform.
This included monitoring system health, addressing any issues or bugs that arose, and
implementing updates and enhancements based on user feedback and evolving
requirements.
52. Models of your project? => 1. Waterfall Model: Meaning:A linear and sequential
approach to software development, where each phase must be completed before moving
on to the next. Answer: Following the Waterfall model, the BookHaven project
proceeded methodically through each stage, starting from planning and requirements
gathering, then moving on to design, implementation, testing, deployment, and
maintenance. This approach ensured a clear understanding of project requirements upfront
and minimized changes during later stages, resulting in a structured and predictable
development process.
2. Iterative Model: Meaning: Involves repeating cycles of development, testing, and
feedback gathering. Answer: Adopting the Iterative model allowed the BookHaven
project to iteratively develop and refine features based on user feedback and changing
requirements. Each iteration involved planning, development, testing, and deployment, with
feedback gathered from users at the end of each cycle. This iterative approach enabled
continuous improvement and ensured that the platform evolved to better meet user needs
over time.
3. Prototyping Model: Meaning: Involves creating simplified versions of the final product
to gather feedback and refine requirements. Answer: By employing the Prototyping
model, the BookHaven project created early versions of the user interface and specific
features to gather feedback from stakeholders and users. These prototypes helped validate
design decisions, identify potential issues, and refine requirements before proceeding with
full-scale development. As a result, the final product closely aligned with user expectations
and preferences, leading to higher satisfaction and usability.
(Assume karo ki apne waterfall follow liya hai toh ye answer, ya fir prototype follow kiya
hai toh voh answer ase!)

53. The entities and relationship’s between them and the attributes? => Entities:

Customer: [ C_name: Text - C_address: Text - C_email: Text - Cid: Text (likely a unique
identifier for the customer) ]

Product: [ - Pid: Text (likely a unique identifier for the product) - P_name: Text
P_quantity: Number - P_price: Number ]

Admin: [ - A_id: Text (likely a unique identifier for the admin) - A_name: Text -
A_role: Text ]

Message: [- Mid: Text (likely a unique identifier for the message) -M_name:Text
M_message: Text - M_contact: Text ]

Order:[ - O_id: Text (likely a unique identifier for the order) - O_price: Number
O_total: Number - O_quantity: Number ]

Cart: [- Rid: Text (likely a unique identifier for the cart item) - R_quantity: Number -
R_status: Text ]

Relationships:

- Customer manages Cart (one-to-many) - Customer chooses Product (many-to-many)

- Product is added to Cart (many-to-many) - Admin sees Message (many-to-many)

- Admin sends Message (one-to-many) - Customer checks Order (one-to-many)

- Order has Product (many-to-many)

54. What additional attributes would be useful to capture about a customer besides
name, address, email, and ID? (e.g., phone number, purchase history) => - Additional
attributes like phone number, purchase history, and membership status could provide a
more comprehensive view of the customer.

55. Since both Product and Price entities have a "Pid" and "P_quantity" attribute, can
these entities be combined? If so, how would you handle historical price changes? => -
Combining Product and Price entities could simplify the model, but historical price changes
would need to be tracked separately or through timestamps to maintain accuracy.
56. What attributes are missing from the Order entity to understand the complete picture
of an order? (e.g., order date, order status, list of items ordered? => - Attributes such as
order date, order status, payment method, shipping details, and a list of items ordered are
essential for a complete understanding of an order.

57. How does the "Cart" entity relate to the "Order" entity? In other words, how do items
move from the cart to an order? => - The "Cart" entity typically holds items selected for
purchase by a customer, while the "Order" entity represents completed transactions after
items are moved from the cart and payment is processed.

58. Who is the recipient of the message (M)? Does the message come from a customer or
the admin? => - The recipient of the message depends on its purpose; it could be either a
customer or an admin, depending on the context of the communication.

59. Context level DFD! => ENTITES: Customer/User: Represents the person interacting with
the online book store. - Admin: Represents the system administrator managing the online
book store.

Data Flows:

Customer interacts with store: This bi-directional flow indicates the customer browsing,
searching, reviewing books, and potentially placing orders. The system would respond by
displaying book information, order confirmation, etc.

User Report & User Detail: This suggests the admin can generate reports or view details
related to users.

Book Report & Book Detail: Similar to user reports, this indicates the admin can generate
reports or view details related to books.

Order Report & Order Detail: This suggests the admin can generate reports or view details
related to orders.

Manage Book Stores: This flow likely refers to the admin managing the book inventory or
store operations (not shown in detail here).

In summary: This context level DFD provides a high-level overview of the information
exchange between the online book store system and its users (customers and admins). It
focuses on the main functionalities without diving into the specifics of how these
functionalities are achieved.

60. Level 1 DFD! => Entities: Customer: Represents the person interacting with the online
bookstore.

-Admin: Represents the system administrator managing the online bookstore.

Data Stores: Book Information: Stores data about the books offered by the bookstore,
likely including title, author, price, quantity, and description.
- Customer Detail: Stores customer information, likely including name, address, email, and
potentially order history (although order history is not explicitly mentioned here).

-Order Detail: Stores details about customer orders, likely including order ID, items ordered,
price, and potentially order status.

- User Review: Stores user reviews of books, likely including reviewer ID, book ID, rating, and
review text.

Processes: - Customer Process Order: This process encapsulates the functionalities related
to a customer placing an order. The data flow indicates the customer interacts with the
system to browse books (likely stored in Book Information) and potentially place an order
(resulting in Order Detail being updated).

- Manage Book Inventory: This process likely involves the admin managing the book
information (adding, updating, or deleting books) stored in Book Information.

- Manage User Review: This process allows the admin to manage user reviews (potentially
approving, deleting, or editing them), which are stored in User Review.

Data Flows: - Customer interacts with store: This bi-directional flow indicates the customer
browsing, searching, potentially reviewing books, and placing orders. The system would
respond by displaying book information, order confirmation, etc.

- Manage Book Information: This flow shows the admin updating the book information
stored in the Book Information data store.

- Manage User Review: This flow indicates the admin managing user reviews stored in User
Review.

Additional Notes: This level 1 DFD provides more detail compared to a context level DFD by
decomposing the high-level processes into sub-processes. The specific details of how a
customer places an order or how the admin manages books or reviews are not shown here.
These lower-level functionalities can be further explored in level 2 DFDs.