|
|
|
|
User Requirement SpecificationObjectiveThe purpose of this work is to ascertain and record the users’ requirements for an EDM / workflow system. The document produced includes details of the existing and proposed IT infrastructure and business practices. It is recommended that the process includes a high level view of the information requirements and document handling patterns of the whole organisation in addition to a detailed study of the area(s) chosen for the pilot(s). The process may take place in two stages, with the high level study being concluded in advance of a decision on the area(s) for the detailed study. In this case, the client may decide if an interim report is required. The User Requirement Specification (URS) is constructed in such a way that it can be used as the basis from which to develop an Invitation to Tender (ITT) as part of the procurement exercise for a system to meet the client's needs. It is an internally focussed document, including discussion of options and explanation of technical processes for reference as appropriate / requested. MethodDesignated people from the relevant areas are interviewed. Notes of the interviews are produced and fed back to the interviewees for agreement. The existing IT infrastructure are documented as needed, together with any plans for upgrading and any impact of an EDM system on these proposals. The outcome of these processes are written up in a User Requirement Specification. This is circulated in draft form for comment and then issued as a final document. DeliverablesA report containing an overview of the client’s information requirements, a User Requirement Specification and a discussion of options / technologies as agreed. An interim report setting out the high level view and making the case for selection of pilot site(s) can be provided in addition if required. Clients who have benefited from this Service:
|
