Project

Plan
 Project scope
Project scope
 Function:
The main function of the application is to provide the user the ease of finding solutions tO their
any problem by just posting it on the website. The website also allows them to add their own
details on to the website and also ad problems to the solutions.
 Performance:
The application will be able to perform satisfactorily on all web browsers. It is also compatible
with all operating systems for better performance an operating system of windows 98 or above is
expected.
 Constraint:
The followin are the constrains of the system
1) Cannot support more than 100 users at a time.
2) Cannot opened at multiple windows simultanieously.
3) Single user cannot have multiple account.
 Interface:
In order to post any problem the user should fulfill theminimum requirement of browser being
internet explorer 5.0 or any higher versions, google chrome,mozilla firefox are also compatible
with the site.

Feasibility
 Technology and system feasibility: The whole system is designed into the latest
technologies. Visual Basic is used to implement the front end. Since it is platform
independent any operating system can support it. SQL server is used to design the
database which is the most resent technology and it is easy to connect front end and back
end with complete security. It uses the latest hardware technologies like Pentium 4
Systems so it is easy to operate.
 Economic feasibility: Not much expertise will be required to manage the system as it
is easy to operate .The project is economically feasible. The cost incurred is shared.
 Operational feasibility:

Schedule feasibility: The software has a single interface to enter problems and solution for each
user. These values are used to update the data in the database at the backend for both the product and
the customer.

Project Risks
Risks Category Probabilit Impact
y
Technology will not Meet Expectation TE 40% 1
End Users Resist System BU 30% 3
Lack of Development Experience TE 25% 2
Failure to meet deadline BU 20% 1
Database Inconsistency PS 30% 1
Changes in requirements TS 20% 2
Deviation from Software Engineering Standard PS 25% 3
System crash TE 20% 1
Impact Values

1-Catastrophic

2-Critical

3-Marginal

4-Negligible

Risk: Database inconsistency

Mitigation
If the database is inconsistent then it may happen that item information is not delete even if is sold
out. In order to prevent this from happening, developer who are in contact with database, and/or use
the function that interacted with database should keep in mind the possible errors that could be caused
due to poor programming/error checking. The database should be updated consistently so that once
the item is sold then it should be deleted from database.

Monitoring
Each user should be sure that the database is left in the condition it was before it was before it was
touched, to identify possible problems. The first notice of database errors should be brought to the
attention of the other team members.

Management
When this occurs, the organization would call a meeting and discuss the cause of the database
instability, along with possible solutions.

Risk: Lack of Development Experience

Mitigation
In order to prevent this from happening, the development team members should be trained for the
required languages and techniques necessary to develop this software. Any member of the team who
is experienced in a particular facet of the development tools will need to instruct those who are not as
well versed.

Monitoring
Each member of the team should watch and see areas where another team member may be weak.
Work should be divided among members such that everyone has knowledge in their job.

Management
The members who have the most experience in a particular area will be required to help those who
don’t. New developers should take interest and make an effort In learning new techniques and
languages.
Resources Identification
Human resource

Resource Type Cod Base Avg. Project Core Avg. Cost

e Headcount Availability Resource
Team Leader TL 1 100% Yes
Sachin
Viswakarma
Modeling Team: MT 3 100% Yes
Static Modeling:
Vardhini Vartak
William John
Dynamic
Modeling:
Raj Yadav
Sachin
Viswakarma
Coding Team: CT 2 100% Yes
Sachin
Viswakarma
Raj Yadav
Testing Team: TT 3 100% Yes
VardhiniVartak
William John

Environment Resource
Resource Type Code Initial Initial product used
Investment
Hardware Hw Server,personal computer
Network NW Database Server
Resources R
Software Tools SOT SQL ,VB 10.1

Reusable Resources:
Resource type Code
IEEE Format of SRS SRS
Existing Database EDB
Login and Register page of previous project LRP

Timeline charts
Work tasks Jan Jan Feb Feb Feb Mar
21 28 4 11 25 4
Problem statement definition
Requirement gathering
Construction of SRS
Object mode;
Milestone: Requirement Analysis
complete
FP calculation
Design user interface
 Milestone: Design complete
Front end implementation

Work tasks Mar Mar Mar April April April

11 18 25 1 8 22
Database establishment and connection
Coding and validation
Calculation of bill for customer
Milestone: Implementation complete
Testing database connection and
updating
Link Testing
Fix the defects
Milestone: Testing complete

Project Plan

Work Task Planned Actual Planned Actual Assigned Effort Notes

Start Start complete complete Person Allocated
Date date
Requiremen 21st Jan 28th Jan 4th Feb 11th Feb All Gather
t analysis Member data from
user
Object 4th Feb 4th Feb 11th Feb 13th Feb All UML
oriented Member Diagrams
design
-models
FP 11th Feb 11th Feb 13th Feb 13th Feb All Effort and
Calculation Member cost
estimation
Design user 25th Feb 4th Mar All Internet
interface Member Browser
Coding 11th Mar 18th Mar All
Member

Database 11th Mar 25th Mar All

connectivity Member
Testing 25th Mar 8th Apr All
Member
Maintenanc 8th Apr 22nd Apr All
e and Member
feedback
Function point estimation

External Inputs:-
Date
Name of Customer
Password
Login Id
Count =4

External Outputs:
Count =0

External Inquiries:-
Solutions available for problems
Count =1

External Logical Files:-

Customer Log
Supermarket Log
Count=2

External Interface:-
Count=0

Weighing Factor
Information Domain value Count Simple Medium Complex Total
Number of User Inputs 4 x 3 4 6 =16
Number of User Outputs 0 x 4 5 7 =0
Number of User Inquiries 1 x 3 4 6 =3
Number of User Files 2 x 7 10 15 =100
Number of External Interface 0 x 5 7 10 =
Count Total =119

Value added function Value

Backup and Recovery 4

Data communication 2
Distributed Processing 3
Performance Critical 2
Existing Operating Environment 5
Online Data Entry 0
Input Transaction over Multiple Screens 5
ILFs Updated Online 3
Information Domain Value Complex 2
Internal Processing Complex 5
Code Designed for Reuse 5
Conservation/Installation in Design 3
Multiple Installations 5
Application Designed for Change 5
Total VAF 49

The estimated number of FP can be derived as

= 49x [0.65+0.01x119]
= 90.16