Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Course Registration System

No description
by

azura Pandi

on 2 January 2014

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Course Registration System

Course Registration System for KKTM Rembau
Sabarina Bt Othman GP02158
Nor Azura Bt Pandi GP02155

CRS
Project Management Plan
OBJECTIVES:
to define the development activities in terms of the phases and iterations required for implementing a computerized class registration system for KKTM Rembau.
FLEXIBLE course structure
to register for online courses
students can modify their course selection by adding or dropping courses
SCOPE:
describes the overall plan to be used for developing the Course Registration System for KKTM Rembau
Constraints
System Investigation
manually by ink and paper, which is very slow and consuming much efforts and time.
help of managing and saving data of KKTM Rembau’s students properly.
To develop a course registration system for Kolej Kemahiran Tinggi MARA (KKTM) Rembau where students select courses and register in the course via the Course Registration System (CRS).
Process Model
Iterative process starts with a simple implementation of a subset of the software requirements and iteratively enhances the evolving versions until the full system is implemented.
5.2 Schedule and Milestone

ASSUMPTION:
allow students to select four course offerings for the coming semester.
each student will indicate two alternative choices in case a course offering becomes filled or canceled.
No course offering will have more than ten students.
In a period of time students can change their schedules
be able to access the on-line system during this time to add or drop courses.
be able to access the on-line system during this time to add or drop courses.
No course offering will have fewer than three students.
A course offering with fewer than three students will be canceled.
Professors must be able to access the on-line system to indicate which courses they will be teaching & also need to see which students signed up for their course offering.
Payments for registration to Entrance Exam conducted by the KKTM Rembau are supposed to be done using DD (Demand Drafts). And then a registered user sends the copy of registration form and the DD to Collage office.
. The transactions are then validated by registration office personal manually.
Scalability: current system do not scale well. For example, a new course added to the mainframe based registration system will require a source code change of the main online registration program
Batch updates vs. (close) Real-time updates: There is no real-time automated update of mainframe registration system data for transactions through the current online registration system. Accumulated transaction records are applied overnight via a scheduled job.

The basic idea behind this method is to develop a system through repeated cycles (iterative) and in smaller portions at a time (incremental).
Risk Management
Each phase consists of development iterations in which a subset of the system is developed.
Reduce technical risk;
Provide early versions of a working system;
Allow maximum flexibility in planning features for each release; and
Enable scope changes to be handled effectively within an iteration cycle.


5.1 Work breakdown Structure
The high level schedule showing project phases, iterations, and milestones is contained in the CRS Schedule.
There is a six-month timeframe to implement a production system of a course registration system from project commencement

Project Roles and Responsibilities
Budget
Hardware and Software Resources Requirement
Construction Method

Object-oriented design using UML for the graphical representation and documentation of the design
Prototyping
Apache Server with MySQL running as the back end database and PHP used as the server side language to implement a limited and functional prototype for the registration system.
The prototype will be a working example of part of the system for demonstration and proof of concept purposes only.
Several high profile hosting companies support mySQL and PHP Comparisons can be drawn later based on performance, execution time, efficiency, memory usage by implementing the system in different servers with various traffic load.
Resource Acquisition Plan
prepared to recruit a Senior Developer with several years PHP experience, and experienced System Integrator, and 2 Implementor/Testers (Junior Grade), with at least 1 years PHP experience
Training Plan
Conducted for the project team prior to the commencement of design activities:
• Object Oriented Analysis & Design
• Introduction to the Rational Unified Process
• Advanced PHP Features

System Release
This Software Development Plan addresses the first 2 releases of the CRS Key features are targeted for the first 2 releases.
Release 1
must contain as a minimum the basic functionality as listed below:
o Logon
o Register for courses
o Interface to Course Catalog Database
o Maintain Student Information
o Maintain Lecturer Information
Release 2
should include:
o Submit Student Grades
o View Grades
o Select courses to teach

The functionality for Release 3 has not yet been determined. It is anticipated that this release will contain enhancements to the existing functionality.
Future replacement of the legacy Billing System and Course Database System is targeted for Release 4 in Year 2018.

6.1 Hardware
6.1.1 Network
College network infrastructure (wired and wireless)
6.1.2 Computers
Monitor Operating System :Window 7 64 Bit Processor
Processor Speed: Core i7 2.4Ghz Processor
Memory Available: 4 GB, 256 MB Nvidia Graphics card
Hard Disk Capacity: 250GB
Database size : 5.26 MB
Front End code : 5 MB
Keyboard
Mouse
Printer

6.1.3 Mainframe
The environment will host the KKTM Rembau databases

.
6.2 Software
6.2.1 Operating Systems
Operating System: Microsoft Windows XP
Front End tools: HTML, CSS, ASP. NET
Back End tools: PHP, Apache, SQL Server

6.2.2 Client Application
Java and Java Script compatible browser:
Netscape IE Opera
6.2.3 Network System
Network software and protocols in order for systems to communicate:
TCP/IP
HTTP
HTTPS
FTP


Gantt Chart
Thank you
Full transcript