CS计算机代考程序代写 SE 433/333 Software Testing and Quality Assurance

SE 433/333 Software Testing and Quality Assurance
Final Report Project
Format
publications
two-column
Content
IEEE Computer Society format for conference
Between four and seven pages using the
:
http://www.ieee.org/conferences_events/conferences/publishing/templates.html
(use
the
format templates).
You should use the following section breakdown (respecting the suggested titles):
• Introduction A very brief introduction giving a high-level overview of your project.
• Problem Statement What are the problems that you are addressing in your project.
• Methodology A description of the solution/approach that you propose.
• Results A summary of the results of your analysis.
• Conclusion A brief summary of the important points of your project, of the significant
results, and a plan for future work. Also, you have to mention the tasks done by every group member for this project.
Evaluation
In evaluating your project, I will be looking for the following main points:
• That you spent a reasonable amount of effort understanding, analyzing, and/or implementing a software engineering approach for a software quality or testing problem.
• That you have been rigorous in devising and following a methodology to analyze/propose your approach.
• That you have spent the time and effort to produce a quality report. Assessment
1. As indicated on the project proposal description, the project final report with the coding/evaluation is 65% of your project’s grade
2. You will be graded on the quality and content of your report using the criteria mentioned above.
The report is the main deliverable for this project with the source code, so please pay special attention to the quality of the writing. In particular, use a precise, concise, and focused style. Avoid vagueness and repetitions, and do not state the obvious (in the context of the course).
Check the grammar and spelling. If you can, ask a colleague to review it.

Submission:
• The PDF report and the analyzed/implemented source code.
• All the text and diagrams(if any) must be electronically produced.
• Your names in the document.
• The report must be in a single PDF file.
• Submit your work by March 18, 23:59 P.M