How Can We Help?

Creating software in 8 steps using SageTea’s Text-to-Software

You are here:
< Back

In general, software creation using Text-to-Software follows this cycle:

1. A business analyst takes business requirements in English – the common language of business worldwide – from clients either over the phone, in a text document, on a website, or from an SQL database.
2. The business analyst then feeds the requirements into Text-to-Software, where they are processed.
3. When the requirements are converted into the Text-to-Software format, in one button click, the business analyst can then upload a program that does what the English say it is supposed to do.

The cycle is done without programming, giving users reductions in cost and time.
Text-to-software provides an automated project management process that you can use to plan and coordinate your project. This process is integrated and unified and ideally suited for developing an application.

There are eight steps in this project management process, which begin at the point where you have a client in the contract negotiation stage.

The steps are:

1. Edit your project data—Set up the detailed project information, such as company name, address, logo.
2. Set your automation mode—Identify the level of automation you want Text-to-Software to perform.
3. Create use cases—Set up the basic usage scenarios.
4. Convert Text-to-software—Use documents to make your Text-to-Software application.
5. Create an estimate for the end customer—Provide your customer with a general idea of how much the application will cost and how long it will take to create.
6. Upload the application to create a working demo—Publish a proof of concept program that will show your customer how great the software will be.
7. Publish the design—Using Text-to-Software’s automated system, generate the design documents to give to your customer.
8. Generate customer contract—Create the contract.

Step 1: Editing Your Project Data

Developing software using the Text-to-Software Project Lifecycle, begins when you have engaged with a client who wants to see a proof of concept/prototype before signing the contract for a full development project.

The first thing you will want to do in this case is to create a new project and edit the project data to reflect the project. Project data includes:

• Developer/company name
• SageTea Certification ID
• Average Requirement Development Time (The average amount of time it takes you to develop a single requirement. This will affect the project estimate and contract.)
• Hourly Rate (The rate you will charge per hour. This affects the project estimate and contract.)
• Developer/company address
• Customer name
• Customer address
• Developer/company logo
• Reporting logo

Once you have finished this step, the next step in the Text-to-Software Project Lifecycle is Step 2: Setting Your Automation Mode.

TO EDIT YOUR PROJECT DATA

1. Click Project Lifecycle, Edit Project Data.
2. Fill out the following fields:

• Developer/Company Name
• SageTea Certification ID
• Avg Requirement Development Time (hrs)
• Hourly Rate
• Company Address
• Customer Name
• Customer Address

3. Click the Developer/Company Logo graphic and browse to the logo you want to use.

4. Click the Report Header (TIFF) logo and browse to a TIFF file you want to use on your reports.

The next step in the Text-to-Software Document Lifecycle is Step 2: Setting Your Automation Mode.

This step follows Step 1: Editing Your Project Data in the Text-to-Software Project Lifecycle.

Step 2: Setting Your Automation Mode

Setting the automation mode identifies the level of automation that Text-to-Software will perform on text when you upload documents to be converted into the software.

• Manual Mode—The least-automated mode. Text-to-Software relies more on developer input.
• Semi-Auto Mode—Text-to-Software makes more assumptions than Manual Mode.
• Full Auto Mode—The most automated mode. Text-to-Software relies less on developer input.

TO SET YOUR AUTOMATION MODE
• Click Project Lifecycle, then click one of the following:
– Manual Mode
– Semi-Auto Mode
– Full Auto Mode

The next step in the Text-to-Software Project Lifecycle is Step 3: Creating Use Cases.
This step follows Step 2: Setting Your Automation Mode in the Text-to-software® Project Lifecycle.

Step 3: Creating Use Cases

The Text-to-software® Project Lifecycle provides a set of standard use cases that you can use as a starting point for your project. These show the high-level steps to gather text for a target application that you can turn into a prototype.
These standard use cases outline the process of a software development project. You can edit and remove them as you customize your project.

TO CREATE STANDARD USE CASES
1. Click the Requirements Analysis tab.
2. Click Project Lifecycle, Start Standard Project.

The next step in the Text-to-Software Project Lifecycle is Step 4: Converting Text-to-software.
This step follows Step 3: Creating Use Cases in the Text-to-software® Project Lifecycle.

Step 4: Converting Text-to-software and Editing the Software

In this step, you will take the text gathered from the meetings with your client and create an initial version of the software. You can use this software as a preliminary proof of concept to take to the client. It will allow you to create an estimate for the edits you will likely have to do to the software, publish a design, and get the customer to sign on the dotted line.

TO CONVERT TEXT-TO-SOFTWARE
1. Click the Requirements Analysis tab.
2. Click Project Lifecycle, Import Word doc.
3. Navigate to the location where your document is stored.
4. Click Accept.

EDITING THE SOFTWARE
Once you’ve created your initial application, you can edit in various ways:
• By editing the existing document and re-converting to software;
• By editing the software using the SageTea application; or
• By exporting the software to a Word document, editing that document, and re-importing it.

To create an application, you can use Text-to-software. When you use Text-to-software, you import a Word document and Text-to-Software transforms it into an application. But that application probably will not be perfect the first time, or maybe you just want to change the way something looks or behaves. Chances are you will need to edit the application.

If you export the software to Word, the document you get won’t look like the document you imported. It will be written in SageTea® grammar. But when you open it, you’ll probably be able to understand what is going on. If not, you can consult the Help topics about Text-to-Software.

Exporting the document into the Text-to-Software grammar has the advantage of making it easier for Text-to-Software to understand.
Related Help topics:
• Connecting to the Application Server
• Uploading Applications

The next step in the Text-to-software® Project Lifecycle is Step 5: Creating an Estimate for the Customer.
This step follows Step 4: Converting Text-to-software in the Text-to-software® Project Lifecycle.

Step 5: Creating an Estimate for the Customer

Once you have created a preliminary application using Text-to-software®, you can use the Text-to-software® Project Lifecycle tools to create an estimate that you can edit and deliver to your customer.
Text-to-software® will produce a generic, automated estimate for you based on the number of use cases and requirements in your projected final application. You will want to customize this estimate according to your own experience, level of knowledge, and knowledge of the customer.

TO GENERATE AN AUTOMATIC ESTIMATE
1. Click Project Lifecycle, Create an Estimate.
2. In a document editor, customize the estimate.
3. Use the estimate as a sales tool with your customer.

The next step in the Text-to-software® Project Lifecycle is Step 6: Uploading Application to Create a Working Demo.
This step follows Step 5: Creating an Estimate for the Customer in the Text-to-software® Project Lifecycle.

Step 6: Uploading Application to Create a Working Demo

At this point, you can upload a demo of your application to the server where it will reside. Uploading an application means it goes live for people to see and use it.
You can download the application and make edits to it at any time (for more information, see the Editing Applications Help topic).
When you’re happy with your demo, show it to your potential client and impress them. This will encourage them to sign the contract so that you can make final edits.

HOW TO UPLOAD AN APPLICATION
1. Click the Connection tab.
2. Type the appropriate information in the following boxes in the Login Details section:

• Username
• Password
• SageTea Server Address
• SageTea Server Port

3. Click Connect.
4. Once you’re connected, click the Upload App button.

The next step in the Text-to-software® Document Lifecycle is Step 7: Publishing the Design.
This step follows Step 6: Uploading Application to Create a Working Demo in the Text-to-software® Project Lifecycle.

Step 7: Publishing the Design

Text-to-software® is an advanced tool that will automatically publish the use cases and requirements of your application as a detailed design document. This saves you the time and effort of having to create a design document when you’ve already done the work of collecting the use cases and requirements and fed them into Text-to-software® anyway.

The requirements will be published as a Word document that you can edit and format so that it matches the branding of your company and you can present it to your client.

TO PUBLISH THE DETAILED DESIGN
• Click Project Lifecycle, Publish Software Detailed Design.

The next step in the Text-to-software® Project Lifecycle is Step 8: Editing Contract Terms and Generating the Contract.
This is the final step in the Text-to-software® Project Lifecycle. It follows Step 7: Publishing the Design.

Step 8: Editing Contract Terms and Generating the Contract

Text-to-software® gives you a tool that you can use to generate a preliminary customer contract. This contract contains legal text that you can review and edit before you send it to your customer to sign.
This contract is based on the project data that you entered in step 1: Editing Your Project Data, and on the contract terms that you will edit now.

TO EDIT CONTRACT TERMS
1. Click Project Lifecycle, Edit Project Data.
2. In the Contract Terms box, edit the contract terms to reflect your company’s requirements and policies.

TO GENERATE THE CUSTOMER CONTRACT
• Click Project Lifecycle, Generate Customer Contract.

Previous Creating Rules with Text-to-Software
Next Creating Use Cases and Requirements Using Text-to-Software
Table of Contents