BSA/385 Introduction to Software Engineering : Software Testing Environment Proposal

Preview (7 of 22 Pages)

100%

BSA/385 Introduction to Software Engineering : Software Testing Environment Proposal - Page 1 preview image

Loading page ...

Running head:SMITHSOFTWARE TESTING ENVIRONMENTPROPOSAL1Software Testing Environment ProposalBSA/385 Introduction to Software EngineeringGiven the assignment to define, develop, and propose standards for a software testingenvironment at Smith Systems Consulting, how would you outline acomprehensive project planthat includes the software development process, quality assurance procedures, and the formalprogram specification? Additionally, discuss how the proposed standardized approach will helpSmith Systems Consulting maintain project efficiency, keep clients confident, and ensure smoothcontractual obligations. In your response, ensure to cover the phases of the SoftwareDevelopment Lifecycle (SDLC), the importance of quality assurance, and how Smith can benefitfrom using Agile Development Methodology for Kudler Fine Foods. Provide a well-structuredanswer, with a word count requirement of 750-1000 words.

BSA/385 Introduction to Software Engineering : Software Testing Environment Proposal - Page 2 preview image

Loading page ...

BSA/385 Introduction to Software Engineering : Software Testing Environment Proposal - Page 3 preview image

Loading page ...

SMITHSOFTWARE TESTING ENVIRONMENTPROPOSAL2AbstractSmithSystems Consultinghas received some feedback and concerns that their processes andprocedures are not sufficiently documented. This lack of professional documentation has causedsome loss of potential contracts for the firm. The Learning TeamBravohas been given theassignment to define, develop, and propose standards for a software testingenvironment atSmith. This will be accomplished by defining the Smith engagement approach, introducing thewaythefirmworkswithclientsandhowprojectsaremanaged,definingthesoftwaredevelopment and qualityassurance processes and procedures, describingindetail testingprocedures to be exercised, describing the infrastructure including hardware and softwarecapabilities that will make up the software testing environment, and by defining the format andrequirements for development of formal program specification.

BSA/385 Introduction to Software Engineering : Software Testing Environment Proposal - Page 4 preview image

Loading page ...

SMITHSOFTWARE TESTING ENVIRONMENTPROPOSAL3SmithSystems Consulting recently tasked Learning Team Bravo (LTB) with developinga standardized project plan, approach, and testing procedures. It is Smith’s goal to showprospective clients that Smith is efficient and is confident that they are able to performcontractual obligations smoothly. The following procedures will be generalized so that Smithwill be able to utilize this project plan in any project. This standardized project plan that LTBdeveloped will enable Smith to focus the resources of their project rather than developingprocedures to complete the project.Software Development Processes and ProceduresSmith Systems Consulting understands that there is not a clear-cut solution for eachindividual software development project and wishes to utilize a process that accounts formultiple variables when developing new software. In order to accurately define this process,Smith will benefit from a System Development Lifecycle (SDLC) approach. This means thatSmith will first need to determine the needs of the company. Within this phase, the first step is toidentify Smith’s stakeholders followed up with developing a project timeline and budget.Stakeholders will consist predominately of Smith employees so that in-house management willhave a firm grasp on the resources needed.The next stepin the SDLC approach is to form an analysis team to identify the needs ofthe various stakeholders as well as to better understand the needs of the proposed system. Thisanalysis team is responsible of keeping the stakeholders informed by using data flow diagrams asthe project progresses for an all encompassedstrict change control process. This step is vital inquality assurance which will be discussed at a later time. Smith will also be responsible indesigning methods required by the needs of the project. Methods include resources, tools, newmodels and various techniques used to fully identify system requirements. In some cases third-party vendors are valuable for they provide and use tools that some methods may require. Third-

BSA/385 Introduction to Software Engineering : Software Testing Environment Proposal - Page 5 preview image

Loading page ...

SMITHSOFTWARE TESTING ENVIRONMENTPROPOSAL4party vendors will be procured via contract and are subject to a determination of need by theproject stakeholders.Afinalized data flow diagramwill be presented for the next step. A design team will thendetermine the most effective and efficient approach to implement the design. Stakeholders willbe consulted before any final orders are given to include the procurement ofvendorsand theresources they will provide. Oncea vendor and resource aredetermined the design team willexecute the design as part of the project plan timeline. Smith will initiate developer testing aswell as end-user testing to ensure the final product meets the project plan criteria. Afteracceptance testing, the system will be implemented and the training phase will begin.Upon full implementation completion, a maintenance phase will begin. During this phaseSmith will be involved through its entire life cycle. Any and all contracts, to include telephonesupport, will be included as essential elements of this system.Quality Assurance Processes and ProceduresSmithis dedicated to providing development solutions to business information processesof the highest quality to its clients. This quality is measured and ensured through the use ofresource and tools put in place from the very start of the project. In order to strengthen existingbusiness processes by the practical application of new technologies, Smith will use highly trainedand qualified project managers (PM’s). Each of Smith’s PM’s has a multitude of experience andflawless track records that show they will stay on time and within the budget. Smith PM’s willprovide weekly updates to shareholders as well as daily meetings to ensure everyone involved inthe project is on track, but more importantly that there are no concerns for delays. Any concerns

BSA/385 Introduction to Software Engineering : Software Testing Environment Proposal - Page 6 preview image

Loading page ...

SMITHSOFTWARE TESTING ENVIRONMENTPROPOSAL5will be of utmost importance and PM’s will alleviate concerns with additional resources toaddress the problem with minimal operations impact or deviation from the project plan.As mentioned earlier,a strict change control process will be usedto ensure that theproject is kept within scope. Any changes to the project must be approved. Also mentionedearlier, Smith realizes that that there is not a clear-cut solution for each individual softwaredevelopment project and wishes to utilize a process that accounts for multiple variables whendeveloping new software. This strict change control process will reflect Smith’s project plan ofpriorityand secondary goals.These goals will be defined during the analysis phase however thestakeholders will have the option to make changes during the change control process. Primarygoals are to be strictly followed and any deviation to them must occur due to imminent danger orjeopardy to the project itself. Secondary goals on the other hand are identified as flexible and arenot bound such a strict change control process. Adherence to the change control process is vitalfor project success and not reliant on the outcome of each individual system developmentlifecycle phase.Formal Program Specification DocumentSmith systems will be recommending several changes to the current system at KudlerFineFoods. This is due in large part by the hardware and software that areout of date. Alllocations for Kudler Fine Foods including La Jolla, Del Mar, andEncinitas have a similar layoutof multiple PII Win9x to includeoffice 97,Novell 4.11 Servers and NT Server support.Locations also sport56k modem for internet connection. The system isrelatively old andcoulduse replacement systems such as the latest in Windows operating systems and hardware. For this

BSA/385 Introduction to Software Engineering : Software Testing Environment Proposal - Page 7 preview image

Loading page ...

SMITHSOFTWARE TESTING ENVIRONMENTPROPOSAL6project, Smith Consulting recommends an Agile Development Methodology to better serveKudler’s needs. This approach will promoteextensive testing and reviews from the owner.Design ConsiderationsPossible reasons for the development are to improve sales with Kudler Fine Foods and toboost customer satisfaction.KFF has a strongreputation and is taking measures to improve onthis by the implementation of arewardsprogram.A feasibility study will addressseveralconcerns that exist such as how much to invest and identifying acceptable risks.Team Bravobelievesthat thenumber one constraint will be thebudget. Since KudlerFine Foods is a smaller business with only three store locations the budget for implementing anew system for each location will be notan easy task.The budget will be closely monitored inregularprogress reports within theAgileSystem Development Lifecycle (SDLC).The goals and guidelinesof this proposal will be solely based on the project plan withinthe AgileSDLC.To reiterate, the main goal of the project is to provide a service to customersthat allow them to attain rewards for every product that they purchase, whether it is a bag ofpotatoes or a magazine.The secondary goal, or byproduct of the system, will be an increase ofcustomer satisfaction and loyalty.System Development Life CycleIn review,the software method of choice will bethe Agile SDLC.Taking a closer look,Smith Systems Consulting will use the Scrum methodology. With Scrum, this developmentmethodology will be centered on testing and reviews after each sprint,or increment. A ScrumTeam and Scrum master willbeformedto carry out the plan. The Scrum Master an owner willperiodically reviews thework after each increment.The steps will be organized and put in

Preview Mode

This document has 22 pages. Sign in to access the full document!

Report

Study Now!

Document Details

Related Documents

BSA385 Technical Article Document: Frequent Shopper Program

BSA385 � Introduction to Software Engineering : Frequent Shopper Program

DevOps and Its Importance Study Notes

Veeam Certified Engineer VMCE-V12

Modules 1 - 3 Basic Network Connectivity and Commu

Notes CCNA

CCNA 200-301 Portable Command Guide 5th Edition 20

CCNA 200-301 Portable Command Guide 5th Edition 22

CCNA 200-301 Portable Command Guide 5th Edition 36

Foundations of Novell Networking Section 26

Company

Explore

Study Tools