不良需求的影響測量.pdf

《不良需求的影響測量.pdf》由會員分享，可在線閱讀，更多相關《不良需求的影響測量.pdf（19頁珍藏版）》請在三個皮匠報告上搜索。

1、Measuring the Impact of Bad RequirementsJulian Frattini,BTH SwedenMeasuring the Impact of Bad Requirements“by Julian Frattini is licensed under CC BY 4.0.Requirements impact subsequent Software Development Activities2024-11-20SERT Conference on Software Engineering 20242App Store ReviewsInterview Tr

2、anscriptsCompetitor AnalysisRequirementsElicitationRequirementsArtifactArchitecturalDesignSoftwareArchitecturePrototypingDevelopingSoftwareTest ImplementationTest CasesTest ExecutionBug ReportRevisionDeployingProductQuality Assurance of Requirements often means checking against normative rules2024-1

3、1-20SERT Conference on Software Engineering 20244Requirements artifactQuality scoreQuality assessment toolWriting guidelinesconsisting of normative rulesMost requirements quality assessment measures produce only vague results.Does the precision of quality assessments matter?Normative rules are often

4、 easy to check and can often be automated.Effort spent on Requirements Artifacts needs to be justified2024-11-20SERT Conference on Software Engineering 20245Requirements EngineeringProject DurationCreating Test Casestoo riskyCreating Test CasesCreating Test Casesgood-enoughtoo costly2024-11-20SERT C

5、onference on Software Engineering 20246Good-enough Requirements EngineeringHow good is good enough?Requirements Quality is the Impact of Requirements Artifacts on Activities2024-11-20SERT Conference on Software Engineering 20247Requirements Artifacte.g.,SRS,use case,Quality Factore.g.,sentence lengt

6、h,complexity,characterize1*Activitye.g.,implementing,testing,affects*Attributee.g.,duration,completeness,impactcharacterize1*1*Requirements artifacts are only as good as they support the activities in which they are used.Writing guidelines fail to properly reflect quality because they are void of th

7、e actual impact.The local Context mediates the Impact of Quality Factors on Activities Attributes2024-11-20SERT Conference on Software Engineering 20248Requirements Artifacte.g.,SRS,use case,Quality Factore.g.,sentence length,complexity,Context Factore.g.,domain knowledge,experience,Attributee.g.,du

8、ration,completeness,Activitye.g.,implementing,testing,affectsimpactcharacterizecharacterize1*1*1*Context(e.g.,human)factors influence the impact of artifacts on activities.Use Case:Distinguish Causes from Effects2024-11-20SERT Conference on Software Engineering 20249Requirements artifactQuality fact

9、orActivityAttributeContext factor”It constantly takes more time to specify our test cases when our more junior testers are assigned,and the use cases do not contain clear postconditions.”Users of requirements artifacts often focus on the effects of the bad requirements,not the causesHistorical Data

10、can reveal the Impact of Requirements Quality2024-11-20SERT Conference on Software Engineering 202410”It constantly takes more time to specify our test cases when our more junior testers are assigned,and the use cases do not contain clear postconditions.”UCPostconditionTester Exp.Testing DurationUC1

11、Exists1 year3:12hUC2Missing2 years6:04hUC3Missing 14 years2:45hUC4Missing11 years2:39hData AnalysisThe duration of specifying test cases increases by a factor of 2 if a use case lacks postconditions and a tester has less than 3 years of experience.Quantitative analyses on historical data identify qu

12、ality factors that actually matter in a context.2024-11-20SERT Conference on Software Engineering 202411Requirements Quality Assurance at ScaleA holistic view on Requirements QualityA Quality Factor may have different Impacts on different Activities2024-11-20SERT Conference on Software Engineering 2

13、02412App Store ReviewsInterview TranscriptsCompetitor AnalysisRequirementsElicitationRequirementsArtifactArchitecturalDesignSoftwareArchitecturePrototypingDevelopingSoftwareTest ImplementationTest CasesTest ExecutionBug ReportRevisionDeployingProduct+-+REQ42:The current documentation shall be access

14、ible as a static website.REQ42:The current documentation shall be hosted on an AngularJS web frontend.Tradeoffs of different impacts caused by one quality factor make quality assessment non-trivial.Requirements Artifacts affect all Activities that use them as Input2024-11-20SERT Conference on Softwa

15、re Engineering 202413App Store ReviewsInterview TranscriptsCompetitor AnalysisRequirementsElicitationRequirementsArtifactArchitecturalDesignSoftwareArchitecturePrototypingDevelopingSoftwareTest ImplementationTest CasesTest ExecutionBug ReportRevisionDeployingProductCollections of potential Activitie

16、s and their Attributes already exist2024-11-20SERT Conference on Software Engineering 202414Requirements-affected activities have several(measurable)attributes.Some activities are much less commonly studied than others.Comprehending a requirement precedes all other activities.Collections of potentia

17、l Quality Factors already exist2024-11-20SERT Conference on Software Engineering 202415http:/ Without the activity-based quality perspective,this collection is just a set of normative rules again.Use Case:Systematically evaluate Requirements Quality in your Context2024-11-20SERT Conference on Softwa

18、re Engineering 202416App Store ReviewsInterview TranscriptsCompetitor AnalysisRequirementsElicitationRequirementsArtifactArchitecturalDesignSoftwareArchitecturePrototypingDevelopingSoftwareTest ImplementationTest CasesTest ExecutionBug ReportRevisionDeployingProduct1.Identify the requirements artifa

19、cts in your process that you want to subject to quality assurance.2.Identify the activities in which these artifacts are involved,and which attributes represent their performance.3.Find out which factors might influence their attributes.4.Identify context factors that may mediate the impact.5.Measur

20、e these factors.6.Conduct a data analysis on historical data to quantify the alleged effect.Use Case:Assemble relevantRequirements Writing Guidelines2024-11-20SERT Conference on Software Engineering 202417postcond test.exp=-length=-passive=-Requirements Writing GuidelinesAll requirements engineers m

21、ust adhere to the following writing guidelines:1.Requirements must be no longer than 70 tokens.2.Use cases should always contain a postcondition.3.Following guidelines based on quality factors proven to be relevant in your context ensures requirements that are good enough.Conclusion2024-11-20SERT Conference on Software Engineering 202418ContactExperiencing issues with requirements quality in your context?Feel free to reach out!julian.frattinibth.se https:/julianfrattini.github.io/https:/ Conference on Software Engineering 202419