In Text-to-software, the term “use case” refers to a complete process, a complete workflow, from beginning to end. This process covers a full scenario. A use case will probably contain all of the other Text-to-Software components: elements, groups, activities, states, transitions, events, and actions.
Each of these use cases is a complete process, but has many steps inside it. You could put each of these use cases in the same application, but they are each separate workflows.
Adding, Renaming, Reordering, and Deleting Use Cases
You can create new use cases and then add requirements to them, or you can turn an existing group into a use case. The elements contained in the group then become the use case’s requirements.
NOTE! For information on how to create a use case using Text-to-software, see Creating Use Cases Using Text-to-software.
TO MAKE A NEW USE CASE
1. On the Requirements Analysis tab, right-click in the Use Cases box, and click Add.
2. In the Please enter a name for this Use Case box, type a name for the use case.
3. Click OK.
TO TURN A REQUIREMENT INTO A USE CASE
• On the Requirements Analysis tab, right-click a requirement in the Use Cases box and click Become Use Case.
TO TURN A GROUP INTO A USE CASE
• On the Requirements Analysis tab, right-click a Group in the Forms/Groups box and click Become Use Case.
TO TURN AN ELEMENT INTO A USE CASE
• On the Requirements Analysis tab, right-click an element in the Elements/Fields box and click Become Use Case.
TO RENAME A USE CASE
1. On the Requirements Analysis tab, right-click, right-click a use case in the Use Cases box and click Rename.
2. In the Please enter a new name for this Use Case box, type a name for the use case.
TO REORDER USE CASES
1. In the Use Cases box, right-click and click Reorder.
2. Click a use case to select it, then click the up and down arrow buttons until it falls where you want to in the list.
3. Repeat Step 2 with other use cases until you are happy.
4. Click Done.
TO DELETE A USE CASE
NOTE! There is no confirm and no undo for this action.
• In the Use Cases box, right-click the use case you are dead certain you want to delete and click Delete.
Adding, Renaming and Deleting Requirements
Requirements are the things that need to be done in your workflow.
Requirements are not components like activities, forms, and fields. Instead, think of requirements as a virtual checkbox on the To Do list of your workflow. Everything else—fields, screens, events—goes into letting you checking off those boxes.
You create fields, screens, events, and all other Text-to-Software components to fulfill your list of requirements.
There is a requirement behind every component of Text-to-Software. Each screen, activity, form, field, transition, event, and action has a requirement behind it.
Every requirement is in a use case. Once you have created a requirement in a use case, you can then create the associated Text-to-Software component.
NOTE! For information on how to create a requirement using Text-to-software, see Creating Requirements Using Text-to-software.
TO ADD A REQUIREMENT TO A USE CASE
1. Click the Requirements tab.
2. In the Requirement box, type a name for the requirement.
3. In the Use Cases box, click the use case you want to add the requirement to.
4. Type a description of the requirement in the Description box.
5. Click the Add button.
TO RENAME A REQUIREMENT
1. In the Use Cases box, right-click a requirement and click Rename Requirement.
2. In the Please enter new name for this requirement box, type a name for the requirement.
3. Click OK.
TO DELETE A REQUIREMENT
• In the Use Cases box, right-click the requirement you are utterly sure you want to delete, and click Delete Requirement.
Creating Software Using the Text-to-Software Requirements Tab
When working in Text-to-Software, most of the time is spent on the Requirements Tab. This is where the application’s data and logic are created. The “Requirements” tab is the main tool in SageTea for analyzing requirements, organizing and developing them into a SageTea Application.
When first launching Text-to-Software, there will be data loaded into the tool. This is called Default Application in the Software Lifecycle field, and includes some states, activities, groups, and elements. This isn’t really an application, but a few initial data elements to begin working with.
The Requirements Tab can be used to manipulate this data to create an application in manual mode without connecting to the Text-to-Software server.
NOTE! Closing Text-to-Software without saving the application data will cause a prompt to save the application. To upload or download the application data to the server, requires a connection to the server.