Software Project Plan

8/10/2019 Software Project Plan

http://slidepdf.com/reader/full/software-project-plan 1/35



1.0 Introduction1.1 Project ScopeDescription of Software

Console Based Bidding/Selling program

Inputs Login/Password of sellers/bidders Item information including: itle! starting bid! description! and ending date Item to be searc"ed #eedbac$ comments %additional functionalit&' #eedbac$ score %additional functionalit&'

(utputs otal amount in sales number of items total items unsold total amount of mone& spent b& a bidder number of items purc"ased b& bidder items bidder bids on t"at are in progress wit" totals)number in)progress! number winning!

* amount of winning items

Processing #unctionalit&• Input of login/password b& user and/or seller

• +ut"entication/,alidit& is c"ec$ed

• (nce aut"enticated sellers can post items t"at t"e& want to sell

• Searc" item results will be in lists

• Items will be put in alp"abetical order so it-s easier for bidder to find w"at t"e& are

loo$ing for

• Bidders can bid on a ailable items based on mone& a ailable and "ow muc" t"e& are

willing to spend on an item



• +t t"e end of t"e time period gi en! t"e person w"o would spend t"e most will win t"e

item

• + collection of operations will ta$e place after eac" auction. Suc" as declaring t"e

winner! updating items sold! dollars spent! and searc" list

1.2 Major Software unctions

#unctionalit&:Seller:

• Be able to post an item to sell

• Set Item s details upon bidding: title! description! starting price! ending date

• Be able to iew "istor&: total dollar amount sold! total unsold! items wit" no bids

• ,iew dollar amount of winning items

!idder:

• Place bid on in)progress1 items

• in bids! if "ig"est bidder on end date

• ,iew bid "istor& and details: total dollars spent and number of items! and dollar amountof winning items

• ,iew items t"e& bid on t"at are in progress wit" totals: number in)progress and numberwinning

"ministration:• +lp"abetical list of items

• Searc"ing mec"anism for items %based on $e&words for words in t"e title ordescription'

• Displa& +ccurate Item price



• 3"arge winning bidder accurate price and add amount to seller s totals

1.# Performance$!e%a&ior Issues

"ere are no special re4uirements for performance or be"a ior to note.

1.' Mana(ement and Tec%nical Constraints

ime 3onstraints:

• Deadline of Software Project 5anagement Plan: 5arc" 6! 2078

• Deadline of Software 9e4uirements Specification: 5arc" 2 ! 2078

• Drop dead deli er& date of completed program: +pril 7 ! 2078

• (ur team members are all full)time college students! and t"us "a e limited time to wor$

on t"e project.

;nowledge 3onstraints:

• "e following table s"ows w"at programming languages eac" team member "as

$nowledge of. <=ig"l& S$illed< means t"e team member is er& familiar wit" t"e

language! <;nown< means t"e team member "as some familiarit& wit" t"e language!

<Pending< means t"e team member is currentl& learning t"e language! and <>one< means

t"e team member "as no significant $nowledge of "ow to use t"e language.

Team Member

)nowled(e "ndrew *o%n )enn+ *os%

C,, =ig"l& S$illed =ig"l& S$illed =ig"l& S$illed =ig"l& S$illed"ssembl+ - /) ;nown ;nown >one ;nown

P P >one ;nown >one ;nown

!.N3T >one ;nown >one ;nown

C >one ;nown >one ;nown



TM4$CSS >one ;nown >one ;nown

5rupal >one ;nown >one >one

4inu6$7ni6 s%ell

scriptin(

>one ;nown >one ;nown

*a&a >one >one ;nown >one

S84 Pending >one Pending >one

C9 >one >one Pending >one

• +n& languages not listed are un$nown to an& of t"e team members. "us! t"e project

must be conducted entirel& using t"e abo e languages! unless we wis" to in est a large

amount of e?tra time learning new languages.

• If team wis"s to use database languages in t"e project! we will "a e to wait until ;enn&

and +ndrew get far enoug" in t"eir Database class t"is semester to "a e learned it.

• >one of t"e team members are aware of "ow to create a single application using multiple

programming languages.

#inancial 3onstraints:• (ur customer is unwilling to pa& an& mone&.

• (ur team members are all of limited means financiall&! and as we are alread& pa&ing

t"ousands of dollars for t"e class alone! we are unli$el& to be able to afford spending an&

mone& on t"e project.

• @i en t"e abo e factors! our budget for t"is project! not including transportation

e?penses! is limited to *0.

ec"nical 3onstraints:

• eam-s program must be capable of running on t"e professor-s computer t"roug" an eas&

step)b&)step process.



• "e program must be able to run 4uic$l& enoug" so t"at it-s user)friendl&.

• "ere is no upper bound gi en for "ow muc" acti it& t"e auction s&stem will be

"andling! so t"e program must be capable of running properl& e en for e?tremel& large

numbers of users and transactions.• "e program is designed to be used b& ordinar& people! so its interface must be easil&

usable e en b& someone wit" no programming bac$ground.

2.0 Project 3stimates

2.1 istorical data used for estimates

Astimates for t"e Software Project Plan were formed b& considering our team members writingspeed in t"e past and estimating t"e section s lengt". Astimates for t"e production of t"e correctfunctionalit& are based on t"e comple?it& of tas$! past e?periences! and emplo&ing rigoroustesting once a tas$ is completed. "e design section "as a minimum of . "ours for t"e main

project to ensure sufficient time is dedicated to it.

2.2 3stimations Tec%ni ues "pplied and ;esults

(nl& one estimation was made based on past "istorical data and educated guesses.

2.# 3stimates

ESTIMATES FOR SOFTWARE PLAN

Section <roup Member;esponsible

3stimated Time Needed- ours

1.1 os" 71.2 o"n 71.' +ndrew 72.1 ;enn& 72.# ;enn& 8#.1 +ndrew 8#.2 +ndrew 7#.# o"n 7'.1 os" 7'.2 o"n 7



'.# +ndrew 8'.' +ndrew 7=.1 ;enn& 2=.2 ;enn& 7

.1 os" 2

.2 o"n 7Time Spent in Meetin(s 3stimate: 70

Time Spent ;e&isin( inal Project: CPresentation 1 Preparations: 7

Software Plan Total 3stimated Time: '0

ESTIMATES FOR PROGRAM

Task/Base Functionality: Estimate Time Nee e!"ou#s$

raining in programming languages %in totals' 8C

7ser 4o( In$4o( out S+stem

Design 7Implementation 8

esting 7

Seller :Post Item to sell wit" title/description/ Starting Price/And date


esting

,iew Seller s Items Status %In)progress/Sold'

Design 0 .Implementation 8

esting 7

,iew otals/=istor& % otal sales/ of items/ otal unsold/>o bids'


esting 8

!idder:



,iew List of Items purc"ased %,iew =istor&' wit" totals:) otal * spent %completed'! >umber of items boug"t! Status %in progress/done'

) otal number of bids in progress! Bids winning! * amount of winning items

Design 2Implementation Eesting

Searc" #unction:


esting 2

3ategor& S&stem for Items


esting 7

Bid Price Displa&) place specified starting bid if no ot"er bids s"own) S"ows =ig"est Bid if 5ore t"an two bidsDesign 0.Implementation 2

esting 2

Bid Pa&ment/9esult

)price is second "ig" bid F 70G! c"arged to winning sellerafter time is o er

)If no bids! bid ends status c"anges to completed and no transactionta$e place


esting 2

;e&words in title and description #or Searc"




esting 2

Database #unctionalit& De elopment and testing for all features: 20

Total 3stimate for Pro(ram: 1''

A%%ITIONAL F&N'TIONALIT(

)enn+>s "dditional unctionalit+

+llow user to c"ange password


esting 7

If a field "as data entered and t"e user tries to 4uit t"en displa&: are &ou sure &ou want toe?itH nameJ "as data entered into it and will not be sa ed1


esting 2

Lea e an K1 out of star rating after purc"ase


esting 2

)enn+>s Total: 1

"ndrew>s "dditional unctionall+

>otif& a seller w"en t"e end date of an item t"e& listed for sale "as been reac"ed.

) ell t"e seller w"at item it was! w"et"er it was successfull& sold or not! and if so! "owmuc" it was sold for.




esting 2

Seller can edit t"e starting price or end date of an in)progress item t"e& listed for sale! if nobod&"as t"us far bid on it.


esting 2

Seller can cancel t"eir listing of an in)progress item if nobod& "as t"us far bid on it.


esting 2

Bidder notification w"en t"e end date of an item t"e& bid on "as been reac"ed.

) "e notification s"ould tell t"e bidder t"e item! if t"eir bid was successful or not! andt"e final sale price was.


esting 8

Let bidder $now if t"e& "a e alread& made a bid.

)+s$s user if new bid s"ould be placed.


esting 7

Displa& an error message w"en an incorrect or none?istent login id or password is entered.




esting 0 .

"ndrew>s Total: #1.=

*o%n>s "dditional unctionalit+Securit& +lgorit"m


esting 7

5essage Boards


esting 2

+dd comments to a user member Design 0 .Implementation 8

esting 2

3"ange currenc& format to Auropean or S st&le


esting 7

3"ange data format to Auropean or S st&le


esting 7

*o%n>s Total: 2'.=

*os%>s "dditional unctionalit+:

"e list of items sold under eac" categor& is in alp"abetical order




esting 7

Displa& an error message w"en a bidder t&pes in an in alid item to bid on


esting 7

3alculate t"e a erage of t"e ratings to see an o erall rating for eac" seller

Design 7

Implementation 8esting 2

9eplace password input c"aracter wit" ? s


esting 0.

*os%>s Total: 1=

36tra unctionalit+ <roup Total: /?

T@T"4 3STIM"T35 @7;S @; P;@*3CT:

TasA ours

Software Plan 60



Base #unctionalit& 7 7+dditional #unctionalit& EMProject 2 3ompletion! 9e isions! and Preparations 272@roup 5eetings 8

Total =2=2.' Project ;esources

"ile a complete team would contain all of t"e following personnel! + >ew =ope "as four teammembers. Aac" team member will be performing multiple jobs.

• Required ta!!

o Project 5anger) o"n

o Project eam Leader) o"n

o

Business +nal&st) o"no Software +rc"itect);enn&

o Designer)+ndrew

o Software De eloper)+ndrew

o Software ester) os"

• Required o!tware

o 5icrosoft ,isual Studio 2072 3FF

o 5icrosoft (ffice %or open source e4ui alent'

o +dobe P"otos"op %or open source e4ui alent'

o 5icrosoft indows (S

o Dropbo?

o S$&pe

o @oogle Docs

• Required Hardware "to run Visual tudio#$e%elop&ent so!tware'

o 7.C @"N or faster processor



o 7 @B of 9+5 %7. @B if running on a irtual mac"ine'

o 7 @B %> #S' of a ailable "ard dis$ space

o 600 9P5 "ard dri e

o DirectK O)capable ideo card running at 7026 ? MCE or "ig"er displa& resolution

#.0 ;isA Mana(ement#.1 Project ;isAs

• Loss of eam 5ember: If a team member were to drop t"e class! or worse! die.

• Indisposed eam 5ember: If a team member were to become incapacitated or ot"erwiseuna ailable for a significant lengt" of time! suc" as due to injur&! illness! or ot"er

problems.

• Personal Data Loss: If a team member-s computer or ot"er memor& storage de ice

cras"ed! causing t"eir wor$ done t"us far to be lost.

• (nline Data Loss: Data we "a e stored online mig"t be lost! per"aps due to unforeseen

tec"nical difficulties on t"e part of t"e website.

• (nline Data na ailabilit&: Data we "a e stored online ma& be made temporaril&

una ailable at an important time! per"aps due to sc"eduled maintenance on t"e part of t"e

website.

• Irresponsible eam 5ember: If a team member were to become irresponsible and refuse

to do t"e wor$ assigned to t"em.

• Procrastinating eam 5ember: If a team member were to refuse to do wor$ until t"e

absolute last minute.

• 3onflicting 9esponsibilities: If a team member were to become so bus& wit" ot"er

responsibilities! suc" as "omewor$ or e?ams from ot"er classes! t"at t"e& are temporaril&

unable to in est time on t"is project.



• 3ompiler Incompatibilities: If using different compilers caused code written b& one team

member on t"eir compiler to not wor$ for t"e ot"er team member on t"eir differing

compiler.

•

ime 9uns (ut: If it loo$s li$e we will be unable to meet t"e project deadline.

#.2: ;isA Table

9is$ >ame Probabilit& Impact 958 Pointer

Loss of eam 5ember Low 3ritical 5itigation 7!

5onitoring 8!

5onitoringC!5anagement 2

Indisposed eam5ember

Low =ig" 5itigation 7!

5onitoring 7!

5onitoring !

5onitoring C!

5anagement 2

Personal Data Loss 5edium =ig" 5itigation 7!

5onitoring C

(nline Data Loss Low 5edium 5itigation 8!

5onitoring C

(nline Datana ailabilit&

Low 5edium 5itigation 8!

5onitoring C

Irresponsible eam5ember

Low 3ritical 5itigation 7!

5onitoring !



5onitoring C!

5anagement 2

Procrastinating eam5ember

=ig" 5edium 5onitoring !

5onitoring C!5anagement E

3onflicting9esponsibilities

=ig" =ig" 5itigation E!

5onitoring 2!

5onitoring C!

5anagement 2

Poor Astimates =ig" 5edium 5itigation 2!5onitoring 7!

5onitoring C!5anagement 7

Language Incapabilit& Low =ig" 5itigation 6!

5onitoring 7!

5onitoring C!

5anagement 6

3"anged9e4uirements

Low =ig" 5onitoring C!

5anagement 8Language LearningDifficult&

Low =ig" 5itigation 2!5itigation 6!

5itigation O!

5onitoring 7!

5onitoring C!

5anagement 7

nable to 5eet 5edium 5edium 5onitoring 6!

5onitoring !5onitoring C!

5anagement !

5anagement C

3oding Arrors =ig" =ig" 5itigation O!



5onitoring C!

5anagement 8

Debugging Difficulties =ig" =ig" 5itigation O!

5onitoring 7!5onitoring !

5onitoring C!

5anagement 7!

5anagement 8

+dditional#unctionalit&Problems

5edium Low 5onitoring 7!

5onitoring !

5onitoring C

3ode 5ergingDifficulties

=ig" 5edium 5itigation C!

5itigation O!

5onitoring !

5onitoring C!

5anagement 7

Personal 3onflict Low =ig" 5onitoring C

Alectronic Sabotage Low ,aries depending on

se erit& potentiall&critical.

5itigation 7!

5itigation 8!5itigation !

5onitoring C!

5anagement 2

3ompilerIncompatibilities

Low Low 5itigation M!

5onitoring C

ime 9uns (ut 5edium 3ritical 5itigation 2!

5itigation O!

5onitoring 7!5onitoring !

5onitoring C!

5anagement 7

5anagement 2!

5anagement M



#.#: @&er&iew of ;isA Miti(ationB Monitorin(B Mana(ement

5itigation

7. =a e a bac$up for all project wor$ so far completed)) stored online.

2. +llocate an e?tra amount of time for project tas$s ) assume t"at project tas$s ma& ta$e

longer t"an estimated! and plan accordingl&.

8. eam members s"ould not delete an& project wor$ t"e& "a e done e en after t"e& upload

t"em! in case t"e online data is lost some"ow.

6. eam members s"ould begin learning t"e programming language of c"oice before we

actuall& "a e to code t"e project ) preferabl& o er spring brea$ at t"e latest.

. +ll team members s"ould ensure t"e& "a e some form of anti) irus and firewall installed.

C. eam members s"ould $eep eac" ot"er informed of t"e met"ods b& w"ic" t"e& are

implementing t"eir portions of t"e code wit" s"ort e)mail summaries.

M. +ll team members s"ould use 5icrosoft ,isual Studio as t"eir compiler.

E. eam members s"ould "a e slig"tl& reduced wor$loads during wee$s w"en t"e& "a e

multiple e?ams! and s"ould be assigned larger wor$loads to ma$e up for it on ot"er

wee$s w"en ot"er team members "a e t"e same problems.

O. +llocate ade4uate debugging and testing time in project sc"edule.

5onitoring

7. If a team member t"in$s t"e& will not be able to meet t"eir deadline on a tas$! t"e&s"ould immediatel& e)mail t"e group to sa& so.

2. eam members s"ould tell t"e group about an& e?ams or projects from ot"er classes t"at

ma& pre ent t"em from wor$ing on t"is project.

8. If a team member feels t"e& ma& "a e to drop t"e class! t"e& s"ould warn t"e group asearl& as possible.

6. If a team member can-t ma$e an assigned meeting time! t"e& s"ould sa& so in ad ance.

. "e team leader s"ould regularl& as$ team members "ow t"eir tas$s are progressing.



C. "e team s"ould briefl& discuss all t"e project ris$s! and possible new ris$s! at least once per meeting.

5anagement

7. In t"e e ent t"at a team member is unable to complete a tas$ on t"eir own or ta$es toolong! team leader s"ould assign anot"er team member to assist t"em. "e two teammembers s"ould t"en meet in person to o ercome t"e "urdle.

2. In t"e e ent t"at a team member is unable or unwilling to do a job! t"e team leader s"ouldassign anot"er team member to perform t"e tas$. If t"e team member is beingirresponsible! t"e team leader and t"e rest of t"e team s"ould t"reaten t"e team memberwit" negati e e aluations.

8. If it becomes necessar& to ma$e large re isions of earlier documentation to t"e point t"atit distracts from ot"er project tas$s ) "a e one person put in c"arge of re ising all t"eearlier documentation as necessar&! wit" t"e ot"er team members just telling t"at personw"at t"e& c"anged! so t"at t"e rest of t"e team can focus on t"e current portion of t"e

project instead of spending all t"eir time re ising t"e documentation o er and o er again."e team leader s"ould (; t"e final re ision for eac" part of t"e project. "e least adept

coder s"ould preferabl& be assigned t"is tas$.

6. In t"e e ent t"at we "a e to c"ange programming languages! we s"ould decide at ameeting w"et"er it would be better to reduce t"e project scope before we go to t"e troubleof starting o er wit" anot"er language! and t"e team s"ould pic$ a new language t"at atleast t"ree people in t"e group alread& $now! as we are unli$el& to "a e time to learn anew language.

. In t"e e ent t"at t"e group is unable to meet in person! we s"ould "old a group meetingo er S$&pe.

C. In t"e e ent t"at a member can-t ma$e it to a meeting! t"e team leader s"ould send t"eman e)mail summariNing t"e decisions and results of t"e meeting.

M. In t"e e ent t"at it loo$s li$e we literall& cannot meet t"e deadline for t"e project! wes"ould reduce t"e project scope and just tr& to "a e some partiall& functional program toturn in.

E. If a team member appears to be procrastinating! t"e team leader s"ould politel& butincessantl& remind t"em to start t"eir tas$ soon.

'.0 Project Sc%edule'.1 Project TasA Set

Process 5odel

7. 5odel: aterfall 5odel



#ramewor$ +cti ities and +cti ities

2. 3ompiler: ,isual Studio 2072

8. Language: 3F

• as$s to be accomplis"ed

• Set up a login and password for users to access

• Password input replaced b& ?-s

• Limit username siNe between C)7

• #irst c"aracter must be a letter

• Sellers lists items a ailable for sell in t"e database

• ;eep rac$ of Seller information

•

Items to sell

• Details about item: itle! Description! Starting price! ending date! total dollar amount!total unsold! items wit" no bids

• ;eep trac$ of Bu&er/Bidder information



• List of items t"e& purc"ased wit":

• otal dollars spent

• >umber of items

• Items t"e& bid on t"at are in progress wit" totals:

• >umber in)progress

• >umber winning

• Dollar amount of winning items

• Searc"ing mec"anism

• +lp"abetical list of items

• Different categories of items

• Loo$ing for words in t"e title or description

• "e bidding process

•

During an in)progress auction! t"e bidder can place a bid on t"at items t"at must be"ig"er t"an t"e current price s"own w"ic" is starting price if no bids! bid price if one bidor second "ig" bid F 70G if multiple bids %bid price if bid price is less t"an second "ig" F70G'

'.2 unctional 5ecomposition

!ase unctionalit+:• Seller

o +bilit& to c"oose item categories



o Aditable item details

itle

Description

Starting Price

Anding Dateo List of items

Sold

In)progress

(r bot"o List of totals for items

* amount of sales

>umber of items

otal unsold %completed'

>o bids %in)progress'• !idder

o List of items

Purc"ased wit" totals

otal * spent%completed'

>umber of items purc"ased

Items t"e& bid on t"at are in)progresso List of totals

>umber of bids in progress

>umber of bids winning

* amount of winning itemso Bidding on in)process items from +>Q list

Place specified starting bid if no ot"er bids s"own

Place bids "ig"er t"an current price s"own

Bid price if one bid or second "ig" bid F 70G if multiple bids %bid price if bid price IS LASS t"an second bid F 70G'.

• "dministration

o 5ust "a e login IDs and passwordso Searc" b&

3ategor&



"dditional unctionalit+:• Seller

o >otif& seller w"en end date of an item listed for sale "as been reac"ed

"ic" item

Successfull& sold or notIf sold! "ow muc" sold for

o +bilit& to cancel item if no bids "a e been placed• !idder

o >otif& bidder w"en end date of an item t"e& bid on "as been reac"ed

"ic" item

Successful bid or not

If won! "ow muc" boug"t for o If bidder attempts to place a bid on item! interruption in t"e s&stem occurs if

bidder "as alread& placed bid on t"at item.

S&stem notifies bidder t"e& "a e alread& placed bid

+s$s user if t"e& would still li$e to place t"e bido Lea e a K out of star rating after purc"ase

• "dministration

o Displa& error message w"en an incorrect or none?istent login ID or password isentered

o

Securit& algorit"ms to $eep user passwords secureo +llow user to c"ange password

t&ping in current password! t"en new password twiceo 5essage board for items being soldo +bilit& for all users to add comments to a seller or bu&ers profileo +bilit& to c"ange currenc& format to Auropean or S st&leo +bilit& to c"ange date format to Auropean or S st&leo If a field "as data entered and t"e user tries to 4uit t"en displa&: are &ou sure &ou

want to e?itH nameJ "as data entered into it and will not be sa ed1o List of items sold under eac" categor& can be listed alp"abeticall&o Displa& error message w"en a bidder t&pes in an in alid bido 3alculate a erage of t"e ratings to sees an o erall rating for eac" seller o 9eplace password input wit" ?1-so Set a limit of user name siNe between C)7 wit" onl& letters and numbers! first

c"aracter must be a letter.



'.# TasA NetworA and Timeline C%art

as$ as$ Duration Predecessors

7 5eeting 7 . "ours

2 Decide +dditional #unctionalit& 7 "our 78 Software Project Plan Section 7 8.M =ours 7

6 5eeting 2 7. =ours 2

Software Project Plan Section 2 6 "ours 6

C Software Project Plan Section 8 2. =ours 6

M 5eeting 8 7. =ours 8!6

E Software Project Plan Section 6 6 =ours M

O Software Project Plan Section 8 =ours M

70 Software Project Plan Section C 8 =ours M

77 5eeting 6 7. =ours !C!M72 Software Project Plan Section M . =ours 77

78 5eeting 6 =ours E!O!70!77!72

76 Software Project Plan 9e ision C =ours 78

7 Project 7 Presentation Preparation 7 =our 77

7C Project 7 Presentation o 3lass 7 minutes 76!7

7M Learning Programming Languages 8C =ours

7E (t"er 5eetings 20 =ours 7C

7O Project Part 2 200 =ours 7C

20 9e isions of Project 7 C =ours 7O

27 Implementing Login #unctionalit& =ours 7M!7O

22 Implementing Seller #unctionalit& 8O. =ours 7M!7O

28 Implementing Bu&er #unctionalit& 7 =ours 7M!7O

26 Implementing Searc"ing 5ec"anism 72 =ours 7M!7O

2 Implementing Bidding Process 7C =ours 7M!7O

2C Implementing +dditional #unctionalit& EO =ours 7M!7O

2M 9e isions of Project 7 and 2 72 =ours 27!22!28!26!2 !2C!2M

2E #inal Presentation Preparation 7 =our

20 #inal Presentation 7 minutes 2E

Section : Staff (rganiNation=.1 Team Structure

"e team roles and responsibilities for t"e team are determined b& w"o is best suited for eac"

position. o"n is t"e most $nowledgeable member of t"e team so "e is t"e Project eam Leader



and 5anager. =is responsibilities include ensuring deadlines are met! issues are resol ed swiftl&!

and t"at e er&one understands w"at t"eir assignments are.

"e project will be di ided into database and forms for design. ;enn& and +ndrew are in a

database class and are better suited to design and implement t"e tables and 4ueries t"at will be

re4uired. o"n and os" "a e a bac$ground wor$ing wit" form based applications %,B.>A ' and

would be better suited to designing "ow t"e forms will loo$! integrate 4uer& result data! and

function

"e entire team will ser e as software de elopers and testers w"en writing t"eir own code. "eir

responsibilit& is to ensure t"e code segment "as sufficient comments and deli ers on its re4uiredfunctionalit& wit"out enormous mista$es or bugs.

=.2 Mana(ement ;eportin( and Communication

"e team will "old meetings e er& "ursda& morning at 77:00 +5 to discuss current project

progress. #or more immediate communication all members "a e access to eac" ot"er s email!

cell p"one numbers! and S$&pe. In addition! all members will briefl& discuss t"eir current status

on 5onda&s and ednesda& before/after t"e software engineering classes. Dropbo? and email

will be used as primar& means to s"are important artifacts. "e team will identif& le el of

progress b& using metrics created during a er& detailed design p"ase.

.0 TracAin( and Control Mec%anisms

.1 Software 8ualit+ "ssurance

Rualit& is a $e& aspect of a product. "ere are se en elements to assure t"is.• +pplication of ec"nical 5et"ods



• #ormal ec"nical 9e iews• Software esting• 3ontrol of 3"ange• 5easurement• 9ecord ;eeping• 9eporting

+pplication of ec"nical 5et"ods• It-s good if &ou $now "ow to code! but if t"e planning is bad and &ou don-t understand

w"at t"e correct problem is! &ou will end up wit" t"e wrong results• "e anal&st pla&s an important role in t"is. =e/S"e s"ould $now "ow to:

o @rasp abstract conceptso (rganiNe solutions to smaller problems

o +bsorb facts from different sourceso nderstand t"e user/client en ironmento +ppl& "ardware and/or software s&stem elements to t"e en ironment

• 5odeling "as to ta$e placeo #ocuses on w"at t"e s&stem "as to doo =elps in understanding function and be"a ior to ma$e implementation easier o =elps determine completeness! consistenc&! and accurac&o Basicall& a mapped representation

• Partitioningo + project as a w"ole is usuall& er& complicated and ta$es man& stepso Brea$ing down t"e problem to smaller pieces will ma$e t"e problem easier!

because doing small increments won-t be as comple?

#ormal ec"nical 9e iews• Preparation for t"e product is essential• 9e iews mig"t include error detection! inspection! a wal$ t"roug"! and ot"er assessments• Doing t"is is a good learning tool for t"ose w"o are not t"at familiar wit" planning and

design• 5eetings are important• suall& during meetings! updates are broug"t up. 5embers s"ow t"eir assigned

completed tas$s• "e ne?t steps mig"t be presented! along wit" possible c"anges• +not"er factor is duration of t"e meeting• If a meeting is too s"ort! important announcements mig"t be missed



• If a meeting is too long! time will be wasted t"at could be used to wor$ • "en a meeting-s about to close! and if decisions are made about a project! attendants of

t"at meeting sign off to indicate t"at t"e& agree to it and are responsible• If participants don-t accomplis" w"at needs to be accomplis"ed! t"e& are t"en "eld

responsible

Software esting• + product isn-t deli erable if it doesn-t do w"at &ou want it to do 700G of t"e time• + few of t"e wa&s to test

o "e college wa&: "en &ou compile a program! put in alues t"at &ou $nows"ould wor$ to ma$e sure &ou get t"e rig"t result

o "e business wa&: Brea$ it Purposel& tr& and come up wit" solutions t"at s"ouldfail. "en &ou can wor$ from t"ere to fi? t"e errors so e entuall& &ou can-t

purposel& brea$ t"e program•

5ore t"an just w"en t"e software is completed. It s"ould start earl& in t"e project• +bout 80G of t"e project in ol es testing

3ontrol of 3"ange• "ere will certainl& be c"ange some time during a project. "ings will come up t"at are

una oidable.• "e goal is to minimiNe c"ange• Before a c"ange is to be made! ma$e sure it is necessar&• If a c"ange is to occur! t"ere will probabl& be a cost w"et"er it-s time! mone&! or bot"• 3"anges s"ould be anal&Ned! reported! and recorded



5easurement• 5eas

urementsarene er

perfect•

"e& are based on estimates and prior $nowledge and e?perience• as$s are measured b& time spent and completeness• 5easurements turn opinions into facts• Data is gat"ered and processed. "roug" measured anal&sis! t"ere-s:

o 3"aracteriNation:

@ain understanding of processo A aluation:

Determine t"e status wit" respect to t"e planso

Prediction:"roug" understanding and information! attributes can be predicted

o Impro ement:

#i?ing errors! getting t"roug" obstacles! and inefficiencies



9ecord ;eeping• Aac" element of a project needs to be recorded• A er&t"ing from diagrams! to outlines! to code! c"anges! and ot"er elements need to be

written down to document w"at "as been done! and w"at needs to be done.•

"en members of a group are assigned tas$s! t"e& are recorded so t"e& $now w"at t"e&are responsible for and are "eld accountable for t"ose tas$s

9eport• @oing along wit" recording is t"e concept of reporting

o + report is generated from t"e information t"at is gat"ered from t"e meetingso Some of t"e information t"at mig"t be in t"e report includes:

"at was re iewedH

"o re iewed itH

"at were t"e findingsH

3onclusionsH

.2 C%an(e mana(ement and control

Introduction"e 3"ange 5anagement Plan was created for t"e 3IS8M : (n)Line +uction S&stem %(+S'

team! + >ew =ope! in order to set e?pectations on "ow t"e approac" to c"anges will bemanaged! w"at defines a c"ange! t"e purpose and role of t"e c"ange control board! and t"e

o erall c"ange management process. +ll sta$e"olders will be e?pected to submit or re4uestc"anges to t"e (+S Project in accordance wit" t"is 3"ange 5anagement Plan and all re4uestsand submissions will follow t"e process detailed "erein.

C%an(e Mana(ement "pproac%"e 3"ange 5anagement approac" for t"e (+S will ensure t"at all proposed c"anges are

defined! re iewed! and agreed upon so t"e& can be properl& implemented and communicated toall sta$e"olders. "is approac" will also ensure t"at onl& c"anges wit"in t"e scope of t"is projectare appro ed and implemented.

"e 3"ange 5anagement approac" is not to be confused wit" t"e 3"ange 5anagement Processw"ic" will be detailed later in t"is plan. "e 3"ange 5anagement approac" consists of t"reeareas:

• Ansure c"anges are wit"in scope and beneficial to t"e project• Determine "ow t"e c"ange will be implemented• 5anage t"e c"ange as it is implemented



"e 3"ange 5anagement process "as been designed to ma$e sure t"is approac" is followed forall c"anges. B& using t"is approac" met"odolog&! t"e (+S project team will pre entunnecessar& c"ange from occurring and focus its resources onl& on beneficial c"anges wit"in t"e

project scope.

5efinitions of C%an(e

"ere are se eral t&pes of c"anges w"ic" ma& be re4uested and considered for t"e (+S project.Depending on t"e e?tent and t&pe of proposed c"anges! c"anges to t"e project documentationand t"e communication of t"ese c"anges will be re4uired to include an& appro ed c"anges intot"e project plan and ensure all sta$e"olders are notified. &pes of c"anges include:

• Sc"eduling 3"anges: c"anges w"ic" will impact t"e appro ed project sc"edule. "ese

c"anges ma& re4uire fast trac$ing! cras"ing! or re)baselining t"e sc"edule depending ont"e significance of t"e impact.

• Scope 3"anges: c"anges w"ic" are necessar& and impact t"e project s scope w"ic" ma& be t"e result of unforeseen re4uirements w"ic" were not initiall& planned for. "esec"anges ma& also impact t"e sc"edule. "ese c"anges ma& re4uire re ision to projectscope statement! and ot"er project documentation as necessar&.

"e project manager must ensure t"at an& appro ed c"anges are communicated to t"e projectsta$e"olders. +dditionall&! as c"anges are appro ed! t"e project manager must ensure t"at t"ec"anges are captured in t"e project documentation w"ere necessar&. "ese document updates

must t"en be communicated to t"e project team and sta$e"olders as well.

C%an(e Control !oard

"e 3"ange 3ontrol Board %33B' is t"e appro al aut"orit& for all proposed c"ange re4uests pertaining to t"e (+S Project. "e purpose of t"e 33B is to re iew all c"ange re4uests!determine t"eir impacts on t"e project ris$! scope! cost! and sc"edule! and to appro e or den&eac" c"ange re4uest. "e following c"art pro ides a list of t"e 33B members for t"e IS Project:

Name Position CC! ;ole

. Battaglia Project Sponsor 33B 3"air

+. ,osNat$a Project 5anager 33B 5ember

. 5ajor Project eam 5ember 33B 5ember



;. rena Project eam 5ember 33B 5ember

+s c"ange re4uests are submitted to t"e (+S Project 5anager b& t"e project team/sta$e"olders!t"e Project 5anager will log t"e re4uests in t"e c"ange log and t"e 33B will con ene e er&

"ursda& to re iew all c"ange re4uests. #or a c"ange re4uest to be appro ed! all 33B membersmust ote in fa or. In t"e e ent more information is needed for a particular c"ange re4uest! t"ere4uest will be deferred and sent bac$ to t"e re4uestor for more information or clarification. If ac"ange is deemed critical! an ad "oc 33B meeting can be called in order to re iew t"e c"ange

prior to t"e ne?t sc"eduled wee$l& 33B meeting.

;oles and ;esponsibilities

"e following are t"e roles and responsibilities for all c"ange management efforts related to t"e

(+S Project:

Project Sponsor:• +ppro e all c"anges to budget/funding allocations• +ppro e all c"anges to sc"edule baseline• +ppro e an& c"anges in project scope• 3"air t"e 33B

Project 5anager:• 9ecei e and log all c"ange re4uests from project sta$e"olders• 3onduct preliminar& ris$! cost! sc"edule! scope anal&sis of c"ange prior to 33B• See$ clarification from c"ange re4uesters on an& open issues or concerns• 5a$e documentation re isions/edits as necessar& for all appro ed c"anges• Participate on 33B

Project eam/Sta$e"olders:•

Submit all c"ange re4uests on standard organiNational c"ange re4uest forms• Pro ide all applicable information and detail on c"ange re4uest forms• Be prepared to address 4uestions regarding an& submitted c"ange re4uests• Pro ide feedbac$ as necessar& on impact of proposed c"anges

C%an(e Control Process



"e 3"ange 3ontrol Process for t"e (+S Project will follow t"e organiNational standard c"ange process for all projects. "e project manager "as o erall responsibilit& for e?ecuting t"e c"angemanagement process for eac" c"ange re4uest.

7. Identif& t"e need for a c"ange %Sta$e"olders' T 3"ange re4uester will submit a completedc"ange re4uest form to t"e project manager.

2. Log c"ange in t"e c"ange re4uest register %Project 5anager' T "e project manager will$eep a log of all submitted c"ange re4uests t"roug"out t"e project s lifec&cle.

8. A aluate t"e c"ange %Project 5anager! eam! 9e4uester' T "e project manager willconduct a preliminar& anal&sis on t"e impact of t"e c"ange to ris$! cost! sc"edule! andscope and see$ clarification from team members and t"e c"ange re4uester.

6. Submit c"ange re4uest to 33B %Project 5anager' T "e project manager will submit t"ec"ange re4uest! as well as t"e preliminar& anal&sis! to t"e 33B for re iew.

. (btain Decision on c"ange re4uest %33B' T "e 33B will discuss t"e proposed c"angeand decide w"et"er or not it will be appro ed based on all submitted information.

C. Implement c"ange %Project 5anager' T If a c"ange is appro ed b& t"e 33B! t"e projectmanager will update and re)baseline project documentation as necessar&.

Sponsor "cceptance

5ate:



.0 "ppendi6

Customer ;e uirements:

Software Project Plan

Documents

Transcript of Software Project Plan