Slide 1Project ScopeSoftware Development Processes and ProceduresQuality Assurance Processes and ProceduresDesign ConsiderationsSystem Requirements Specification (SRS)System Requirements Specification (SRS)System Requirements Specification (SRS)System Requirements Specification (SRS)Testing ProceduresReliability TestingAccuracy TestingFault TestingPerformance TestingTest ChartsHardware and Software CapabilitiesClosing ThoughtsReferencesQuestions?SMITH SOFTWARE TESTING ENVIRONMENT PROPOSALTeam BravoSmith Systems ConsultingProject ScopeDefine the Smith Consulting engagement approach. Define the software development and quality assurance processes and procedures.Describe in the detail the testing procedures to be exercised in the following areas:o!!! Programso!!! Systems o!!! InterfacesDescribe the infrastructure including hardware and software capabilities that will make up the software testing environment.Define the format and requirements for development of formal program specification. This program specification is the document to be provided to the software developers working on a Smith development project.Software Development Processes and ProceduresIn order to accurately definethe Software DevelopmentProcess and Procedures,Smith Systems Consulting will first define a System Development Life Cycle (SDLC)FeasibilityAnalysisDesignImplementTestMaintainQuality Assurance Processes and ProceduresQuality is measured and ensured through:Resource and toolsHighly trained Project ManagersWeekly updatesDaily meetingsStrict change control processApproval processGoalsPrimarySecondaryDesign ConsiderationsBudgetFrequent Shopper Rewards ProgramCustomer Satisfaction and LoyaltySystem Requirements Specification (SRS)Derived from customer requirementsWill cover:Business functionsInputsOutputsSystem interfacesConstraints:BudgetHardware changesSoftware development methodsSystem Requirements Specification (SRS)Answers the following questions:What is the information system or software going to accomplish?With what system hardware, software and users will the program interact?What are the performance requirements, such as capacity, speed and recovery?What, if any, are the constraints on the design?System Requirements Specification (SRS)PurposeSystem Requirements Specification (SRS)•Scope• Definitions, Acronyms, and Abbreviations• References• Overview• System Perspective• System Requirements• System Interfaces• Hardware Interfaces• Software Interfaces• User Interfaces• Communication Interfaces• Memory Constraints• Operations• Site Adaptation Requirements• System Functions• User Characteristics• Constraints• Assumptions and Dependencies• Apportioning Requirements• Functional Requirements• Performance Requirements• Design Constraints• Standard Compliance• System AttributesSupporting InformationTesting ProceduresDevelop procedures for each level of testingSupport Smith developed softwareSupport Commercial-off-the-ShelfReliability TestingReduce the rate of failureGuarantee system capable of managing all input and output processesHandling Data Output ExceptionsInclude Stress TestingAccuracy TestingImperative that input must be received, stored, translated and output correctlyUtilize Use CasesFault TestingInject Faults to test for errors and handlingPerformance TestingResource UsageIdentify Performance BottlenecksBenchmarkingTest ChartsTesting Chart Figure 1Expected Results Figure 2Hardware and Software CapabilitiesHewlett Packard QuickTest Professional 10.0Supports functional and regression test automationIntel Quad-Core processorsIncreased processor speed for quicker testing2GB of MemoryIncreased memory capacity for load testingSimultaneous testingWindows 7 Operating SystemClosing ThoughtsReferencesOCM (2011). “Reliability Testing” Retrieved on March 26, 2012 from http://www.ocmtestlabs.com/default.asp?mode=testcategories&catid=9Carnegie Mellon University (1999). “Software Testing.” Retrieved on March 26, 2012 from http://www.ece.cmu.edu/~koopman/des_s99/sw_testing/Hewlett Packard (2009). “Software Solution” Retrieved on March 26, 2012 from http://www8.hp.com/us/en/software/software-solution.html?compURI=tcm:245-937061Smith, C. U. (1990). “Performance Engineering of Software Systems.” Addison-Wesley. Page 40 Para