Software Requirements and Patterns

Citation Author(s):
Joel
López Villareal
Brandon
Gustrowsky
Germán
Alférez
Submitted by:
German Alferez
Last updated:
Wed, 12/20/2023 - 17:51
DOI:
10.21227/qmby-e668
Data Format:
License:
0
0 ratings - Please login to submit your rating.

Abstract 

To make it possible for the model to distinguish the connection between requirements and the software architecture pattern during training using GAI, the expected response for a specific requirement was labeled with a software architecture pattern with the prefix “Software architecture pattern: ” and its explanation with the prefix “Explanation: ”. The requirement itself was also labeled with different sections to let the model recognize the following sections: “Title: ”, which defines the title of the individual requirement, “Description: ”, which explains the characteristics of the requirement, such as a brief description of the expected functionality of the requirement, “Precondition: ”, which defines the steps that need to take place before the functionality specified in the requirement runs, “Postcondition: ”, which specifies the expected result after the functionality specified in the requirement runs, and lastly, the “Sequence: ”, which specifies the steps that the user/system will follow in order to interact with the functionality specified in the requirement.

Instructions: 

N/A