HappyFood Takeout Ordering System.docx

HappyFood Takeout Ordering System.docx

《HappyFood Takeout Ordering System.docx》由会员分享，可在线阅读，更多相关《HappyFood Takeout Ordering System.docx（44页珍藏版）》请在冰豆网上搜索。

HappyFoodTakeoutOrderingSystem

HappyFoodTakeoutOrderingSystem

SoftwareRequirementsSpecification

Version1.02016.05.01

WrittenByHappyFoodR&Dteam

ChongqingUniversityofPostsandTelecommunications

SoftwareCollege

Teammembers:

WangHaixu（Leader）

YangLei

LiuYizhao

ChenGuancong

YangQiufan

AllRightsReserved

List:

1.1WriteObject：

4

1.2BackgroundoftheProject：

4

1.3TargetRange：

4

1.4UserCharacteristics：

5

1.5DefinitionofTerms：

5

1.6Referencematerial:

5

2.1.1User’sregistering,logininginandchangingpersonalinformationfunctionalmodule.6

2.1.1.1.1Thechildfunctionaldescription-Theuserlogininfunction7

2.1.1.1.2Functionalbusinessprocess-Theuserloginfunction：

7

Businessflowchart:

7

2.1.1.2.1Thechildfunctionaldescription-Userregistrationsubsystem:

8

2.1.1.2.2Functionalbusinessprocess-Userregistrationsubsystem9

2.1.1.3.1Thechildfunctionaldescription-Userlogoutsystem:

11

2.1.3User’sorderingtakeoutfunctionalmodule.19

2.1.3.1.1SubFunctionDescription-Searchnearbybusinesses19

2.1.3.1.2Sub-functionbusinessprocesses-Searchnearbybusinesses19

2.1.3.2.1SubFunctionDescription-Categoriessubsystem20

2.1.3.2.2Sub-functionbusinessprocesses-Categoriessubsystem21

2.1.3.3.1SubFunctionDescription-Shoppingcartsystem21

2.1.3.3.2Sub-functionbusinessprocesses-Shoppingcartsystem22

UseCaseDiagram：

22

2.1.3.4.1SubFunctionDescription-examineProductInformationSubsystem23

2.1.3.5.1SubFunctionDescription-Functionalsubsystemspayment23

2.1.3.6.1SubFunctionDescription-OrderProcessing25

2.1.4Businessman’sacceptingordersfunctionalmodule.27

2.1.4.1.1SubFunctionDescription–ViewCustomerOrderSystem27

2.1.4.1.2SubFunctionBusinessProcessDiagrams-ViewCustomerOrderSystem27

2.1.4.2.1SubFunctionDescription-AcceptOder’sSubsystem28

2.1.4.2.2SubFunctionBusinessProcessDiagrams-AcceptOder’sSubsystem29

2.1.4.3.1SubFunctionDescription-DenialOrdersSubsystem29

2.1.4.3.2SubFunctionBusinessProcessDiagrams-DenialOrdersSubsystem30

2.1.4.4.1SubFunctionDescription–Businessunsubscribeapplicationsubsystem31

2.1.4.4.2SubFunctionBusinessProcessDiagrams-Businessunsubscribeapplicationsubsystem31

2.1.4.5.1SubFunctionDescription–Handlingcustomerbacknailsystem32

2.1.4.5.2SubFunctionBusinessProcessDiagrams-Handlingcustomerbacknailsystem33

2.2Performancerequirements34

2.3Datarequirements38

2.4Userinterfacerequirements39

2.5InterfaceRequirements41

2.6Securityneeds41

2.7Troubleshootingdemand44

2.8Environmentalneeds45

2.9OtherRequirements47

1.1WriteObject：

WritingthisRequirementsSpecificationisinordertoclearoursystem’sdetailedrequirementsandmaketheuseofunitsconfirmthesystem’sfunctionalityandperformance.Andalsohelpthesoftwaredesignersanddevelopersdesignanddevelop.

1.2BackgroundoftheProject：

Innowdays,thefast-pacedlifemakespeoplehavemoredemandforTakeout.Whetherstudentsorofficeworkers,orothers,intheirworkdays,morepeoplechoosetakeoutinsteadofeatinginarestaurant.Becauseofthisphenomenon,oursystemcameintobeing.First,wehaveenoughpotentialusers.Becauseinonehand,thepeoplewhochoosesthetakeoutcanorderingthetakeoutbyaneasierway.Intheotherhand,theowneroftherestaurantcangetmoreorderformtomakemoney.It’sthewaycankilltwobirdswithonestone.

1.3TargetRange：

System’stargetrangeisveryfree.Iftheareahaverestaurantsjoinoursystem,theypeopleintheareacanusesystemtoorderingthetakeouttheywant.

1.4UserCharacteristics：

Theuserofsystemmayhavethefollowingcharacteristics:

（1）:

Havingrequirementoftakeout.

（2）:

Supportingandchoosingthesystemtogettakeout.

1.5DefinitionofTerms：

User:

Thepersonwhoisregisteredbythesystemandhavetherighttousethesystemtoorderthetakeout.

Businessman:

Thepersonwhoisregisteredbysystemandhavetherighttousethesystemtogettheorderform.

System:

TheHappyFoodSystem

1.6Referencematerial:

PracticalSoftwaredocumentationwriting-----TsinghuaUniversityPress（ISBN:

978-7-302-10373-8）

SoftwareEngineering（4thEdition）----POST&TELECOMPRESS（ISBN:

978-7-115-32653-9）

ThinkinginUML（2ndEdition）---ChinaWater&PowerPress（ISBN:

978-7-5084-9234-6）

2.1：

FunctionalRequirements：

System’smainfunctionsdividedintothefollowingfour:

（1）:

User’sregistering,logininginandchangingpersonalinformationfunctionalmodule.

（2）:

Businessman’sregistering,logininginandchangingindividualinformationfunctionalmodule.

（3）:

User’sorderingtakeoutfunctionalmodule.

（4）:

Businessman’sacceptingordersfunctionalmodule.

2.1.1User’sregistering,logininginandchangingpersonalinformationfunctionalmodule.

Theusercanthroughvisitourpoorhappyonlinereservationsystem,，tologinorregister，getwhatyouwantallkindsoffood。

accesstothewebsite，directaccesstothiswebsitehomepage。

youcanchooselanding，Ifalreadyregisteredcanchoose，onlyregisteredcustomerscanorder。

registeredtoprovidecustomernameandpassword,canautomaticallydetectthecustomername，iftherehavebeenahintisnotavailable。

inadditionaddpasswordfunction,landingcanchoosememory,namelynexttimewithoutpassword,youcandirectlyentertheloginstatus.

2.1.1.1.1Thechildfunctionaldescription-Theuserlogininfunction

Usecasename：

UserLogin

sketch：

Theuserthroughthephoneapporwebloginreservationsystem

participants：

user，Thesystemadministrator

include：

Mobilephoneclient，webclient

extend：

no

inheritance：

no

precondition：

Theusertoenterthecorrectpassword

Details:

Processingflowandmainpoint：

【Step1】userClickonthephoneAPPorwebclient

【Step2】systempromptuserentertheusernameandpassword

【Step3】userentertheownusernameandpasswordandsubmit

【Step4】systemvalidatetheinputnameandpassword，andaccordingtothecorrespondinginformationreturnonsuccessorerrors.

Outputdescription：

succeed：

jumptothedisplayordersystemmaininterface

failure：

returnedtothedisplayuserinterface

Postconditions

Exception:

limit：

no

annotation：

no

2.1.1.1.2Functionalbusinessprocess-Theuserloginfunction：

Businessflowchart:

2.1.1.2.1Thechildfunctionaldescription-Userregistrationsubsystem:

Usecasename：

Userregistration

sketch：

userSubmitaphonenumberandmessageauthenticationcodeinthephoneappandwebtoregister

participants：

user，Thesystemadministrator

include：

user，Thesystemadministrator

extend：

no

inheritance：

no

precondition：

Userstoprovidepersonalinformationaccordingly，Suchasmobilephonenumber

Details:

Processingflowandmainpoint：

【Step1】ClickonthephoneAPPorwebtheregistrationscreen，Choosetoregister*

【Step2】Fillinthepersonalinformationandtakeamessageauthenticationcode

【Step3】Getverificationcodeandenterit

【Step4】Waitforsystemverification，andaccordingtothecorrespondinginformationreturntoregistrationorpromptverificationcodeerror。

Outputdescription：

succeed：

Jumptothedisplayordersystemmaininterface

failure：

Verificationcodeerrororpersonalinformation

Postconditions

Exception:

limit：

no

annotation：

no

2.1.1.2.2Functionalbusinessprocess-Userregistrationsubsystem

Businessflowchart:

Atpresentregisteredaccountcategoriesasfollows

（1）Quicksignupforanaccount：

andmeetthefollowingconditionsapplyreal-nameauthenticationofusers，heaccountstatusissetto"quickregistration"：

logonmode:

registeredmobilephonenumber,notreal-nameauthentication,unboundedanybankcardinformation,userinformationismissing,thetypesofcertificates,certificatenumberisnotinconformitywiththeconditionsdonotconformtothevalidationrules,nopersonalinformation（name,iddate）relatedbusinessoperations

（2）Standardregisteredaccount：

Theuseraccountinformationandtosatisfythefollowingconditionsandnotreal-nameauthentication,applicationisaccountreal-namestatussetto"standardregistration"：

logonmode：

Usingmobilephonenumbertocompletethebasicregistration,bindingacashcard,nomissingfields,giveinformation,orhavepersonalinformation（name,iddate）relatedbusinessoperations

（3）Real-nameauthenticationaccount：

Usersinthepoorhappychannelsuchaswebsites,mobileclientapplicationreal-namecertification,andthroughthebackgroundchecking,willtheuseraccountreal-namestatusissetto"real-nameauthentication".

2.1.1.3.1Thechildfunctionaldescription-Userlogoutsystem:

Usecasename：

userlogout

sketch：

Afteruserthroughthephoneapporweb asuccessfullogin，hasloggedintotheinterface，afterthesuccessofthecancellationsystemclearmemoryofcustomername,theshoppingcartandotherpersonalinformation，andreturntolandinginterface.

participants：

user，Thesystemadministrator

include：

Mobilephoneclient，webclient

extend：

no

inheritance：

no

precondition：

Theusersuccessfullylogsinordersystem

Details:

Processingflowandmainpoint：

【Step1】LoginuserclicksonacellphoneorwebAPPside;；

【Step2】Opentheuserlogoutinterface，systempromptedtologout

【Step3】logoutsuccess，returntotheloginscreen

Outputdescription：

succeed：

Jumptothedisplayorderlogininterface

failure：

no

Postconditions

Exception:

limit：

no

annotation：

no

2.1.1.3.2Functionalbusinessprocess-Userlogoutsubsystem

Businessflowchart:

2.1.2Businessman’sregistering,logininginandchangingindividualinformationfunctionalmodule.

2.1.2.1.1Functionaldescription-loginpage:

Usecasename:

logininterface

Description:

merchantsbym