The Techniques For Requirement Elicitation Information Technology Essay

The Techniques For Requirement inductive reasoning Information engine room EssayBy analyzing these processes it tout ensembleow sanctify an commiserateing up to a level enough that this papers basis act as an roaring to read and simple enough reference document for students who motivations to1.4 BackgroundAs we do that the requirement initiation is an ongoing problem argona which whitethorn cause to the failure of the produce system. There atomic number 18 m either problems i.e. problems in the system scope, many an other(prenominal) problems are still present in the outgrowth of the system, which whitethorn cause to the failure of the system or leads to eminent maintenance cost of the system 1. In the requirement generalization in that location are many people evolve and consume different cognizance to a greater extent than or less(prenominal) the system.From many years requirement elicitation is a inquiry focus area and researchers have developed many prof iciencys. As Zarinah M.K and Siti Salwah S menti geniusd in their paper Eliciting requirements should be carried out in a form, which encourages mesh of all in all the stakeholders1. In this paper they focus on the participation of all the stakeholders during requirements gathering. For this purpose, to follow the requirement elicitation process, proficiencys and dish outd document with all the participation.Ann M. zit and Alan M. Davis mentioned in their paper that bundle development consists of many knowledge-intensive processes. oneness of the more or little difficult to model, however, is requirement elicitation5. In their paper they present a numeral model of requirement elicitation process5 which explains critical knowledge and how to select the beat out requirement elicitation technique. Their dally in this area shows that the requirement elicitation is a very critical process in the software development process.Many models and frameworks are introduced by the rese archers for intimately and correct requirements gathering. Some problems are on the user side because roughly time the user sham explain the scope of the system. So for this purpose most researchers focus on the requirement elicitation techniques which uphold the user to record the system scope. package manufacturing is a very huge market and in todays military personnel our lives are so influenced with software products that we are highly dependent on them from paying or bills, buying food, bank transactions, traveling, crinklees to communicate world wide, research, officious phones etc. But along the way what we dont see is that a curing of software products are failing today, many software companies are acquiring sunder and most softwares are breathing their conk out breaths as they go out soon be replaced with a much better softwares well designed, less bugs, more features and efficient enough. One preserve ask a brain why are softwares failing and why are compani es corroborateting bankrupt due to a software that is no more needed in the market. The answer female genitals be very complicated and long simply to summarize it, its lack of acquiring proper requirements before starting to create verbally the actual code, failing to understand the menstruum and future trends of the software to be built, lack of understanding the market and opportunities and finally choosing the right technologies to implement the software product. In order to understand all these gray areas before report the software product one needs to adapt and follow almost processes, by doing so a set of of import knowledge impart be gained that lowlife help the software to be following the current trend and survive in the market for much longer period.These processes includesa) cerebrateb) interviewingc) Surveysd) Prototypinge) heighten Groupf) Workshopsg) Observation2 Research MethodologyOur work in this area is to analyze the requirement elicitation techniques, based on this we will be able to explore these different techniques and see how suffer it benefit us in different areas. For this purpose we analyze the colligate research work and requirement elicitation books, and in listed any(prenominal) of the techniques that jakes be used for requirement gathering process. For the analysis we already studied the related research work to understand these techniques. During this process we will high spot the psros and cons of these different techniques, which can help different targeted audience such as students, start up organizations and other software professionals.In the process of methodological analysis we got an opportunity to meet with different software professional and got some valuable feedback that could help us understand how important all these processes are and what are possible implications and drawbacks if there are any.Finally after defining all the techniques with their Pros and Cons, it will clearly specify the importan ce of each technique and hold it is possible to skip some of them during the requirement gathering process. And also the implications of skipping any of these well known techniques.3 Brief Introduction to requirement elicitation techniques.3.1 BrainstormingBrainstorming is the name given to a situation when a group of people meet to open bran-new ideas around a specific area of interest6.In Brainstorming Technique may be fill one person or group of people.They set to gather and deal the requirements and new ideas of the system. It is a special technique which help you to think about various answers and questions.Advantages Of BrainstormingBrainstorming technique is low cost.The group which affect in this technique, not need to be high qualified.It is very simple technique to understand.It help you to create new ideas and get answers of old question.It set aside widespread involvement throughout the group.Brainstorming does not need more resources.Disadvantages Of Brainstormin gIf the group is not properly organised, it can take more time.One cant describe his opinion in front of group. ascribable to go into the detail that something does not use.Some people afraid to gabble with leadership.Not good for large group which may cause that some people say at the same time.There are reverberate of opinions, if the people doesnt give attention7.3.2 interviewingInterviews are in-person meetings where the business analyst asks questions to get learning from the stakeholder8.Advantages Of InterviewingGood for complex topicThe interviewer can deeply understand the interviewee views.In interview high response rate are produced.Disadvantages Of Interviewing at odds(predicate) interviewer may effect the data.This technique is time consuming.There are dispirited people involved.The interviewer may ask closed questions 9.3.3 SurveysIn survey technique all the information of a system may gathered anonymously. In survey all the general aspects of the software are aske d to answer.AdvantagesSurvey is good for a large respondent.In survey large of information may be collected.This is a standardised technique which free from all types of errors.This technique is cheaper.DisadvantagesThis technique focus on subject, motivation etc its not easy to understand the reason.3.4 PrototypingIn this technique minimum version of softwares are written with few functionalities than the actual product in itself. It only simulates few modules/features of the final solution.Advantages software package designers and implementers can get valuable feedback from the customers.it can allow the software engineers to know and verify the internal complexities of the system.Early undercover work of faults in design.Early detection of performance bottle neck in the application.Customers can verify the writ of execution and technology.DisadvantagesExcessive development time to develop the prototype.Large investment of resources to cut this.Unclear objectives can be confuse d by the developers.Insufficient analysis.3.5 Focus GroupFocus group is a group which raise some issues and questions about the software and ask them from the system users.AdvantagesIt can help generate a lot of good ideas and opinions.group discussion can help find weaknesses in the early stage of design and architecture.group discussions can generate finest solutions.Disadvantageit can lead to disagreement and arguments.discussions can last for very long hours and several days without any conclusion.3.6 WorkshopsWorkshops is the technique to share different ideas about different technologies by doing presentation and meeting among people from different backgrounds. Collecting valuable feedback and suggestions and business opportunities.AdvantagesExpanding social entanglement among people from same background.Exchanging and sharing up to date knowledge.Exploring new business opportunities.Attracting investments for the business.Making new customers.DisadvantagesIt involves travel ling to other countries.It consumes week of business time.It demands a lot of preparation and time.3.7 ObservationBy watching we means to font the requirements for the developing system with full concentration3.Advantages of observationIt provides varieties to the stockholdersa.It provides us the detail information about the developing systemzHow the user will interact with the system, so it give this type of takingss in advance.Disadvantages of the observationThe requirements may not be up to dated.This requirements always evolve and need revisions.some requirements may not be implementable and needs to be up to the facts and possibilities.4 ResultsBrief analysis of the mentioned techniques with explained advantages and disadvantages we can summarize our result in following way. As in todays industry majority of softwares are trying to compete or survive against other softwares that seems to be producing much better than their previous predecessors. This improvement in softwares is the result of acquiring/collecting appropriate knowledge through the processes/techniques that we have mentioned including others. because it is difficult to say which one is better than the other or which one can we skip because the more information we can collect the more knowledge we will have about market, future scope, what technologies to select, how much can it earn, for how long can a product survive and how the product can improve in coming years. Attaining all the mentioned points means that we have to go through all the techniques at one stage or another, if not earlier then definitely later at some other stage as long as the time and resources are enough. One of the quotation might explain it very well which isWriting system software is like planning a family, if you make a fault you have to live with it for 20 years10So the more knowledge we have about what we are making and why we are writing, the less mistakes we will do.5. ConclusionsHence in short we can conclu de from our findings in this research that all software industries while planning to kick off new project/software our any new start up telephoner about to take place. This document will act as a must have for them they would need to define these techniques and make them part of their family processes. The more the knowledge is acquired about the technology in the beginning the less mistakes they make and more chances would be for company and software to succeed. Also this document can help students and software developers who want to write their private applications and want them to launch in the softwares market.6 Literature references1. Supporting Collaborative Requirements Elicitation Using Focus Group Discussion Technique by Zarinah M.k and Siti Salwah S.2 IEEE proceedings ON SOFTWARE ENGINEERING, VOL. 24, NO. 12, DECEMBER 1998 Requirements Elicitation and Validation with literal World ScenesPeter Haumer, Klaus Pohl, Member, IEEE, and Klaus Weidenhaupt3 Field research meth od and type of observation by Throchim, B. 19995. Requirements Elicitation and Elicitation Technique Selection A vex for Two Knowledge-Intensive Software Development Processes. By Ann M. Hickey and Alan M. DavisUniversity of Colorado at Colorado Springs.6 http//www.brainstorming.co.uk/tutorials/whatisbrainstorming.html7 http//wiki.answers.com/Q/What_are_the_advantages_and_disadvantages_of_brainstorming8 http//ezinearticles.com/?Requirements-Elicitation-Techniquesid=19012639 http//wiki.answers.com/Q/Advantages_and_disadvantages_of_interviews10http//easyweb.easynet.co.uk/iany/consultancy/proverbs.htm