Designing Blockchain Solutions: Defining Non-Functional Requirements
In this course the goal is to define the non-functional requirements necessary for development of a blockchain solution. The course begins by defining the types and the role non-functional requirements play in designing a blockchain solution. Learners will focus on six categories of non-functional requirements and what those categories mean across the different levels of the architecture. The course will showcase a representative architecture for framing non-functional requirements and provides four use cases and tips when defining non-functional requirements for a specific project.
What you will learn:
- Define non-functional requirements and their role in designing a blockchain solution
- Identify the categories of non-functional requirements
- Define the different levels of the architecture in a blockchain solution
- Examine the important requirements for defining non-functional requirements through use cases
This course is part of the following course program:
A Step-by-Step Approach to Designing Blockchain Solutions
Courses included in this program:
Who Should Attend: Product managers, solution designers, solution architects
Dr. Hunter Albright is a faculty member at the University of Colorado, Boulder, and teaches at the Leeds School of Business and the School of Engineering. As the executive director of the university’s blockchain alliance, he is leading the research, application, and education of blockchain technology and solutions. He is a member of the C4’s Certified Bitcoin Professional Advisory Board and supports the IEEE’s blockchain efforts as the co-chair the of IEEE Blockchain Education Initiative and co-chair of the IEEE Blockchain for Transactive Energy Initiative.
Publication Year: 2021