Creating good software relies heavily on modeling, which involves representing the design of software systems using diagrams. The Unified Modeling Language (UML) is a standard method for this, but manually developing these diagrams can be complex, time-consuming, and requires significant expertise.
This project aims to simplify the process by automatically generating UML diagrams, such as class diagrams and use case diagrams, from software requirements. Instead of building a custom machine learning model from scratch, this approach uses a Large Language Model (LLM), like GPT, through an API. The application will act as an LLM agent where users input their software requirements. The system will then create specific prompts to communicate with the LLM, which will generate the relevant UML diagrams based on those requirements.
In essence, this project explores using advanced AI tools (LLMs) to automate the generation of UML models, making the process faster, easier, and more accessible for software developers.
Your question is general and I am guessing there are several assumptions you are making about the process or journey from requirements to the UML diagrams.
You do not specify the purpose and level of detail or precision you want in the UML diagrams. With an unknown end goal for the UML this makes offering advise difficult.
There also seems to be an assumption that the requirements are textual in form. It is also possible to represent many requirements in a graphical form. I have used graphical forms for the majority of requirements in industry projects since 2008. These were large projects o approximately 270 engineering-years of effort.
The process of the elicitation of requirements is an iterative act of discovery, education and communication between the customers (or users of the solution) and the developers. Often the customers do not know and cannot clearly communicate the solution requirements. The requirements are developed through iterations with proposed ideas from the customers and feedback refinement from the developers, as the people learn from each other and come to a common understanding.
As development proceeds from a stable and by definition incomplete set of requirements through design the accuracy of the requirements intent must be maintained and be traceable. The set of requirements at the start of design work do not need to be complete, but need a certain amount of stability in a core sub-set. Design work will both uncover additional requirements and questions arise because the precision is increasing. Also design work will uncover solution constraints that were not visible at the initial requirements elicitation time, thereby necessitating the modification of a requirement. New technologies and inventive ideas can cause a reconsideration of a requirement.
Lastly, during the design work a point will be reached for the Build or Buy decision. This is an economic business decision. If Building then are the resources available and development time acceptable. Constraints can cause a modification of the requirements. If Buying then what sub-set of the requirements does the existing product provide.
- Badges
- Science topic
- Similar topics
- Statistics
- Survey