​determining system requirements 546 c2​ ​​Question :The purpose of the requirements determination is to capture a clear and high-level explanation of the system and user requirements stated in the systems request. The explanation consists of a very detailed list of requirements that can be used as input to the analysis phase, which requirements lead into the design of a system. Requirements that focus on business user needs are called business requirements and sometimes user requirements. In the design phase, business requirements evolve into technical requirements, and they describe how a system will be implemented. ​​Requirements can be functional or nonfunctional. A functional refers to a process the system has to perform or information it needs to contain. Nonfunctional refers to system properties such as performance and usability. Requirements are gathered in a report called requirements definition stating all functional and nonfunctional requirements in a text form. An effective way to gather requirements is to jointly have business users and analyst to elicit requirements. There are several techniques to gather requirements such as one-to-meetings, JAD sessions, observation, questionnaires, and prototyping. During requirement meetings, the analyst will ask open or close-ended questions for requirements gathering. ​​ Required Reading Zhu, Z. (n.d). Requirements determination and requirements structuring. Retrieved from http://www.umsl.edu/~sauterv/analysis/6840_f03_papers/zhu/ Interlabs. (2012). Determining System Requirements. Retrieved from http://www.interlabs.bradley.edu/uskov/cis475/Topic_07/Topic_07.pdf Brun, R., & Rademakers, F. (n.d.). Guidelines for developing a good GUI. CERN. Retrieved from http://indico.cern.ch/event/0/session/6/contribution/169/material/paper/0.pdf Hoffer, J., George, J., & Valacich, J. (2002). Modern Systems Analysis and Design. 3th ed. Retrieved from http://www.scribd.com/doc/19286753/Determining-System-Requirements AICPA. (2012). Conducting effective interviews. Retrieved from http://www.aicpa.org/interestareas/forensicandvaluation/resources/practaidsguidance/downloadabledocuments/10834-378_interview%20whiite%20paper-final-v1.pdf IT Project Management Certificate Program. (2004). JAD guidelines. Retrieved from http://www.ksinc.com/itpmcptools/JADGuidelines.pdf Buzzle. (2012). JAD planning and training. Retrieved from http://www.buzzle.com/articles/jad-planning-and-training.html Brandenburg, L. (2013). Using wireframes or prototypes to elicit, analyze, and validate software requirements. Bridging the Gap. Retrieved from http://www.bridging-the-gap.com/using-wireframes-or-prototypes-to-elicit-analyze-and-validate-software-requirements/ McClendon, M., Regot, L., & Ackers, L. (2012). What is prototyping.? Retrieved from http://www.umsl.edu/~sauterv/analysis/prototyping/proto.html Modern Analyst. (2014). What is a context diagram and what are the benefits of creating one? Retrieved from http://www.modernanalyst.com/Careers/InterviewQuestions/tabid/128/ID/1433/What-is-a-Context-Diagram-and-what-are-the-benefits-of-creating-one.aspx Recommended Reading Businessballs. (2013). Business process modeling. Retrieved from http://www.wipro.com/Documents/resource-center/library/process-modeling-simulation.pdf?Mobile=1 ​​Case Assignment One of the potential problems with gathering information requirements by observing potential system users is that people may change their behavior when observed. What could you do to overcome this potentially confounding factor in accurately determining information requirements? What guidelines should you follow? How can you differentiate between facts and opinions in requirements gathering? Why can both be useful? Write this assignment in 4-5 pages. Assignment Expectations Length: Follow the number of pages required in the assignment excluding cover page and references. Each page should have about 300 words. Your assignment will be evaluated based on the Rubric. properly cited references per apa format is a must