4.System Planning

8/12/2019 4.System Planning

1/12

OnlineClassifiedPortal.com

4.1 Requirement Specification

4.2 Feasibility Study

4.3 Risk nalysis

4.4 !ife Cycle "odel

4.# $ffort %istribution %ia&ram

4.' (ask %ependency %ia&ram 4.) Pro*ect Sc+edule

22


2/12


Requirements of client describe as follo,-

System s+ould proide secure and accurate data.

System s+ould easy to operate.

System s+ould proide information related to firm.

Guest-Site:

System s+ould display different Classifieds/ads ,it+ detail

information i.e. actiated by admin.

System s+ould proide facility to re&ister t+emseles as user

or adertiser.

System s+ould proide facility to searc+ particular classified

,it+ detail information.

System s+ould proide facility to &uest user to &ie t+emie, related to site as a feedback.

System s+ould proide company information0 policy0 etc.

User-Site:

System s+ould display different classified/ads ,it+ detail

information i.e. actiated by admin.

System s+ould proide facility to send query to adertiser for

particular classifieds/ads.

System s+ould enable to &et response from adertiser for

t+eir query.



System s+ould proide facility to sae particular

classifieds/ads as per t+em c+oice.

System s+ould proide facility to update user personal profile

and pass,ord.

System s+ould proide facility to &ie t+em ie, related to

site as a feedback.

23

4.1 Requirement Specification


3/12


Advertiser-Site:

System s+ould proide a facility to purc+ase a ne, sc+eme

as per t+em c+oice for upload classifieds/ads. System s+ould proide facility to upload t+eir classifieds/ads

in different sc+eme accordin& to different display format

aailable and mana&e t+em classified as per t+eir

requirement.

System s+ould enable to receie query from user for

particular classifieds/ads and &ie t+em response.



System s+ould proide facility to update user personal profile

and pass,ord.

System s+ould proide Sc+eme led&er t+at contain current

status of sc+eme and classifieds/ads upload in different

sc+eme.

System s+ould proide remainder related sc+eme status i.e.

sc+eme epiry and epiry point.

System s+ould proide facility to &ie t+em ie, related to

site as a feedback.

Admin-Site:

System s+ould proide follo,in& information to dmin.

Re&istered user information

dertiser information and t+ose sc+emes0 and

classifieds/ads information.

Feedback information

System s+ould proide facility to mana&e follo,in& database

entry to admin.

Sc+eme master

Price master

Cate&ory master Subcate&ory master

City

State

Country

Policy

dmin account master

System s+ould enable to actie /approe follo,in& request

Sc+eme request

Classifieds/ads request

System s+ould proide facility to upload and mana&eclassifieds/ads be+alf of adertiser.

24


4/12


System s+ould proide Sc+eme led&er of particular adertiser

t+at contain current status of sc+eme and classifieds/ads

upload in different sc+eme.



Feasibility study plays ery important role in t+e deelopment of any

system0 but ,+en it is t+e case of deelopment of any soft,are t+en its importance

increases muc+ more because in t+e case one s+ould be ery clear about aailability

of t+e time and resources. efore startin& t+e deelopment of t+e soft,are ones+ould &ie considerable amount of time for feasibility study because t+e successful

completion of pro*ect depends upon feasibility.

(+e feasibility of our pro*ect +as been *ud&ed on t+e basis of time0

tec+nolo&y0 resources aailable and pro*ect len&t+.

Time:

(+is pro*ect takes at least # mont+ to be completed if ,e take +elp of

reused components ot+er,ise it ,ill take ' mont+s to be completed.

e ,ill not make use of components and t+erefore ,ill be able to

complete t+e pro*ect in ' mont+s. (+us accordin& to time t+e feasibility is not

t+at ri&+t.

Technology:

(+e necessary tec+nolo&y0 i.0 front5end deelopment tool0 back5end

database tec+nolo&y and arious ot+er tools namely installation tools0 etc. for

deelopin& t+e system0 are already aailable ,it+in t+e or&aniation. So t+is

problem is feasible.

Resources:

e need &ood kno,led&e soft,are en&ineers and practitioners. e need

6et connection.

e +ae all t+e resources in t+e desired amount.

Project Size:

(+e Pro*ect sie mi&+t be aboe 1#777 !OC. (+is is *ust t+e rou&+assumption because ,e don8t +ae any basis of t+e past pro*ects.

2#

4.2 Feasibility Study


5/12


(+us t+e pro*ect oerall feasibility is normal and t+erefore ,e +ae

undertaken t+is pro*ect.

it+ t+e deelopment of t+e soft,are0 ,e +ae defined some proactie

risks before tec+nical ,ork initiated. (+is part of documents includes t+e risk

mana&ement step.

91: Risk : Unrealistic Deadline

Proaility : !"#

$m%act : &igh

Descri%tion:

ecause of t+e s+ort duration and lar&e system t+ere is

Probability not to complete t+e pro*ect ,it+in deadline.

'ontingency Plan:

From t+e startin& day of t+e pro*ect0 ,e +ae ,orked +ard and

ery speedily to complete t+e pro*ect ,it+in deadline.

()* Risk : 'ustomer +ill change re,uirements

Proaility : "#

$m%act : &igh

Descri%tion:-

(+e customer ,ill c+an&e t+e requirements ery frequently as

t+e pro*ect be&ins. So0 ,e +ae probability no to complete t+e pro*ect as

t+e customer required.

'ontingency Plan:

From t+e past pro*ect0 ,e +ae kno,led&e about it. So ,e

interact ,it+ customer eery time ne, ,ork be&ins and conduct F(R ;

reise t+e ,ork as t+e customer requires.

2'

4.3 Risk nalysis


6/12


(.* Risk : Develo%ers $ne/%erienced

Proaility : !"#

$m%act : &igh

Descri%tion:

ell deelopers of t+e soft,are are ineperienced of t+e .6$(

enironment. So0 t+ere is probability not to complete t+e pro*ect.

'ontingency Plan:

From t+e startin& day of t+e pro*ect0 ,e +ae ,orked +ard and

,e referred t+e books and also take t+e &uidance of t+e intelli&ent to

complete t+e pro*ect.

Technical Risk

01 2anguage Di33iculties

(+e familiarity ,it+ t+e front5end lan&ua&e is illustrated in t+is risk.

(+e reasons be+ind t+is risk are as follo,s-

(+e Pro*ect is mandatory built .6$( platform. Since t+is lan&ua&e is

ne, to t+e pro&rammers0 t+e pro&rammers mi&+t face somedifficulties.

s no one from t+e pro&rammers is partially familiar ,it+ t+is

platform0 some functionalities mi&+t not considered in

implementation or some functionalities mi&+t not ac+ieed

completely.

)1 S%eci3ication amiguity

(+e compleity of t+e requirements or inappropriate understandin& is

included in t+is risk. (+e reason be+ind t+is risk is as follo,s-

(+e specification of t+is pro*ects little profound and +ard to identify.

2)


7/12


.1 Technology Unkno+n

(+e risk is concerned ,it+ t+e unrealied tec+nical conditions.

(+e reasons be+ind t+is risk are as follo,s-

(+e platform ,e s+ould be ,orkin& on is client5serer enironment0

,+ic+ is introduction to all of us.

(+e lack of conceptual implement on t+is kind of enironment is

ne,.

The 3ish one diagram de%icting risks o3 our %roject

So3t+are Risk 4anagement Plan

1 i&+li&+t risk5item status in mont+ly pro*ect reie,s.

Compare ,it+ preious mont+8s rankin& status

#


8/12


(+e Online Classified Portal pro*ect requires frequent user interaction.

For t+at reason0 our first c+oice included t+e Prototype model. >o,eer0 ,e +ad

doubts about t+e prototype model0 and t+erefore ,e concluded to use t+e Spiral

"odel. (+e risk5based approac+ of t+e Spiral "odel is si&nificant to t+e

deelopment of t+is prototype0 and it ,ould also +elp select an establis+ed lifecycle

model or determine a different model constructed from arious p+ases of ot+erlifecycle models. fter re&ular reie,s0 ,e decided t+at t+e best approac+ ,as to use

a +ybrid model t+at ,ould implement t+e risk mana&ement of t+e spiral model alon&

,it+ t+e incremental model0 ,+ic+ is a miture of t+e prototype model and t+e linear

sequential model. Currently0 t+e pro*ect reoles around t,o establis+ed sta&es-

Requirement nalysis and Prototype %eelopment. boe fi&ure s+o,s t+e life

cycle for t+e deelopment process as ,ell as entry and eit criteria for t+e different

p+ases of t+e pro*ect.

2@

4.4 !ife Cycle "odel


9/12


Project Planning: 2 to 3 A

Re,uirement Analysis: 17 to 2# A

Design: 27 to 2# A

'oding: 1# to 27 A

Testing 6 Deugging: 37 to 47 A

37

(estin& and

%ebu&&in&

nalysis 937547A:

nd

%esi&n

9475#7A:

Codin&

91#527 A:

4.# $ffort %istribution


10/12


%eliery Confirmation

7ote:e prepare documentation of eery P+ase.

31

Re,uirements

Analysis

Re,uirements

Gathering

8stimation Scheduling

Testing

'oding 9

$ntegrating

4odule

Designing

4.' (ask %ependency %ia&ram


11/12


ork reakdo+n Structure


12/12


(ime line

33

Documents

4.System Planning