Case Study - Petrie's Electronics - Week 6

705 WordsSep 23, 20133 Pages
Business Systems Analysis Petrie’s Electronics Case Study - Week: 6 1. Why don’t information systems projects work out as planned? What causes the differences between the plan and reality? * A systems information project may sometimes work outside of its intended plan due to a variety of reasons; notable ones are: * Money * Time * Maintenance Requests A developer’s goal is to create a system that meets criterion laid out by a business and/or to simply out perform its peers. In relation to money, the developer’s goal may be hindered due to the costs of his/her project exceeding the “spending cap.” In addition, time proves to be a factor when new findings mandate certain alterations for a code in progress. Moreover, arising maintenance requests could change the foundation that a system in progress has established. The reality of systems implementation and operation is that no plan is ever concrete because it could un-expectantly or foreseeably change at any given moment. 2. Why is it important to document change requests? What happens if a development team doesn’t? * Database administrators usually support different business units with each unit having their own set of unique procedural requirements. Formalizing and documenting the change request process minimizes the potential for miscommunication between the business units, application development areas and the database administration unit. This is even more important to remote database services providers, meaning that if an organization doesn’t have a formal change request process in place, they’d have to create their own. There are dozens of change management and source code versioning tools available on the market today. The prices can range from thousands to tens of thousands of dollars. 3. When a project is late, do you think that adding more people to do the work helps or

More about Case Study - Petrie's Electronics - Week 6

Open Document