New trends in software process modeling

Memo
Respected CIO, since our company has planned to implement the methodology of software engineering, I have gone through all the aspects of the decision to state a brief report. The company Raid aldhafiri has maintained a fine reputation in the IT services world. So the decision of choosing Raid aldhafiri for seeking services is a wise one. It has been developing systems that are based on software to carry out acquisitions accurately and automatically. The company develops Intrusion Detection Systems, which is our major concern. It has been developing hybrid detection systems that combine the functionality of anomaly as well as signature based detection to provide complete protection against intrusions and hackers. The company’s unique identity in the concerned service provider world will be an advantage for the execution of the future implementation (Bendraou & Jézéquel, 2010).
Apart from IDS, the company has also reliable record in implementing ERP systems. They have proven track of implementing SAP based systems, which make the network infrastructure reliable. Since our company aims at reviving its network infrastructure by implementing the software engineering approach, Raid aldhafiri has all the professionals who will consider all the aspects that can be improved in order to increase our productivity.
Methodology Chosen
The methodology that has been chosen after careful considerations is Prototyping. The pros and cons of the selected methodology can be better understood if we have an understanding about what prototyping is. The prototyping methodology aims at modeling the system that is required. The prototype model consists of programmed modules of the input and output methodology, maintenance of databases, user interface etc. The approach of prototyping gives the designer space and ideas to make the final system in accordance with the needs. The raw model consists of the initial designs. These designs are tested, and altered with respect to the results of tests. The prototyping methodology is based on software engineering. Software experts do the programming, mostly in COBOL. Prototyping methodology is one of the most reliable methodologies to attain desired results. This approach may take a while, but the final results are just according to needs. So it is a wise decision to go for prototyping methodology in order to avoid any loss in the future after the implementation of the system (Acuña & Sánchez-Segura, 2006).
Problems which are likely to be solved include:
Our main concern is to solve the major problems that are affecting the productivity of our company. The implementation of this strategy can solve the following problems:
1. It can reduce the human involvement. As we have been focusing on making most of the systems automated, this will cut the manpower needed. It can also reduce the risks of human error.
2. The faster system will enhance the growth of the company.
3. It will reduce the cost of development.
These are the major problems, which can be solved after the implementation of this methodology. Other advantages are, network traffic control and filtration, intrusion detection and protection and improved reputation in the market (Cappelli, 2010).
Problems which may be caused
Although the system implementation is not a risk, but there are some future concerns like the implementation of the automated system needs trained staff to handle it. The revival of the network infrastructure through the implementation of this strategy may need to merge a number of departments. The system will need up gradation after some period. The updated system will be in favor of our company but it may be costly.
Recommendation
Considering all the advantages and pitfalls of the methodology, it is recommended that our company should go for the implementation of the methodology. We are in dire need to revive our network, to compete with other companies in the market. It is also recommended that before the execution of the plan, training sessions should be conducted to prepare the employees for the future change.
References
Acuña, S. T., & Sánchez-Segura, M. I. (2006). New Trends in Software Process Modeling.
Canada: World Scientific.
Bendraou, R., & Jézéquel, J. (2010). A comparison of six uml-based languages for software
process modeling. Software Engineering , 10-15.
Cappelli, C. (2010). Reflections on the modularity of business process models: The case for
introducing the aspect-oriented paradigm. Business Process Management Journal .