Service Request SR rm 022

Topics: Software testing, Requirements analysis, Systems Development Life Cycle Pages: 12 (3499 words) Published: April 25, 2015


Service Request SR-rm-022
BSA/375 Eric Secrist
David Beasley

Service Request SR-RM-022

Hugh McCauley, the Chief Operations Officer of Riordan Manufacturing, has placed a service request, SR-rm-022 to integrate all existing Human Resources tools into a single integrated application across all plant locations. The business would like to take advantage of a more sophisticated, state-of-the-art, information systems technology to replace their current Human Resources Information System or HRIS (Riordan Manufacturing, 2006.) In response to this request, this document will outline the following items. The information-gathering techniques and systems analysis tools proposed for this project. Critical factors to ensure the sucessful gathering of information required for the project. Description of the project scope and the areas of project feasibility, and key stakeholders of which requirements will be collected are also discussed. INFORMATION GATHERINT TECHNIQUES AND SYSTEMS ANALYSIS TOOLS

To ensure project success, it is important to gather your key stakeholders together to discuss the system. Key Stakeholders for this project would be key management personnel, IT staff, and users of both the legacy system, and the new system. Your key stakeholders will also be the first level of intelligence gathering performed. Key management personnel such as Hugh McCauley, the COO, who can give the corporate view of the legacy and the new system. HR Director Yvonne McMillian and Payroll/Tax Clerk Anan Richlich can give an exact use case on the HRIS system, and will be the two primary sources of legacy information. Director Yvonne can determine training requirements with the help of the IT department. The IT department can provide information about the legacy system and the capabilities of the current infrastructure of the business. IT can also judge and approve new requirements, privacy structures, and future support needed to maintain the system. Face-to-face interviews will allow information gathering from these key individuals. Questions, an outline of topics, and a primary agenda will be provided beforehand to maximize the use of available time in hectic schedules. We will also be occasionally meeting to discuss the direction the system is heading, timelines, priorities, and key players' lists to ensure success of the project. There is another primary source of information which needs addressing, and this is the group of people who handle information we will be adding which did not exist in the legacy system. This group can submit examples of their files, which will determine another part of the scope of the system, and use cases of how that information is gathered. After this information has been collected, documented and studied, the system development process can begin. The system will be designed using the Joint Application Development (JAD) method. JAD is a prototyping method which gathers our key players listed above, along with other designated individuals to collectively refine business requirements while in conference with the design team of the software and the support team from IT. "The JAD process also includes approaches for enhancing user participation, expediting the development, and improving the quality of specifications. It consists of a workshop where knowledge workers and IT specialists meet, sometimes for several days, to define and review the business requirements for the system.” (Joint Application Design - Wikipedia, The Free Encyclopedia, n.d.) Using this prototyping method ensures that each key factors such as project support and misdirection will not be an issue. This also ensures that the project gets the continued support it will need in the future to succeed. SCOPE AND FEASIBILITY

During the Analysis phase of the Systems Development Life Cycle (SDLC), several areas of project feasibility come into play. As discussed above, determining fully...

References: Cutler, T. P. (2015). Internal vs. external threats - Digital locksmiths. Retrieved from http://digitallocksmithsinc.com/2013/03/27/internal-vs-external-threats/#.VQ5XR-HZBww
Riordan Manufacturing (2006). Riordan Intranet. Retrieved March 15, 2015 from http://ecampus.phoenix.edu/secure/aapd/cist/libraries/IT Service Requests.htm
University of Phoenix 2005-2009
Unified Security Management USM Platform. (2015). Retrieved from https://www.alienvault.com/products?utm_source=Google&utm_medium=CPC&utm_term=%2Balienvault&utm_campaign=SITELINK-ALIENVAULT_USM&gclid=COrosKLUv8QCFRSIfgodGr4AUg
Joint application design - Wikipedia, the free encyclopedia. (n.d.). Retrieved from http://en.wikipedia.org/wiki/Joint_application_design
Bicara, Bedes (2009). Bicara Property. Retrieved January 16, 2010 from http://bicaraproperty.wordpress.com/2009/08/19/scope-of-feasibility-analysis
BambooHR: Human resources software for small and medium businesses. (2015). Retrieved from http://www.bamboohr.com/
Valacich, J. S., George, J. F., & Hoffer, J. A. (2012). Essentials of Systems Analysis and Design (5th ed.). Retrieved from The University of Phoenix eBook Collection.
Dennis, A., Wixom, B. H., & Roth, R. M. (2012). System analysis and design (5th ed.). Retrieved from The University of Phoenix eBook Collection.
Continue Reading

Please join StudyMode to read the full document

You May Also Find These Documents Helpful

  • Service Request SR rm 022 Essay
  • Service Request Sr Rm 022 Essay
  • Service Request SR-rm-022, Part 1 Essay
  • Essay about Service Request Sr Rm 004
  • Service Request SR-rm-022, Part 1 Essay
  • Riordan Service Request Sr-Rm-022 Essay
  • Service Request SR Rm 022 Part2 Essay
  • Service Request SR-rm-022, Part 1 Essay

Become a StudyMode Member

Sign Up - It's Free