385_Week_2

Week 2 Frequent Shopper Program Part I Since Smith Consulting has been contracted to develop the Frequent Shopper Program for Kudler Fine Foods. There are a couple of things we need to figure out first before we start developing the program. You might be thinking this is easy just start programming it isn't that easy. So there are a couple of methods that we will be talking about that programmers use to help them start the process. Now not only would just a programmer use these but so would a consulting firm like smith consulting. The the methods that we are going to talk about are the Waterfall Method, Spiral Model and Agile Processes. As we discuss these methods we will see both the advantages and disadvantages of both and why one is better the other for companies to use when it comes to doing projects. Sometime we think that being overly nice is a great idea but can it cause bigger issue in keeping deadlines' These are some questions we will answer as we look into some of these methods. One of the last things we will taking about is testing and how that is handled buy each method. At the end you will be able to determine which method you like the best. The waterfall method this is what it looks like it goes back and forth between stage so for example you start out at requirements and then you go to design and then you go back to requirements. The same thing happens with design and phases as you go through a phase you go back to it again the reason for this method is because there is less rework to be done. For example if you to design a program and you go back to the requirements spot then as you are designing it then you won't miss any parts of the program. Sometimes if you just start to program and forget to check on what is need and then you get half way done with the program then you have to go back and reprogram the program or redo it. Which could cost your company not only time but money. Requirements Design Phases Implementation Testing Maintenance The steps above is what is used during the waterfall method phase during my research I have found that this one is the method that a lot of companies lean towards. There are some advantages and disadvantages of the waterfall method lets look at them. Advantages * Simple and easy to use: Phases are executed and completed serially, with specific entrance and exit criteria for * moving between phases. Orderly execution of phases is easy to comprehend. * Practiced for many years and people have much experience with it: The process is well understood, and many people * are comfortable with its execution. * Easy to manage due to the rigidity of the model: Each phase has specific deliverables and a review process. * Facilitates allocation of resources (due to sequential nature of phases): Distinct phases facilitate allocation of * personnel with distinct skills. * Works well for smaller projects where requirements are very well understood: It isn’t necessary to add complexity of * iteration if requirements are well known up front. Disadvantages * Requirements must be known up front: It’s difficult to imagine every detail in advance. Most projects start out with * some uncertainty, and more details are learned as the project progresses. * Hard to estimate reliably: To gain confidence in an estimate, there may be the need to design and implement * parts, especially riskier ones. Estimates become more precise as the project progresses. * No feedback of system by stakeholders until after testing phase: The process does not facilitate intermediate versions. * Stakeholders often need reassurance of progress and confirmation that what is being developed meets * requirements. * Major problems with system aren’t discovered until late in process: The testing phase is where these problems are * found, but it leaves very little time for correction, resulting in potentially disastrous effects on project * schedule and cost. * Lack of parallelism: Each phase is executed to completion. Disjointed parts of the system could otherwise be * completed in parallel. * Inefficient use of resources: Team members can be idle while waiting for others to complete their dependent tasks0 * or for phases to complete. Also, someone good at requirements analysis is not necessarily good at * programming. Now that we have seen both the advantages and disadvantages of the waterfall method let take a look at a couple of other methods that a company could use then we will finish up by talking about how a company would go about testing each method. The second method we are going to look at is Spiral method this method is just like it sounds it is a spiral look at the graph below this shows how the method states and stops. There are also so advantages and disadvantages to the spiral method as well that we will be taking a look at. Advantages of the spiral model * Risks are managed early and throughout the process: Risks are reduced before they become problematic, as they are * considered at all stages. As a result, stakeholders can better understand and react to risks. * Software evolves as the project progresses: It is a realistic approach to the development of large-scale software. * Errors and unattractive alternatives are eliminated early. * Planning is built into the process: Each cycle includes a planning step to help monitor and keep a project on track. Disadvantages of the spiral model * Complicated to use: Risk analysis requires highly specific expertise. There is inevitably some overlap between * iterations. * May be overkill for small projects: The complication may not be necessary for smaller projects. It does not make * sense if the cost of risk analysis is a major part of the overall project cost. Now that we have look at the second method there is one more method we need to look at and that method is agile process. One thing with this model is that I found was strange is that there was a representative that was in the group. In the agile process there is also are also close knit teams that work together as well. Now lets take a look at the adavanges and disadvantages of the agile method. Advantages of an agile process * The project always has demonstrable results: The end product of each iteration is working software. * Developers tend to be more motivated: Developers prefer to produce working artifacts and tend not to like creating * documentation. * Customers are able to provide better requirements because they can see the evolving product. Disadvantages of an agile process * Problematical for large application: Agile methods are more readily used for smaller projects. There is debate * about their utility for large projects. * Documentation output is questionable: Since documentation takes second place, there is a question as to whether * necessary documentation will ever be produced. Now that we have look at all three and how we would test them all. The first one will be the waterfall method. Since this method you go back and forth between implementation ant testing this would be very hard so what I would do is I would go and take the program and put it on one machine and run it and do all the testing that is needed before we implement the program throughout the whole company. The Spiral method is the next method that we would need to test now the way we would test this we would do a test right after we right the code. Then after we do the integration then we would run another test then after that test then implement the program. That to me seems to be a lot of testing wow. I would do all of my coding first then I would verify everything I needed to do then I would use a test machine and do a test on that machine. Last but not least the Agile method of course the method is all over the place in my mind so when you go to test it just test as you go because programmers in this method do not like to document there programs. So it is hard to know what the program is suppose to do. In conclusion, we took a look at three different software engineering methods and how they are used in programming. Now keep in mind these are used in programming to start all the way to finish the program it is almost like a path. The three we chose were the waterfall spiral and agile methods. They all have there ways of doing things but we find that the waterfall method is used the most. Resoucres Software Engineering Modern Approaches SECOND EDITION Eric J. Braude Boston University, Metropolitan College Michael E. Bernstein Boston University, Metropolitan College