1 / 12

SQA Plan

SQA Plan. SETEAM1 Adam Jundt (Team Leader) Philip Galloway Roland Craddolph Steven Chu Philip Galloway Kyle Becker Patrick Rogers-Ostema. SCENARIO.

zeus-robertson
Télécharger la présentation

SQA Plan

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SQA Plan SETEAM1 Adam Jundt (Team Leader) Philip Galloway Roland Craddolph Steven Chu Philip Galloway Kyle Becker Patrick Rogers-Ostema

  2. SCENARIO • A medium size company with a small department. The company wants the IT department to develop innovative approaches to improve the business processes.

  3. INTRODUCTION • In order to develop an SQA plan that will improve the business process of the company at hand, we have decided to advocate the development of a project dashboard to track and monitor key data within any business environment. This will include things such as Earned Value analysis data & budget tracking as well as graphical representations of all user data. The various aspects leading to a possible SQA plan are described in the following pages.

  4. REQUIREMENTS ELICITATION 1.) Why is the process needed? 2.) What will the process do? 3.) How much will it cost? 4.) When will the process begin service? 5.) How long will the process be in service? 6.) Will the process stand alone, or will it improve a process already in place?

  5. PROGRAM IMPLEMENTATION & TESTING: Extreme Programming Implementation - Because our company is composed of a small IT department, we will use an extreme programming approach for the programming and testing portions of this project. We feel that this methodology matches our experience and project statement perfectly.

  6. PROGRAM IMPLEMENTATION & TESTING: Extreme Programming Testing - We will utilize automated testing in the form of unit testing. We have chosen to use the JUnit classes to help us out here because they are free, and we would like to keep this project as low budget as possible. This will confine us to using Java. JUnit testing involves using assert statements that will be fully automated and will be executed before every submission of code. Also, these test cases will be written in a report before programming begins.

  7. PROGRAM IMPLEMENTATION & TESTING: Extreme Programming Testing Cont…- As another method of software quality assurance, we will also be doing customer testing. We will poll a small set of users to discover their thoughts on the current state of the project. This will occur once every two weeks, which is the recommendation of extreme programming.

  8. PROGRAM IMPLEMENTATION & TESTING: Extreme Programming Programming - As discussed earlier, we will be implementing the project in Java so that we can accomplish automated testing. We will use paired programming to help ensure: • Much cleaner code • Better tested • Easily refactor code • Keeps employees honest • Helps employees learn from each other • Everyone knows and modifies all parts of the code • More easily changed requirements (less cost) We will also be open for changing requirements and will follow an iterative development.

  9. PROJECT DASHBOARD “WOW We Are So Good Dashboard” This is an effective dashboard because it displays in each area of the operation where we lack in and what needs to be important.  If we combine the Average Salary By Work Department and Budget By Project, shows how much each team and their projects are worth for the company.  The outstanding balances is what counters the Budget By Project, by showing how each team lead is behind on sales on their team.  The bottom diagrams show how much each site is selling to their respective region.  Currently, Amsterdam, Toledo, and Ontario are the higher sellers, whereas Lawrence is at the bottom of selling.

  10. PROJECT DASHBOARD

  11. RESULTING SQA PLAN

  12. Questions? You know you got em...

More Related