Agile System Analysis

703 Words 3 Pages
Computer based transactions can be a great thing when everything behaves and runs the way it is expected. However there is always the chance that the system will have a glitch, or that the person on the other end does not know how to navigate the system in general. Sometimes computer-based transactions can be more difficult as there is not another person to talk to and explain the situation at hand. Some people I know personally could not fight their way out of a brown paper bag let alone navigate through a computer-based transaction. In my opinion as a customer, I prefer to be able to speak to a real human instead of a computer. Computers cannot always understand the person on the other end whether it is because of accent, lack of education, …show more content…
Technology is ever growing and I do see that we are headed in the direction of computer-based transactions and expanded e-commerce could eventually replace person-to-person contact. However I do not feel as though it is a good idea as it will most likely be the customers themselves that suffer with a lack of person-to-person contact. As learned in the reading, agile methods generally use a spiral model which represents many revisions based on user feedback. The final product eventually will evolve from the use of this feedback and changes made because of the feedback itself. In an agile approach, intense interactivity between developers and individual users is required. Agile system development is unique as it is adaptable to the project at hand and every project is handled differently. Using the agile method allows for many trial runs of the product which in turn helps the finished product be more successful. Since the product is being continuously tested, there is less of a chance that the product will fail in the end. I find this approach fascinating as this is how I would want to create something. When I am building a program in one of my classes, I test it out several times before …show more content…
With spiral models, there may be several versions of the same product released, which will be tested and fixed along the way. After each release, customer input is then taken back to improve the product for a future release. This process will continue however long the product is around. Information for spiral modules received from http://www.tutorialspoint.com/sdlc/sdlc_spiral_model.htm. The role of a Systems Analyst varies from job to job. For the most part they are responsible for investigating, analyzing, designing, developing, installing, evaluating, and maintaining a company’s information systems. The Systems Analyst needs to continuously interact with users inside the company as well as outside vendors. To be a successful candidate as a Systems Analyst one should have technical knowledge, oral and written communications skills, an understanding of business operations, and critical thinking skills. Most often companies want a Systems Analyst to have a college degree in Information Systems, computer science, or business. They also would like the candidate to have some IT background. I can say this is not always the case. I work at the hospital and the Job description for the IT

Related Documents