1 / 19

EDUPLAN

EDUPLAN. by AlphaSOFT. AlphaSOFT Members Bayram Çağdaş Kocabıyık Ertan Ertangün Orhan Toprak Assistant: Çağatay Çallı Supporter Company: Portakal Teknoloji. Presentation Outline. Why EDUPLAN is needed? Project Definition Architectural Details of EDUPLAN

maryknight
Download Presentation

EDUPLAN

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EDUPLAN by AlphaSOFT

  2. AlphaSOFT Members • Bayram Çağdaş Kocabıyık • Ertan Ertangün • Orhan Toprak • Assistant: Çağatay Çallı • Supporter Company: Portakal Teknoloji

  3. Presentation Outline • Why EDUPLAN is needed? • Project Definition • Architectural Details of EDUPLAN • Technologies that we plan to use • Current Progress

  4. Why EDUPLAN is needed? • Necessity of standardization between educational institutes • Difficulties faced in the current educational quality management system • A solution: Shift from paper to electronical environment

  5. Project Definition • A sample hierarchical structure which demonstrates the process of creating a course plan

  6. A Sample Hierarchy

  7. Project Definition • A sample hierarchical structure which demonstrates the process of creating a course plan • Definition of the project from user’s view • The contributions of EDUPLAN to create the hierarchical structure • Comparisons and warnings • Archiving of the previous versions • Watching the success of the course plans (using the student feedbacks)

  8. Architectural Details • User interaction • Signup, login, logout module • Abstract purpose module • Curriculum module • Course plan module • Student Feedback module • Comparison module • Versioning module

  9. User Interaction • 4 different user types: • Ministry staff • Managing group (zümre) • Teacher • Inspector • Different pages for different user types • Different authorizations for different user types

  10. Signup, login, logout module • Enable users to signup to the system • User types and authorization levels are determined during signup • Enable existing users to login to the system • Determines the type of the page displayed to the user according to the user type • Enable users to logout from the system

  11. Abstract purpose module • Designed for the usage of ministry staff and managing group type users • Allows ministry staff to create, edit and delete abstract purposes • Authorization of managing group user type is limited to display the abstract purpose only • Works together with versioning module

  12. Curriculum module • Designed for managing group and teacher user types • Enables managing group to create, edit, delete curriculums • Authorization of teacher user type is limited to display the curriculum only • Contains a data type “Expected Gain” • Works together with versioning and comparison modules

  13. Course plan module • Designed for managing group and teacher user types • Enables teacher to create, edit, delete course plans • Authorization of managing group user type is limited to display the course plan only • Works together with versioning and comparison modules

  14. Student feedback module • Designed for inspector and managing group user types • Enables inspector to fill in the results of the student feedbacks to the system • Authorization of managing group user type is limited to display the student feedbacks • Contains alarm feature • Works together with versioning module

  15. Comparison module • Designed for teacher and managing group user types • Two different types of comparisons: • Vertical: between curriculum and course plan • Horizontal: between different course plans • Contains an alarm feature within vertical comparison • Works together with curriculum and course plan modules

  16. Versioning module • Designed for all types of users • Prevents the loss of previous versions of entities which are changed • Useful in conditions where previous entities were more successful • Works together with abstract purpose, curriculum, course plan and student feedback modules

  17. Technologies

  18. Current progress • GUI concept design finished • Databases under development • GUI under development

  19. Thanks for listening

More Related