BSA 385 Week 2

Topics: Agile software development, Waterfall model, Requirements analysis Pages: 5 (805 words) Published: March 1, 2015
Smith consulting was contacted by Kudler Fine Foods to develop a program for a new frequent shopper program. In order to make sure that the project is a success, Smith Consulting will be deciding on a method to follow. A method is described as a guide that is used to structure, plan, and control the process of developing an information system. There are many different methods that Smith Consulting can look into. One of the more popular methods is the waterfall method. Based on the idea that you only move forward in a project. The steps are sequential and must be completed before moving to the next one. There are many variations of waterfall method. Most of them follow something close to the following steps: Conception or Requirements

Testing and Debugging
Conception or requirements is the process in which the project scope is set and the requirements are discussed. This is the beginning stage so everything is brought to the table and the ideas that the client have are passed on to the developers. The design process is when the basic flow of the software is fleshed out. This does not involve coding, but more of a rough draft that gives the programmers framework on how the coding should be laid out. During construction, programmers develop the code and write the actual application. After construction comes integration. This is when all the coding is brought together on the hardware to make sure it works properly. Testing and Debugging is the phase in which problems are addressed and patches are developed to overcome issues. Once the software has been properly tested, the program is installed throughout the company. The final process is maintenance. This can be an on call setup as needed, or a company can have a contract in which someone is available at any hour for a certain length of time. The benefits of waterfall is it is a strict structure to follow and has a rigid guideline that does not deviate. This can also be a disadvantage in that the steps have to be completely finished before moving forward. This sometimes slows down the process. If this is an issue for this project another method to consider would be the Agile method. The Agile Method is a method that is more flexible and allows for the flow to go in all different directions. It was developed by a group of gentlemen and are based on the following principles: Customer satisfaction by rapid delivery of useful software

Welcome changing requirements, even late in development
Working software is delivered frequently (weeks rather than months) Close, daily cooperation between business people and developers Projects are built around motivated individuals, who should be trusted Face-to-face conversation is the best form of communication (co-location) Working software is the principal measure of progress

Sustainable development, able to maintain a constant pace
Continuous attention to technical excellence and good design Simplicity—the art of maximizing the amount of work not done—is essential Self-organizing teams
Regular adaptation to changing circumstance
Benefits of Agile method are the amount of communication, the ability to go back and forth between steps, and the ability to make changes late in the project. Some disadvantages are that it has a lack of structure which in turn often lacks necessary documentation. It is also not a great method for people that haven’t had a lot of time in the field due to the chaos jumping from step to step in a non-sequential order.

One of these 2 methods will more than likely be sufficient for Smith Consulting to get the job done. During the initial consult, Kudler Fine Foods will need to express their desires of functional and non-functional requirements. Functional requirements are actual requirements of the program such as tracking spending of customers, gathering customer information, logging out after a set idle time, etc. Non-functional requirements...

References: Waterfall model. (2015). Retrieved from
Software development methodologies. (2015). Retrieved from
Principles of agile manifesto. (2001). Retrieved from
What is agile model – advantages, disadvantages and when to use it. (2015). Retrieved from
Continue Reading

Please join StudyMode to read the full document

You May Also Find These Documents Helpful

  • Bsa 385 Week 2 Essay
  • BSA 385 KFF Week 2 Essay
  • BSA 385 Week 3 Individual Assignment Essay
  • Bsa/385 Week 3 Essay
  • Bsa 385 Week 3 Essay
  • Frequent Shopper BSA/385 Essay
  • BSA 375 Week 2 Essay
  • Bsa 310 Week 2 Essay

Become a StudyMode Member

Sign Up - It's Free