LEARNING PLATFORM

Title:
1|Page
Author:

For decision / discussion / noting

Document Control

Issue Issue Date Version Issued To

1 Oct 05, 2018 1.0 M Raja

CONTENTS

2|Page
1 BACKGROUND:.............................................................................................................................5
2 PROJECT DEFINITION:.................................................................................................................5
2.1OBJECTIVES:............................................................................................................................5
3 PROJECT DELIVERABLES:.........................................................................................................6
4 SCOPE:.............................................................................................................................................7
5 ASSUMPTION AND CONSTRAINTS..........................................................................................7
6 ACCEPTANCE CRITERIA:...........................................................................................................7
7 PROJECT APPROACH:..................................................................................................................8
8 INTERFACES:.................................................................................................................................8
8.1 MANAGE USERS AND ACCESS CONTROLS.....................................................................8
8.2 MANAGE CERTIFICATE APPLICATIONS...........................................................................8
8.3 DESIGN QUESTIONNAIRE....................................................................................................8
8.4 APPLY FOR A CERTIFICATE................................................................................................8
8.5 NOTIFICATION........................................................................................................................8
8.6 HELP TUTORIALS...................................................................................................................8
9 ASSUMPTIONS:.............................................................................................................................8
10 BUSINESS CASE:...........................................................................................................................9
10.1 PROJECT ORGANISATIONAL STRUCTURE:.................................................................10
11 STAKEHOLDERS:........................................................................................................................10
12 PROJECT EXECUTIVE / SPONSOR:..........................................................................................10
13 PROJECT MANAGER:.................................................................................................................11
13.1 PROJECT TEAM:..................................................................................................................11
14 QUALITY:.....................................................................................................................................12
14.1 TESTING TYPES..................................................................................................................12
15 PROJECT PLAN:...........................................................................................................................13
15.1 OVERALL APPROACH.......................................................................................................13
16 KEY MILESTONES......................................................................................................................14
17 MANAGEMENT CONTROLS AND GOVERNANCE...............................................................14
18 REFERENCES:..............................................................................................................................16

3|Page
1 BACKGROUND:
 Overview of e-learning platforms and the need for innovative solutions in education.
 The significance of AI and ML in enhancing learning experiences.

2 PROJECT DEFINITION:

3 PROJECT DELIVERABLES:

4 SCOPE:

5 ASSUMPTION AND CONSTRAINTS

 Project scope is fixed by requirements section in PID
 Project team has sufficient experience on the business idea
 Project sponsor is readily available for change/request solution.

6 ACCEPTANCE CRITERIA:
1. Product owner owns the acceptance criteria and the development team understands them
2. Acceptance Criteria are negotiable between the product owner and the development team
keeping in mind about the Major areas of project Development

 Development Cost
 Scalability
 Security
 Performance
 Ease of use

7 PROJECT APPROACH:
The Development will be an agile approach following the best practices of SDLC. The project
starts with the plan in place and the development will have a four phase method for each
iteration.

Plan

Iteration 1
4|Page
 Define - Design - Develop - Deploy

Iteration ..N

Define - Design - Develop – Deploy

8 INTERFACES:
The system will be developed along with several other Service developments including client
interfaces, technical interfaces and the product must deliver:

The Key interfaces will be:

 Manage users and access controls

 Manage certificate applications

 Design questionnaire

 Apply for a certificate

 Notification

 Help Tutorials

9 ASSUMPTIONS:
The Project will be subject to the following assumptions:

o Sufficient resources will be available to complete the project

o General support and client involvement will be forthcoming

o Implementation of the application will be done on a new infrastructure and is

therefore considered a new development.

10 BUSINESS CASE:
10.1 Project organizational structure:

Name Role
Sponsor Mark Remmy
Project Team Onedata Software

5|Page
 Solutions

M Raja BA and Scrum Master

Vignesh Sarode Project Manager

Kuppuswamy Fullstack Developer

Kannan Database Specialist

Dhivya Software Developer

Dhakshana Software Developer

Dhanraj Software Tester

11 STAKEHOLDERS:
Mark Remmy, Raja M

12 PROJECT EXECUTIVE / SPONSOR:

Mark Remmy

13 PROJECT MANAGER:
13.1 Project team:

Name Role Responsibilities

Sponsor Mark Remmy
Project Team Onedata Software Solutions
Raja M BA and Scrum Master To Give a strategic overview with links to
6|Page
 project requirements and business level
ideaa
To Drive and track progress of the
Vignesh S Project Manager workstreams of the overall project against
the project objectives
To Provide expert knowledge on the
Kuppuswamy K Fullstack Developer development and technical front on
utilizing the technology to its fullest
To Provide expert knowledge on the
Kannan G Database Specialist development and technical front on
utilizing the technology to its fullest
To Provide expert knowledge on the
Dhivya M Software Developer development and technical front on
utilizing the technology to its fullest
To Provide expert knowledge on the
Dhakshana R Software Developer development and technical front on
utilizing the technology to its fullest
To Provide expert knowledge on the
aspects of quality Assurance and the
Dhanraj K Software Tester
methodologies involved in different types
of testing

7|Page
14 QUALITY:
This test plan describes the testing approach and overall framework that will drive the testing of the
Application.

 Test Strategy: The Test rules will be based on, including the givens of the project (e.g.:
start / end dates, objectives, assumptions); description of the process to set up a valid test (e.g.:
entry / exit criteria, creation of test cases, specific tasks to perform, scheduling, data strategy).
 Execution Strategy: describes how the test will be performed and process to identify and
report defects, and to fix and implement fixes.
 Test Management: process to handle the logistics of the test and all the events that come up
during execution (e.g.: communications, escalation procedures, risk and mitigation, team
roster)

14.1 Testing Types

Functional Testing type of software testing whereby the system is tested against
the functional requirements/specifications. Functions (or features) are tested by feeding them
input and examining the output.

Integration Testing is a level of software testing where individual units are combined
and tested as a group. The purpose of this level of testing is to expose faults in the interaction
between integrated units.

System Testing is a level of software testing where a complete and integrated software is
tested. The purpose of this test is to evaluate the system's compliance with the specified
requirements.

8|Page
15 PROJECT PLAN:
15.1 Overall Approach

Implementation

The Project will be managed broadly by Agile methodologies of project management,

in that it will have a defined beginning middle and end. As described the project has
been split into workstreams with the purpose of making the project objectives more
discrete and enabling a more focussed approach.

A Project Manager will be assigned to monitor the progress of the project; This role
should not just be about scoping and reporting on any issues but should identify the
way forward and should instigate service developments and changes.

Measures of Improvement

The following measures will be utilised to assess the success of the final product and
ultimately the success of the project.

The targets will not be achieved immediately, as there will be an implementation

settling down period to be expected, and time required for the Development/Support
team to start to take effect. Therefore the expectation is that through the first Iteration
start up, a review of the data will be taken and an assessment made and then again at
the end of the year. Where there is no current baseline, one needs be agreed or
assumed, or agreement that this information is collected over a two month time period
and stipulated to gain a full year effect to use as a baseline.

Resource Plan

The human resource requirements for the project are as follows: The Project Board
(Stakeholder) and Project Team needs to have sufficient decision making authority to
support the progress of the project at various stages or to halt the project if required.

9|Page
 Risk and Issues

An initial risk assessment has indicated the following potential risks to the success of
the project. However a rolling / active risk log will be kept and managed for each of
the workstreams.

16 KEY MILESTONES
The project will be delivered in milestones. The Key milestones are given below:

 Project Kickoff
 Business Requirements
 Product Customization
 Product Parameterization
 System Integration Testing
 User Acceptance Testing
 Product Readiness Testing
 Release 1 Go Live
 Release 2

17 MANAGEMENT CONTROLS AND GOVERNANCE

 Everyday standup to happen at the start of the day to address the project objectives

 Meeting schedules to be published in advance with agendas and minutes produced for
each meeting.

 A file on the dropbox paper will be set up for storage. Documents will be sent out by
email to those who don’t have access.

10 | P a g e
18 WORKFLOW DIAGRAM

11 | P a g e
19 REFERENCES:
Forest management certification is a voluntary process for verifying responsible forest
practices. It is up to a forest owner, or representative of a group of forest owners and
operators, to initiate the certification process by requesting an independent certifier to inspect
the forest and to see if the management meets the FSC requirements, encapsulated in the FSC
P&C. Only an FSC accredited certification body can evaluate, monitor and certify companies
to FSC standards, and only continuous compliance can assure that certificate holders can keep
their certificates. wiki

12 | P a g e