dimanikulin VS fva

Quality Attributes, also known as non-functional requirements, are the characteristics of a software solution that describe how well it performs in terms of its operation, maintenance, and evolution. Quality attributes are not directly related to the functionality of the software, but rather to how well it meets certain standards or requirements.

I began my journey as an architect with requirements selection. By selecting the right requirements, an architect can ensure that the software is designed to meet specific business goals and objectives, as well as technical and operational requirements. This helps ensure that the software is scalable, maintainable and meets the needs of both the end-users and the stakeholders. It's worth noting that my approach to selecting requirements differed from that of a product manager because I needed more technical requirements. I divided architect requirements into four parts:

My first step in the role of an SME was getting to know what Multimedia Data is. I started learning it as I understood that my whole photo album is Multimedia Data itself. Then I realised that I need to use a solution to search for Multimedia Data - Multimedia IR systems. However, there are many Multimedia IR systems, and it was a long way to select one of them to start searching more efficiently. Thus, several Multimedia IR systems, that are present on the market and available for end users, were analyzed.

Undeniably, we should remember about licenses. As FVA Software uses third-party tools and libraries, their respective licenses should be included in the code. In addition, I had to create the FVA License and gained an understanding of what a license is and how to create one.

Initially, the list was much longer, but as some of the tools/libraries became outdated, I moved them to a separate table using the same format. You can find the old dependencies list here.

The first artifact to consider was Value Proposition which has the following components:

"Again no. I would have started from Design Thinking, if I was familiar with it."

I realized that I need Multimedia Organizer as well. Unfortunately, I didn't find a Multimedia Organizer that could fully satisfy my needs (fixing problem metadata, working with digiKam and Synology etc.) That's why I started creating my own product to cover my needs.

Then I started using it... What I discovered in a flash is that current Multimedia IR systems do not provide a flexible and automated functionality to import Multimedia Data into Multimedia IR systems. But that wasn't the only problem.