High Quality Institute – Teaching And Learning System (TLS)

Objectives

High Quality Institute (HQI) is an educational firm that provides the students with many different courses in the field of Information Technology. With the advancement of technology and increase in the number of students, HQI has decided to implement a new technological system called Technical and Learning System (TLS). This will comprise of a learning system for undergraduate and postgraduate courses and there will be many features and functionalities that will be implemented in the system.

The primary aim of the project is to provide the students with an advanced and automated teaching and learning system with improved quality and streamlining of activities.

The project will have the following objectives:

• Successful design and development of the undergraduate and postgraduate courses and learning systems.
• Deployment of these two systems and their integration for the deployment of a teaching and learning system.
• Accomplishment of the project tasks and activities with minimal risks and under the estimated schedule and budget.

The report covers the functional and non-functional requirements of the project along with a Work Breakdown Structure (WBS) supported by the table describing project activities and their duration. Project budget, poster and recommendations have also been covered in the report.

• Ability to allow the students, members of the staff and administrative members to securely login to the system.
• Ability to view the undergraduate and postgraduate courses that are available with their details such as duration, fee structure, modules covered etc.
• Assignment of a student to a course along with an advisor.
• Registration of the students for a particular unit by an associated advisor.
• Ability to the students to select an alternative advisor if the one assigned to the student is not available
• Ability of the system to keep a track of the students along with their courses and units and the advisors assigned to them (Dabbagh & Lee, 2014).
• Ability to allow the users to exchange emails between each other securely.
• Ability to communicate with the other users using a network connection and the chat functionality installed in the system.
• Ability to extract reports on the student details, advisor details along with the course information in a customized manner.
• Ability to the system to create data backups at regular intervals to maintain information security and privacy.

• System performance must be maintained so that the users do not face any issues in terms of the lags or faulty connections.
• System availability must be included as one of the non-functional requirements so that the students and the other system users may access the system at any hour and from any location.
• System shall be reliable and must present updated and valid information in the reports that are extracted or the response to any of the actions performed by the users.
• Usability shall be included as one of the prime system qualities so that functional aspects listed above are covered and the user experience attained from the system is high (Broy, 2015).
• Supportability is one of the essential system qualities that must be present and included in TLS so that the changes in requirements, technologies, users etc. can be handled and incorporated as and when required.
• The system must be easy to use and it shall also be easy to maintain. The maintainability of the system must be non-complex so that the updates can be easily installed.
• Security is an extremely important and significant non-functional requirement that shall be present in the TLS so that any of the security risks, threats and attacks are avoided and prevented.

The Work Breakdown Structure and its supported table displayed above illustrate the project tasks and activities and the duration that will be required for the accomplishment of every task. The project will be completed in five phases as displayed in the WBS above. TLS has been kept at the top most level followed by the five phases and then comes the sub-activities that will be covered under every phase. The five phases that have been displayed above include initiation, planning, execution, testing & implementation and closure (Miyahara, 2011).

The 3-level WBS shows the project activities in a hierarchical manner so that the project tasks and activities are completed and accomplished with much ease and the determination of project estimates is also easier (Hans, 2013). 

The critical tasks are highlighted in yellow color:

The project will involve many costs and there will also be many benefits that will be earned as a result. On the 5-year return on investment of the project, the net present value and its calculation has been described below.

Conclusions and Recommendations

The project will be completed in five phases as displayed in the WBS section in the report. The overall duration of the project will be 108 days and the allocation of the schedule has been done on the basis of the effort that will be required for project completion. The project will earn an internal rate of return as 15% that shows that there will be considerable benefits that will come out of the project.

There will be many changes that will be introduced in HQI after the implementation of TLS. The management and administration must be ready to deal with such changes in terms of migration of the business activities to the new system, change in the business operations and many more. There shall be a change management plan that shall be designed in advance for this purpose (Lindberg, 2013). There may also be many of the risks that may emerge during the project. The primary category of these risks will be security risks and attacks. These risks may be introduced due to the increased access points and the operational errors executed by the users leading to enhancement of the security vulnerabilities. These risks shall be handled by using risk management procedure with adequate identification and analysis of the risks. The overall project management must also be efficiently done so that the project goals are met and there are no major risks involved (Kumar & Gregory, 2013).  

References

Broy, M. (2015). Rethinking Nonfunctional Software Requirements. Computer, 48(5), 96-99. https://dx.doi.org/10.1109/mc.2015.139

Dabbagh, M., & Lee, S. (2014). An Approach for Integrating the Prioritization of Functional and Nonfunctional Requirements. The Scientific World Journal, 2014, 1-13. https://dx.doi.org/10.1155/2014/737626

Kumar, M., & Gregory, M. (2013). An exploration of risk management in global industrial investment. Risk Management, 15(4), 272-300. https://dx.doi.org/10.1057/rm.2013.8

Lindberg, D. (2013). Change Management Tools for Systemic Results. Change Management: An International Journal, 12(3), 1-6. https://dx.doi.org/10.18848/2327-798x/cgp/v12i03/50736

Miyahara, T. (2011). Scheduling and Management of Information System Implimentation Prosess: IT Project Management Based on Work Breakdown Structure. Japanese Journal Of Radiological Technology, 67(4), 393-399. https://dx.doi.org/10.6009/jjrt.67.393

Hans, R. (2013). Work Breakdown Structure: A Tool for Software Project Scope Verification. International Journal Of Software Engineering & Applications, 4(4), 19-25. https://dx.doi.org/10.5121/ijsea.2013.4402