Riordan Service Request Section One
BSA/375
XXJanuary XXXX

Riordan Service Request Section One The Chief Operating Officer (COO) of Riordan Manufacturing has input a request, asking the IT department to integrating the information system in the Human Resources department (HR). This request is to take advantage of more sophisticated information system technology and integrate it into the HR departments in the different Riordan Manufacturing locations. This service request will highlight several topics. The main topics that will be discussed are, who are the company’s stakeholders that information will be gathered from for requirements. What type of information-gathering techniques and systems analysis tools are to be used and or proposed to aid in the completion of the project request.
Key Stakeholders Mr. Hugh McCauley the COO initiated the service request and he should be the first individual to ask and gather information about his idea of the service request and of what he is looking for about what system requirements for a new Information System for HR. The Director of Human Resources, who is Yvonne McMillan should also be interviewed for her requirements and how does she see what is needed for connectivity to all other business locations using a new Information System. Asking any and all employees who use the current system the company has and what improvements can be done. All of these individuals information is a way of gathering information for this service request. Information Gathering Techniques The primary information gathering technique will be as a proposal to use the Use Case method. A use case is a methodology used in system analysis to identify, clarify, and organize system requirements. The use case is made up of a set of possible sequences of interactions between systems and users in a particular environment and related to a particular goal (Rouse, 2007). Use case should contain activities that are significance to the users. A use case can be related to a particular goal, as it gathers information for analysis. With the utilization of use cases the systems is has descriptive names and areas of information to input by the user. Each use case will be 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). The High priority levels of information will be implemented in the system, while implementing the lower rated use case information. As the system is implemented and tested it will incorporate all user information for stability of the program. An actor or trigger should be assigned to each use case. The actor is the individual inputting information on the system, software prompts from another IS system or another hardware device from an IS system. These interaction with the main system are the triggers on how things can be improved on in the IS system to achieve a specific goal. “Each use case describes how an external user triggers an event to which the system must respond” (Valacich, George, & Hoffer, 2012, p. 149). Use case has elements for information gathering these are listed as preconditions, normal course, alternative course, post conditions, exceptions, and summary of inputs and outputs. During information gathering process the planning of who to ask information from needs to be looked at carefully by the developer of the system. The information will help the developer better understand the function requirements of the system, making for a better understanding of the system that will be implemented and assist in finishing the project. The most common ways to gather information for the use cases are through interviews and JAD sessions. As-is cases will be assessed and looked at for other means of gathering information for this system. With the interview and JAD, further research will be done to gather more information . Project Scope and Feasibility Planning of this project will include a project scope, this scope involves determining and documenting a list of specific goals, deliverable items, individual tasks, costs and project deadlines. It can be the difference maker between a business’ success and its failure. Project scope helps define the different section and functions that are needed to complete the system prior to its development. This scope can also help in these areas of estimate the system, estimate the effort required, estimate the time required which are all important parts of determining the systems ability to be developed. The defining of the functions and needs to be fulfilled by the system being developed. According to Woolridge, Hale, Hale, and Sharpe (2009) “effective scope definition will reduce the impact of scope changes and increase the resource estimate accuracy, thus reducing the likelihood of scoping-caused project failure.” The project scope should be clearly defined to prevent any information from becoming unclear, not understood and to prevent inefficiency. If the project scope is not defined in a way to be easily understand, the process of developing a system can be inefficient and costly. Having the project scope defined will answer questions of operability (will it work) and budgeting of cost. The budget and cost of implementation of the project has to be reasonable for stakeholders to want it done, all personnel who will enfluence the implementation will need to be willing to change with the new system. The feasibility of this project depends on the way that it will solve the problems. Last is the new system being proposed should be introduced slowly for all persons to be able to use the system with minimal errors.

Conclusion As the information is gathered for this project, an in-depth interview of key personnel will give vital information on how to determine the system and use. Utilizing the Use Case, will gather information to be used to help determine the scope of the project. The stakeholders who can be of an enfluence can be a part of the development early, with a better understanding of what the system will be about. Getting involved wll allow personnel be better informed on the project of whom, why and what the system will do.

References
Rouse, M. (2007). Software requirements/Use Case. Retrieved from http://searchsoftwarequality.target.com/definition/use-case
Valacich, J., George, J., & Hoffer, J. (2012). Essentials of Systems Analysis and Design (5th ed.).
Woolridge, R. W., Hale, D. P., Hale, J. E., & Sharpe, R.S. (2009, July). Software project scope alignment: An outcome-based approach. Communications of the ACM, 52(7), 147-152.

Bottom of Form
Top of Form
Bottom of Form