ReimburseMe: IEEE Website Requirements Specification Document

This document was created to gather document requirements for a new application which would change how a lecturer would claim expenses. Currently the way in which they claim expenses is dated, where they go on their business trip as normal and keep a copy of all receipts that they would making claims for. On their return they would then fill in a claim form where they would then attach the receipts themselves or scan copies. This is a lengthy process and takes time and I feel that with the right requirement elicitation techniques that a more efficient way of doing reimbursements can be created. In order to do this, requirements will be gathered from a number of stakeholders such as the business owner, lecturers themselves as well as other stakeholders such as developers and the finance departments. Once these requirements have been gotten they will then be detailed within the document below and then be inputted into the IEEE document. A number of various elicitation and analysis techniques will be used to gather these requirements. Some of these techniques that will be used will be a brainstorming session where we will be able to gather many different requirements that each stakeholder would feel and need that the application would need. Surveys will then be sent to lecturers within different colleges to get a different viewpoint from each so that each colleges claim expense system will be taken into account so that the application will not just be beneficial to one college. Interviews will then take place with the lecturers and a developer in order to get high priority requirements that will be needed right from the offset of the application and will indicate what they feel is needed in the most as well as any problems that might be encountered throughout the project. Interface analysis will then be used to evaluate the interface types and how the application would operate and a general idea of its layout. This will be done with a use case diagram that will show how the user and the finance department will interact with the system as well as the lecturer themselves that would be the main user of the application. Wireframes would then also be used to show how each page on the application would look. A Moscow analysis will also be used to show the high requirements that will be needed in the application as well as additions that may be added into the project if the budget and timeframe allows