AUTHOR:

Foram Joshi

Shirin Rajan

Nitin Sachdeva

REVIEWER:

Bhavna Raina

Komal Patel

e-PAATHSHALA

PROJECT PLAN

VERSION 1.2

JANUARY 26, 2013

Page 1

OVERVIEW

This is the Project plan for e-PAATHSHALA WEBSITE, Team 4’s IT314 Software Engineering course project.

TARGET AUDIENCE

Developers

Mentors

DOCUMENT REVISION HISTORY:

Version Primary Author(s) Description Reviewer(s) Date

1.0 Shirin, Nitin First Draft Komal, Bhavna 17th January 2013

1.1 Foram Template added Komal, Bhavna 23rd January 2013

1.2 Shirin Dates modified Bhavna 26th January 2013

Dates modified Bhavna 20th February 2013

Page 2

TABLE OF CONTENTS:

1. Introduction…………………………………………………………………………………….3

2. Monitoring and Control…....................................................................3

3. Requirement Management.................................................................4

4. Quality Control.....................................................................................4

5. Schedule and Milestones.....................................................................5

6. Organisation Co-ordinating Team .......................................................6

7. Cost estimation.....................................................................................8

Page 3

1. INTRODUCTION:

Most of the online educational websites that are available on the Internet are

either school-based or provide resources for a limited number of state boards. For

our project, we propose the development of a website which provides the users

study material spread across various state boards in addition to the CBSE and

ICSE boards.

We have been given this opportunity by Ms. Shikha Agarwal who is our live client

for the project. It has been her vision to develop an interactive educational

platform for the students for an interesting learning experience. Currently, the

project aims to target only the Junior High school students and will be expanded

in the future to more classes in view of the success that it earns.

This website plans to include detailed solutions to textbook questions in an easy-

to understand format, detailed explanation with reasoning, real-life examples that

help relate theory with practical applications, suitable animations and graphics

through effective visual media, a variety of tests, monthly quizzes, detailed

performance reports, concise notes and an open discussion forum resembling a

doubt clearing session. The flexibility to study anytime and go through it any

number of times ensures that learning is made easy, complete and thorough. The

need for such resource management proves to be useful for students to set their

goals higher, work for it and achieve it.

2. Monitoring and Control:

The project will be monitored by conducting timely meetings among the team members

and taking inputs by our mentor Arun Gupta. There are various modules for different

work assigned. There may be sub modules and 1 leader for each module, so that

respective group members report to leader for any progress and problems. Different

modules will be focused on different parts of projects. There will be reviews and testing

process for each module separately, and it will be conducted after completion of every

Page 4

phase.In each phase, there will be appropriate documentation to ensure that the entire

team is aware of the progress of each and every sub-group. Project will be tested

regularly for any error detection and correction through various stages of

implementation.

3. Requirement Management:

Requirement specification document will contain all the requirements specified in

requirement phase, verified and signed by Ms. Shikha Agrawal(live-client). It will be

closely monitored in every phase and will be updated according to the need of the

project.

4. Quality Control:

Every team member will ensure to the best of his abilities that they don’t miss any requirements which are mentioned in SRS and try to implement it optimally. Team members will ensure that GUI is user friendly (easy to use and easy to understand to end user. To maintain the quality of each deliverable, a review process will be followed for each deliverable. During the requirement phase, to ensure the quality of SRS, there will be regular questionnaires and interviews. During the coding phase, proper coding conventions and standards will be followed. ). Each module will be monitored regularly and appropriate changes will be done according to results of testing and it will also be updated to all documents. As a result we will try to develop high quality product that is comparable with other competitive products available in the market. In short we will try to give our end user a well-designed as well as a desired product.

Page 5

5. Schedule and Milestones:

Sr.no Tasks Deliverables Deadline

1. Finalizing the project idea Project Topic 12th Jan 2013

2. Need of the project, feasibility analysis,

Proposal

Feasibility report

Technical proposal

16th Jan 2013

3. Planning for the work to be done in course

of project

Project Plan 27th Jan 2013

Revising feasibility as per requirements 29th Jan 2013

5 SRS SRS document 16th Feb 2013

6 User Manual v1, Test Plan User manual ,Test plan 21st Feb 2013

7 Study product features & customer

requirements and make Traceability Matrix

Traceability Matrix 28th Feb 2013

8 System and database design 12th march 2013

9. Coding 26th March 2013

10. Final Testing System testing report,

user manual

1st april 2013

11. Final Final product along

with relevant

documentation

4th April 2013

Page 6

Detailed plan for above milestones:

Requirements gathering and analysis: In this phase we will gather the information about the requirements of the students of Different Schools from different broads . A questionnaire will be prepared and report including information about the requirements will be prepared. We will complete the gathering of information and compilation by 13th Feb, 2013. Thereafter, we will analyze the data collected; prepare an SRS document which will encompass all the essential requirements gathered. Thereafter the first draft of user manual, traceability matrix and system test plan will be prepared by 21th Feb, 2013.

Designing: In this phase, design of different modules (database design and User Interface design) and access privileges for different users will be prepared. At the end of this phase, low level design and high level design will be prepared by 10th March, 2013. The design will include Entity Relationship Model, Relational Schema for the database, User Interface Design and other diagram to explain in detail.

Coding and Unit Testing: In this phase, all the modules designed in the design phase will be programmed and individually tested with different test cases to ensure correct and expected functioning of the module. Codes developed by different members for different modules will be documented so that they are accessible and easily understood to the rest of the team. Code written in this phase will be tested against the requirements that it should fulfill when given appropriate input.

Integration and System Testing: In this phase, all the modules created above will be integrated and tested using one or more of the testing methods like top-down testing, bottom-up and other testing methods according to the requirement. This will also involve α and ß testing for which will help in providing last improving touches to the system. The final product along with the documentation will be available by 4th April, 2013.

6. Organisation Coordinating Team:

Names Responsibility

Bhavna Raina ● Project management.

● Review Documents.

● Delegate meetings and facilitate

proceedings.

Page 7

● Organize human resources and assign roles.

● Monitor project progress.

● Client interaction

● Documentation

● Design

● Programming

● Survey

Foram Joshi ● Documentation

● Online transaction implementation

● Programming

● Testing

Ganpat Meena ● Documentation

● Survey

● Testing

Shirin Rajan ● Documentation

● Programming

● Requirements gathering

Udit Pandey ● Documentation

● Programming

● Design

Aditi Agarwal ● Documentation

● Database design

● Testing

Komal Patel ● Documentation

● Client interaction

● Survey

● Online transaction implementation

● Design

● Testing

Saurabh Singh ● Documentation

● Database design

● Testing

Page 8

Nitin Sachdeva ● Documentation

● Programming

● Requirements gathering

Receivers:

Ms.Shikha Agrawal has agreed to be our client and plans to launch the website before

the next academic session i.e around the time of June or July this year.

7. Cost Estimation

Keeping an average of 9 hours per week for an individual,

we get 9*9 hours per week= 81 hours per week.

Till the final project deadline, 10 more weeks are left.

So, total project cost will account to 10*81 hours= 810 hours.

Hence, the cost estimated for our project comes out to be 810 person-hours.