Open space discussion on UML use-case at the Seminar on "Software Engineering: Research and Practice"

December 20, 2014 I was honored to participate in the "Software Engineering: Research and Practice" seminar hosted by Fudan University. In the afternoon open space activity, I recommended UML use-case as one of the 6 topics and became the moderator of this topic. This topic was discussed with a number of teachers and industry experts. Finally, as a representative of this topic, I briefed you on the topic of discussion. This article attempts to sort out the discussions that were recorded at the time.

1, in the industry UML and use case has not been widely used, can be used case to express the original SRS expression content, has been quite good. It is difficult to make full use of oose benefits. There are 1 reasons to speculate that structured process thinking based on functional decomposition is a more natural mode of thinking, and object-oriented thinking is a thought that needs to be promoted. Therefore, whether in school learning, or in the real application of industry, UML use-case stay at the drawing level, not the modeling level.

2, Rung's successful experience in UML is methodology first.

3, the UML Use-case has become the almost necessary course content in the software engineering.

4, Beihang Liu Chao introduced the new method of abbreviation RUCM, which is characterized by the use of restricted natural description language to express demand, which is currently in the Graduate class of Beihang University. This is probably the best way to solve Use-case's difficult day.

5, from a chronological perspective, the expression of demand after 3 generations: 1, the traditional Srs;2,use-case;3,user story, the latest use-case2.0 is comprehensive to the User story learning. The user story is value-oriented and controls the granularity to facilitate development in short iterations. The original use-case does not have a clear control of particle size, resulting in large-granularity use cases that cannot be implemented in agile short iterations. The SRS of the traditional large document form is not considered at all in short iterations. The User story caters to the process-oriented scenario, but is more dynamic in the recent industry. Perhaps Use-case 2.0, which integrates user stories, will be a bridge between the campus and the industry.

Open space discussion on UML use-case at the Seminar on "Software Engineering: Research and Practice"