Release and Maintenance Plan, Essay Example

Introduction

The course taken in consideration with the completion of the project that has been documented in line with this requirement is based upon the desire of creating software that would ease-out the process by which an independent healthcare organization takes charge of their responsibility to the society that they hope to serve. Keeping record in line with this mission is an important part of the process by which organizations that serve the most common needs of the community re able to make the most comprehensive procedures by which they assume their role as a service provider to the people. In relation to this, it is very important to understand the fact that the course of development by which this project progresses is based upon the capability of the members of the group to see through the most efficient manner by which they could address the needs of the organization and the stakeholders who are hoping to be served through their operational approaches in the healthcare industry.

Taking into consideration that most of the stakeholders of the organization belong to the lower-end of the economic level of concern, it is essential to note that these individuals have less chances of having old healthcare records that they have incurred in the past years. Although this is the case, it should not be neglected that the simple appointments they may have had with local dentists and other healthcare professionals should also be recorded; in case they really have a clean slate of health records, the program to be created shall provide a basis of f the foundation of the new records that should establish the healthcare report of the clients who are to be served by the organization. The organization of records should be aimed towards imposing a better source of strength and competence on the part of the group of volunteer healthcare professionals as they hope to make the best of their resources in refining the course by which they serve their patients and/or clients. It is also assumed that through this particular program, the service that the organization provides the society it gives attention shall be improved especially in looking through the supplies and particular medical operations that are needed by some of the patients especially in consideration with the health case they are in need of dealing with. In relation to this, the building and the release point of the project to be completed should be well prepared for, hence is to be documented in this presentation.

Summary of Build and Release Process

As mentioned in the previous reports, the team members who are to work on this project are given at least a month to a month and a half to complete the tasks embedded within the set of project plan operations that are seen to have a great impact on how the program is supposed to work for the organization. In line with this building process, it is essential that modern considerations on how EHR or electronic healthcare record programs actually work. As the project being proposed is more dependent on creating a mimicking feature of the said bigger scope of programming, it is essential that the features and functions of EHR be duly examined in line with this plan.

As the building or the creation process begins, it is important to keep record on what points have already been considered and what tasks have already been completed. Since the team members to complete particular tasks, it is essential that during the process of creating the program establishing cooperation among everyone included in the process is given particular attention to. To note this important factor in the process of conditioning the team to complete the project, it is very important to schedule regular meetings that could help put the attention of the creators on the focused target date of completion and the target quality that needs to be addressed in relation to the project being imposed.

Everything must be up to date and recorded properly for the sake of establishing a progress report. This will help the team members create a more cooperative environment among themselves especially that they are to begin to create a working environment that correlates with everyone else and how they complete their given tasks. Keeping an orientation work towards the most complementing aspects of project completion shall put every member of the team on the right track while aiming to complete the entire project within the given time. Before the actual release of the program for the organization’s use, the team should be able to assure the organization of the program’s competence in handling the responsibility it is expected to respond to.

At the point of release, it is important measure the software program’s complete documentation is given towards the end users. Through this, the end users would have full understanding on how the program works at the point of receiving the program itself. What makes the release of the program much easier to handle is the fact that every single detail that the program is to run on is documented and given proper attention to in the manual that is to be released for the end users to check. The release point shall involve a brief dissemination session that would assist the users in seeing through the technical elements that make up the program and be able to work around them. The creators should be able to guide the end users step-by-step during this point hence giving them a proper understanding on what particular technical skills they should master in line with the need to operate the said program.

If in case the organization’s administrators ask for the help of the team in further training the staff into embracing the new course of operation that they should be able to mandate in relation to their responsibility of handling client records, the team should be ready to accept the said responsibility. Being able to give assistance to the new users of the program is a process of assuring that the entire program would work for the best values that the organization deserves to receive. The end client’s values are the most important elements that could determine this project’s success. Hence, as part of the post-release schedule for the project, a feedback campaign shall be launched to be able to collect data that would define the competence of the program when put into actual use. The feedback could from the administrators, the end users or the operators and the clients who are being served. It shall measure the before and now experiences of the said stakeholders as they get involved in the utilization of the created software program. At this point, the creators are to be given the chance to divert or transform any particular weaknesses that come out in the survey hence making the program they created more competent in serving the needs of their clients.

Summary of Release Verification and Sign-Off Procedure

Once the program has been approved and the survey or feedback results have already been addressed, the release of the program for the use of the organization in full swing of operation could be considered. Notably, the verification of the competence of the program should follow a crucial pattern of trial and error that should finally be addressed during the final end of the trial use of the program. Once this is completed then signing of contracts are to be considered hence passing on the responsibility of dealing and operating with the program to the administrators of the organization for whom the program has been basically made.

Review of Maintenance Plan

Serving as a probable source of warranty assurance to the end-users of the program, the team is to give the organization and its staff members an assistance-span that ranges from one to two weeks of constant support. The users shall also be given an online access to the support system that the team shall create and post online. This support system shall consist of the basic FAQs of the about the program that might become a problem of the end-users later on. Aside from the questions, there would also be an online chat that could give proper support to the users in case their question is not listed in the FAQs. Besides that, the manual that is to be handed to the operators shall give a step-by-step basic technical guideline as to how particular issues should be handled with an immediate response. Through this, the final operators are expected to take on the initiative to check on the manual first before calling the problem a subject of emergency that must be called for.

In case the software bugs down or at some point have some technical problems that are beyond control of the operators or online support specialists then a program check up shall be considered whereas a part of the team who created the program shall be asked to look through the system and fix what needs to be readjusted as needed. Relatively though, if the case overpasses the two week period of free support that guarantees the support warranty that the team is responsible for, then the agent or the technical support to be sent over might in some way require fees to be paid on the part of the clients to be served.

Final Summary of Overall Results and Conclusions

The end results of the application of the program are deemed to have a great impact on how the organization performs its duties to the communities it is trying to reach out to. The compelling ways by which such conditions are expected to create a manifesting impact on the organization’s function is based on the program’s capability to handle the crucial stages of recording data and the operators’ capability to handle emergency situations that involves the need to control the situation through technical skills and understanding on the overall performance of the program.

With the manuals and the online support programs prepared for the users of the software, it is expected that technical operators who are to be appointed to mandate the control over the data to be encoded within the system would be given the just assistance as to how they should be able to make a good indication of excellence in responding to unprecedented situations that could involve system crash or recording errors. In this regard, it is then expected that fewer instances of system debugging shall be scheduled hence pointing out to the fact that the operation of the software shall follow a regular maintenance check from the creators of the program within at least the first six months of using it for the organization’s operation. Along with the elements to be checked herein is the safety operations embedded within the system’s code hence protecting all the files kept within the database of the program.

References

Kerzner, Harold (2003). Project Management: A Systems Approach to Planning, Scheduling, and Controlling (8th Ed. ed.). Wiley.

Lewis, James P. (2000). The project manager’s desk reference: a comprehensive guide to project planning, scheduling, evaluation, and systems. p.185.

Horch, John W. (2005). “Two Orientations On How To Work With Objects.” In: IEEE Software. vol. 12, no. 2, pp. 117–118, Mar., 1995.