Question

Please re-write paragraphs.

-In the following slides I will be discussing the three different methods that are for determining the requirements for gathering information. I will discuss the advantages and disadvantages of each method, along with explaining the Level-0 Data Flow Diagram, the last thing I will be discussing is the method in which I chose for determining the requirements for the student furniture webstore that the Pine Valley Furniture store decided to plan and implement first.

- The above slide has the three different methodologies listed that are used for requirements gathering. They are the traditional, contemporary, and radical methodologies. I am going to discuss what’s involved in each methodology along with what are the advantages and disadvantages of each methodology.

- The traditional method of doing things is the old way of doing things in which many organizations still use today. I think this method should still be used to some extent because I feel you still get good solid information and feedback from your users. In the traditional way the organization can interview people to see what the ”issues and operation of the current system” and the system coming. (Valacich & George, 2020, p. 148) Traditionally you would interview a lot of different people that have different “needs to find synergies and contrasts among system requirements “(Valacich & George, 2020, p. 148) One of my favorite traditional methods are sitting in on workers as during their daily routine and seeing how they perform their daily tasks and what other tools they need to accomplish them. One last traditional method is to go over old “business documents” so that the organization can see “issues, policies, rules, and directions”. The traditional method also has (examples that are solid that show the use of the organizations data and information). The advantages of traditional methodology are you will get more (solid and correct information from your users when you observe them during their daily work tasks, when the documentation and procedures are analyzed they will give information about the organization as well as identifying the current system requirements, it allows the analyst to work with having the procedures and documentation in front of them to refer back to, the documentation will list everyone who is involved in the current system.)The disadvantages of directly observing employees are that it can be (costly and take up too much time, procedures come up missing, users are repeating what’s already been done, the procedures and documents being analyzed may need to be updated along with they may be hard to find, and one last disadvantage is that the documents and procedures may say one thing about operation but the organization operates in an entirely whole different way.

- The contemporary method is similar to the traditional method. In the contemporary method is where “managers, analysts, users, and other members” that are needed are brought together in a JAD which is a Joint Application Design that is an arraigned process where “very intense meetings” take place to identify and go over the “systems requirements.” (Valacich & George, 2020, p. 159-160) The other thing that happens during use of a contemporary method are (prototypes are developed for the system that clearly define the system requirements are understood in solid terms by showing working versions of system features.) (Valacich & George, 2020) The advantages of the contemporary methodology are in using the Joint Application Design it will allow the users to effectively take place in the process, the organization will have a more solid and precise statement of the systems requirements, and everyone will have a better comprehension of the organizations goals.) ("Prezi", 2020). Some other advantages of the contemporary methodology are in using prototyping because this is where at the (beginning stages of the development prototyping lets the identification of the potential risks involved and to rectify the errors, also when the “developers and testers” are making the prototype they can very easily make it to accommodate what the customer wants and needs with being able to make adjustments when necessary, as well as when showing it to the customer this is the perfect way to do so, and when using prototyping the “developers have a great chance of getting much wanted “valuable feedback” from the users so this will save them a great deal of time, effort, and money down the road. According to "Velvetech"(2020), The disadvantages of using the contemporary method are in using the (JAD) Joint Application Design is the more expensive way to go because there are many more people involved and there is not enough resources available.) ("Prezi", 2020). The disadvantages of using prototypes are that “the initial result of a prototype is never the market-ready product”, (making changes all the time will make so there are many designs and changes within the code, and this will slow down the flow in which the employees are doing their tasks), ("Velvetech", 2020) and sometimes “software vendor that covers for the cost of a prototype.” According to "Velvetech"(2020),

Answer 1

-In the subsequent slides i will be able to discuss the three different methods that are for determining the necessities for gathering information. I will be able to discuss the benefits and drawbacks of every method, together with explaining the Level-0 Data Flow Diagram, the final thing i'll be discussing is that the method within which I chose for determining the necessities for the scholar furniture webstore that the Pine Valley Furniture store decided to plan and implement first.

- The above slide has the three different methodologies listed that are used for requirements gathering. they're the normal, contemporary, and radical methodologies. i'm visiting discuss what’s involved in each methodology together with what are the benefits and drawbacks of every methodology.

- the normal method of doing things is that the old way of doing things during which many organizations still use today. i feel this method should still be wont to some extent because I feel you continue to get good solid information and feedback from your users. within the traditional way the organization can interview people to work out what the ”issues and operation of this system” and therefore the system coming. (Valacich & George, 2020, p. 148) Traditionally you'd interview plenty of various folks that have different “needs to search out synergies and contrasts among system requirements “(Valacich & George, 2020, p. 148) one amongst my favorite traditional methods are sitting in on workers as during their daily routine and seeing how they perform their daily tasks and what other tools they have to accomplish them. One last traditional method is to travel over old “business documents” so the organization can see “issues, policies, rules, and directions”. the standard method also has (examples that are solid that show the employment of the organizations data and information). the benefits of traditional methodology are you'll get more (solid and proper information from your users once you observe them during their daily work tasks, when the documentation and procedures are analyzed they'll give information about the organization still as identifying this system requirements, it allows the analyst to figure with having the procedures and documentation before of them to refer back to, the documentation will list everyone who is involved within the current system.)The disadvantages of directly observing employees are that it may be (costly and take up an excessive amount of time, procedures come up missing, users are repeating what’s already been done, the procedures and documents being analyzed may have to be updated together with they will be hard to seek out, and one last disadvantage is that the documents and procedures may say one thing about operation but the organization operates in a completely whole different way.

- The contemporary method is analogous to the standard method. within the contemporary method is where “managers, analysts, users, and other members” that are needed are brought together during a JAD which could be a Joint Application Design that's an arraigned process where “very intense meetings” occur to spot and re-examine the “systems requirements.” (Valacich & George, 2020, p. 159-160) the opposite thing that happens during use of a up to date method are (prototypes are developed for the system that clearly define the system requirements are understood in solid terms by showing working versions of system features.) (Valacich & George, 2020) the benefits of the contemporary methodology are in using the Joint Application Design it'll allow the users to effectively occur within the process, the organization will have a more solid and precise statement of the systems requirements, and everybody will have an improved comprehension of the organizations goals.) ("Prezi", 2020). another advantages of the contemporary methodology are in using prototyping because this is often where at the (beginning stages of the event prototyping lets the identification of the potential risks involved and to rectify the errors, also when the “developers and testers” are making the prototype they'll very easily make it to accommodate what the customer wants and wishes with having the ability to form adjustments when necessary, further as when showing it to the customer this is often the proper thanks to do so, and when using prototyping the “developers have an excellent chance of getting much wanted “valuable feedback” from the users so this can save them an excellent deal of your time, effort, and money down the road. in keeping with "Velvetech"(2020), The disadvantages of using the contemporary method are in using the (JAD) Joint Application Design is that the dearer thanks to go because there are more people involved and there's not enough resources available.) ("Prezi", 2020). The disadvantages of using prototypes are that “the initial results of a prototype isn't the market-ready product”, (making changes all the time will make so there are many designs and changes within the code, and this can prevent the flow during which the staff do their tasks), ("Velvetech", 2020) and sometimes “software vendor that covers for the price of a prototype.” consistent with "Velvetech"(2020),