Project plan for E-mandi

SOFTWARE PROJECT PLAN 4/8/2023

Project Plan

Online College Magazine

Prashant Kumar

PAGE 1 OF 8 DOCUMENT.DOCX


Table of Contents

1. Aim 32. Project Overview 3

2.1 Objective...........................................................................................................................32.2 Project Scope.....................................................................................................................3

3. Process Model 43.1 Justification.......................................................................................................................4

4. Project Schedule 5.

4.1 Major Project Milestones..................................................................................................54.2 Gantt chart For Project......................................................................................................64.3 PERT Chart for Project.....................................................................................................6



1. AIM

To develop an online version of the existing vegetable market in india and to make the transaction between the general customers and the retailers and the wholesalers transparent.

2. PROJECT OVERVIEW

2.1Objective

As we have in our current system, a whole lot of the general customers suffer due to the lack of information about the retailers

o The farmers suffer at the hands of the buyers as it is much lower than the price offered by the government.

o General customers have inadequate information about the best price of a product available in that area.

o Even its difficult for the retailers to keep track of the wholesaler activity in the marketo The buyers who buy from the farmers are the ultimate gainers in the process.

But our project takes the system to the next level. Its major features are

The customers will be cognizant of the various products available at the best price in the market.

The farmers will know the prices set for the vegetables by the government It will also calculate the rate of inflation in the various regions and the price difference

cross the regions. It will help the the retailers to find out the wholesalers from whom they have to get

their products Our project can contribute to maintain a well stabilized economy

2.2Project Scope

The scope of this project covers a lot of the section of societyAs already mentioned, it will take under its ambit

The general customers The retailers The wholesalers The farmers



3. PROCESS MODEL

The Model we are going to use in this project will be V-Shaped Model or Verification and Validation Model where verification is the developing side and validation side is the testing side. It is a sequential path of execution of processes. Every phase in the software development cycle has a corresponding phase in the testing cycle. Different phases and their testing are being arranged in V-Shaped Model as:

3.1Justification

We use this model as:o As in our project we have fixed requirements which are very clear. o Testing is emphasized in this model more than the waterfall model having higher

chance of success over the waterfall model due to the early development of test plans during the life cycle.

o Will lead to less no. of defects in the project then Waterfall Model where any defect in the software cannot be determined, till the software reaches the testing phase.

o But in this model, defects are noticed in the initial phases, due to which they can be corrected easily.



4. PROJECT SCHEDULE

4.1Major Project Milestones

S.No.

MilestoneEstimated Start Date

Estimated Completion

Date

Estimated Hours

Number of Resources

Number of Days

1Software

Requirements Specification

22/1/2013 5/2/2013 48 3 11

2 System Design 6/2/2013 18/2/2013 60 3 9

3 Architecture Design 20/2/2013 5/3/2013 60 3 10

4 Coding 6/3/2013 2/4/2013 120 3 20

5 Unit Testing 4/4/2013 17/4/2013 60 3 10

6 Integration Testing 18/4/2013 25/4/2013 30 3 6

7 Functional Testing 26/4/2013 3/5/2013 30 3 6

8User Acceptance

Testing5/5/2013 7/5/2013 12 3 2



4.2Gantt chart For Project

4.3PERT Chart for Project



5. RISK MANAGEMENT

5.1Risk Management Strategy

The risks involved in this project and the possible mitigation strategies are Performance risk - As the foremost risk involved in the projects is whether the product will be

complete according to the user requirements. Often the requirements deviate slightly or completely from the software produced. But already a wide survey has been done of the whole lot of benefitted sections of the society and a detailed list of the user requirements has been made. The users include all the farmers and the retailers and also the general customers and the wholesalers.

Cost risk- cost risk is somewhat which cannot be avoided. It all depends on the engineers and the problems faced in the later stage of the project. Nevertheless, a wide estimate has been made of the

1> possible inflation rates that can occur. 2> the possible offshoots in the deadline that can occur and the resulting effects on costs 3>the workers condition and the resulting loss due to unavoidable conditions

Support risk- already the software has been developed taking care of the conditions which can allow it to expand or the user requirements modifies slightly then the software is capable of adapting to the conditions. Also the engineers are being regular and broad minded and so the maintenance and upgrade won’t give too much of a problem.

Schedule risk- the only risk involved in this category is the time limit which has to be maintained for the project. Since the project magnitude and the functionalities are huge, a possible risk of the offshoot is there

But our project plan already considers these offshoots and for each section of task, a possible margin has been kept in between the finish of one task and the commencement of another task.

Software risk- the software risks are about the engineers and the managers who work on the projects. Lack of expertise on the part of the professionals which includes poorly designed interfaces and the lack of management from the managers are the source of risks. But including competent workforce and managers in the team would lower the risk to a much low level.

5.2Initial Risk List

This is the initial risk list; the risks are listed in priority order from top to bottom. Descriptions are provided below the table. Risks with a pre-mitigation magnitude of 2.0 or below are not listed.



Risknumber

Risk Priority (H, M,

L)

Likelihoodof

Occurrence

Risk name: brief description Mitigation Strategy

“ACCEPTED” or

“MITIGATED” with pointer

to plan.

1 M Performance risk: deviation from the user requrements mitigated

2 H Cost risk: whether the costs involved will offshoot the estimated costs

mitigated

3 L Support risk : concerning the adaptation and management and upgrade of the software

mitigated

4 M Schedule risk: whether the time completion of the project will go beyond the deadline

mitigated

5 M Software risks : involving inappropriate UIs and incompetence from the work force

miigated


Project plan for E-mandi

Documents

Transcript of Project plan for E-mandi