Joint Application Design (JAD) JAD brings team approach into play gathering users from various departments and IT specialists together in 3-to-1 ratio for a structured work session It allows users to share their opinions on the current system, and gives a chance through shared purpose to come to a consensus on what needs to be changed Teamwork makes one modern technique of systems requirement identification very successful. Joint Application Design (JAD) The old saying - 'Two heads are better than one'- gives a great basis for understanding on importance of group work. Joint Application Design (JAD) is a great addition to the usual requirement determination processes. Therefore, these traditional information-gathering techniques need a counterpart or a substitute that will eliminate, at least in part, problems plaguing the analysis process. Access to emotional feedback is impossible, unless follow-up interviews are scheduled, subsequently adding to the cost. Questionnaires disadvantages: It is hard to create questionnaires that will give all possible answer options customer wants to give There is always a high risk of question ambiguity. They are not as time consuming as interviews are. They are easier to analyse than interviews, because they consist of multiple-choice and true and false questions created with an interpretation system in mind. Questionnaires can reach a large number of users in a short period of time. Questionaires- Cheaper option A cheaper way to get feedback from users is a questionnaire. Even with structuring interview questions, analysts have to do a lot of guesswork when choosing aspects most beneficial for business needs of the organisation Not as many people from various parts of the company are interviewed, because of cost, so there exists high possibility for bias. Usually many follow-ups are necessary for clarification, making the process more expensive. The following disadvantages are evident: It is hard to set convenient time for interviews with all the people able to provide insight into the problem. Traditional requirements elicitation techniques The most common techniques of requirement elicitation are interviews and questionnaires These techniques allow IT professionals to get feedback on the processes of the organisation as they are now, and get a sense of what is lacking in the current system. Results of reviewing industry statistics are there to prove it: '60% to 80% of errors originate in the user requirements and functional specification' stage. Systems development process The systems requirements identification stage is one of the most important integral parts of the process, that can 'make or break' the project. (what are some of the methods looked at last week) Benefits received from adding JAD to currently used information gathering tools include savings on time and resources, and systems requirements written through cooperation of future users and IT development teams. method that brings together business and IT professionals in a structured workshop to determine and discuss system requirements. JAD Joint Application Design (JAD) was developed by IBM in the late 1970s. JAD Workshops There are two main types of workshops that we are interested in as information gatherers: Joint Application Design (JAD) - or Joint Requirements Planning (JRP) - and Brainstorming. Gather data to identify business requirements JAD Workshops
2 Comments
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |