A proposed workable applied solution should be introduced upon approval from the working organisation/company. If an applicable solution is not possible, a detailed implementation plan should be provided.
ahmed.moner
Q.docx
Q: Implementation
A proposed workable applied solution should be introduced upon approval from the working organisation/company. If an applicable solution is not possible, a detailed implementation plan should be provided.
Testing: Provide system/acceptance testing.
· Test Plan created for future testing. (not implemented)
· System/Acceptance testing is conducted in order to ensure that the defined goals and objectives are achieved successfully. (implemented system)
Installation: For those developing a workable system, provide the software and hardware requirements for installation of the system (not for developing the system). User manual should be provided to show the step by step instructions how to use the system by providing the print screen of the user interface with labels.
In a case where the students could not develop a complete system or a workable system, then, they should provide a system prototype, which will include the system concept.
Support plan: Establish the implementation action plan (for prototype system), and a post-implementation review (feedback) (for workable system).
Business impact of the application
The impact of an applied solution must be discussed in the report. The discussion may consists of content related to business process, cost, productivity, efficiency, effectiveness, timeliness, competitive advantage, value forces, etc.
This is just example for what I need .Do the same
IMPLEMENTATION
This implementation part shows how the trainee turns the previous plans and diagrams of the support requests system into action in Dallah Albaraka. Testing There are three stages of tests to ensure the system function effectively. These tests are unit test, system test and user acceptance test. Unit test: test by focusing on a single unit- single class. System test: test a set of classes that should work together, if they work without any error or not.
Testing
There are three stages of tests to ensure the system function effectively. These tests are unit test, system test and user acceptance test. Unit test: test by focusing on a single unit- single class. System test: test a set of classes that should work together, if they work without any error or not.
Q1. The clearness of information in the system.
Q2. The system is clear in languages
Q3. User friendly interface.
Q4. Ready templates are useful.
Q5. Requests status are clear.
Q6. Workshops of use the system is clear and useful.
Q7. The easiness of use the system.
User acceptance test: this test makes for the system’s end-users to check the develop of the system will work in effective way. The trainee implemented this test by did survey for end users of the support requests system.
Installation
Send the proposal solution to the Information Systems & Services (ISS) department. Then, ISS department will use ManageEngine ServiceDesk software to start developing the support requests system.
User Manual
User manual provides the end user with the steps on how to use the support requests system. First page will be the login to the system then, will display the home page. After that, the user can display the profile page. Then, there is a request page for order new request also receive the solution in the solution page. Refer to Appendix G
Action Plan
The action plan shows what is the system objective, the expected output and the responsible people.
· Rationale of Making The Project
The system created to help the IT department to conduct the project process electronically rather than manually and that make it more efficient and faster.
· Expected Outcomes
1- Make the process of filling the Risk Assessment form available online.
2- Allow the risk assessment manger to keep track of the forms state.
3- Keep backup of the forms in database.
· Responsible Person/Office
The project manager from the Quality department will be responsible in receiving risk forms. The IT department in RCMC will be responsible about the installation and maintenance of the system.
• Availability: the support requests system will be available during working hours and the technicians will help users and solve requests.
• Security: only authorized technicians and end users can access the system by enter their company’s emails and passwords. The server will also be protected by a firewall and updated antivirus program.
• Ease of use: the user-interface will be easy to understand and use by eliminate unrequired cells and by add some features such as: Arabic language, ready templates of the requests.
• Operation: the system will work in any web browsers. This will hence ensure that users are encouraged to use the system without need for specific and additional software.
• Daily backup for database will be available: this will create trust and assurance to end users and this will promote the delivery of services.
• Awareness: the user will know how to access the support requests system and how to use it in effective way.
