-
31
pages
-
English
-
Documents
Description
Requirements Specifications Interaction AnalysisBill MitchellSoftware and Systems Research LabsDepartment of ComputingMotorola UK Research LabsUniversity of SurreySunday, June 22, 2003Reality of Engineering Requirements Specifications• Rapid development of lightweight specifications• Specification by example scenarios• Poor coverage of scenarios• Disjoint engineering groups with little communication• Extreme pressure to ship on timeHence large number of defects only found in field testing2Motorola LabsResearch Project PilotFATCAT an internal tool, takes sets of scenarios (in e.g MSC notation):• analyse scenarios coverage• find conflicts• construct interesting FI testsCurrent Pilot coordinated by Motorola UK Research lab with:• UI Design Group • UI Software Tool Development Labs• System Architecture Group• Testing Group• Testing Tools Software Management Group• Requirements Specification Managers• EU 6th Framework STReP, Forming a consortium:3Motorola LabsStandard TechniquesInternal study of 200 TETRA MSC scenarios with Spin and standard MSC automata synthesis algorithms (Alur, Leue etc).Result:• state explosion• generated many “bogus” errorsTwo other Motorola Research Labs built POTS system with Switch in SDL for model checking with FDR. Result:• state explosion problems• only found conflicts when the algorithm directed towards error statesFor wireless telecomms specifications, standard model checking not always the right ...
-
Publié par
-
Langue
English