This is the final chapter of the body of this report. This report starts with the Introduction and defining the problem identified and solution to the identified problem. Then move on to review others work that’s the present trend or presently available solution to the similar problem identified. As such two systems were identified it’s proved that the proposed system leads the existing ones with rich functions and more features.
Chapter 3 outlines the adopted technology and why they’re selected to implement the solution in a brief fashion. Chapter 4 and 5 are approach & analysis and design respectively. This gives enough idea about the implemented system and the tasks that are performed by the proposed SAIMS-HND.
Chapter 6 is about implementation. It details about how design and analysis are implemented with brief code segment, algorithms and pseudo codes.
Finally Chapter 7 briefs about the approaches how the system is evaluated and it presents the objectives taken into consideration for testing and it shows the test result in graph.
Conclusion as a whole
When the solution introduced by this project gets to the production, there will be more features and more drawbacks compared to the general workflow of the system, as shown in the Table 8.2.
|1||Students can check their payment received information and pending payment information||The system can not support online payment|
|2||Administrator has a full control of the entire system and can provide access level privileges to students and other staff members||When the number of students increase increased the system the administrator’s task will be huge and needs and the system lacks some mechanism to handle it.|
|3||All the query results can be generated in PDF from the system using the PDF Generator module hence it eliminates the manual data typing works and time consuming||Based on the system’s processing power it may consume a reasonable time to generate the report.|
|4||Students can select modules as per their wish and administration doesn’t need to manually send and collect the module selection form from students.||There should have an email sending mechanism in order to notify the students that the module registration when the selection period is activated and disabled.|
Considering the feature-drawback set given in the Table 8.2, inability of accepting online payment and handling the huge set of records is a huge drawback of the system and it may consume the huge processing power. However, as explained this kind of outage does not affect the accessibility of average users. Therefore, it can be concluded that the increase of the unavailability can be mitigated considering the overall workflow of SAIMS
In overall conclusion, although there are few drawbacks on performance and scalability aspects, they can be effectively mitigated, and the Students Academic Information Management System can be used to automate the Academic tasks of Bachelor of Information Technology.
Limitations of the project
While system has reasonable functions it has few limitations and that can be expanded in future. They are,
- This system is limited not to accept online payment.
- Creating an effective way to add users than adding one by one
- Effective handling of repeating modules as there is a possibility for a subject to be repeated.
- Creating a mobile accessing system.
- Effective handling of registering marks and modules collectively rather than entering one by one.
This chapter concludes the report and highlights some characteristics of the proposed solution and the possibility of expending its features in future. Further it’s mentioned, it possibly tries to give a clear picture about the implemented solution and ways and technologies that are used to implement the system.