Abstract: A system for use-case software development includes an interface renderer for interpreting a user interface definition code and displaying a user interface, a request dispatcher for processing a request from the interface renderer, and a request handler for processing the request and checking a use-case name contained in the request. The system further includes a use-case handling program, invoked by the request handler, for performing logic defined by a use-case corresponding to the use-case name and according to a use-case state and returning an interface definition specifying an interface layout and controls that are interpretable by the interface renderer, and a server page container for receiving the interface definition and providing the user interface definition code to the interface renderer.

Abstract: A method for modeling requirements of a product includes defining an abstract use case for each feature of said product, hierarchically decomposing each abstract use case until concrete use cases are specified for each feature, depicting every actor who would use the product as communicating with a concrete use case through a boundary, and programmatically extracting requirements from the use case diagram. Programmatically extracting requirements further includes converting use case diagrams into directed acyclic graphs, where each use case corresponds to a node of a graph and each relationship between a pair of use cases is represented by a directed edge between the corresponding pair of nodes in the graph where a directed edge points from a parent node to a child node, converting the directed acyclic graph into a tree, and searching the tree to extract the requirements.

Abstract: A method and device with instructions for testing a software application include creating a system model for the software application, wherein the system model includes an activity diagram, and applying one or more test annotations to the activity diagram to control test generation for testing the software application. Further, test annotations and the system model are processed to create one or more test cases, and the software application is tested using a test execution tool that uses the test cases.