Riordan Service Request Section One
Henry Ford
BSA/375
Date
Foreman Ph.D

Riordan Service Request Section One
Riordan Manufacturing has solicited assistance in facilitating Human Resource tool integration in a system wide application. The system wide application will be compatible with each single location. This particular section will address multiple areas of interest. The areas of interest are as follows: 1. Key stakeholders 2. Requirements for the new system 3. Information gathering techniques 4. System analysis tools and 4. Project scope.
Key Stakeholders
A Key Stake holder is a person that participates in a project or is affected by the outcome of the project. The collaboration of the Key Stakeholder is essential to the refinement of scope. Key Stake holders contribute a significant about of input. This input is gathered by the Project manager or management group. For the purposes of this project our information will be cultivated and drawn from Hugh McCauley, Yvonne McMillan and employees that will be in regular use of the finished product. Hugh is the COO of Riordan. Yvonee is the Human Resources Director. Hugh was the person who made the initial request. As such, the information gathered will originated from Hugh, Yvonne and the “fore mentioned” employees.
Information Gathering
There are information gathering techniques. The techniques are also called tools. The tools are: Use Cases, Interviews, Flow Charts, Requirement Lists. Information can be gathered from Team Meetings, Customer Meetings, Templates and Special Discussions. The meetings are designed to yield the Project “Use Case.” However, in most builds, there will be a numerous amount of Use Cases that are created to accommodate the scope of the project. These “Use Cases” are orchestratively tied together to create a seamless project not only in theory, but in practice and execution. Initially, the information gathering phase is to enhance the methodology of the proposed Use Case. In order to make the project scalable, each Use Case is assigned a descriptive name. The Use Case is also given a reference number. However, the Use Cases are incremental and they are correlated to each specified case. Each Use Case is given a priority level (low, medium, or high). In use cases “priority may be assigned to indicate the relative significance of the use case in the overall system” (Valacich, George, & Hoffer, 2012, p. 150).
There is also value in using Interviews and Requirement Lists to yield a significant amount of information which will contribute to the Use Case. The information must be gathered in a comprehensive and timely manner. These are the key factors to ensure that the Analysis is performed correctly. The success of the project is predicated on the information gathering.
The information which is contributed from the users is compiled carefully. However there should be the developer’s perspective on this information. From the Developers perspective in order to understand the primary and peripheral aspects of the Project. The Developer will have to have a paradigm that will be able to relay common function with applicable code processes.
Project Scope and Feasibility
A scope statement should be written before