Developing Software for an Organization
In the software engineering field, experts define software development methodologies as those processes that divide the work of software development into sequential, parallel, or smaller sub-processes or steps to enhance project management, product management, and design (Al-Zewairi et al., 2017). The methodologies may involve the prior definition of particular artifacts and deliverables completed and created by project teams to maintain or develop an application. Numerous projects of software development fail to reach their objectives, or a project team may decide to abort the process of developing them. A failed software development project may endanger human life, cause economic issues, and may lose its welfare (Gill et al., 2016). To understand how to develop software for an organization, it is important to compare and contrast commercial, open source, and internally developed software methodologies.
tailored to your instructions
for only $13.00 $11.05/page
Software Development Matrix
|Criteria||Open source||Commercial||Internally developed|
|Cost|| || || || || || |
|Software assurance needs and expectations||In terms of software assurance, opens source software is cheaper and highly reliable||However, expectations, in this case, is to improve security measures for the software||Assurance is that the software is centrally controlled.||Expectations include guaranteeing the effectiveness of the software.||Assurance, in this instance, includes the higher opportunities of customizing software.||Internally developed software is expected to have more experienced software developers|
|Software assurance objectives||To ensure that the product use, procedures, and processes utilized to sustain and produce the software conforms to every standard and requirements specified to govern software.||Ensure that software is free from accidental or intentional vulnerabilities at any time of functionality and lifecycle.||Ensure that the product functions effectively and efficiently to meet its goal.|
|Software assurance coding and development plan||Coding plan would include guidelines that promote tech support.||Coding should ensure that the product matches the strict license requirement||Coding must leave room for customization.|
Evaluation of Software Maintenance
The organization’s software seeks to improve Accounting Systems Accounting needs since the accounting process is currently cumbersome. Some of the features the accounting systems software will have include a basic accounting functionality tool. The tool will manage standard accounting needs such as financial reports, account reconciliation, invoicing, and general ledger (Lenarduzzi et al., 2019). The software will also have an integration feature, which would allow it to easily amalgamate with already existing software. Since the organization has its own processes and strategies in place, the software must be easy to use and should work well with the existing techniques. The software will further incorporate an international utilization tool for its overseas operations.
The schedule will have a specific period in which the software update would be undertaken. To begin with, the schedule would have a list of specific installations that would be implemented every day (Kossek et al., 2019). The schedule would further be flexible to ensure that it can be adjusted. In addition, before implementing the schedule, the plan would be tested for a particular period to find out how it would operate before the actual implementation (Rahman et al., 2021). The potential impact of the software is improved accounting techniques; however, since it is an internally developed software, it has security issues due to the limited resources needed to address the challenges. Despite these reasons, compared to the conventional software, the software has higher chances of success.
Software Maintenance Plan
Since this gadget is supposed to make the accounting process more manageable, it has various important features. Some of its characteristics include a billing and invoicing tool that would remind customers about their payments and produce invoices. The other feature is the payroll tool that would keep track of such elements as employee income tax and deductions (Marushchak et al., 2021). The software will further handle bookkeeping, and in this case, it would reconcile purchases and sales with the general ledger. Additionally, the software will have a reporting tool for producing income statements and trial balances. These characteristics are essential in ensuring the software functions accordingly in its role of traffic management and control.
Currently, there are numerous problems associated with the organization’s accounting needs. The source of this issue can be attributed to the available software, which lacks the necessary capacity to efficiently manage basic accounting processes (Thottoli, 2020). As a result, there have been several mistakes related to the organization’s accounting department, some of which have cost the company financially. The new accounting software has updates that make the accounting process more manageable by automating certain operations. For instance, the billing and invoicing tool has automated the process of sending customers reminders concerning their payments (Matus et al., 2017). The impact of this is that customers can be promptly reminded at specific periods to pay the organization.
To achieve the required goal and priorities of the schedule within a specific time, it is important to plan. The essence of having a schedule is to help the organization understand what it can realistically achieve at a particular time. The implementation schedule, in this case, would include training of individuals directly involved in the use of the software (Rehman et al., 2018). Training programs would ensure that these individuals understand how to use the gadget, thereby making it easier for them to analyze data. The schedule would further involve identifying the most affected sections within the accounting department. Since it is new software, the schedule would include a testing period to ensure that it functions properly. The test is also important in discovering different vulnerabilities of the software.
Al-Zewairi, M., Biltawi, M., Etaiwi, W., & Shaout, A. (2017). Agile software development methodologies: Survey of surveys. Journal of Computer and Communications, 05(05), 74-97. Web.
as little as 3 hours
Gill, A. Q., Henderson-Sellers, B., & Niazi, M. (2016). Scaling for agility: A reference model for hybrid traditional-Agile software development methodologies. Information Systems Frontiers, 20(2), 315-341. Web.
Kossek, E. E., Rosokha, L. M., & Leana, C. (2019). Work schedule patching in health care: Exploring implementation approaches. Work and Occupations, 47(2), 228-261. Web.
Lenarduzzi, V., Sillitti, A., & Taibi, D. (2019). A survey on code analysis tools for software maintenance prediction. Advances in Intelligent Systems and Computing, 165-175. Web.
Marushchak, L., Pavlykivska, O., Liakhovych, G., Vakun, O., & Shveda, N. (2021). Accounting software in modern business. Advances in Science, Technology and Engineering Systems Journal, 6(1), 862-870. Web.
Matus, A., Guerra, E., Fuertes, W., Gomez, M., Aules, H., Villacis, C., & Toulkeridis, T. (2017). On the development of an electronic invoicing solution to integrate SMEs with a tax-collection egovernment-platform. 2017 Fourth International Conference on eDemocracy & eGovernment (ICEDEG). Web.
Rehman, F. U., Maqbool, B., Riaz, M. Q., Qamar, U., & Abbas, M. (2018). Scrum software maintenance model: Efficient software maintenance in Agile methodology. 2018 21st Saudi Computer Society National Computer Conference (NCC). Web.
Thottoli, M. M. (2020). Knowledge and use of accounting software: Evidence from Oman. Journal of Industry-University Collaboration, ahead-of-print(ahead-of-print). Web.