Problem Statement: There is not a way to report, sort, or filter on a set of requirements by Team Ownership, in order to facilitate the updating of the
Team Ownership data to control the access.
Request: Provide an ability to manage Team Ownership data for a set of requirements
• Ability to create a view using the Team Ownership data
• Ability to filter a view using the Team Ownership data
• Ability to sort the view using the Team Ownership data
• Ability to export a set of requirements showing the Team Ownership data
• Ability to capture metrics based on Team Ownership data
• Ability to update the data for Team Ownership using the import capability.
Justification: Team Ownership is used as a mechanism for controlling the ability for the Vendor to update a requirement in addition to the usage of Roles.
If a requirement has a Team Ownership of ABC, the Vendor Link admin role is used to view, update, manage the requirement set. If a requirement has a Team
Ownership of XYZ, the Vendor Requirement Analyst Role controls the ability to view, update and manage the requirement set. Team Ownership is not an attribute.
So it doesn’t function as an attribute. While there is an ability to change the Team Ownership for multiple requirements (either by selecting the
requirements, or by selecting a page/200 requirements), there is not a way to select the requirements—without going through line by line to view the value.
And there is no way to verify that the updates were made—without going line by line to view the data.
Sample workflow(With Business Impacts)
1. XYZ creates a new requirement(s) and fills in the attributes, including status = draft and Current Organization = XYZ
2. Approval event occurs with an accompanying ReqType123
3. ReqType123 is approved by the ApprovingAgency
4. ABC Requirement team update the following attributes and links the requirement(s) to the ReqType123 using the Implemented by Link type.
a. Status = approved
b. Current Organization = ABC
5. Please note, these actions currently do NOT change any permissions for XYZ—they can still modify the requirement, based on how the initial design for controlling access was set up. Ideally, we would like to control access using the value of the Status attribute, however, that wasn’t possible at the time.
6. ABC Requirement team updates Team Ownership – in one of two ways
a. Selecting and opening the requirement and updating Team Ownership within the requirement
b. Selecting several requirements from a view and changing team ownership – this capability is limited:
i. Can only select and change up to 200 – this is difficult for a large number of requirements
1. Also once you select the 200 and change them, it is difficult to see where you are
2. Unable to verify without going through each page and traversing line by line—sometimes there are errors and it doesn’t update
3. With the time lag for the system, this can easily take more than 30 minutes for 1000 requirements
ii. Can’t sort the items in the view by Team ownership, so you have to traverse line by line to see
which need to be updated and select them (this can take time if there are a lot of requirements and links)
iii. Can’t filter the items in the view to display only the items with the Team ownership of XYZ.
iv. Can’t import changes
v. Can’t run an export showing the values—therefore can’t run metrics to verify the status
