Moodle Proposal
Moodle Proposal
Moodle Proposal
1
Objective of the Project:
To design and develop a search engine friendly Web 2.0 LMS integrated platform for The Centre for
Business and Professional Excellence having a very fresh, creative and delightful theme. The basic
concept of the website is to provide an online platform for users, especially students to get access to
online learning courses.
Scope of Work:
The scope of work in the discussed project includes the development of following modules.
2
Google and Yahoo perspectives shall be
undertaken.
W3C validation HTML & X-HTML Linking According to W3C
Website Development Description
Table less website A table less, div based website will make it
more search engine friendly.
Google Analytics Integration of Google Analytics for statistical
data of visitors on the website
Integration with CMS / back-end This will be done in the best manner
Back-end & Moodle based CMS Development
Edit/remove/add Courses As per site requirement
Edit/remove/add Images As per site requirement
Edit/add/remove Meta data/Title tags For Better search engine ranking
Edit/add/remove Alternative tags/Anchor tags For Better search engine ranking
Edit/add/remove Banners As per site requirement
Edit/add/remove Blogs/Forums For better interactivity, search ranking and site
features.
Manage Videos As per site requirement
User Management For managing the members of the website.
Site Functionality
Student
•The Student can then select from a range of courses (which have been uploaded by Teacher)
•Payment can be recognized either via Paypal , Direct (via the use of a Course Code number issued
directly to the Student by The Administrator, Teacher) or by VISA.
3
•Courses can be configured to be EITHER available to all Student OR only available to certain Groups.
•Once payment has been received, Student can retake exams as often as they wish within a pre-
configured time window (e.g. 3 months etc.)
•On completion of each exam, Student can review a report of his/her individual performance
•On completion of each exam, Student can choose to print or view a report detailing the correct answer
and the Student answer.
Teacher
•The Teacher will review course activity reports for Groups and Individuals that have been assigned to
The Teacher by the Administrator.
•Teachers can communicate, via LMS, with Student who are members of the Teachers Groups
Administrator
•Will allocate Student to courses, Student to Student Groups, Teachers to courses, and Teachers to
Student Groups
•Teachers can communicate, via LMS, with selected Student and Student Groups
4
PROJECT WORK FLOW:
MODULES FUCNTIONALITIES
5
Teachers, with permissions, can manually enroll Student or
unenrol Student in their courses.
Each person needs only one account for the Moodle site. Each
account can have access to different courses, and the courses
resources and activities.
Roles:
New roles can be created, copied from existing roles and edited.
Some standard roles include: Course creator can create courses,
6
teach in them, and assign others to teacher roles.
Student can participate and view activities but not create them
All grades for many kinds of activities can be viewed on one page.
Full user logging and tracking - activity reports for each Student are
available with graphs and details about each module (last access,
number of times read) as well as a detailed "story" of each
Student’s involvement including postings etc on one page.
Assignment Module:
7
Student can upload their assignments (any file format) to the
server - they are date-stamped.
Choice module:
The Choice module is like a single question poll. Can either be used
to vote on something, or to get feedback from every Student
8
Forum Module:
Glossary Module:
The Glossary module is one of the modules that best illustrates the
way that Moodle can fundamentally improve upon the experience
of a traditional classroom
9
glossary, their ideas are given weight and attention and often
result in a greater pride or ownership of the assignment
Lesson Module :
10
with content and questions.
Jumps are associated with each choice that link to other lesson
pages.
Choices that are answers to questions and can be scored and given
individual feedback.
Resource Module
11
Video formats, Audio formats
File handling in Moodle 2.0 has a File picker that is associated with
specific resources or activities, allowing uploads from server,
private, recent or on the fly. Files have attributes for author and
license/copyright.
Certificate Module System generates a pdf certificate and sends to the Student
12
We can also add borders, watermarks, seals and even show grade
information.
1 General Settings
1.2 Introduction
2 Issue Options
2.3 Delivery
13
2.4 Save Certificates
3 Locking Options
4 Text Options
5 Design Options
14
5.2 Border Image
At PHP-Powerhouse we are very diligent about each project that we take up. Our team works in an
extremely systematic and coordinated method, ensuring that you are kept informed and in loop
throughout the production and execution of your project.
3 SRS Final We will complete the Functional specification in view of your comments.
4 Approval The final and formally approved specification will then be the basis for
delivering the final product.
5 Architecture Every project is staffed with an Architect who will close on the Technical
Design and Architecture of the websites. The Architect will ensure that
the database design is optimal, websites are scalable and the
development and design standards are set. Deliverable out of this phase is
15
database schema.
6 Project Kick-off The Project Manager will brief the programming team on the
requirements, Creative Design and Prototype Mock up Creative design
including logo designing, home page and other page mock ups, style
sheets, etc. will be initiated.
7 Creative- We will build a non-working prototype that will include all major screens.
Design/Prototype The user interface will be non-navigable, but complete in all respects.
Mock-up This will also include the look and feel of the site, logo, etc. We prototype
all the major screens and get approval before developing them.
8 Approval A review and approval on the prototype will be required from your end
for further actions.
9 Final Approval This will be considered as your Final approval, and development will
begin on the same.
10 Development We will begin writing the application. We follow all the standard
development processes, like design reviews, code reviews, unit testing
and peer testing.
11 Testing Our expert quality Analysts will test the software in-house. The hours
budgeted here will be used in testing throughout the development
process.
12 User Acceptance Complete system will be released for your testing.
Testing (UAT)
13 Feedback You will comment on the UAT results and provide approval to proceed.
14 Final Version We will provide quick turnaround to fix any problems that are pointed
out by you during UAT, resulting in the Final Version.
15 Approval You will review the Final Version and give your approval.
16 Launch We will provide our assistance in placing the product online
16
Technologies
We propose using PHP/SMARTY based Moodle platform as a technology for your project. Reasons for
selecting this technology are given below:
Integration opportunities - All open source products, like phpBB and Wordpress, are created using
PHP. Adding new modules to the program as well as integrating with other open source projects
becomes seamless.
Scalability - Large sites like Facebook.com and mySpace.com are created using PHP.
Cost savings - Being open source, you don’t pay any license fee. Hosting for PHP is cheaper than that
for Microsoft technology.
Abstraction - Internet technology evolves too fast. Every year one has to update the look and feel of
the site because it gets outdated. Separating the presentation layer in SMARTY makes this job very easy
because you are not touching the heart of the application.
17
Tier Role Technology
Presentation Tier This tier will contain the user CSS, SMARTY, Ajax , PHP
interface, which will be available
to the end users. All the Ajax
effects will be created using
yahoo UI framework
Business Tier This tier will manage business PHP code
processes, rules and logic. This
will contain the components and
the business logic.
Database Tier This tier contains database MYSQL
having all the data
18
Architecture:
In order to provide accessibility, scalability, flexibility and robustness, the application should be built
using the MVC (Model, View, and Controller) architecture using SMARTY and PHP.
SMARTY is used to abstract the PHP code from HTML i.e. SMARTY becomes your presentation layer.
This architecture facilitates the separation of the application code from presentation. Typically, the
application code contains the business logic of your application, written and maintained in PHP code.
This is the heart of your application. It is a bad practice to keep business logic and presentation at the
same place. Presentation controls the view of the end user. This is the face of your application.
This architecture allows you to change the presentation without touching the business logic and
changing the business logic without changing the view.
Database:
We will use MYSQL 5.0 Database. All the queries and tables can be migrated to Oracle in future if you
want to scale the site.
Web Server:
Apache web server that runs on Linux will be used for the web server.
Operating System:
Linux 10.2 and Microsoft Windows will be used as the development environment.
Resource Allocation:
Project Team:
A Project Manager who would manage complete development lifecycle of the project and
would also communicate with client on regular basis.
One Senior Graphic Designer, one Developer will be assigned to the project.
Two testing and Quality Engineers will be assigned for testing the application.
19
Features of Development life cycle:
Prototype and High Level Diagrams: - Documents are always necessary in a well defined
process but it is very difficult for Student to figure out upfront what they will get for their money.
Prototype and High level diagrams help the clients to have a clue of what will be delivered after
coding.
Module releases: - Every project is divided into multiple modules. As soon as a module is
completed we send the demonstration version to the Student. This enables Student to track
progress and notify us with any change in flow.
Periodic review and update to the client: - Project is reviewed by the project leader every
week and update is provided to the client about the schedule, completed targets and planned
targets for the next week.
Common Libraries: - We have coded a set of libraries which the developers uses while coding
the application. These are common functions required while coding of any project. This helps
expediting the development and virtually eliminating bugs as these libraries are well tested and
optimized.
Knowledge management: - Common functions and solutions to challenges and issues are added
in our Knowledge management application. We believe in solving a problem or coding commonly
used function once. This also helps us reduce the development time.
20
Task and bug tracking system: - Tasks while development and bugs while debugging are the
most important aspects of the projects.. Generally it becomes very difficult to manage bugs
where multiple Quality Engineers and developers are working on an application. For this, we
have a project management application to manage/track both bugs and tasks .Use of above
referred application with advanced reporting, tracking and auditing features not only makes it
easy to manage but also enables improvements in each project.
Source code and version control system: -Developing an application without source code and
version control is a big risk. We use Visual Source Safe for Microsoft Technologies and SVN for
other technologies.
Frequent review of SLA and planning documents by Project Leader: - Project leader is
responsible for meeting all requirements. Therefore project leader has to review the
development and SLA documents regularly to make sure project is on track and inform client
accordingly.
Warranty:
We stand by our work. There is a 90 days limited warranty on all our work. Once the application is
completely tested and has been launched for public use there will be one month of warranty period
where any bugs with the application are fixed. This period cannot be used to add any additional
features into the site. This period can be extended or reduced at the time of final signing of agreement.
Maintenance:
Maintenance, upgrades, changes, etc. will be provided at $10 per hour. For larger maintenance jobs, we
will be pleased to quote and lock the price based upon our hourly rates.
21
Technical Accomplishments:
Over the past few years, PHP-Powerhouse has built a strong base in adorning skills based on different
technologies. We have developed several projects in the technologies listed below and are confident of
delivering clean and high quality code in anyone of them.
Databases:
My SQL 4.0, 5.0
SQL Server
Platform:
Unix / Linux
Apache
Hope this is in line to your expectation, please let me know if any disconnect, so that I along with my
technical team of experts could put light on the same.
Looking forward to hear from you and henceforth building a long-term mutually beneficial
relationship.
Warm Regards
Priya
Business-Manger Development and Analyst
PHP-Powerhouse
22