System and method for representing software development requirements into standard diagrams

A system for deriving use case diagrams for software development, the system comprising:

• at least one processor;
• and
• a computer-readable medium storing instructions that, when executed by the at least one processor, cause the at least one processor to perform operations comprising:
• retrieving one or more core components from each of a plurality of software development requirements,
• wherein the one or more core components comprise at least one of a core message and a condition, and
• wherein the plurality of software development requirements are in unstructured textual format;
• determining at least one activity from the one or more core components;
• determining at least one of a class and an attribute from the one or more core components, wherein determining the class comprises determining the class from the core message based on a pre-defined set of rules and a statistical model via an iterative shortlisting process;
• and
• deriving at least one use case diagram based on the at least one activity and the at least one of the class and the attribute,
• wherein deriving the at least one use case diagram comprises aggregating a set of similar activities from the at least one activity based on domain knowledge.

A non-transitory computer-readable medium storing computer-executable instructions for:

• retrieving one or more core components from each of a plurality of software development requirements,
• wherein the one or more core components comprise at least one of a core message and a condition, and wherein the plurality of software development requirements are in unstructured textual format;
• determining at least one activity from the one or more core components;
• determining at least one of a class and an attribute from the one or more core components,
• wherein determining the class comprises determining the class from the core message based on a pre-defined set of rules and a statistical model via an iterative shortlisting process;
• and
• deriving at least one use case diagram based on the at least one activity and the at least one of the class and the attribute,
• wherein deriving the at least one use case diagram comprises aggregating a set of similar activities from the at least one activity based on domain knowledge.