Relative Content

Tag Archive for system

Creating system diagrams for a small app

I am learning system design (on my own) and still I am not clear on a few things. Assume there is a simple application with a front-end and a database for storing of the data.
In the system architecture diagram, will there be only two parts (UI and DB) or should I include some UI modules for calculations, for example? And what about hardware devices that the system is using?

Creating system diagrams for a small app

I am learning system design (on my own) and still I am not clear on a few things. Assume there is a simple application with a front-end and a database for storing of the data.
In the system architecture diagram, will there be only two parts (UI and DB) or should I include some UI modules for calculations, for example? And what about hardware devices that the system is using?

What is the difference between user requirements and system requirements?

From what I’ve read I believe user requirements are just the system requirements given in lay mans terms, is this correct? I’m specifically referring to the book “Software Engineering” by Ian Sommerville which I am obligated to follow. Given the example below from said book, why is there not a user requirement to match the second system requirement. For example “the user requires the report to be generated after 17.30 on the last working day of the month.” To me that is still in natural language so it is readable by the user. How much detail should be included in a user requirement vs system requirement and where do you draw the line?

System design to store and run an ELT process

We have an app where we integrate with lots of third part POS. we aggregate the POS data after the user integrates their POS. we currently use custom aggregator (ELT) to collect this data periodically once the integration is completed.
We do use a third party system to store this. however, we want to move to our own system. I am planning this move using a microservice that can store credentials and rotate the access token.
is this an appropriate system design?
The idea is that the once the user initially integrates we will store them on the main app as well as store the credentials in a RabbitMQ. The microservice will then fetch the data from RabbitMQ and then set it up.