Application category — Application Profile page
Requirements, Assumptions, Participants, Actors tabs

This tab displays the project assumptions for the development project in which the current application is being developed. Assumptions provide details relating to management of the project, such as division of responsibilities.

To add assumptions or update ones in the list, put the tab into edit mode by clicking Edit. After making your changes, click Save to save them.

If the Edit button contains a lock ( Edit ), you cannot use the edit function unless you provide a password. To unlock the tab, click the button and enter the password in the Password Required to Edit pop-up window. When you have finished your edits, click Save, which returns the tab to a protected status and saves your updates to the application rule. To enable or remove application password protection, see the Advanced Options tab on the Application Overview landing page.

To add an assumption to the list, click and then type in the details about that assumption. To modify an existing assumption, update the text directly in its row. To delete an assumption from the list, click in its row.

This tab displays the project's participants and their roles. This list helps to identify the anticipated resources required to implement the project.

To add participants or update ones in the list, put the tab into edit mode by clicking Edit. After making your changes, click Save to save them.

If the Edit button contains a lock ( Edit ), you cannot use the edit function unless you provide a password. To unlock the tab, click the button and enter the password in the Password Required to Edit pop-up window. When you have finished your edits, click Save, which returns the tab to a protected status and saves your updates to the application rule. To enable or remove application password protection, see the Advanced Options tab on the Application Overview landing page.

To add a project participant to the list, click . The Project Participant window opens in which you specify the details about the participant. To modify an existing role, double-click its row to update its information in the Project Participant window. To delete an assumption from the list, click in its row.

The Project Participant window has the following fields. The information in these fields is displayed in the list on the Participants tab.

Field	Description
Role	Identifies the project role of the participant; for example, Release Manager or User Interface Developer.
Type	Identifies whether the participant belongs to the owning organization (Internal) or is a consultant to the project or is otherwise outside the owning organization (External).
FTE	Identifies how many full-time equivalents (FTEs) have this role on the development project for the application.
Enablement Plan	Identifies the enablement plan required for a person to perform this role in the development project. The enablement plan typically states what training courses someone participating in this project role needs to have to effectively perform the role (such as self-study courses, instructor-led training, and so on).
Responsibility	Describes the responsibilities of the project participant that has the identified role on the project. When adding or modifying a participant in the Project Participant window, you can use the following rich text controls: Icon Result (Arial) Change the font of selected text. (8) Change the font size of selected text Bold the selected text using the <strong> HTML tag. Make the selected text italics. Make the selected text underscored. Change the font color of the selected text. Choose a color from the palette. Set the background color of the selected area. Choose a color from the palette. Convert the selected paragraphs to an unordered list (<ul> tag). Convert the selected paragraphs to an ordered list (<ol> tag).

This tab lists the actors that participate in this application’s business process steps, and details about each actor. Actors perform work in the application. Users, external services, or the system itself are examples of actors.

To add actors or update ones in the list, put the tab into edit mode by clicking Edit. After making your changes, click Save to save them.

To add an actor to the list, click , and then specify the details about that actor. To delete an actor in the list, click in its row.

This tab displays the requirements that have been captured for the current application and the project for which it is being developed.

Think of the set of requirements as the inventory of events, conditions, or functions that must be satisfied and tracked in the development project. They also provide benchmarks against which the application can be tested. A good requirement:

• Describes the need in business terms so that it is easily understood by the implementation team.
• Has an identified category type (such as 'Enterprise standard' or 'Business rule') and level of importance to the application.
• Indicates its current implementation state (such as 'Open' or 'Withdrawn').

Examples of requirements are:

• Remaining budget must be calculated to two decimal points
• Routing Transit Number must be 9 digits long

For each listed requirement, the following information specified for that requirement is displayed. (For more detailed information about some of the columns, see Using the Add/Edit Requirement window section below.

• Requirement ID — Identifier for the requirement.
• Category — Requirement category.
• Importance — Importance to the project.
• Status — Development status.
• Updated — When it was last updated.
• Update By — Who last updated it.
• External Req ID — External tracking system's identifier for this requirement (if the development team uses such a system).
• Association — Applications, flows, and specifications that link to this requirement. Not all requirements have links to them.

Working with requirements on the Requirements tab

To view or modify detailed information about a requirement listed on this tab, click its name. The Add/Edit Requirement window opens displaying the information relating to that requirement. If the underlying rule belongs to an unlocked RuleSet version, you can modify the information in the window.

To enter a new requirement, click the Add Requirement link. The Add/Edit Requirement window opens for specifying the details for the requirement.

Using the Add/Edit Requirement window

When reviewing or entering a requirement, the Add/Edit Requirement window opens and displays the following tabs and fields. When you have updated the information in the window, click OK to save. As it saves the information, the system updates the corresponding Application Requirement rule (or creates the rule, when you add a requirement).

Field	Description
Requirement ID	The identifier used by the development project to refer to the requirement. For example, ER_001_Calculate_HW_Cost.
Short Description	A descriptive phrase about the requirement.
RuleSet	The RuleSet which contains the underlying rule for the requirement. You can save the requirement to any unlocked RuleSet in the current application stack (the current application and its built-on applications). The rule is an instance of Rule-Application-Requirement. (See About Application Requirement rules).
RuleSet Version	The RuleSet version that contains the underlying rule for the requirement.
Details tab	Displays detailed information about the requirement.
Category	The category for the requirement. The standard categories are: Business Rule Change Control Enterprise Standard Functional Non Functional (A project team can set custom values for this list. See Application Requirement rules — Completing the Definition tab for details.)
Importance	A value that indicates the importance of this requirement. The standard values are 1 - Critical, 2- Very Important, 3 - Important, 4 - Desirable, and 5 - Useful. (Your project team can set custom values for this list. See Application Requirement rules — Completing the Definition tab for details.)
External Req ID	Optional. The ID of a requirement stored in an external system that is tracked as a reference to this requirement.
Status	The requirement's current implementation status in the development progress of the application and project. This setting reflects the development state of the requirement, at the current stage of the project's development. It answers such questions as has the requirement been met (Complete), or has the requirement been deferred (Defer)? The standard values are Complete, Defer, New, Open, and Withdrawn. (A project team can set custom values for this list. See Application Requirements — Completing the Definition tab for details.)
Description	The requirement's detailed description. When adding or modifying a requirement, you can use the following rich text controls: Icon Result (Arial) Change the font of selected text. (8) Change the font size of selected text Bold the selected text using the <strong> HTML tag. Make the selected text italics. Make the selected text underscored. Change the font color of the selected text. Choose a color from the palette. Set the background color of the selected area. Choose a color from the palette. Convert the selected paragraphs to an unordered list (<ul> tag). Convert the selected paragraphs to an ordered list (<ol> tag).
Associations tab	Displays a list of the applications, flows, and specifications that are associated with (linked to) the requirement. To remove an association (link) to this requirement for one of the listed items, click in its row. Only the link is removed. The underlying item remains in the system.
Rule Type	The type of item linked to this requirement. Applications, flows, and Application Specification rules can be linked to requirements.
Rule Name	Name of the associated item.
RuleSet	RuleSet that contains the associated item's underlying rule.
Version	RuleSet version that contains the associated item's underlying rule.