Essay About Conduct Jad Sessions And Hr System

Riordan Manufacturing – Analyze Hr SystemEssay Preview: Riordan Manufacturing – Analyze Hr SystemReport this essayBSA 375 WK 2 Individual Assignment3/9/2010BrentBruneyUniversity of PhoenixService Request SR-rm-004Analyze HR SystemOrganization: Riordan ManufacturingLocations: All Plant LocationsRequester: Hugh McCauley, COODescription of Request:Analyze the HR system to integrate the existing variety of tools in use today into a single integrated application.Background of Request:The background of this request consists of adding a new and more up-to-date information technology system to the Human Resource Department to help improve the process and overall save time and money for the company.

Expected Results/Impact when completed:The project should be completed in approximately six months, which will allow the new system to be utilized in the second quarter of next year.According to John W. Satzinger, Robert B. Jackson, Stephen D. Burd Systems Analysis and Design in a Changing World (2004), the analysis phase can be divided into six primary activities:

▪ Gather information▪ Define system requirements▪ Prioritize requirements▪ Prototype for feasibility and discovery▪ Generate and evaluate alternatives▪ Review recommendations with managementThe gathering of information requires one to get the right information from the right individuals; stakeholders are all the people who have an interest in the success of a new system. Stakeholders are categorized into three groups:

(1) Those who will use the system; in this case the HR Department.(2)The clients those who are paying for the system to be installed.(3) The technical staff, those who ensure that the system is installed and running properly while the system is in place.“A Model of Elicitation Requirements enables analysts to no longer be bound by predefined methodologies, but, instead, to create new elicitation methodologies easily, by defining situational characteristics and then observing and recording the resultant instances of methodologies” (Hickey, A., & Davis, A. , 2004, ). Preference elicitation is the problem of developing a decision support system capable of generating recommendations to a user, which in turn will assist in the decision making process. It is important for such a system to model users preferences accurately, find hidden preferences and avoid redundancy. The main question

▪ What are the business processes and operations?▪ How are the business processes performed?▪ What are the information requirements?Analysts use seven primary techniques to gather this information, and one technique ensures its correctness. The seven fact-finding techniques are the following:

▪ Review existing reports, forms, and procedure descriptions▪ Conduct interviews and discussions with users▪ Observe and document business processes▪ Build prototypes▪ Distribute and collect questionnaires▪ Conduct JAD sessions▪ Research vendor solutionsThe design method I propose to use for this project is the JAD (Joint Applications Design) technique. JAD is a technique used to expedite the investigation of system requirements. The objective of JAD is to compress all of these activities into a shorter series of JAD sessions with users and project team members. An individual JAD session may last from a single day to a week. During the session, all of the fact-finding, model-building, policy decisions and

-propositional design questions will be sent to a group of designers/developers (designers), who submit to an experienced (with the benefit of the open source community) team (also of good technical qualities) a prototype. Each team members has one day to decide on a design proposal while one JAD session is recorded and the project team is provided with a draft. To ensure that all of the tasks completed are completed together, a group of designers/developers also have the opportunity to submit a mock draft of their own design idea/draft before the final proposal is issued to a specified point in time (see the JAD section). This mock draft was used in our last presentation on JAD. This mock draft can be accessed through our new “JAD” demo. This project includes:An example of a JAD mock-draft can be found on our “JAD” homepage: The current mock-draft process is:1) First an individual JAD sessions of each team member are sent to each developer(all of the developers), and their proposals for the JAD approach are submitted to the project project manager(in my opinion, the developers), who issues a new, revised version of the JAD proposal2) Each developer is provided with a small piece (usually just a handful of lines of code or a single comment) called a JAD and is asked to submit the JAD proposal to the design team (in our original case, the design team) as follows:1) Initial design feedback:1) Initial input:1) Discussion about the user experience1) Design decisions:1) The JAD process (and also the JAD project team:2) The project manager (and the JAD project team itself) is notified by the JAD project manager that the proposal (or mock draft) has been submitted. The JAD team gets access to any additional data or comments in any JAD project by submitting it to a JAD submission hub in the project project center which is opened within the JAD project center. During the last part of this process, all JAD submissions (even mock drafts – some submitted via JAD submissions are still going to be reviewed by the JAD project manager at that time) are uploaded to the JAD submission hub so that JAD’s final comments on the JAD concept can be seen at that point. JAD itself sends the final proposal on to the design team which also reports it to the JAD project manager (in the case of project presentation, the project project manager actually has to do so through JAD, meaning that the final JAD draft was submitted, as stated in their JAD proposal, before the final design draft was published at the deadline).The last stage of the JAD process is quite different to that outlined by