Bsa 375 Week 2 Information Gathering Analysis

3198 Words13 Pages
SR-rm-022 Jacques Bonnette BSA/375 July 9, 2012 Joseph Langdon Analysis To determine the requirements of this system, many key stakeholders need to be used to gather information. They include the Chief Operating Officer, Hugh McCauley; the director of human resources, Yvonne McMillian; the employee relations manager, Andrea Gambey; the compensation and benefits manager, Terri Carranza; the payroll manager, Silvija Peterson; mid-level management; low-level management; and members of the staff. These people were chosen because they oversee and perform in the general operation of the HR department and use the applications daily. This makes them invaluable to information gathering. Information Gathering An interview schedule with key decision makers, as well as staff users should be set up. A purpose for each interview should also be defined in order to get a general idea of what information will be gathered from each meeting. The reasoning behind using different members of an organization, is that many users and people will have…show more content…
This will require the programmers to transform the program specifications into working code. Once the HR programs are developed, the systems analyst can use the variety of tests to verify that the HR system is working as intended. Testing is the most important phase because it ensures that many interruptions in operations are avoided, thus ensuring that no revenue or data is lost. It is also important to note that the system analyst needs to develop and finalize the system documentation and user guides. In programming the HR software, the specific modules must be assigned to programmers based on skill level, which was determined in project planning. The HR modules should be separate but be able to pull information from the server and each other as needed (Dennis, Wixom, & Roth, 2012). The modules should

More about Bsa 375 Week 2 Information Gathering Analysis

Open Document