The Case for this Module invites you to look at the idea of requirements analysis as an expression of more than just a rather mechanical elicitation of “needs

The Case for this Module invites you to look at the idea of requirements analysis as an expression of more than just a rather mechanical elicitation of “needs” — as, in fact, a potentially politically charged process in which social and technical criteria are likely to become intermixed. The following articles generally sums up the standard process of requirements analysis in the context of stakeholder needs. Gottesdiener, E. (2008). YAGNI Your requirements documentation. EBG Consulting, Inc. Retrieved from http://www.requirementsnetwork.com/system/files/YAGNI.pdf CareWorks Technologies. (2011). Eliciting project requirements, tips and techniques. Retrieved from http://www.careworkstech.com/news/eliciting-project-requirements-tips-and-techniques Ouellette and Associates. (2010, January). Ten tips for successfully gathering business requirements. Developing the human side of technology. Retrieved from http://www.ouellette-online.com/article-10Tips.html Sauter, V. (2007) Feasibility. Retrieved from http://www.umsl.edu/~sauterv/analysis/feasibility.htm Ambler, S. W. (2011). Agile requirements modeling. Agile Modeling. Retrieved from http://www.agilemodeling.com/essays/agileRequirements.htm The US government has a major interest in website usability, as a result of a mandate given to it by the Americans with Disabilities Act. DHHS has issued fairly specific guidelines for how usability might be assessed and tested, including the use of specific personas. The site can be used to illustrate and augment knowledge of how requirements are used in systems development. Usability.gov (N.D.) Evaluate your current site: Usability methods. US Department of Health and Human Services. Retrieved from http://www.usability.gov/methods/analyze_current/index.html. Please review all subsections: Evaluate Your Current Site; Learn About Your Users; Task Analysis; Personas; Scenarios; Measurable Usability Goals Case Assignment Read the assigned readings, supplemented if you wish with material from the optional readings and perhaps the supplementary background as well, and even other outside reading you might find by yourself to be useful. Then write a short paper stating your position on the question: “What are the main data collection techniques to elicit requirements? Is one better than another? What is the preferred method?” Case Assignment Expectations Your paper should be short (5-6 pages, not including cover sheet and references) and to the point. It is to be structured as a point/counterpoint argument, in the following manner. You are expected to: Begin this paper by stating your position on this question clearly and concisely Citing appropriate sources, present the reasons why you take this position. Be sure to make the most effective case you can. Then present the best evidence you can, again citing appropriate sources, against your position — that is, establish what counterarguments can be made to your original position. Finally, review your original position in light of the counterarguments, showing how they are inadequate to rebut your original statement. By the end of your paper, you should be able to unequivocally re-affirm your original position. You will be particularly assessed on: Your ability to see what the module is all about and to structure your paper accordingly. Your informed commentary and analysis — simply repeating what your sources say does not constitute an adequate paper. Your ability to apply the professional language and terminology of systems design and analysis correctly and in context; you are expected to be familiar with this language and use it appropriately. Your effective and appropriate use of in-text citations to the assigned readings and other source material to support your arguments.