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:

• BA, who takes the requirement from customer
• Architect, who designs technical Skelton and usage of sequential diagrams to translate BA descriptive requirements to technical blueprints
• Developers, who actually develop the BA requirements to actual working product based on Architect guidelines.

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.

Usecase-1: Page should have a form that takes details of the Customer. Users can enter the details and can submit the details.

Usecase-2: Page should display the details of the customer.

#java #spring boot #redis #kafka #software developent #elastic search