Skip to main content

Updating Requirements

Requirements are divided into pages, such as Overview, Modules, and UX/UI. After you update a page, you should save and regenerate your work.

info

Once you purchase Requirements, your Digital Blueprint is archived as view-only. You cannot update an archived Blueprint. All of the information from your Blueprint will be imported into your Requirements and be viewable in the Project Navigator.

Adding, Editing, and Deleting Content​

Most fields are text boxes. You can type in your changes directly. This is how you update elements such as your Problem to be Solved and Solution.

To add list items, click next to an existing list item, and press Enter. This will create a new empty list item. For example, in Overview > General, you can add list items under Challenges by pressing Enter in an existing entry:

Empty list item under Challenges

Type in your new challenge item. If you want to delete the new item, click the Cancel icon.

On some pages, you can add new sections, such as new modules or design considerations. For example, on the User Types page, click Add User Type.

Button to add new User Type

There are two options:

  • Use AI to Generate: Archie will generate a new user type based on your input. In the prompt, type in information related to the new user, and click Send.
  • Start from Scratch: Fill out a blank card manually.

If you want to delete a user type, scroll to the bottom of the user type card, and click Delete User Type.

Button to delete new User Type

Site Maps and Wireframes​

info

Site Maps and Wireframes can only be generated or modified by Archie. They cannot be changed manually by users.

Saving and Regenerating​

When you are done modifying a page, click Save Save. If you have not saved yet, you can remove your changes by clicking Undo. Requirements save button

If Save is greyed out, there are no pending changes.

After saving, click Regenerate to populate your changes to related areas on that page. For example, your Problem to be Solved and your Solution are connected. If you added several new issues to your Problem to be Solved, then you will need to click Regenerate to have Archie update your Solution, and other dependent areas.

Requirements regenerate button

When you click Regenerate, you have two options:

  • Regenerate Page: The entire page will be regenerated.
  • Give Archie Instructions: A prompt will appear. You can type information Archie should add while regenerating. Click Send.

You should not make new changes while your page is regenerating. Saving and regenerating only applies to the current page. For example, if you regenerate the User Types page, the Modules page is not regenerated. The Modules page will need to be opened and regenerated separately.

danger

If you do not Save, and you leave a page, your changes will be lost. If you do not Regenerate, connected elements on the page will not be updated to reflect your edits.

If you need to regenerate a page, Save is deactivated. However, you can still edit the page. If you edit something, Save is activated, and Regenerate will be deactivated.

Attention Needed Messages​

When you open a page, you may see Attention Needed Attention Needed icons. This means that changes occurred on the current page or a different page, but those changes were not applied to the area displaying the Attention Needed.

Application Type header with the needs attention icon.

To address these warnings, click the Attention Needed icon. Chose an option from the dropdown. The exact terminology will vary depending on the element. For example, if the icon is next to a Description inside an specific module called Admin Control, the dropdown will display:

  • Regenerate Description: The Description will regenerate.
  • Regenerate Entire Module: A prompt will open, so you can give Archie more information. Click Send. The entire Admin Control module will regenerate.
  • Dismiss Warning: Nothing regenerates. This option is useful if you want to make some manual changes, and regenerate later. If you dismiss a warning by accident, click Undo at the top of the page.

You can update the areas with warnings manually, click Save Save, and then click Regenerate. The reason you need to regenerate again is that your manual changes may affect other areas that did not initially have a warning. For example, if Solution is displaying an Attention Needed, you can update it manually. However, you will now probably see that same warning next to Pain Points. This is because those two areas are interconnected. You can choose to manually fix every message yourself, and skip regeneration, but this would be very time consuming.

Working with Requirements: Best Practices​

Your Requirements are divided into five pages:

  1. Overview
  2. User Types
  3. Modules
  4. Application Services
  5. UX/UI

These pages are ordered this way on the sidebar for a reason. It represents the hierarchy of dependencies. Changes in the Overview page will probably mean that all pages underneath it will need to be regenerated by Archie. Changes to Application Services will mean changes to UX/UI, but will not affect User Types.

Saving your work does not use tokens, but regenerating does. You will use your tokens more efficiently if you work on Requirements pages sequentially. For example:

  1. Input all your changes in Overview, save and regenerate.
  2. Open your User Types page. It will say it needs to be regenerated. Input any manual updates FIRST, then save and regenerate.
  3. Do the same for all other pages, in descending order.

For more information about tokens, see Managing AI Requests and Tokens.

on this page