Business Requirements

Functional Requirements

Analysis Tools

The University Community needs to be able to analyse the use of the University Search Engine in order to assess how effective the use of the tools to manage content have been and to determine the configuration (or offering) from the University Site Search.  The analysis must be able to provide information in relation to:

1. Navigation / Access route to the search engine itself
2. Search terms analysis
3. Ranking of content versus search terms (i.e. what if results analysis)
4. Business Intelligence Dashboard (POTENTIAL FUTURE REQUIREMENT FOR IA)

Content Management Tools

The University needs a transparent policy backed up with easy to use tool and guidance, in order for content publishers to manage their meta data in order to influence the search engine:

1. Establish a policy on UoE strategy/promotion versus School/Department/Data Ownwer strategy/promotion
2. Establish a theme for use of tools (e.g. avoid using sponsored links/ads as they are very commercial and require continuous monitoring - don't want ads lingering past their useful date)
3. Establish meta data schema, with associated impact on search engine results
4. Establish best practice for web publisher (what templates to use, which tools serve which function)
5. Establish governance (NEED TO EXPAND)

Search Engine Management / Search Results Presentation

The University site search will be a living application requiring configuration and customisation of how it operates and more importantly how it presents the search results:

1. Ability to change facets
2. Ability to manage multiple configurations (if rolling out bespoke searches for data sources or departments)
3. Ability to manage indexing service
4. Procedure for rolling out new schema/forms and raising user awareness of what they tools offer

Security / Provisioning

1. Ability to control impact on search engine of changes to meta data (i.e. ensuring that UoE content is not outstripped by local content)
2. Ability to set authorisation limits on the content (i.e. edlan only, ease authenticated, global).

Project Deliverables

1. Load Testing
2. Content / Schema definitions
3. Assessment of tools

Non-Functional Requirements