1 / 77

Online School Registration System

Online School Registration System. Solomon Ng Pei-Yu Wang Evan Chiu Curtis Wong. Outline. Overview of the system Customer Requirements SPECsoft Team Required Resources System Design User Interface Testing & Quality Assurance. The OSRS System. Two interfaces to the system

sandro
Download Presentation

Online School Registration 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. Online School Registration System Solomon Ng Pei-Yu Wang Evan Chiu Curtis Wong

  2. Outline • Overview of the system • Customer Requirements • SPECsoft Team • Required Resources • System Design • User Interface • Testing & Quality Assurance

  3. The OSRS System • Two interfaces to the system • Student Interface (web based) • Administrator Interface (windows based) • Two types of users: • Students • Administrators

  4. Required Student Functions • Registration • Student Information • Tuition Payment • Information Search • Schedule Function

  5. Required Administrative Functions • Account Administration • Class Schedule Administration • Course Administration • Information Search • Tuition Management

  6. Performance Requirements • Each “click” should respond in no more than 3 seconds • Longer search functions should not take more than 10 seconds • Reasonable uptime is required. • Quick recovery if system is ever down

  7. SPECsoft Team • Implementation of software project will be done using the Waterfall Model

  8. SPECsoft Team • Controlled Decentralized (CD) Team

  9. Resource Estimation • Lines of Code Estimation

  10. Resource Estimation • Engineer Costs based on $40/hr for Engineers and $80/hr for the Manager

  11. Resource Estimation • Three servers will be needed to achieve the performance and reliability required by the customer • Dell PowerEdge 8450 (4 Processors) • Estimated Cost: $148,761.00

  12. Resource Estimation • Microsoft SQL 2000 Server will be used as an off-the-shelf product • Licensing is by CPU • Estimated Cost: $60,000

  13. Resource Estimation • Estimated Total Cost: $253,474

  14. System Design • ERD Modeling • DFD Modeling

  15. User Account Data Object

  16. Courses Data Object

  17. Enhanced ERD • Relation of Courses and users • Data Object Modeling

  18. Data Object Specification

  19. Data Object Specification

  20. Account Object • Student Object • Administrator Object • Information of Student Account • Represent Student in database • Information of Administrator Account • Represent Administrator in database

  21. Course Object • Course Object • Section Object • Information of Course such as name… • Represent Student’s Academic History • Represent Schedule • Information of Specific Section of Course such as time, room… • Represents a Specific Section in Schedule

  22. Catalog Object • Term Object • Catalog Object • Pointer of Course • Represent Term of Student’s Academic History • Pointer of Section Object • Represent Catalog in Database

  23. Multi-Level Data Flow Diagram • Break down System • Focus on Functional Module • Focus on Data transfers • Layered System

  24. System Partitioning • Partition the system into modules

  25. Level 0 - OSRS • Internet Connection • Bank System • Connection • Registration • Catalog Searching • Student information

  26. Level 1 – Menu System • Login System • Main Menu • Submenu

  27. Level 2 – Login System • Check ID • Display Main Menu

  28. Level 2 – Student Info • Display Student information

  29. Level 2 – Search Catalog • Input Query • Search Database • Display Matches

  30. Level 2 – Pay Balance • Check and Charge Card • Display Error • Update Database

  31. Level 3 – Display Pay Page • Get Account Balance form Database • Display Pay Menu • Send information to Charge

  32. Level 2 – Academic History • Selection of Term and Year • Search in Database • Display Error • Display Result

  33. Level 2 - Registration • Display Registration • Add Course • Drop Course • Update Database

  34. Level 3 - Display Registration Page • Get current schedule of account • Communicate with add class and drop class after updating database

  35. Level 3 – Add Class • Check Course ID, Student ID • Update Database • Display Error • Communicate with Display Registration Page

  36. Level 3 – Drop Class • Check Course ID, Student ID • Update Database • Display Error • Communicate with Display Registration Page

  37. Level 0 - Administrator • Window Interface for User • LAN System • Edit Accounts • Edit Catalogs

  38. Level 1 – Main System • Login Menu • Display Main Menu

  39. Level 2 – Administrator Login • Display Login Menu • Check ID • Display Error

  40. Level 2 - Catalog • Display Menu • Search Function • Update Course • Display Course Information

  41. Level 2 - Account • Display Menu • Search Function • Update Account • Display Account Information • Update Student Academic History

  42. Architecture • System Architecture • Client Architecture • Server Architecture

  43. System Architecture Diagram

  44. System Architecture • Data Storage Layer • Functional Service Layer • Communication Layer • Internet • User Interface Layer

  45. Client Architecture Diagram

  46. Client Architecture (Administrator Only) • GUI for system Administration • Access Control • Loader • WIN API Interface • Utility Functions

  47. Server Architecture Diagram

  48. Server Architecture (Cont.) • Application Server • Administration Function • TCD / TD Protocol • Security Controller • User Access Controller • Data Management • SQL API 3. Database Access

  49. Server Architecture • Two Logical Servers • Web Server • Application Server • Common Database Server

  50. User Interface • Common Goals • Easy interface with user • Menu driven system • Consistent look and feel • Two Interfaces • Student (Web) • Administrator (Windows)

More Related