In this project, the record-keeping software needs to be developed as a priority for the organization. It will help to keep the data and records of the organization safe. The software needs to be developed with the help of a few stakeholders and some materials will be required for the development of the record-keeping software.
The objective of this project is to develop the record-keeping software is to develop a system that keeps all the data and records of the organization.
Some resources are required for the successful development of the software.
- Hardware- The hardware is the basic requirement for the development of the software. This is necessary to hold the system and operate it successfully.
- Internet- The internet is another essential thing that is needed for the development of record-keeping software.
- Computer system- The updated computer system is required to develop record-keeping software (Tippett, et al., 2017).
Stakeholders and their roles
- Project manager- The project manager is one of the most important stakeholders in record-keeping software development.
- Programmer- The programmer is another stakeholder in the development of the record-keeping software development.
- Developer- The developer is also an important stakeholder in the development of the record-keeping software development.
|Project manager||To supervise the project|
|Programmer||To program the software as per the data storage needs|
|Developer||To develop the initial design of the software|
|Business Analysts||To evaluate the previous and current business data for improving the decision-making process in the organization (Sugandhi, et al., 2021).|
|Project manager||Regarding design, documentation, programming, testing maintenance, and delivery||Email, phone, video conferencing, and meeting||Daily|
|Programmer||Regarding design, documentation, programming, testing maintenance, and delivery||Email, phone, video conferencing, and meeting||Daily|
|Developer||Regarding design, documentation, programming, testing maintenance, and delivery||Email, phone, video conferencing, and meeting||Daily|
|Business analysts||Regarding design, documentation, programming, testing maintenance, and delivery (Oladele,2014)||Email, phone, video conferencing, and meeting||Daily|
The project schedule consists of the steps that are mandatory to complete the successful completion of the development of the record-keeping software. It involves many stages that are mentioned as follows. The timeline to complete the tasks is also mentioned in parallel to
|Design – It refers to the designing of the software that is the blueprint to develop the software.||15 days|
|Documentation- It refers to documentation of the basic design that needs to be implemented.||1 month|
|Programming- The programming of the software is the most essential part of the development of the software.||2 month|
|Testing- The testing is the pre-run stage where the software is tested and checked for its successful working of it.||Month|
|Maintenance- The maintenance of the software is like the after-care of the software once it is developed.||Month|
|Delivery- The delivery is the completion stage of developing the software. It is considered successfully developed software thereafter (Mateen, et al., 2019).||15 days|
Issues management plan
The successful completion of the development of record-keeping software goes through many hurdles. These issues are covered in the table mentioned below:
|Technical||This issue is required to be solved by the technical team.||Few days, a few weeks, or a few months|
|Budget||These are management issue that needs to be settled with the owner.||Few days, a few weeks, or a few months|
|Schedule||The schedule is an issue that needs to be timely managed to avoid exceeding the project deadlines.||Few days, a few weeks, or a few months|
|Integration issues||The integration issues of the software are crucial this that need to be looked after by the project manager for preventing problems at a later stage.||Few days, a few weeks, or a few months|
|Communication breakdowns||The communication breakdown is also another problem that I solved by the programming, development, and testing team when occurs.||Few days, a few weeks, or a few months|
|Mismanaged timelines||The schedule is an issue that needs to be timely managed to avoid exceeding the project deadlines.||Few days, a few weeks, or a few months|
|Feature overload||The software that needs to be developed for record-keeping needs not to be overloaded with features. This is the responsibility of the developer.||Few days, a few weeks, or few months|
|Lack of specification in the features||The lack of specification in the features of the software should be taken care of by all the stakeholders for the successful development of the software.||Few days, a few weeks, or few months|
|Lack of alignment between developer and user||The lack of alignment is also an issue for the development of the software. This is solved by the proper communication between the developer and the user (Fritz & Müller,2016).||Few days, a few weeks, or few months|
Fritz, T., & Müller, S. C. (2016, March). Leveraging biometric data to boost software developer productivity. In 2016 IEEE 23rd international conference on software analysis, evolution, and reengineering (SANER) (Vol. 5, pp. 66-77). IEEE.
Mateen, A., Zhu, Q., & Afsar, S. (2019). Record keeping system of bugs for software quality assurance. International journal of advanced smart convergence, 8(4), 207-213.
Oladele, F. (2014). Record Keeping To Book Keeping To E-Records: What Next? IOSR Journal Of Humanities And Social Science (IOSR-JHSS), 19(7), 120-124.
Sugandhi, R., Soumya, V., Jha, M., Sanyasi, A. K., Adhikari, A., & Awasthi, L. M. (2021). Development of electronic record-keeping software for remote participation in Large Volume Plasma Device upgrade using Angular 2 and NodeJS web technologies. Review of Scientific Instruments, 92(7), 075102.
Tippett, E., Alexander, C. S., & Eigen, Z. J. (2017). When Timekeeping Software Undermines Compliance. Yale JL & Tech., 19, 1.