TheWeddingPlanningSystem

SoftwareRequirementsSpecification
Version1.0
3May2012
DanCoulter
SidneyHaynes
JohnsonHu
RosyUpreti
SepidehDeliri

Preparedfor
SWE620SoftwareRequirementsAnalysisandSpecification
Instructor:Dr.FrankArmour
Spring2012

WeddingPlanningSystem

TableofContents
1.

PROJECT DRIVERS........................................................................................1
1.1 THE PURPOSE OF THE PROJECT........................................................................................... 1
1.1.1 The user problem or background of the project effort..........................................1
1.1.2 Goals of the Project..............................................................................................1
1.2 CLIENT, CUSTOMER, AND OTHER STAKEHOLDERS....................................................................2
1.2.1 Buyer and Owner of the System...........................................................................2
1.2.2 Customers of the System.....................................................................................2
1.2.3 Other Stakeholders..............................................................................................2
1.3 USERS OF THE PRODUCT.................................................................................................... 3
1.3.1 The hands-on users of the product.......................................................................3
1.3.2 The Priorities Assigned to Users...........................................................................4
1.3.3 User Participation.................................................................................................4
1.3.4 Maintenance users............................................................................................... 5
1.3.5 User Hierarchy..................................................................................................... 6

2.

PROJECT CONSTRAINTS................................................................................6
2.1 MANDATED CONSTRAINTS.................................................................................................. 6
2.1.1 Solution Design Constraints.................................................................................6
2.1.2 Implementation Environment of the Current System...........................................7
2.1.3 Partner or Collaborative Applications...................................................................7
2.1.4 Anticipated Workplace Environment....................................................................8
2.1.5 How long do the developers have for the project?...............................................8
2.1.6 What is the financial budget for the project?.......................................................8
2.2 NAMING CONVENTIONS AND DEFINITIONS..............................................................................8
2.2.1 Definitions............................................................................................................ 8

3.

FUNCTIONAL REQUIREMENTS.......................................................................9
3.1 THE SCOPE OF THE WORK................................................................................................. 9
3.1.1 Context Diagram.................................................................................................. 9
3.2 THE SCOPE OF THE PRODUCT........................................................................................... 10
3.2.1 Product Use Case Diagram.................................................................................10
3.2.2 Product Use Case List......................................................................................... 10
3.3 FUNCTIONAL AND DATA REQUIREMENTS..............................................................................11
3.3.1 Functional Requirements Use Cases..................................................................11
3.3.2 Functional Requirements Use Case Mock-ups....................................................23

4.

NON-FUNCTIONAL REQUIREMENTS..............................................................25
4.1 LOOK AND FEEL REQUIREMENTS........................................................................................25
4.1.1 The Interface...................................................................................................... 25
4.1.2 The Style of the Product.....................................................................................26
4.2 USABILITY AND HUMANITY REQUIREMENTS...........................................................................26
4.2.1 Ease of Use........................................................................................................ 26
4.2.2 Personalization and internationalization.............................................................28
4.2.3 Ease of Learning................................................................................................ 28
4.2.4 Understanding and Politeness Requirements.....................................................29
4.2.5 Accessibility Requirements................................................................................29
4.3 PERFORMANCE REQUIREMENTS.......................................................................................... 29
4.3.1 Speed and Latency Requirements......................................................................29
4.3.2 Reliability and Availability Requirements...........................................................30
4.3.3 Robustness or Fault Tolerance Requirements.....................................................30
4.3.4 Longevity Requirements....................................................................................31
4.4 OPERATIONAL REQUIREMENTS........................................................................................... 31

SoftwareRequirementsSpecification

Page

WeddingPlanningSystem

1. Project Drivers
1.1 The Purpose of the Project
1.1.1 The user problem or background of the project effort
FruitionWeddingPlanners(FWP)isacompanywhichhelpstoorganizesuccessfulwedding
eventsfortheirclients.FWPprovidesguidanceandhelpsclientsinthedecisionmakingand
planningprocessesassociatedwiththemanyaspectsoforganizingawedding.Currently,FWP
hasconsultantswhichmeetwiththeircustomerbase,whichrepresentsbothclientsandvendors
alike.Theseconsultantsareofferingtheirservicesasadvisersandcommunicatorsactingasa
middlemanbetweenbothparties.Currently,theconsultantsleveragefacetofacemeetingsas
wellasphonecallsandemailsasaformofimmediatecommunicationwiththecustomers.
Customsoftwaresolutionsarebeingusedtosupporttheconsultants,intheformofacase
managementsystemwhichoffersminimalsupportfortrackingandmanagingeachclient's
weddingevent.
OverTime,thecurrentandpotentialfuturecustomerbasehasbecomemoretechnologically
affluent,adaptingtotheinternetageandbreakthroughsinmobiletechnology.Asaresultthereis
nowahighdemandbythemarkettoprovideonlineservicesforcustomeruse.FWPwouldlike
topenetratetheecommercemarketandutilizetheeconomiesofscalethroughthedevelopment
ofanonlineweddingplanningtool.Theweddingplanningtoolwillbecomeasystemaccessible
onlineandusedbyconsultants,vendors,andclientsalike.Eachuserbasewilltakeadifferent
perspectivetowardsthetool,basedontheneedsoftheirroleswithintheweddingplanning
system.Clientswillusethetooltoplanouttheirweddings.Vendorswillusethetooltomarket
andselltheirservices.Consultantswillusethetooltoassistininteractionsbetweenbothclients
andvendors.Thustheweddingplanningsystemwillsolvealargeaccessibilityand
communicationsproblemfortheFWP,andencouragemoreinteractivityonbehalfofall
customersandexpandthecustomerbase.ThissolutionwillalsomodernizetheFWP.
1.1.2 Goals of the Project

TheSystemshallincreaseFWP'sclientbaseby50%

TheSystemshallincreaseFWP'svendorbaseby20%
TheSystemshallreducethetimeofplanningandorganizingtheweddingrelatedservices
by50%
TheSystemshallreducethecostforclientsandvendorstofacilitateweddingrelated
servicesby15%
4.4.1
TheSystemshallincreaseFWP'soverallprofitby25%
Partner Applications........................................................................................... 31
4.5 MAINTAINABILITY AND SUPPORT REQUIREMENTS....................................................................31
4.5.1 Maintenance Requirements................................................................................31
4.5.2 Supportability Requirements..............................................................................32
4.6 SECURITY REQUIREMENTS................................................................................................ 32
4.6.1 Access Requirements......................................................................................... 32
4.7 CULTURAL AND POLITICAL REQUIREMENTS...........................................................................32
4.7.1 Cultural Requirements.......................................................................................32
5.

PROJECT ISSUES........................................................................................33
5.1 NEW PROBLEMS............................................................................................................. 33
5.1.1 What problem could the new product cause in the current environment?.........33

WeddingPlanningSystem

1. Project Drivers
1.1 The Purpose of the Project
1.1.1 The user problem or background of the project effort
FruitionWeddingPlanners(FWP)isacompanywhichhelpstoorganizesuccessfulwedding
eventsfortheirclients.FWPprovidesguidanceandhelpsclientsinthedecisionmakingand
planningprocessesassociatedwiththemanyaspectsoforganizingawedding.Currently,FWP
hasconsultantswhichmeetwiththeircustomerbase,whichrepresentsbothclientsandvendors
alike.Theseconsultantsareofferingtheirservicesasadvisersandcommunicatorsactingasa
middlemanbetweenbothparties.Currently,theconsultantsleveragefacetofacemeetingsas
wellasphonecallsandemailsasaformofimmediatecommunicationwiththecustomers.
Customsoftwaresolutionsarebeingusedtosupporttheconsultants,intheformofacase
managementsystemwhichoffersminimalsupportfortrackingandmanagingeachclient's
weddingevent.
OverTime,thecurrentandpotentialfuturecustomerbasehasbecomemoretechnologically
affluent,adaptingtotheinternetageandbreakthroughsinmobiletechnology.Asaresultthereis
nowahighdemandbythemarkettoprovideonlineservicesforcustomeruse.FWPwouldlike
topenetratetheecommercemarketandutilizetheeconomiesofscalethroughthedevelopment
ofanonlineweddingplanningtool.Theweddingplanningtoolwillbecomeasystemaccessible
onlineandusedbyconsultants,vendors,andclientsalike.Eachuserbasewilltakeadifferent
perspectivetowardsthetool,basedontheneedsoftheirroleswithintheweddingplanning
system.Clientswillusethetooltoplanouttheirweddings.Vendorswillusethetooltomarket
andselltheirservices.Consultantswillusethetooltoassistininteractionsbetweenbothclients
andvendors.Thustheweddingplanningsystemwillsolvealargeaccessibilityand
communicationsproblemfortheFWP,andencouragemoreinteractivityonbehalfofall
customersandexpandthecustomerbase.ThissolutionwillalsomodernizetheFWP.
1.1.2 Goals of the Project

TheSystemshallincreaseFWP'sclientbaseby50%

TheSystemshallincreaseFWP'svendorbaseby20%
TheSystemshallreducethetimeofplanningandorganizingtheweddingrelatedservices
by50%
TheSystemshallreducethecostforclientsandvendorstofacilitateweddingrelated
servicesby15%
5.1.2
TheSystemshallincreaseFWP'soverallprofitby25%
Will the product create other problems?............................................................33
5.1.3 What limitations exist in the anticipated implementation environment that may
inhibit the new product?................................................................................................ 33
5.2 RISKS........................................................................................................................... 33
5.3 WAITING ROOM.............................................................................................................. 34