Abstract

Use case analysis is a common technique used to ascertain the functional requirements of a software system. A use case diagram is a kind of Unified Modeling Language (UML) diagram created for use case analysis. Creating effective use cases can be a determining factor in building a system that meets users' needs. However, writing use cases is a difficult and time-consuming process, requiring the user to manually fill out a form or write text in a specific, pre-stipulated format. Many students lack the technical knowhow to do this. Our research offers a software solution that resolves this issue. By combining natural language algorithms, such as Part Of Speech (POS) and Name Entity recognition (NE), with a set of grammatical rules created and implemented as a Finite State Machine (FSM), our system extracts the relevant items from the text and automatically translates the plain or unstructured text into a structured one. The paper has been tested on standard examples with excellent results.

Highlights

  • The use case model is composed of two parts: The use case diagrams and the use case specifications

  • The use case model comprises actors, use cases, and associations, all of which are depicted in a use case diagram

  • Our paper examines a new field of information extraction, one that utilizes the power of the computer to perform one of the most critical tools of use cases for system analysis

Read more

Summary

Introduction

The use case model is composed of two parts: The use case diagrams and the use case specifications. The use case model comprises actors, use cases, and associations, all of which are depicted in a use case diagram. 2000), each use case represents a major piece of functionality that is complete from beginning to end, and is described within a use case specification. The specification includes the following processes: the basic flow of the use case, the alternative flows, involved actors and stakeholders, conditions, and references to other related use cases. The business rules associated with use case interactions must be specified or at least indicated by these rules

Methods
Results
Conclusion
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.