## 5 Research Results
### Case Study: Development of the Blockchain-Based NFT Trading Web 3.0 Application  
The initial step involved the teacher, playing the role of the customer, in defining the product backlog. Since the teachers assumed this role, here is how they defined the product backlog: \"I want to create a next-generation Web 3.0 platform that allows users to buy, sell, and trade NFTs (Non-Fungible Tokens) securely. The platform should leverage blockchain technology to ensure transactions are transparent and decentralized, with each NFT purchase being executed through a smart contract. The goal was to make user's being able to browse various NFTs, create their own listings, and securely handle payments using cryptocurrency. The platform should be scalable, reliable, and easy to use, especially for people who may not be familiar with blockchain or Web 3.0 technology. The platform to support a large user base was also needed, and any updates to the system should happen seamlessly without downtime\". Following this, teaching assistants and students analyzed the product backlog. They first divided it and made connections between the demands and the sprints, aligning them with the overall objectives of each sprint. The non-technical demand for the first sprint was defined as: follows \"I want a marketplace where users can list NFTs for sale, browse listings, and make purchases\". The non-technical demand for the second sprint was as follows: \"Users need to manage their profiles and interact with NFTs, and transactions must be automated through smart contracts\". The final demand was as follows: \"The platform must be scalable, support thousands of users, and handle updates without downtime\". The product backlog was then divided into a set of user stories presented in Table 6. Each user story had tasks, acceptance criteria, priority, and several story points (a measure of the effort required to deploy and implement the demand). \begin{table}
\begin{tabular}{l l l l} \hline \hline
**Sprint No.** & **User Story** & **Priority** & **Story Points** & **Acceptance Criteria** \\ \hline \multirow{8}{*}{1} & As a developer, I want to identify & \multirow{2}{*}{High} & \multirow{2}{*}{5} & A list of identified \\  & microservices required for the & & & microservices with their \\  & NFT e-commerce platform so I & & & functions clearly described. \\  & can structure the system properly. & & & \\ \hline \multirow{8}{*}{1} & As a developer, I want to define & \multirow{8}{*}{8} & API documentation for \\  & RESTful APIs for each & & & each service with end- \\  & microservice so the services can & & & points, request/response \\  & communicate with each & & & formats, and authentication \\  & other efficiently. & & & mechanisms. \\ \cline{2-4}  & As a developer, I want to create & \multirow{8}{*}{3} & \multirow{8}{*}{3} & A clear and complete \\  & an architecture diagram showing & & & architecture diagram \\  & the relationships between & & & illustrating the interaction \\  & services so I can visualize & & & between services. \\  & service interactions. & & & \\ \cline{2-4}  & As a developer, I want to & \multirow{2}{*}{High} & \multirow{2}{*}{8} & A fully functional and \\  & NFT Listing Service using Docker & & & containerized NFT \\  & so it can be deployed. & & & Listing Service. \\ \hline \hline \end{tabular}  
* As a user, I want to access the API documentation in a user-friendly interface (Swagger/Postman) so I can understand and interact with the API.  
\end{table} 
Table 6: Sprints and user stories. In the first sprint, students identified the key microservices that would be the core of the NFT marketplace platform. Each microservice was designed to be independent, scalable, and aligned with a decentralized architecture [45]. Students defined three main microservices to be developed: the User Management Service, NFT Listing Service, and Marketplace Service. The first microservice handled user accounts within the NFT marketplace platform.