Requirements Management Repository

[Joshua Dumas]

I need some advice on best practices when it comes to the following....

BACKGROUND: We are a healthcare company and our customers are our own internal business users - my team is responsible for documenting requirements across multiple systems. Today we are using JSM as a request system where folks within our company document their needs/enhancements. In the JSM form is a field where requirements are documented. 

ISSUE: I feel those business requirements should live in a system/project and shouldn't be a part of an enhancement request. 

That request system also has projects and mandates for which we'll use Confluence to collaborate with our organization. Today, business requirements are stored in a page.

ISSUE: For projects and mandates we use Confluence, here our business requirements are NOT centrally managed - so far we have requirements in JSM (for small enhancements) and Confluence  (for projects and mandates)

Lately, we've introduced a solution architect in the middle of requirements and development. Once Business Requirements are documented a solution architect should solution which systems are impacted.

ISSUE: Not sure where the solution architect would work and where those "tasks" for a development team would live?

Today within JIRA each system within our company has its own project in JIRA. After a solution architect has solutioned the business requirement something should be created in each of those systems to develop based on the requirement and based on the solution architect's design 

Any recommendations on how would....

A) Store requirements in a central location - what would you use for that?

B) Where would you recommend a solution architect work?

C) How would you take the items a solution architect has solutioned and get into those systems/projects???