Manage Requirements

Overview

The Requirements tab helps you define and organize the core activities and actions that shape your application. By breaking down functionality into manageable components, you can ensure your application aligns with user needs and business goals. Use the Requirements tab to create a visual story map and refine your application's key processes.

In the Requirements tab, you can

• manage activities,
• manage actions,
• connect design objects to actions,
• fine-tune your requirements, and
• export csv

Manage activities

Organize and update the activities to ensure your application’s high-level requirements are accurate and well-ordered.

Rearrange activities

To rearrange the activity columns:

1. On the Requirements tab, click REARRANGE ACTIVITIES.
2. In the Rearrange Activities display, click and hold an activity.
3. Drag and drop the activity into the desired order. The order reflects the left to right order on the story map.
4. Click SAVE.

Add an activity

To manually add a new activity:

1. Click ADD ACTIVITY. The Add Activity card displays.
2. Enter a clear and concise title for your activity in the Name field.
   Tip:The name should be specific enough to convey the activity's purpose at a glance. Avoid overly general names and ensure it reflects the main function of the activity within your application. For example, instead of "Process," use something like "Customer Onboarding" or "Claim Submission."
   
3. (Optional) Enter a description of the activity's purpose or objective in the Goal field.
4. Click SAVE.

Edit an activity

1. Hover over the activity card at the top of the column.
2. Select the pencil icon that appears.
3. Update the NAME or GOAL field.
4. Click SAVE.

Delete an activity

To remove an activity and all its associated actions:

1. Hover over the activity card.
2. Select the trash icon .
3. Finally, click DELETE

Manage actions

You can manage actions by adding new ones, editing existing details, or deleting those no longer needed.

View action details

To review the current configuration of an action card:

1. Click an action card. The action detail screen displays.
2. Review the following details for the action:
   • Status: The current state of the action.
   • Description: A detailed explanation of the task.
   • Type: The specific category assigned to the action.
   • Persona: The user role responsible for the action.
   • Connected design objects: A list of Appian objects associated with the requirement.

Add an action

To manually add an action:

1. Hover over the activity card and click ADD.
   Result: The Add Action card displays.
2. Select a status to indicate the current progress of the action, such as Not Started, In Progress, or Done.
3. In the Name field, enter a clear and concise title.
4. (Optional) In the Description field, enter a detailed explanation of the action.
5. (Optional) Select the action type from the Type dropdown list.
6. (Optional) Select the persona responsible for the action.
7. Click the ADD button to save.

Edit an action

To update the details of an action:

1. Hover over the action card and click the pencil icon .
   Result: The action detail screen displays.
2. Modify the fields as needed.
3. Click SAVE CHANGES.

Delete an action

To permanently remove an action and its associated data:

1. Hover over the action card you want to delete.
2. Click the trash icon .
3. Click DELETE to confirm.

Alternatively, if you are on the action detail screen, click DELETE.

Connect design objects to actions

You can associate design objects, such as record types, process models, reports, and interfaces with any action. This ensures that all relevant objects are linked to the correct actions, making it easier for developers to understand how the application is structured. It also simplifies ongoing maintenance by clearly mapping the relationships between design objects and actions for future reference.

To connect a design object to an action:

1. Click the action you want to modify.
   Result: The action detail screen displays. Here, you will see the connected design objects.
2. Select and complete one of the following options:
   • NEW: This option allows you to add a new object to your application. After creating the object, you can return to the Requirements tab, where the object will automatically be connected to your action.
   • ADD EXISTING OBJECTS: To connect objects that already exist in your application:
     • Open the action detail screen by clicking an action card.
     • Click ADD EXISTING OBJECTS.
     • Select the objects you want to link, such as record types or process models.
     • Click ADD TO APPLICATION to confirm the connection.

Once you're done, the design objects display in the object list. You can view details such as their name, description, last modified by, and last modified date. Use this view to manage the objects associated with the action.

Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close

Fine-tune your requirements

A well-organized story map makes it easier for your team to understand the overall structure and flow of the application. Here are some tips for customizing your story map for clarity:

• Organize the story map: The story map is structured to reflect your application’s user journey and development strategy via activities and actions. Rearrange the activities and actions to ensure they follow these two directions: - Activities are ordered horizontally from left to right to represent the chronological user journey. Rearrange the activities to create a narrative flow that shows the step-by-step path a user takes through your application over time. - Actions are stacked vertically (top to bottom) under each activity. Drag and drop the actions to reorder by implementation priority, placing essential actions at the top and moving more sophisticated ones lower.
• Use clear and descriptive names: Ensure that each activity and action has a clear, descriptive name that reflects its function. Avoid generic names, specific labels help users understand the purpose of each element at a glance.
• Break down complex processes: If an activity becomes too complex, break it down into smaller, more manageable activities. This avoids overwhelming the story map and makes each part of the process clearer.

Export CSV

Exporting your story map to a comma-separated value (CSV) file allows you to share your application's story map with stakeholders or import it into external tools such as Jira or Azure DevOps. This helps you ensure your requirements remain consistent as you move from architecting a solution in Composer to project execution.

To export your requirements as CSV:

1. On the Requirements tab, click EXPORT CSV.
2. Save the generated StoryMapExport file to your local machine.

The exported file contains all the fields nested within their parent activities. Below is a breakdown of what each field indicates:

CSV Field Name	Composer	Jira Field	Description
issue type	Activity / Action	Issue Type	Indicates the hierarchy level. Epic for activities and Story for actions.
issue id	N/A	Issue ID	A unique sequence number for each activity. Map this to the Issue ID column when importing into Jira.
issue key	N/A	Issue Key	A placeholder for Jira’s internal ID. This can remain unmapped during initial import.
summary	Name	Summary	The title of the activity or action.
parent	N/A	Parent/Parent ID	The issue id of the activity associated with a action.
description	Description	Description	The detailed objectives or requirements defined for the action.
status	Status	Status	The current progress of the action, such as Not Started, In Progress, or Done.

The CSV file maintains the hierarchy of your story map. When importing into external tracking systems, map activities to parent items (typically epics), and actions to child items (typically stories or tasks).

Feedback