1 / 36

Student Curriculum Planning System

Student Curriculum Planning System. MSE Project Presentation III Kevin Sung. Overview. Component Design User Manual Assessment Evaluation Project Evaluation Demonstration. Project Overview. Providing curriculum planning service to CIS Advisor and Student.

krhodes
Download Presentation

Student Curriculum Planning System

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. Student Curriculum Planning System MSE Project Presentation III Kevin Sung

  2. Overview • Component Design • User Manual • Assessment Evaluation • Project Evaluation • Demonstration

  3. Project Overview • Providing curriculum planning service to CIS Advisor and Student. • SCPS provides auto-generated course plan function for user. • SCPS can perform real-time prerequisite check for user. • Three course plans per student • Student and Faculty can communicate through the same system. • The system is implemented under the .NET Framework. • ASP.NET, C# and SQL server

  4. Component Design

  5. SCPS Class • This class provide interface for user to login to the system.

  6. PlanView Class • This class provide interface for user to elect course plan to be view. • Advisors are provided with extend function of electing which advisee to work with.

  7. CourseView Class • The Course Plan view for CS student or CS advisee • User can start add or drop course from the active course plan by clicking on “Add course” or “Drop Course” button of the individual course

  8. CourseViewIS Class • The Course Plan view for CS student or CS advisee • User can start add or drop course from the active course plan by clicking on “Add course” or “Drop Course” button of the individual course

  9. CourseContainer Class • This is a custom web control that is use to represent a course in the course plan. • Main logics of adding and dropping courses are coded in the this class

  10. ContainerView and PrintView classes • The ContainerView class provides a “zoom in” view of the course when it is selected from the course plan to be added. • The PrintView class provides a printable table view pf the active course plan.

  11. User Classes—User, Faculty and Student classes • The User class is a super class to the Faculty and Student classes. • These classes represent the user of the system—the advisor and the CIS students

  12. Login Sequence Diagram

  13. Load Plan Sequence Diagram--Faculty

  14. Load Plan Sequence Diagram--Student

  15. Drop Course Sequence Diagram

  16. Add Course Sequence Diagram

  17. Save Plan Sequence Diagram

  18. Display Printable Plan Sequence Diagram

  19. User Manual • The setup instruction and basic operation are included in the documentation

  20. Assessment Evaluation • Unit Testing • Testing through individual web form's functions • Integration Testing • Main test cases are tested from here

  21. Unit Testing • SCPS Web Form • btnSubmit Passed • Login Process execute successfully • PlanView Web Form • Page_Load Passed • grdSelectStudent Passed • DataGrid displays correctly the advisee information for advisor to select. • Search Passed • Successfully Execute query enter by the advisor and display the result on the grdSelectStudent. • ddlPlan Passed • The DropDownList successfully let user to select plan to load. • btnLoadPlan Passed • User prompt to the Course Plan View and the correct course plan is loaded

  22. Unit Testing (Cont.) • CourseView Web Form • Save Passed • The course plan will be save back to the database. • Back Passed • The user is successfully lead back to the PlanView.aspx • Clear Passed • The new course plan is automatic generated and loaded. • Print Passed • A table view of the course plan is successfully shown by opening a new window of the PrintView.aspx webform

  23. Unit Testing (Cont.) • CourseViewIS Web Form • Save Passed • The course plan will be save back to the database. • Back Passed • The user is successfully lead back to the PlanView.aspx • Clear Passed • The new course plan is automatic generated and loaded. • Print Passed • A table view of the course plan is successfully shown by opening a new window of the PrintView.aspx webform

  24. Unit Testing (Cont.) • CourseContainer Class • btnAddCourse Passed • User is leaded to ContainerView.aspx and the list of courses is generated for user to select. • listCourse Passed • The DropDownList has provided courses for user to select. • listTime Passed • The DropDownList has provided available times for user to select. • btnSubmit Passed • The button that has added the course to the active course plan when clicked. • btnDropCourse Passed • The button that has dropped the course to the active course plan when clicked.

  25. Integration Testing • T-001 Login System • Passed • T-002 Add Course to Course Plan • Passed • T-003 Drop Course from Course Plan • Passed • T-004 Generate Report • Passed • T-005 Save Course Plan • Passed • T-006 Load Course Plan • Passed

  26. Project Evaluation • Usefulness of the methodologies used • Unified Modeling Language • Object Constraint Language

  27. Project Evaluation (Cont.) • Accuracy of the estimations • Line of Code • Estimate line of code=3000 • Actual line of code=4977 • C# code=4468 • Auto-Generated Code=823 • Developer Written=3645 • Web Form (HTML, ASP, JavaScript)=509 • Auto-Generated Code=227 • Developer Modified=282 • Auto Generation code from IDE used attribute to the difference of estimation

  28. Project Evaluation (Cont.) • Time Estimation • Estimate • 6.18 staff months • 4.99 months • Actual • Phase I ~55.17 hours (74 days, 592 hours est.) • Phase II ~39.42 hours (31 days, 279 hours est.) • Phase III ~82.42 hours (37 days, 333 hours est.) • Total 177 hours, ~1 week • 10 calendar months

  29. Project Evaluation (Cont.) • Time Estimation (Cont.) • Reason of Difference • Difference in working hours per day. • Slack time are not counted. • Inexperience of the developer on estimating the schedule of the project.

  30. Time Distribution By Phase

  31. Phase I Time Distribution Pie Chart

  32. Phase II Time Distribution Pie Chart

  33. Phase III Time Distribution Pie Chart

  34. Lessons Learned • Good understanding of the tool used and system component employed give a good head starts for the project. • Don’t underestimate the complexity of the business logic. • Using good tools and having a good design are critical to the successful conclusion of the project.

  35. Future Work • Upgrading Software Used during deployment • Boost Performance • More Resources • Import Data from the Better Data Source • Better Data Integrity • Always up-to-date data

  36. Demonstration

More Related