MU Moodle Customisation Project

advertisement
Private and
Confidential
MU Moodle Customisation Project
The Proposal
MU Moodle Customisation Project (The Proposal)
Group Project
CMT3342 -
Table of Contents
Introduction ....................................................................................................................2
Approach and Methodology .......................................................................................4
Project Deliverables .......................................................................................................5
Detailed and Itemised Pricing ......................................................................................5
Support & Maintenance Details ...................................................................................9
Executive Summary .......................................................................................................2
Appendix I: Supplier Company Overview .................................................................10
Appendix II: References of previous work..................................................................10
Appendix III: Account Management & Contacts.....................................................10
Appendix IV: Quality Assurance ................................................................................. 11
Appendix V: Detailed specifications of the product ................................................13
1
MU Moodle Customisation Project (The Proposal)
Group Project
CMT3342 -
Request for Proposal
Descriptions:
Customising Moodle for Middleshire University
Mail to:
Middleshire University
FAO: E. Duncker
Procurement Manager
By way of OASISplus/MyUnihub
Executive Summary
Our Company SOSA (Services for Open Source Applications) provides services and special
developments for many open source applications including Moodle. The aim of this
proposal is to bid for an IT project which is offered from the Middleshire University. The
IT project is to customize ‘Moodle’ platform as an usable and deliverable platform for the
professors, staff, and students.
The ‘Moodle’ platform will have a series of features after our customization works. The
main functions are being developed to be a platform for providing information, managing
the assignments, and communication backend between the users. The customized
‘Moodle’ will develop on top of a robust database system so that it can also absorb large
volume of files from students in particular the frequent rate of assignments’ submission.
Before the grading of assignments, the ‘Moodle’ will integrate with specific systems to
conduct plagiarism check. It provides an plagiarism free environment in the initial stage
of assignments’ submission. In addition, professors can rate with the assignments by
using rubrics, traditional direct grading. And, the most important is the way to give
feedback.
Students will have a easy access interface to reach their subject’s assignment, and to
collect all necessary materials that are relation to the course modules. For the knowledge
intakes, the ‘Moodle’ platform will provide the useful materials for students. A tailor
made academic calendar, student’s blog and dairy will also be developed into the system.
For the information security, the ‘Moddle’ will design in the way of hierarchical levels to
gain access to the individual course modules to both related professors and students. The
control of user access is crucial to the system as the course materials and students’
assignments will be developed from time to time. Remember, students will complete the
course phrase by phrase and university staffs will have constant changed and replaced
periodically.
2
MU Moodle Customisation Project (The Proposal)
Group Project
CMT3342 -
Introduction
This document is prepared in response to the request for proposal (RFP) that published
by Middleshire University on 28th Jan 2014, which requires migrating and customising the
Virtual learning environments (VLEs) from Webboard to Moodle-based system.
We (SOSA) have been providing open source developments including Moodle for 10
years and have numerous satisfying records in fulfilling customer expectations. Besides,
we won IT awards in software development competitions like Google Code Jam and Top
Coder on 2012 and 2013 respectively. These awards recognized our skills and
qualifications, we are truly proud and honored by this recognitions.
We confidently say that we have sufficient resources and technical experience to perform
the work specified in the scope of the project.
3
MU Moodle Customisation Project (The Proposal)
Group Project
CMT3342 -
Approach and Methodology
Realization of the project (description)
Justification of the choices we made
Project management approach
Software development model
The chosen development tools and environments
Number of iteration and the purpose
This project will adopt traditional method to develop the new system. Iterations method
adopts multiple iterations; it should be the ideal method to develop ‘Moodle’ and
customization workflows. Regarding the project objective, we need to develop a usable
and deliverable ‘Moodle’ platform to the Middleshire University. If we are using this
method, we could have better defined features in connection with the ‘Moodle’
platform.
4
MU Moodle Customisation Project (The Proposal)
Group Project
CMT3342 -
Project Deliverables
Description of the different stages of prototypes
(from paper design to fully functional prototype)
Documentation related to each stage
The date when they will be delivered
The final prototype and the project report need to be listed
Our experienced consultants will work closer with stakeholders on each project process
for ensuring the deliverables are expected. The following items will be delivered as required
from RFP.
Detailed Schedule of Tasks Allocated
Items
Tasks
Duration
(Working
Day)
Start Date
Completion
Date
1.
Project Proposed
5
17-2-2014
21-2-2014
2.
Initial Stage - Planning with
meetings
5
24-2-2014
28-2-2014
3.
Feasibility Study
10
3-3-2014
7-3-2014
4.
Product Design
5
5.
Cost Estimation
5
6.
Administrative Approval
12
7.
Compilation of Report /
5
Documentation
8.
Implementation
30
9.
System Test
10
10.
Quality Control
10
11.
User Acceptance Test
20
5
MU Moodle Customisation Project (The Proposal)
Group Project
CMT3342 -
12.
Product Review on Functionalities
10
13.
Inspection of Completed Products
10
14.
Review Meetings
5
15.
Generation of Project Report
10
Table 1
6
MU Moodle Customisation Project (The Proposal)
Group Project
CMT3342 -
Detailed and Itemised Pricing
Human Resource Allocation of Project
Upon the project scope has been confirmed, the resource allocation should be addressed
and estimate the cost at this stage. The following is the breakdown of the resource on
man-days.
Role
Project Team Member
Man-days
1
Project Manager
10
2
System Analyst
30
3
Program Developer
25
4
System & Network Administrator
2
5
Quality Assurance Manager
3
6
Training Manager
2
7
Procurement Office
2
Total
74
* Assumed that the working hour from 0900-1800 per day
Detailed pricing on the labor costs
Item Description
Man-day
Hourly Rate
Amount
(GBP)
(GBP)
1
Project Manager
10
30.00
2700.00
2
System Analyst
30
30.00
8100.00
3
Program Developer
25
50.00
11250.00
4
System & Network Administrator
2
30.00
540.00
5
Quality Assurance Manager
3
30.00
810.00
6
Training Manager
2
30.00
540.00
7
Procurement Office
2
30.00
540.00
Total
24480.00
Detailed pricing on the support & maintenance
Based on the hardware and software cost, the annual fee of support & maintenance is
around GBP 4800.
7
MU Moodle Customisation Project (The Proposal)
Group Project
Item Description
CMT3342 -
Qty
Unit Price
Amount
(GBP)
(GBP)
Hardware
1
Dell PowerEdge R620 (Web Server)
2
6000.00
12000.00
2
Juniper SRX240 Firewall
1
1800.00
1800.00
3
Dell PowerVault TL2000 Tape Library
1
9000.00
9000.00
4
Dell OptiPlex 3020 Business Desktop
1
400.00
400.00
1
800.00
800.00
Total
24000.00
Software
1
Red Hat Enterprise Linux (Premium
Subscription) Per Year
1. Effort to be spent on software development based on Object Point Analysis for
those objects that need to be configured or customised. Hourly costs for
experienced programmers are £50 per hour while all other members of staff
cost £30 per hour. In order to able to estimate of the size of the software
(changes), you have to carry out a certain amount of the conceptual design
for your project.
2. Consumables used for the project
3. Capital equipment (appropriate percentage of PCs and software licences)
4. Indirect expenses related to the project such as transportation or training
5. Overheads (in this case to be calculated as 40% of the costs under position 1 to
4)
6. Contingency allowance (10% of the above budget)
7. Profit (50% of the total costs position 1 to 6)
8
MU Moodle Customisation Project (The Proposal)
Group Project
CMT3342 -
Support & Maintenance Details
We will be responsible for system supporting and maintaining during the year contract
period includes hardware and software, and free replacement for not damaged by misuse.
Support and maintenance carried out by the supplier after the product has been
delivered is usually estimated as 20% of the price for the software itself per annum.
•
Remote support
•
Onsite support
•
Short iterations/integrations
•
Testing
•
Prioritization of tasks
•
Measurement of velocity
•
No overtime
•
Refactoring
•
Common code ownership
9
MU Moodle Customisation Project (The Proposal)
Group Project
CMT3342 -
Appendix I: Supplier Company Overview
Description of your imaginary company to the customer company showing the business
acumen, reliability and expertise in the area required.
Appendix II: References of previous work
Imaginary references of projects carried out for other customers.
Appendix III: Account Management & Contacts
The details of the account manager of your company. In small companies there is one
account manager for all customer accounts.
10
MU Moodle Customisation Project (The Proposal)
Group Project
CMT3342 -
Appendix IV: Quality Assurance
Your approach to quality assurance. How do you monitor and control the quality of your
product? This has to include a detailed test plan.
Phase progress monitoring
For controlling the progress of each phase of system development are in schedule
and budget, both parties agreed that a portion of deliverable must be produced
and can be shown its function after one month by vendor. During the trial run, they
will report the progress; show and explain the operation; raise any comments or
suggestions as discussion for preventing or improving any further predicted
problems under control. Then regular weekly review will be held or if tasks are
small, then it will be held in every 2 to 3 days. The effect of review was same as
the first deliverable. It would be the best monitoring method to suit into EHP’s
scale and the monitoring flow was accepted by the vendor as well.
Phase testing
To reduce the time consuming and manpower effort on whole system testing stage.
After each module is completed and running test is passed by the outsourcing
coding team, the team leader assigns an analyst programmer to provide training to
EHP testers. Each module's testing data is pre-designed under quality assurance
with correct and incorrect forms for testing the data validation during input entries;
and testing output result will be verified for confirmation it met the criteria of each
entry under the system specification. Output result was prepared for collating.
Meanwhile, any fault data must be captured for debugging purpose and producing
fault estimates.
Integration testing
Before going to this stage, all modules must be passed its testing. For ensuring
each modules can be worked together in accordance to the requirements. The
pre-designed test cases are used in integration testing and expected the result
should be matched. Any differences during the testing came out will be marked for
record.
11
MU Moodle Customisation Project (The Proposal)
Group Project
CMT3342 -
System testing
System testing is a total completion test on the online store system’s functionality,
consistence, security and performance in open environment. Using different
specialized methodologies for testing as below:

Consistence test:
This test is more or less like integration test but in different environment. Also
using test cases to simulate a complete shopping process at different situation
like placing new order, cancel order, change order and make payment

Performance test:
This test is major to monitor the response speed under predicted the number of
users; ability to cope with large amount of users

Usability and accessibility test:
This test is to ensure the browser compatibility, system operation and
accessibility to normal users as well as disability users.

Security test:
This is to test the system security policy and the open interface to public like
login page, shopping cart page for preventing any abnormal access to the
system.

Maintenance test:
This test is to check the system in normal operation if there have any
maintenance like upgrade, migration, enhancement on hardware and software
Acceptance testing
Acceptance testing is the test by EHP after all system faults had been removed
and got the well tuning on the system.
12
MU Moodle Customisation Project (The Proposal)
Group Project
CMT3342 -
Appendix V: Detailed specifications of the product
This appendix describes your intended product in detail. This includes the requirement
specification, the architecture of your product, a rough idea what the front end might
look like and the tables and relationships of the backend/ database. In other words, you
have to do some of the conceptual design work upfront in order (to do the estimation of
the size of the software and) to give the customer an idea of your product.
13
Download