There are many resources online when we want to learn about different tools for standard enterprise applications. But there are no specific resources which scatter all the enterprise standards. There are no clear tutorials on how the requirement is seen at different levels of software development. I am going to discuss the aspects of the regular enterprise development scenarios and how each person has to responsible for each level of software development.
This article is mainly for the developers who don’t have much experience in the software industry. This article is a bit long, but covers most of the required scenarios which make you comfortable with the software development.
So any software development can be designed by 3 levels:
To make the above explanation more clear I will take an example and will walk through the entire process of designing the application.
Firstly will take a use case provided by the BA. Basically BA will give a visual representation of what and how the end product has to be looked with specific use cases.
Note: Description of the use cases is much self-explanatory. Note: We are not going to develop the UI in this tutorial. Mostly we will be concerned about the backend, how things will work.
So as per the discussion, the next task is to the Architect who designs the system. So Architect has to think about different aspects like scalability, reliability, etc to build a robust system. At this stage, we will get decisions like what tools we have to use and how the interaction happens at technical stages.
#java #spring boot #redis #kafka #software developent #elastic search