Application Specifications
Completing the Details tab

Field

Description

Shape

Select the value that describes the flow shape that this specification represents. (In general, the shape corresponds to a step in the flow.) Options are:

• Correspondence
• Entire flow
• Human based step
• Integration
• Report
• Starting screen
• Subprocess
• Automated step

Trigger

Specify the event method that triggers the specification. This value can also describe how the actor associated with the specification typically accesses the system to perform the work in this step of the flow. Standard values are Email, External Service Call, Image, Letter, Phone, SWIFT, or Web Browser.

Status

Select the implementation status of this specification. This field answers the question about what development state is this specification currently in (for example, whether it is deferred or pending information). The Business Analyst portal uses this field to reflect the overall implementation progress of the application.

This list displays the choices available in the system. The standard statuses are:

• Complete
• Deferred
• New
• Open
• Pending Info
• Withdrawn

You can provide your own values for this list to use with this application. To provide a custom value, create a field value rule specifying the following values and save it in one of the application's RuleSets:

• Applies To: Rule-Application-UseCase
• Field Name: pyCategory
• Field Value: Custom value for this field

To prevent the standard values from appearing as choices, save copies of the following field value rules to a RuleSet in your application, and then set the value of the Availability of those copies to Blocked:

• Rule-Application-UseCase.pyCategory.Complete
• Rule-Application-UseCase.pyCategory.Deferred
• Rule-Application-UseCase.pyCategory.New
• Rule-Application-UseCase.pyCategory.Open
• Rule-Application-UseCase.pyCategory.Pending Info
• Rule-Application-UseCase.pyCategory.Withdrawn

Complexity

Select a complexity that describes the estimated level of effort required to create the specification. Standard values are: Low, Medium, and High. This value is used in the project sizing computation in the Application Profiler.

Protocol

Displayed for a specification of Integration type. Select the system interface protocol for the integration defined in this specification. See Integration — Concepts and terms.

Data Source Exists

Displayed for a specification of Integration type. Select this checkbox to indicate the existence of the other system that the integration defined by this specification connects or responds to.

# Interchanges

Displayed for a specification of Integration type. Specify the number of interchanges expected for the integration defined by this specification. See interchange.

Business Objective

Specify an objective.

Actors

Specify the primary actor that processes the work performed in this specification. Defaults to Any. Click to add more actors.

Subject Matter Experts

Specify the names of people or other resources who are the subject matter experts for this specification. Click to add more rows.

Pre-Conditions

Specify the circumstances that must exist before the steps in the specification can occur. For example 'Customer Service Representative must be logged into the system.' Click to add more rows.

Post-Conditions

Specify the successful end conditions of the specification where the actors' goals are satisfied. A post-condition is the result of the specification completing as anticipated. For example, 'Customer's account is updated to reflect their change of address.' Click to add additional rows.