Explore chapters and articles related to this topic
Project closing
Published in Varun Gupta, Anh Nguyen-Duc, Real-World Software Projects for Computer Science and Engineering Students, 2021
The section presents architectural and technological aspects of the product. Hence, we suggest having separate subsections: [Technology stacks]: includes programming language for front-end, back-end, database technology, cloud services, third-party APIs, open-source library and frameworks, etc. It is important to justify why the technology stacks are chosen.[Overall architectural patterns]: at first, a general architectural view should be provided. In many cases, the architecture reflects the adopted frameworks or libraries. Typical general architectures are client-server, n-tier architecture, micro-service architecture, model-view-controller pattern, etc.[Architectural views]: 4 + 1 architectural view model provides a standard way to describe multiple views of a software system. In case the students are not familiar with these views, it should allow a simpler version of the detailed architecture. At least three different views should be considered whenever the views are applicable to the selected solution: Class diagram: a static structure of the product from an object-oriented perspectiveDatabase diagram: a basic structure of data that is used in the product, including data tables or data objects and their relationships.User experience design: a final screenshot of the font-end design for the product
Demonstration of a blockchain-based framework using smart contracts for supply chain collaboration
Published in International Journal of Production Research, 2023
Tarun Kumar Agrawal, Jannis Angelis, Wajid Ali Khilji, Ravi Kalaiarasan, Magnus Wiktorsson
Following the research question, the study adopted a systems perspective (Arnold and Wade 2015) because it is the sharing of information between units (partners) that are explored. It is further inspired from the established 4 + 1 architectural view model (Kruchten 1995) to explore the various elements within a system. Several studies have adopted a systematic approach for developing frameworks, including actor interaction, rules for interaction and functions; for instance, Salah et al. (2019), Westerkamp, Victor, and Küpper (2020), Kumar et al. (2020) and Li et al. (2020). This study employed a similar five-step methodology, as shown in Figure 1, to explore the research question. We specifically developed a framework that incorporates smart contracts designed in a comprehensive and systematic manner to facilitate collaboration.