Creating Applications in the Text-to-Software Requirements Tab, Using Use Cases and Requirements
In Text-to-Software, most of the time is spent working on the Requirements tab.
The Requirements tab is divided into three sections:
1. The top third section documents the application project and requirements using the Software Lifecycle and Requirement Description of Requirement field, as well as ChatBot.
The top third of the Requirements tab does not directly affect an application. It is used to document requirements and the underlying application structure and logic. Nothing in this top third appears in an application, unless it is eventually transferred to one of the seven fields in the bottom two thirds of the Requirements tab. Business analysts are the primary users of the upper third section of the Requirements tab.
2. The middle third relates to the application’s structure and user interface
3. The bottom third relates to the application’s logic
Helpful Tip! While you can develop applications without completing the top section of the Requirements tab, it is not advisable to do so. Completing this section with as much detail as possible allows for referring back to the initial requirements and logic upon which the application is based when making adjustments and future customizations.
Defining Use Cases and Requirements in the Software Lifecycle Field
The Software Lifecycle field is where application Use Cases and Requirements are defined. (For the definition of Use Case, please see Use Case in Glossary of Terms).
The Software Lifecycle field’s drop down, accessed by right clicking the field, contains useful functions and sub-sections, such as:
• Project – Edit Project Data and Initialize Project
• Text-to-Software – Import Word Doc and Export Word Doc
• Reorder Use Cases
• Reorder Requirements
• Renumber Requirements
• Renumber All
• Add to User Manual
• Remove from User Manual
• Use Cases – Add, Rename, Delete, Instantiate*, Re-Instantiate, Reorder Requirements, Add Requirement and Add Requirements Set
• Requirements – Add, Become Use Case, Rename, Filter Text, Refactor, Move, Change Management, Delete and Design
• Documentation – Application, Add Page, Rename Page, Delete Page and Update Project
• Publish** – Estimate, Work Breakdown Structure, Proposal, Statement of Work, System Design Document, System Quality Assurance Report, User Acceptance Test Plan, Contract, Initialize User Manual and User Manual
• Images – Workflow Diagram, View Image, Edit Image, Delete Image, Add Image to Element and Convert all images to Elements
• Rules – New Rule, Edit Rule, Rename Rule and Delete Rule
• Testing*** – New Test Case, Edit Test Case, Rename Test Case and Delete Test Case
• Automation Level – Manual Mode, Semi Auto Mode and Full Auto Mode
• Save As
*Instantiate creates working elements from the Use Case requirements.
Use Cases can be instantiated in:
1. Manual mode – if the Use Case is instantiated in manual mode only its elements will be created.
2. Semi-Auto mode
3. Full-Auto mode, which will create the corresponding groups, activities and states for that Use Case as well as the elements.
How Use Cases are instantiated for your application can be set in the Project Lifecycle tab at the top of the page.
**Publish is a useful tool as it can be used in business to generate proposal requirements like estimates, Statement of Work, Contract, etc.
***Test can be used to document software testing processes. Every requirement must have a Test Case.
NOTE! Each Use Case should be described in detail and in plain language in the Description field.
Creating Applications from Word Documents
Text-to-Software is a powerful tool that lets you create software right from Word documents.
You can pick from three levels of automation for Text-to-software. Manual mode provides the least automation, only creating use cases and requirements for you. Full auto mode provides the most automation, creating use cases, requirements, screens, activities, forms, fields, transitions, events, and actions. Semi-auto mode falls somewhere in the middle.
The lower levels of automation make fewer assumptions but give you more control. The full-auto mode makes all the assumptions, but that means it might make some assumptions that don’t suit you.
For information on how to structure and optimize your documents to make the kind of software you want, see these Help topics:
• Optimizing Text-to-software Documents
• Creating Smart Parts with Text-to-Software Synonyms
• Writing Text-to-Software Commands
TO IMPORT A WORD DOCUMENT
1. Click the Requirements Analysis tab.
2. Click the Project Lifecycle menu, then click one of the following:
• Manual Mode
• Semi-Auto Mode
• Full Auto Mode
3. Click the Project Lifecycle menu, then click Import Word Doc.
4. Navigate to the document you want to import.
5. Click Accept.
6. Watch as Text-to-Software transforms your text into amazing software.