It’s generally a good practice to document the requirements that you’ve been so busy gathering. To this point, you have done the following:
- Identified business drivers
- Assessed your current state and future needs
- Identified your Portal Committee, Stakeholders, and SME’s
- Solicited and collected feedback
- Determined top wants/needs/requests
Think of these things as parts of the blueprint for your portal. In order to complete the plans, you still need to get your arms around all of the “Techie” stuff that goes into building this. Technical specifications, configuration, topology, and architectural diagrams all have yet to be done.
Enter the Requirements Traceability Matrix. Building a requirements “Traceability Matrix” allows you to trace back your business, functional, and technical requirements to the Business Cases you made earlier, when pitching the Portal concepts to your executive stakeholders.
Simply put, you should (by now) have a list of the following requirements:
- Business Cases: You made your business cases back in Phase I. You should have a list of these handy.
- Business Requirements: These are the requirements that you flushed out via your end-user surveys.
- Functional Requirements: These are requirements that your committee put into place, plus those features/functions requested by your end users.
- Technical Requirements: These are requirements that must be configured in order to provide all of the above.
Here is an example of one filled out with “high-level” information. You can get as detailed as you wish. The main purpose of this document is to be able to measure your level of success with regards to the goals you set and how you achieved them.