water -m project … · 1.1 rm introduction inside the water-m project requirements design (rd) and...

Water-MProject

D1.5CatalogueofRequirements

of 15 D1.5 Catalogue of Requirements

D1.5 Catalogue of Requirements

Readersacknowledgment

Thisdocumentmainlyshows2sections:

1. Presentationofrequirementsmanagementinsidewater-M;2. MasterRequirementslistsupdates.

Tomaximizeefficiencyinprojectfollow-upyoucandirectlyreadthe2ndchapter

Content

1 PresentationofrequirementsmanagementinsideWater-M................................................31.1 RMintroductioninsidetheWater-Mproject.............................................................................31.2 Requirementslistschoreography..............................................................................................4

1.2.1 Masterrequirements................................................................................................................41.2.2 Internalrequirements...............................................................................................................5

1.3 Requirementsmanagementworkorganization.........................................................................51.4 Requirementupdatesandrequirementslistdeliverables..........................................................61.5 Practicalconsiderations.............................................................................................................6

1.5.1 Tools..........................................................................................................................................61.5.2 RequirementmanagementrulesinsideWater-M.....................................................................6

2 MasterRequirementslist...................................................................................................102.1 InitialMasterRequirementslist...............................................................................................102.2 Requirementsaccordingtoprojectspecifications(currentversion)..........................................10

2.2.1 Sources....................................................................................................................................102.2.2 Comments...............................................................................................................................102.2.3 Mainoutputs...........................................................................................................................102.2.4 BusinessRequirements...........................................................................................................112.2.5 FunctionalRequirements........................................................................................................132.2.6 Non-functionalRequirements.................................................................................................152.2.7 ProjectRequirements..............................................................................................................15

History

Date Version&Status Author Modifications

10/11/2017 V1.0 JJ.Busson Initialmasterrequirementlist

15/03/2017 V.1.1.1 JJ.Busson,S.Dedeystere Requirementsaccordingtoprojectspecifications(firstrelease)



1 Presentation ofrequirementsmanagement insideWater-M

1.1 RMintroductioninsidetheWater-MprojectRequirementsdesign(RD)andrequirementsmanagement(RM)inITCprojectsiswidelydiscussedintheliterature.ThereareendlessdiscussionsonprosandconsinregardofprojectcreativityandefficiencyandabouthowtocomplyRMwithagiledevelopmentorextremeprogramming.

Now,consideringWater-Mprojectshifts,itsprojectmanagementalongsidewithITEAreviewers,havedecidedtoresortthismethodtoassist:

• Theprojectoutlining:scopeandlimit;• ThespecificationWater-Mbuildingblocks;• Thecontroltheprojectoutputsaftertheintegrationandpilotphase;• Thecommunicationwith3rdparties;• Theprojectconstructionandfollow-up.

Furthermore,theuseofRMmethod,withWater-Mengineeringteam,shallsupportthecoherenceofprojectoutputsanddocumentation.



1.2 Requirementslistschoreography

Water-Mmaintains2levelsofrequirementlists.

1. Water-Mmasterrequirementslist,atsystemlevel,≃50highlevelrequirements(markAonschema);

2. Water-Minternal&compressiverequirementslist,whichmayhaveseveralhundreditems(markonBschema).

1.2.1 MasterrequirementsMasterlistaimsthecommunicationwithexternalorganizations(mark1onschema).TheyexpressWater-Mcommitments

• totargetedwater-businesspartners;• topotentialITCtechnologicalpartnersand• ITCinnovationcommunity;• andthus,toITEAreviewers.

Masterlistisbuiltupon:

1. Informationfromoutsidetheprojectteam:businesstrends,marketsurveys,technologicalnews,regulationsandstandards,press,bibliography,conferences(mark2onschema).;

2. Inputsfromthirdparties:focusgrouporreferenceusers’communication,disseminationactionsfeedbacks,parallelprojectsandothertrustedpartiesincludingITEAreviewers(mark3onschema).;

3. Synthesisofmostsignificantinternalrequirements,promotedtothemasterrequirementslist(mark4onschema).



1.2.2 InternalrequirementsInternalrequirementsmainlyservetheengineeringprocess.Internalrequirementsaresourcedfrom

1. Heritagefrommasterrequirementupdates:additions,changes,deletions(mark5onschema).;2. Newlyavailableorupdatedengineeringdocumentscompiledintorequirements(mark6on

schema)..

Inreturn,thecollectionandtheelicitationofinternalrequirementshelptheengineeringprocess(mark7onschema)..

• Throughcarefulreadingsandinterpretationofengineeringdocuments,questionsareraised.Inthismatter,thisenhancequalitycontrolofwater-Moutputs.

• Requirementmanagementfacilitatesmajorstepsoftheengineeringprocesssuchasdatamodel,breakdownintobuildingblocks,etc.

Thedetailedrequirementsarealsoamajorsourceoftestsplans

1. testsphase,integrationphaseshallprovethefulfilmentofrequirements;2. field-testsshalldemonstratearelevantsubsetofrequirements,inrealworldconditions;3. Thelistoffulfilledrequirementsisamajorpartoftheproject’sfinalassessment.

1.3 RequirementsmanagementworkorganizationAdedicatedtaskforce(RMtaskforce)willperformtherequirementsmanagementwhichconsistin:

1. Eliciting,classifyingandmergingrequirementsfromthedifferentsources;2. Providingfeedbackstotheengineeringteam;3. Organizingrequirementevaluationsessions:withtheprojectmanagement,WPleadersand

taskleaders,whereeachrequirementisevaluatedinregardofitsnecessity,itsbusinessrelevance,innovationcriteria,anditsfeasiblywithintheprojecttimeframeandbudgets;

4. Whilemaintainingrequirementsquality,traceabilityandconsistency;5. Takesintoaccountexternalfeedbacksandexternalcontextchanges(e.g.:regulations,

standards,WaterbusinessorITCgamechanging);6. Monitorrequirementsfulfilmentduringandafterthetestingandvalidationphases.

Inengineeringteams,technicaldocumentauthors,willbeinvolved

1. inansweringRMtaskforcequestions;2. inrectifyingtheirdocumentswhennecessary.



1.4 RequirementupdatesandrequirementslistdeliverablesRequirementmanagement,atbothdetailedandmasterlevels,isobviouslyacontinuousprocess.

Nowtherearemajormilestonesinthisprocess.ThesesomehowcorrespondtoWPbreakdown:

• AtFPPlevel,inourcaseatFFPV3changerequestlevel:InitialRequirements• Oncegeneralprojectoutlinesarestated==>endofWP1:Requirementsaccordingto

projectspecifications;• Oncearchitectureandbuildingblocksarespecified,whichcorrespondstoendofWP2• Tofeedthetestsandintegrationplans,paralleltoWP3;• AftertheIntegrationandtestingphase==>FulfilledWater-Mrequirements.

Theprojectwillofficiallydeliver3releasesofMasterrequirements

1. Initialrequirements;2. Requirementsaccordingtoprojectspecifications;3. FulfilledWater-Mrequirements.

TheinternalrequirementwillremaininternalstoWater-Mteam.

Thesearenevertheless,accessibletoITEAreviewersuponrequest.

1.5 Practicalconsiderations

1.5.1 ToolsAspreviouslymentionedRM,isarecognizeddisciplineandthereisalargeofferofsoftwarepackageandon-lineservicesaroundRM.InWater-M,tolightentheprocessandlowerinvestmentswehavechosentorelyonspreadsheetsplusmaximumattentioninsideRMtaskforce.

1.5.2 RequirementmanagementrulesinsideWater-MThefollowingparagraphsstatetherulesRMtaskforce,engineeringteam,WPandtaskleadersarefollowinginWater-M.Thesearesubjecttochangesalongtheprojectprogress.



1.5.2.1 ElicitationrulesArequirementissomethingwantedorneededintheproject.

Requirementneedtobeunderstandableandaregrammaticallycorrectandwritteninastylethatfacilitatesreviewbytheaffectedparties.

Theyarewrittenas“shall”statementsusingoneofthefollowingform:

• [object]shall[verb][objectofverb];• [object]shallhave[propertyofobject].

1.5.2.2 OverallrequirementclassesThenatureoftheobjectinsidetherequirementdeterminesleveloftherequirements.InWater-Mwehaveretained8majorcategoriesofrequirements.Requirementsmayconcern:

1. ThewholeWater-Msystem:Systemrequirements;2. Afunctionorgroupoffunctionsand/orInformationtransitingbetweenfunctionèFunctional

requirements;3. Constraintsonabovefunctions,dataortechnicalandortechnicalentitiesèUnfunctional

requirements(security,performance,Customization,Flexibility…);4. Wealsomustconsidertheimplementationrequirements,suchasneedtoimplementacategory

ofproductsonwhichdevelopmentsshallbebased(OS,SQLdatabase)useacertainprogramminglanguage,needsconcerningonsystemsIntegration,etc;

5. Businessrequirements:NeedsfromtheWater-Managementindustryandrequirementtoinsurethefinalsystem/productacquirescompetitiveadvantageinregardofthecompetition

6. Organizationalrequirements:Constraintsontheusers’organization,work,manualprocesses(Note:goodsystemsshouldnotimposetoomanyconstraintsonmanagement);

7. Projectrequirements:constraintsonprojectactivitieslikedocumentation,projectmanagement;8. Productliferequirements:needsonthemaintenanceofproducts.

1.5.2.3 AdditionalclassificationcriteriaTheprojectprogresswilloutlinenecessaryadditionalclassificationssuchas:functionsandsub-functions,datacategories,sub-systems,etc.

ThesearevalidatedwithWPandtaskleaders.

1.5.2.4 RequirementssourcesRMtaskforce,insuretheaudittractbetweenthe(internal)requirementsanddocuments.

RMTaskforcemaintainasetofannotatedmostrecentversionofengineeringdocumentswheresourcesandconsequentrequirementsarereferenced.

Theearlyversionsoftheseannotatedengineeringdocumentsalsoraisequestionstodocumentauthors.

Authorswillmaketheirbestefforttosupplynecessaryprecisionstoclarifythedocuments.



1.5.2.5 Sorting,dupesidentification,Merging

RMtaskforceprocessthenecessarysortingtopinpointrequirementsduplicatesorsimilarities.

RMtaskforceisresponsibletomaintaintheconsistencyofrequirementswithindifferentsourcedocuments,whilemaintainingtraceability.

1.5.2.6 RMoutputsAspreviouslymentioned,RMfacilitatesmajorstepsoftheengineeringprocesssuchadatamodelling,thebreakdownintobuildingblocks,etc.

RMtaskforceprovidesneededextractions,sorting,presentationstoserveengineeringprocesses.

1.5.2.7 RequirementimportanceRMtaskforceproposesrequirements’importance.Requirementimportancewillbevalidatedduringevaluationsessions.

Chosenrequirements’importancegradeswithinWater-Mare:

• N/A:èWhenarequirementneedselicitationbeforeitsimportanceisset;• 0èDeletedrequirement;• 1èMusthave;• 2èBringscompetitiveadvantagestothesystem,althoughnon-compulsory;• 3èNicetohave;• 4èRequirementaddition,forcomfort

Requirementshowingimportancelevelequalto1willbedevelopedinwater-M.

Requirementshowingimportancelevelequalto2shallbediscussed.

Therequirementshowingotherrequirementimportanceareneverthelesskeptintheaudittrack.Thesemaybeusedinfurtherideationsessions.

1.5.2.8 PromotiontoMasterrequirementlist

Masterrequirementcanbeexpressedthoughtthesynthesisofseveralinternalrequirements.TheMasterrequirementwritingisproposedbytheRMtaskforce.RMtaskforceproposesinternalrequirementspromotion.

Eachrequirementpromotionisvalidatedduringevaluationsessions.

Wealsostatedthefollowingrules:

1. Onlyrequirementshowingimportancelevelequalto1or2canbereportedintheMasterList.2. Masterrequirementlistwillonlycomprisetherequirementhavingthefollowingclasses



2.1. OverallBusinessrequirements;2.2. Syntheticfunctionalandunfunctionalrequirements;2.3. Organizationalrequirement(impactsonfinaluserorganisation);2.4. Projectrequirements(additionalactivitiescomparedtoFPP).

1.5.2.9 Requirementevaluationsessions

RMtaskforceorganiseregularrequirementevaluationsessioncomprising:

1. RMtaskforcemembers;2. Projectmanagement;3. RelevantWPandTaskleadersforthegivensession.

Duringthesessions:

1. Detailedandmasterlistofrequirementsarereviewed.2. Proposedevaluationsandpromotionsarediscussedthendecidedinregardofbusiness

relevance,innovationcriteria,andfeasiblywithintheprojecttimeframeandbudgets.3. Decisionsareloggedfortraceabilitypurposes.4. Feedbacktoengineeringteamdocumentsarepresentedanddiscussed.


2 MasterRequirementslist

2.1 InitialMasterRequirementslist

Ithasbeenexposed,toITEAreviewersbeforeFPPversion3requestchangesThislistwasamainsourceforFPP3rdversion.

2.2 Requirementsaccordingtoprojectspecifications(currentversion)

2.2.1 Sources

TheproposedversionofMasterrequirementaimsatfinalizingWP1.Ittakesmainlyintoconsideration

• FPPV3;• Evaluationofstakeholderinteractions;• Analysisofcurrentwaterpolicies;• Usecasesapplicationscenariosanddefinition.

2.2.2 CommentsAsnecessaryfeedbacksonlateusecasesanalysisarenotyettakenintoconsideration,andasevaluationsessionarenotfinalizedthecurrentversionisnotthefinalone.

Followingyellowhighlightedparagraphscorrespondtolevel2ofrequirementimportance“providesacompetitiveadvantagetotheproject”

2.2.3 Mainoutputs

TheachievementofthedetailedrequirementlistonwhichthebellowMasterlistisbased,mainlyenabledtheproposalof

1. projectfunctionalbreakdown;2. neededdataconcepts;3. actorsdictionary.

Totheengineeringteam.ThoseareinputsofWP2andWP3.


2.2.4 BusinessRequirements

Req.ID Description

OBR-001 1

Evaluateandimprovetheperformanceofawaterdistributionnetwork.Water-Mprovideddashboardsaredesigned,takinginconsiderationstateoftheartindicatorsforwaternetworksmanagersandowners(mostoftenmunicipalities)pointofview.TheconjunctionofperformancewatchinganddetailedmonitoringfeaturesprovidedinWater-Mshallpermitto

• Followevolutionofperformanceindicators(alertsincaseofdisruption)• Indicatethelocalisationpointswhereactionsareneeded.

Thiswillserveasthemainoperationalinformationwhichisusedtooptimisethemaintenance:Selectionandplanningofthemostprofitablecorrectiveandevaluativemaintenanceactions.

OBR-002 1

Allowtoperformsubscribersbillingbasedonwaterconsumption.Abilitytoproducethebillinginformationbasedonwatermeters’informationisnowadaysaminimalrequirementforwatermanagementsystem.Now,thescalabilityofWater-M’sarchitectureshallallowtheproductionofanynumberofsubscriber’sdetailedconsumptionbillsreflectingallavailablewaterconsumptionmeasurements(e.g.:1/day).Itwillalsobepossibletoproceedtodetailqueriesonwater-consumptiondataandthereforeprovidenewservicestocustomers.Note:ERPandbillingsystemsareoutsidewater-scope.

OBR-003 1

Facilitatewaterdistributionnetworkmaintenanceandreduceassociatedcosts.Asstressedinabovebusinessrequirements,performancewatchinganddetailedmonitoringfeaturesparticipateinthecorrectivemaintenanceoptimization.Smartalertstriggeringthroughcomplexeventprocessing(CEP)technologiesisoneofthemostadvancedWater-Mcontribution.Thispermitsearlywarningssystemsandshallreduceinterventiontimeafterproblemoccurrence.Thisshallreduceaftermath’scosts.

OBR-004 1

Reducetheamountofwaterlosses.Leaksdetection,leakslocalisationandleaksvolumeevaluationshallimprovetheevaluationofthewaternetworkloses.Earlywarningonleakswillcontributetowaterlossandassociatecostsreduction.Note:Theprojectshallprovideacost-benefitanalysisforwaterlossreductiontakingintoconsideration:

• Monetaryvaluesandotherevaluationmeans;• Thepointofviewsofwaternetworkmanagers,municipalities(usuallynetwork

owners),finalusersandsociety.

OBR-005 1

Preventandreducehealthrisks.Water-Mhasconductedadetailedsurveyonwaterqualitymeasurementsneeds.Thissurveyalsocomprisesanevaluationof:

• Thebestavailablesensingtechnologies;• Theautomatedmethodstooperateasaccurateaspossiblemeasurementof

chemical,physicalandbiologicwatercontent.• ThroughwaterqualitywatchingandthankstoCEObasedalertWater-M

enhancetheprotectionagainst,directhealthriskatconsumerlevelandindirecthealthrisksconsequenttoenvironmentalhazard

• Reducefertilizersandthephytosanitarytreatmentsinirrigationwaters,thankstosmarturbanfarmingmonitoring


Req.ID Description

OBR-006 1

Providedatatodifferentactors.Water-MisbasedonIoTarchitecturestateoftheart.Insucharchitecture,upperlevelapplicationcanaccessallnetworkinformationthroughplatforms.Exogenousdatacanbeaccessedthroughtheplatformsoratapplicationlevel.Bydesign,dataareavailabletoanyuseroranyapplicationprovidedthesecurityprocessinplacegrantsaccess.TheadoptionoftheIoTplatformbasedarchitectureallowsabetteradaptabilitytothedevelopmentofnewapplicationsservicededicatedtonewuserspurposes.

OBR-007 1

AllownewbusinessmodelsforwatermanagementNewideasareemergingtorebuildtheeconomicmodelbymakingtheremunerationdependingonthewaterdistributionperformance,therefore,partiallydetachingtheremunerationfromthevolumessold.Themunicipalitypaystheoperatordirectlybasedonperformancemeasuredthroughpreciseevaluations.TheremunerationisfunctionoftheobjectivesrespectedaswellasthevolumesofwatersoldThus,waterproviderhasamonetaryinterestincontroltheperformancevariablesofthenetwork.

OBR-008 2

TargetenergycostreductioninthewaternetworkInmunicipalities,afterpubliclighting,waternetworkrepresentsthesecondmostimportantelectricitybill.

1. Thanks,totheconstantmonitoringandtoearlywarningsWater-Msystemshallalertwaternetworkstakeholdersonleaksandtransportationabilitylossescausingunnecessaryenergyconsumption(duetopumping)

2. Providedenergymarketdataareavailable,Water-Moptimizationprocessesshallhelptheschedulingofenergyconsumingprocessaccordinglytoenergyprices.

3. Theadvancedremotemonitoringofthewatersystemalsoaimsatreducingthenumberoffieldinterventions(which,nowadays,contributestothereductionoffossilfuelsconsumption)

OBR-009 2

EnsurecompatibilitywithEuropeandirectivesonwaterNamely

1. GroundwaterDirective2006/118/EC2. WaterFrameworkDirective2000/60/ECconcerningdrinkingwater(98/83/EC)

Throughaconstantwaterqualitymonitoringof

1. watersourcesandwastewatertreatmentplantsoutlets,2. clearwaterdistributionnetwork.

OBR-010 1

Minimizeirrigationwaterandenergyneedsinmonitoredurbanfarmingsites.Irrigationaccountsformorethantwo-thirdsoftotalwaterusageabstraction.Innorthernmemberstates,levelsofwateruseinagriculturearelower,withirrigationbeinglessimportantbutstillaccountingformorethan30%insomeareas.

• Inmonitoredurbanfarmingsites,expertsystemswilloptimizethequantityofwaterandlight(alsonutriments)accordinglyto:plantsspeciesandcultivar,cropsdevelopmentstageandhealthconditions,seasons&time,currentandforecastedweatherconditions.

• Whileminimizingwaterandlight,theneedsforenergyisminimized


2.2.5 FunctionalRequirements

Req.ID Description

OFR-001 1

Providestatesofwaterdistributionnetworkdevices.Awatersystemconsistsofapredefinedsetofdevices(Storagereservoir,sectioningvalve,zonemeter,pumpstation,pressureregulator,pressuresensor,subscribermeter)thatcanbemodeledasobjects.Theseobjectshaveastatecomposedbyasetofinformationcomingfromsensors.

OFR-002 1

Detectandlocateleaksinwaterdistributionnetwork.Leakdetectioninthenetworkreducesthevolumeofunbilledwater.Thelocationoftheleakagecanreducethemaintenancecost.

OFR-003 1

Detectandlocateoverpressureinwaterdistributionnetwork.Overpressuredetectioninthepipespreventsleakageandwaterpipedamages.Overpressurelocationhelpstooptimizenetworkandtoadjustwaterdistributionnetworkdevices.

OFR-004 1

Measurevolumeofwatersuppliedforeachnetworkarea.Waterlosscanbecheckedbycomparingthetotalconsumptionofthesubscribersinanareaandthevolumeofwaterpassingthroughtheareasectioningvalve.

OFR-005 1

Providewaterqualitymeasurement.WaterqualitymeasurementhelpstorespondtothegoalofEuropeannormandisanecessitytopreventandreducehealthrisks.

OFR-006 2

Measureenergyconsumptionofwaternetworkdevices.Somewaternetworkdevicesneedenergy(fuel,electricity)whosecostshouldbecalculatedtooptimizeOPEX.

OFR-007 2

Measurethepressureavailableatthesubscriberpremise.Thepressureatthedistributionpoint(ornear)mustbegreaterthanathresholdtoensurequalityofexperienceforthesubscriber.

OFR-008 1 Measuresubscriberswaterconsumption.

Measuringtheconsumptionofthesubscriberallowsbilling.

OFR-009 1

Detectabnormalwaterconsumptionatthesubscriberpremise.Usedtosignaltothesubscriberanabnormalconsumptionavoidswasteandcontributestothesatisfactionofthesubscriber.

OFR-010 1

Useandeventuallyallowtoconstituteageospatialdatabasetolocateandidentifysensor,pipes,waternetworkdevicesandwaterdistributionpoints.Itisnecessarytohaveaccesstoageographicdatabaseincludingnetworktopology.Theseallowtodisplaythevariousobjects,includingsensorandactuators,ofthenetworkonamap,tomakethelinkbetweenanobjectandthedataassociatedwithitandwhataretheupstreamanddownstreamobjectsonapipe.Thisdatabase,willeventuallycommunicatewithavailableGeographicalInformationSystems(GIS)andbuildinginformationmanagement(BIM)systems,throughstandardizedAPIs.ThoseAPIsshallbedesignedbothways.This,tobeabletouseWater-MinformationinGISorBIMbasedGUIs.

OFR-011 1

Useandeventuallyallowtoconstituteawatercontextdatabase.Tocalculatetheperformanceindicatorsthatmeasurethequalityofservice,itisnecessarytoprovidecontextdataonthenetworkonceperyear,whichmaynotbedirectlymeasurable(Costofservice,Networklength,Numberofsubscriber...).

OFR-012 1

Filter,addtimestampandstorerealtimedatacomingfromsensors.Datacomingfromsensorscanbepretreated,aretimestamped,storedastimeseriesandaccessiblebyapplicationsthroughanAPI.


Req.ID DescriptionOFR-013 1 Closethesectioningvalvetoisolateawaterdistributionarea.

Areasectioningvalvescanbeclosedincaseofmajorleakageorcontamination.

OFR-014 1

Setthesensorsandthevariouswaterdistributionnetworkdevices.Sensorsmustbeconfiguredremotely(wheneverpossible)toadjustsomesettingstousecases(thresholds,samplingperiod,transmissionperiod).

OFR-015 1

Detecteventsfromstandardrules.Primaryaswellascomplexeventsthatcangeneratealarmsaremadefrompre-definedrulesandallowforexampletocomparevalueswiththresholds,detectandlocateleaks,...

OFR-016 1 Detecteventsfromuser-definedrules.

Eventsthatcangeneratealarmsaremadefromuser-definedrules.

OFR-017 1

Calculateperformanceindicatorstomeasuretheefficiencyofthewaterdistributionnetwork.Eachyear,someactorsdemandasetofperformanceindicators.Someofthemareusedtocomparedifferentserviceshavingsomesimilarities,tobeabletohavereferences.

OFR-018 2

ForecastWaterDemandModelsforpredictingthewaterconsumptionsinrealtimeandshorttermshavetobeimplementedtooptimizewaternetwork.

OFR-019 1

Provideaman-machineinterfaceforviewingthevariousmeasurementsinthenetworkaswellasfaultsandindicators.Water-Mprovideddashboardsaredesigned,takinginconsiderationstateoftheartindicatorsforwaternetworksmanagersandowners(mostoftenmunicipalities)pointofview.TheconjunctionofperformancewatchinganddetailedmonitoringfeaturesprovidedinWater-Mshallpermitto

• Followperformanceindicatorsevolution(andalertincaseofdisruption);• Indicatethelocalisationofneededactions.

OFR-020 2

Imbed3rdpartyenergycostoptimizationroutinesusing3rdpartyenergytariffdatabase.Reducingenergycostmainlyconsistinorganizingagivenprocessinregardof

1. Processconstrains2. Businessrules,e.g.:performanceindicatorstoreach3. Energyconsumptionfunctionsforeachstepoftheprocess

Using4. currentandforecastedenergytariffs5. Energycostoptimisationroutine

OFR-021 2

ConsiderinstrumentsandmeasurementmethodcalibrationWater-Mshall

• Warnusersonmeasurementsdeviations• Consideratrainingperiodtoobtainreliableindicators• Allowuserstomanuallysetinstrumentsormeasurementroutinesparameters

OFR-022 2

UseweatherandclimatereferencedataLocalcurrentandforecastedtemperatureandprecipitationdata,areusedforseveralUC.TheWater-Mprojectshall,atleast,comprisesuitablemethodstoimportsuchcontextdatainitsenvironment


Req.ID Description

OFR-023 2

ConsiderobtainingsensordataandcommandingactuatorsviaSCADAinterfacesLegacywaternetworkmonitoringinstallationsarebasedonSCADA.Tofastentheintegrationoflegacysystem,itisnecessarytobuildAPIstomostlyusedSCADAsystem

OFR-024 2

BereadyforrivermonitoringandriverfloodalertssystemsUCThismainlymeansintegrating,Waterdepthsensors,waterdepthcalculationderivedfrompressure,dedicatedapplicationsandGUI.

2.2.6 Non-functionalRequirements

Req.ID Description

ONFR-001 1

Adapttodifferentwaterdistributionnetworktopology.Water-Mmustaddresshighpopulationdensityareasandlowpopulationdensityareaaswell.

ONFR-002 1

Haveopenandstandardized(wheneverpossible)interfaces.Water-Mmustbemodular.Componentsmusthavestandardinterfaces,wheneverpossible,atalllevelsofthearchitecturesothattheycanbeeasilyreplaced.

ONFR-003 1

Haveopendatamodel.Water-Mshoulduseadatamodelbasedonstandardizationworkallowstohaveamodelascloseaspossibletonextgenerationstandard.

ONFR-004 1

PerformanceandscalabilityThescalabilityoftheWater-Mshallbedemonstratedsimulatingthebehaviourofacitywithatleast1millioninhabitantsthenevaluatingaveragecosteffectivenessperwatermeteringpoint.

ONFR-005 1

ReadyforstateofartsecuritymechanismsAlthoughtheimplementationofsecuritymechanisminnotpartofWater-M,theprojectshallanalysewhichmechanismsaretobeimplementedandhow.

2.2.7 ProjectRequirements

Req.ID DescriptionOPRJ-001

1 Water-MshallenhanceitsbusinessanalysisOrganizationofbusinesscanvasessession

water -m project … · 1.1 rm introduction inside the water-m project requirements design (rd) and...

Documents