System Development - Essay Example

System Development - Tools and Techniques Information systems failure refers to the failure of developed software to meet the expectation of supporting the human activities within an organization, for which the software was developed. Information system failure could be partial or total failure, and can occur in various ways. This may include; causing significant delays in terms of its implementation and use in the organization, going beyond the organizational budget, the failure to work out its specifications, or the failure to fit into the organization work processes or structure [1]. Information system failure can occur to any organization, since there are a myriad of causes to such failures. However, the underlying factor is the disruption of the organizational functions and the losses that comes with such system failures. Therefore, this discussion seeks to analyze the various causes of system failures within organizations, with a keen interest on the challenges faced by the system developers, while also seeking to unearth the different techniques that can be applied to address the issue of system failures within organizations. Key challenges facing system analysts and developers resulting to systems failure Information systems failure can occur at different points in the implementation of the information system project within an organization. The information system failures may occur during the pre-implementation, implementation and even in the post-implementation stages of the project. The causes of these failures include: Lack of adequate research During the pre-implementation stage, it is important that a comprehensive research is done, to discover the information needs of an organization, and thus determine the sought of the information system that such an organization requires [2]. However, whenever the initial research is poorly or inadequately done, there are chances that the results do not cater for the needs of the organization, or the system eventually conflict with the structure or the work process of the organization. The result of this is that; an information system that does not fit an organization is prepared, which then results to wastage of valuable time and immense resources for the organization, while its information system needs still remains unmet [1]. A good case study of lack of adequate research and incorrect assumptions, is that of the Nuclear Regulatory Commission, where a system was developed to test nuclear reactors, where an error was made through a miscalculation done in the earthquake testing system by the system developer due to inadequate research regarding the system requirements [2]. Five nuclear reactors were developed using the same system, and the error was discovered months after the nuclear reactors had started being used to produce energy. This posed a great health danger, as well as the disruptions of the services of the utility companies that were depending on these reactors, causing them to turn to alternative sources of energy production, such as petroleum and coal power, which were relatively expensive and inefficient [5]. Lack of adequate training or expertise Another major challenge, which falls in the pre-implementation stage of information system development, is lack of adequate formal training, or lack of expertise on the side of the system developers. The lack of training and expertise results to poor system development, where either some of the information system components are left out, or where the information system prepared does not meet every specification of the organizational needs [2]. The weakness of the system developers, owing to lack of adequate training or expertise can also be demonstrated in the testing stage of the information system, where the testing of the system may not be done, or the testing process may fail, or even pose a great danger, due to some system faults. A case example in point, is that of the National Health Service (NHS) in the UK, where a computer system that was meant to store data for 220 trusts has recently collapsed, causing a loss amounting to ?10 billion [7]. The project was meant to enhance the keeping of health electronic records, enabling digital scanning and integrating the Information systems across the country. The Major IT failure was caused by a change in specifications and technical IT projects [7]. Poor communication and provision of incorrect information The introduction of any information system within an organization will definitely affect a lot of people, considering that an information system is meant to assist in the human functionalities with an organization [1]. Therefore, proper communication strategies are required, to ensure that the introduction of the new information system is well communicated to all the organizational stakeholders, to create the much needed buy-ins. Whenever the information system introduction is not effectively communicated to all the stakeholders within an organization, there is bound to be some resistance from some quarters of the organization, which means that the system will not be supported, and thus its implementation will not be effective. Poor communication may result into the formation of overly complex interfaces and other system access points, which would mean that the designated users of the system will have problems using the system [2]. A case study for example, is the complexity of the US government data system, whose causes were discovered to be the abuse of the system, stemming from very complex user interfaces, as was reported to the government by the U.S. General Accounting Office [5]. This simply serves to indicate that there lacked proper communication strategies between the system developers and the intended users of the system, as well as the failure to provide the relevant training to the end users. System developers’ failures Poor development and documentation practices This are causes of system failures, which emanates from the failures of the system developers. The poor development practices by the system developers is associated with poor and inaccurate assumptions, which are not as a result of poor training or lack of expertise, but purely due to negligence and ignoring some system requirements [2]. This in turn results in a system that is malfunctioned, either at the implementation or at the post-implementation stage. Poor documentation of the system information and processes may result to information system failures. Whenever poor documentation or total lack of documentation of information regarding the information system is done by the system developers, there are higher chances of system failure, since the end users of the system may require such documentation for effective operation of the system. Tools and techniques for preventing failures and improving the development of Information Systems Dynamic systems development method (DSDM) The Dynamic systems development method is a tool that is applied by system developers, to ensure that the system development process is comprehensive and involves all the stakeholders of the organization. The key tenets of the Dynamic systems development method are time, cost, quality and stakeholder-participation, where the system developers have to focus on the business need, thus develop a system that meets the information needs of the business, as opposed to applying their own expertise to develop what they think is appropriate for the organization [6]. Another key principle of the Dynamic systems development method is collaboration, where the system developers must work in constant consultation with the organizational stakeholders and the intended users of the information system, to ensures that the system produced is not complex for the users, while at the same time ensuring that all the stakeholders have bought into the idea and are supporting the system [6]. Quality and timely delivery also forms some fundamental principles of the Dynamic systems development method, where the system developers should focus on avoiding any delays in the development and implementation of the information system, to avoid disorienting the users, while causing unprecedented losses to the organization. Additionally, the main focus of the system developers according to this technique should be on delivering an information system of impeccable quality, which will meet all the needs and the specifications of the organization [6]. For example, this technique was applied in the development of the Systems Development Center for the New York Telephone Company in the 1970s [6]. Joint stakeholder Training This is another major technique that is being applied to prevent failures and improve the development of Information Systems. Comprehensive training of system developers, organizational personnel and customers, is an effective tool that has been found to work well towards preventing system failures, since all the stakeholders are trained from the onset of the project formulation, where they give their contribution and specific information regarding the most suitable information system that the organization should acquire [4]. With the involvement of all stakeholders, it has become possible to develop an information system that is accepted and supported by all, while at the same time being properly understood. This in turn prevents the misuse of the information system by the end users, once it has been implemented, which then prevents the failure of the system. Additional testing and constant inspections The additional testing of the information system for several times before it is implemented, and the constant monitoring and inspection of the system once it has been implemented and launched, is a vital technique that helps to prevent the system failure. Additional testing and inspection in this case means that after the overall system has been launched and is found to be working, another set of tests are done for each and every aspect and functionality component of the system, to determine which specific areas of the system could be faulty or potentially faulty, and then rectify them in the course of the system use to avoid future disruptions [4]. A good example is the case of a munitions manufacturer that was supplying detonators to the US air force, which went ahead to test all the detonators and realized that some had curvy surfaces which would hinder the operability of the detonators [3]. Consequently, the US air force was supplied with the detonators that had had a flat surface only; meanwhile the problem causing the curving was being rectified by the manufacturer. Reference list [1] D. W. Beynon. The diffusion of information systems development methods.” Journal of Strategic Information Systems Vol. 12, pp. 29-46, 2003. [2] Meadowcroft, Ben. (2013). Why Systems Fail. Available: http://www.benmeadowcroft.com/reports/systemfailure/ [3] Fault Tree Construction Guide. (1974). Armament Development Test Center United States Air Force. Available: http://www.eogogics.com/talkgogics/infocenter/systems-failure-analysis [4] J. Berk. (2009). Systems Failure Analysis: A Fault-Tree-Driven, Disciplined Failure Analysis Approach [online]. Available: ASM International: http://www.jhberkandassociates.com/systems_failure_analysis.htm [5] W. Perry. Handbook of Diagnosing and Solving Computer Problems. TAB Professional and Reference Books, 1989. 105 – 106. Print. [6] Tuffs, Stapleton & West, Eason. “Inter-operability of DSDM with the Rational Unified Process.” DSDM Consortium Vol. 1, pp. 1-29, 1999. [7] B. Swanson. Minister orders review after computer meltdown causes chaos in NHS [online]. http://www.express.co.uk/news/uk/433817/Minister-orders-review-after-computer-meltdown-causes-chaos-in-NHS Read More