Globalisation and evolution in fields of science have not occurred in a day. Moreover, science is the most dynamic field of research. The process is ever developing and the principals of software engineering is not an exception. Therefore, the motive of software engineering discipline is to continue the culture of developing different application and ensuring smooth execution of those as per requirements. Before discussing the issues faced by software professionals it is important to know the matters they deal with. Centrally, as argued by Jones, Capers (106), for development and maintenance of computer or smart devices’ software engineers are devoted to and make things user efficient. Technically, software applications must comply with systems, discipline and efficiency norms. Hence, within a periodical gap new programming language or software methodology is being invented. Not only the invention, a developer must comply with the throughout maintenance and monitor its performance. In order to do that they have to be disciplined enough to complete series of software engineering process. In case of undisciplined approach, the delivery might have been delayed and other issue from the customers will raise. A disciplined developer is capable of enhancing productivity and satisfies customers at the same time.
In this wide and detailed range of operations it has been noticed that different software systems like cloud computing, big-data, and numerous cyber systems are being consistently innovated to fulfil dynamic needs of customers. The science is itself full of dynamism, in addition to that high market pressure is influencing the engineers to work more for innovation. Therefore, the entire process of software development and maintenance is getting disturbed continuously. According to Casale, Giuliano (39), these challenges are leading towards a disrupted system and demanding more professionals into the disciplined in order to handle the pressure of continuous demand of new software application. The customers are facing issues not in terms of quality of software but the market is seeking for security concerns too. On one hand, there are several quality concerns which are being obvious and to solve all those queries, engineers are compromising with security issues. Therefore, from both the ends the requirements are not met properly. Privacy is important in terms of securing personal data. In this era of globalisation, as discussed in Vitale, Valeria (147), every business organisations is sharing data virtually. The weak development of software leads to incidents of cyber-crime which highlights flaws within the discipline. Developers are partly dependent on consumers in terms of identifying the problem or if there is any security concerns. Actually, until the customers’ are exploring applications the flaws cannot be identified in some cases.
It has been realised that there is a lack of development when it comes to prepare a set of principals regarding development, designing and coding. This loop holes are leading towards delay in delivering projects along with that budget increases. In such cases, the company might faces issues of order cancellation and stakeholder management does not get the desired support from such a flawed software engineering discipline. Above mentioned issues are it has been observed that software development tends to initiate controversy. It is believed that a discussion on flaws helps to generate solutions. The first point which needs to be noticed is that if the discipline is free of flaws there would be no need of discussing such topics. This ensures intensity of the issues related to software engineering. The success rate of industry, which is 30%, itself suggests the flawed nature of its operation for past twenty years. As mentioned before, most of the time there are issues of delay in delivery of order cancellation. Cancellation of order can happen for many reasons including doubts regarding investments, lack of understanding among engineers or lack of expertise to execute the desired outcome. Hence, it can be confidently said that entire system and contemporary practices have become flawed.
There are certain indication which allow us to understand the associations with failures. The first reason of such project failure is the lack of basic conception in designing or difficulties faced by professional regarding understanding the design requirements. Besides, the consistent urge for developing a particular software principal is not fulfilled yet. Practices are haphazard and creates more difficulties the way towards success within this discipline. A large part of engineering methodologies related to software development and maintenance does not particularly address the detail of engineering and theories are not found at a particular source too. Due to the fragmented nature of software theories engineers tend to assume things and execute which leads to unidentified reasons of project failure and increasing dissatisfaction among customers and other stakeholders.
There are several of reading regarding this matter, yet it needs to be realised that with the increasing change in market in terms of customers’ requirements, the occurrence of same project design is almost next to impossible. All the software design is unique and talks time to develop and explore to find out processing faults. However, due to high market demand this known principals are not being followed properly. Above all, deadline is another issue behind faults in desired result. As collected from several system engineer it has been understood that it is an art of adaptation as far as understanding of practices and software products is concerned. The guidance can be found on books of system engineering which offers in detail and well integrated practices and principals for delivering a flawless software solution.
In order to avoid the most recurrent issues regarding software engineering following procedures or practices must be kept in mind.
At first, it must be remembered that software product development needs design based on programme-language that is associated with procedure of software implementation or development. This practice will ensure appropriate application of required software language. Moreover, various literatures like (), highlights the role of organisation in terms of knowledge sharing and training as far as flawless implementation of software engineering practices are concerned.
There is an important part of software development is to design. While designing the software the market need, issues must be remembered. The development must address or intends to solve the ongoing issues the consumers are facing. Delivering a solution means a step towards its mitigation. Customers will not like it to send it back for further amendments. Therefore, to solve that matter while designing the solution engineers must have the plan ready regarding constructing and implementing it without any doubt in mind. In case of any doubt the professionals must address it in level zero while the analysis and planning are going on as if the faulty product is delivered the consequence will be either rejection for taking the order or plenty of complaints. Hence, as described in Gotterbarn, Don (84), it is better to solve the general doubts while it is at discussion stage. Diagrams, designs, blueprints, coding related issues must be resolved and approved from the client in its initial stage only. Therefore, engineers’ effort has serious role to maintain in project outcome. One of the most discussed topic is the unpredictable nature of software applications at after implementation part. In this case, when Agile Software Development technology has been addressed, it has been understood that careful planning and proactive nature of engineers can easily mitigate this issues regarding the practice of faulty discipline.
Therefore, as a major reason ineffective strategies, planning and lack of depth can be considered for such a large proportion of project failure. Therefore, entire design, monetary issues, design, blueprint, trial period all of these must include in practices of software development. In case, the organisational atmosphere is not cooperative enough, those issues must be addressed so that employees can nurture themselves with available sources of knowledge; from both the managers and co-employees. While recruiting professional engineers, HR managers should focus on their knowledge of programming language for ensuring future efficiency.
As per the study of Lanza, Michele, Andrea Mocci, and Luca Ponzanelli (104), to reduce such risk the concept of ‘prototyping’ has become crucial these days. It is associated with a trial run of the developed solution. Both the developers and stakeholders has scope to share opinion regarding mitigating of faults which are subjected to be captured on trial. This process of testing allows the engineers for the second time to reduce the chances of potential risks and identify flaws during design planning. A final design of the software can be applied right after this trial period and solving the identified risk factors. This will allow the engineers to achieve project requirements and they will be able to deliver within the scheduled time. The company will remain cost effective and can save themselves from major risk of losing both the monetary and energy of human resources.
Therefore, to conclude it can be said in an era where every
issue has a digitalized solution software engineers must address every flaws
from their end. It will allow to execute business processes in easier way. The
flaws within the discipline has already been acknowledged and although
solutions are available, software people need to be more system oriented in
order to implement those practices. It is true that they have to face a great
deal of market pressure within a short span of time yet if the right practice can
be evolved then future risks can be avoided. It will be not an issue then to
stick to requirement strictly and yet performing as an efficient professional.
References
Casale, Giuliano, et al. “Current and future challenges of software engineering for services and applications.” Procedia Computer Science 97 (2016): 34-42.
Gotterbarn, Don. “Not all codes are created equal: The software engineering code of ethics, a success story.” Journal of Business Ethics 22.1 (1999): 81-89.
Jones, Capers. “Sizing Up Software.” Scientific American, 279.6. (1998): 104–109.
Lanza, Michele, Andrea Mocci, and Luca Ponzanelli. “The tragedy of defect prediction, prince of empirical software engineering research.” IEEE Software 6 (2016): 102-105.
Libicki, Martin C., Lillian Ablon, and Tim Webb. The defender’s dilemma: Charting a course toward cybersecurity. Rand Corporation, 2015.
Vitale, Valeria. “Transparent, Multivocal, Cross-disciplinary: The Use of Linked Open Data and a Community-developed RDF Ontology to Document and Enrich 3D Visualisation for Cultural Heritage.” Digital Classics Outside the Echo-Chamber: Teaching, Knowledge (2016): 147.
