software quality assurance

| June 14, 2016

Question
Please see the details below about my project if you need any details pls feel free to ask, and send me the price .. •A project proposal: due on 3/24/12 A final project report: due on 3/27/12 . The details are given below. Acceptable project types There are two types of basic choices for your course project, one focusing on testing, and anther focusing on other QA techniques: 1.An application of some specific testing techniques/models to some programs/products you are developing/testing/maintaining/supporting. For example, you may choose to construct control flow and data flow models to test a module you are developing at your work. Another example is the development, validation, and usage of an operational profile for a large software systems you are working on. It’s generally a good idea to consider multiple testing techniques and actually use a couple of them in your project to get a hands-on feeling of how different techniques and models work in practical applications. Pay special attention to the evaluation of your testing/analysis results. Be prepared to answer this type of questions: •How do you know if the testing technique works? •What’s the basis for comparison (baseline)? •What about some other testing techniques that might be appropriate? Your answer can be based on either the practical evidence (executing several types of testing cases and observing the results) or based on logical arguments (suitability of certain testing technique on certain types of products), or both. * Undergraduate students can choose to perform only a high-level analysis to answer the above questions without going into details. 2.You may choose to focus on performing various other quality assurance activities and document the results, while performing limited/small-scale testing. Possibilities include comprehensive inspection, defect prevention and process improvement, formal verification, and fault tolerance. You may also collect inspection/testing/QA records for a product at your work, and construct quality models to analyze the results, to assess the effectiveness of your inspection/testing/QA techniques, or to identify high-defect modules for focused quality improvement actions. If you choose this second type of project, I still want you to perform at least some small scale/amount of testing because it is such an important part of our course. For the QA part, make sure you are focusing on quality that can be quantified and analyzed. (For example, a process definition/improvement initiative with only a logical argument for its superiority is not suitable for this class.) Where to Find Something to Test or to Perform QA on? •Well, I mentioned about your work, a product, or a sub-part of a product, that you are involved at your work. However, if you don’t feel comfortable taking this as your class project or talking about it (without mentioning product name and raw data) in class, you need to find something else to work on. Notice: Your project report must contain testing related technical information, such as test models, test cases, and test results, although you don’t have to give detailed product information. As a rule of thumb, if you feel uncomfortable with the material you have to put into this report, find something else to work on. •Many students used their past projects from work, from their former college/graduate school classes, from their hobby (e.g., game programming), or from their role as users of some specific packages/software/web-site/etc. Apply the same sensitivity rule as for your current project above. •You can get it from someone else. Open source software and programs are a wonderful source for many student projects in the past as well. Project proposals Your project proposal should be around 3-4 double spaced pages in length, and should include the following information: •a one-paragraph abstract (at the beginning of the proposal), •introduction: clearly identify the problem that you are going to address, •brief background information (about 1/2 or 1 page), •the solution strategy you intend to use (which testing technique? what kind of analyses? etc.), •expected results, •analysis of result to be performed, •followup actions, •a rough schedule, •indicate whether you’ll be making a project presentation, and, if possible, your preferred presentation date. In case of a group project, please also pay attention to the following: •Please provide information regarding each team member’s roles and responsibilities. •The amount of work proposed for a group project should be appropriate for the group size. As a general rule of thumb, if something can be comfortably done by a single student, it is not suitable as a group project. •Unless there is a compelling reason, group size of 3 or more is discouraged due to the expectation that everyone in the team will be performing hands-on testing activities using multiple testing techniques. •You only need to submit one proposal and one report for the project, which must follow the same instruction as the individual projects. Project summary or presentation? The choice is yours All the graduate students are required to submit a project summary, Your summary should focus on the main results from your project for us to get the basic picture. Here is a template for your project summary. Project report The project report should be treated as a term paper, around 15 double-spaced pages in length, but no longer than 20 pages, for graduate students. The report should clearly and comprehensively states the background, problem, strategy, activities, results, result analysis, lessons learned, followup actions, and a high level summary (and an abstract at the beginning). Additional material, such as graphs, models, test cases, etc. produced, information sources and raw data, customer surveys, etc., can be included in the appendix and clearly marked as such (so it will not be counted towards your 20 page quota). For undergraduate students, you report should be similar, except the analysis part (see information in the “Proposal” section above). As a result, your report is expected to be around 10-12 pages. But, if you choose to, you can follow the instruction for graduate students as well. Several common mistakes to avoid: •It is supposed to be a “report”, not a set of “presentation slides”. So, limit your use of lists/bullets, and put most of the material/discussions in paragraphs. Similarly, only figures and tables without corresponding discussions do not make a good report. •Your project report must contain testing related technical information, such as important test models, test cases, test results, and analysis of the results. In addition, you need to describe/discuss this information unless it is clearly self-explanatory. •On the other hand, you shouldn’t include all the graphs, models, test cases, etc. produced for the project in the report text itself. As I mentioned above, they can be included in the appendix, if you desire, together with other material, such as raw data, customer surveys, etc. Please make sure that it is APA referncing standard You should consider these things when you do the reports: Quality assurance (QA) includes many techniques and activities aimed at assuring that appropriate functionality has been implemented correctly in the software system or product. We will devote substantial time of this course to various topics related to testing, with a focus on testing techniques, including: •black box or functional testing, •clear box or structural testing, •usage-based statistical testing.

Order your essay today and save 30% with the discount code: ESSAYHELP
Order your essay today and save 30% with the discount code: ESSAYHELPOrder Now