{"id":66,"date":"2019-03-28T11:28:32","date_gmt":"2019-03-28T15:28:32","guid":{"rendered":"https:\/\/sites.bu.edu\/braude\/?page_id=66"},"modified":"2019-03-28T11:40:41","modified_gmt":"2019-03-28T15:40:41","slug":"met-cs-773-software-testing-and-quality-assurance","status":"publish","type":"page","link":"https:\/\/sites.bu.edu\/braude\/courses\/met-cs-773-software-testing-and-quality-assurance\/","title":{"rendered":"MET CS 773 Software Testing and Quality Assurance"},"content":{"rendered":"

Last updated November 3, 2004: Last few changes often in red font <\/strong><\/p>\n\n\n\n\n\n\n\n\n
Background of the Instructor <\/strong>changed if this is red<\/td>\nLearning Objectives <\/strong>changed if this is red<\/td>\n<\/tr>\n
Contacting Eric Braude <\/strong>changed if this is red<\/td>\nPlagiarism Warning <\/strong>changed if this is red<\/td>\n<\/tr>\n
Evaluation of Students <\/strong>changed if this is red<\/td>\nPolicies – Miscellaneous<\/strong> changed if this is red<\/td>\n<\/tr>\n
Forums: Past and Present <\/strong>changed if this is red<\/td>\nProject Structure and Evaluation<\/strong> changed if this red<\/td>\n<\/tr>\n
Home Page of Eric Braude <\/strong>changed if this is red<\/td>\nTextbooks and Materials <\/strong>changed if this is red<\/td>\n<\/tr>\n
Homework and Due Dates <\/strong>changed if this is red<\/td>\nTopics and Class Dates <\/strong>changed if this is red<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
\n

Description from Catalog:<\/h2>\n

This course covers the theory and practice of quality assurance and testing for each step of the software development cycle.\u00a0 It introduces, defines, and contrasts the two pillars of software quality: Verification and Validation.\u00a0 The course covers test case design techniques, test coverage criteria, and tools for static and dynamic analysis.\u00a0 IEEE standards for test design and documentation are included.\u00a0 The course explains test-driven development and its relation with validation in the small and the large. QA for maintenance and legacy applications are covered.\u00a0 The course explores experimental and contemporary approaches to quality such as those inherent in agile development.\u00a0 Laboratory course. 4 cr<\/p>\n

\n

Prerequisites:<\/h2>\n

(1)\u00a0\u00a0\u00a0\u00a0 MET CS 566 or equivalent experience<\/p>\n

(2)\u00a0\u00a0 MET CS 673 (Software Engineering) or equivalent experience in software development.<\/p>\n

\n

Learning Objectives<\/h2>\n
    \n
  • Develop a quality software mindset<\/li>\n
  • Understand how to program with testing in mind<\/li>\n
  • Be able to plan for testing<\/li>\n
  • Be able to test in the small<\/li>\n
  • Be able to test in the large<\/li>\n<\/ul>\n
    \n

    Textbook and Materials<\/h2>\n
      \n
    • Recommended: JUnit in Action by Massol; Manning 2003, ISBN 1-930110-99-5 ($25.17 at Walmart.com) (ask me about this before buying)<\/li>\n
    • Recommended (not required): Software Testing: A Craftsman’s Approach, Second Edition, by Paul Jorgensen, ISBN: 0849308097 \u00a0(ask me about this before buying)<\/li>\n
    • Notes will be distributed for each class<\/li>\n<\/ul>\n
      \n

      Project Structure and Evaluation<\/h2>\n

      Students will be required to write and present a paper that will contain a specialized aspect of test or QA implementation.\u00a0 The paper will concern a testing method, theory or tool.\u00a0 Examples include: Testing Web applications, automated testing, testing real-time applications, QA tools, and bug tracking environments.<\/p>\n

      The project will be in two phases.\u00a0 The proposal phase will count for 20% of the grade and the remainder 80%.<\/p>\n

      \n

      Evaluation of Students<\/h2>\n

      The allocation of grades will be as follows.<\/p>\n

      Exercises:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 60%<\/p>\n

      Project:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 40%<\/p>\n

      Students may be given a number of pass\/fail assignments<\/span> throughout the semester.\u00a0 A \u201cPass\u201d grade is required on all of these.\u00a0 A grade of A or A+ may be given for a pass\/fail homework when the student has gone well beyond the requirements of the problem and has performed exceptionally.<\/p>\n

      Late homework<\/span> will not be accepted unless there is a reason why it was impossible<\/em> to perform the work in time given work and emergency conditions.\u00a0 In that case, the written reason should be attached to the homework, which will be graded on a pass\/fail basis if the reason is accepted by me.<\/p>\n

      \n

      Warning concerning plagiarism<\/h2>\n

      Please cite all references and uses of the work of other.\u00a0 All instances of plagiarism must be reported to the College for action.\u00a0 e-mail, see or call me if you have any doubts about the proper use of others\u2019 material. In any case, clearly acknowledge all sources in the context they are used, including code, of course.<\/p>\n

      \n

      Syllabus<\/h2>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
      Class<\/td>\nDate<\/td>\nTopic <\/em><\/td>\nChapters \/ Notes<\/td>\nProject:<\/p>\n

      (The dates in this column are approximate: See \u201chomework dates due\u201d section for official dates)<\/em> <\/em><\/td>\n<\/tr>\n

      1<\/td>\n9\/13<\/td>\nQuality and Ethics in Software Engineering<\/p>\n

      Creating a software application involves many error-prone steps and many requirements that are unknown at the outset.\u00a0 We explore the implications of this for quality and developer ethics.<\/td>\n

      		Notes<\/td>\n.<\/td>\n<\/tr>\n
      2<\/td>\n9\/20<\/td>\n\n
      Process Quality<\/h5>\n

      Quality Assurance Plans; CMM<\/td>\n

      		Notes<\/td>\n<\/td>\n<\/tr>\n
      3<\/td>\n9\/27<\/td>\nQA and Metrics in Project Management<\/p>\n

      Advisability of metrics, define several, and investigate their practicality; verification vs. validation<\/td>\n

      		Notes<\/td>\nIdentify paper topics: assigned.<\/td>\n<\/tr>\n
      4<\/td>\n10\/4<\/td>\n\n
      QA in Requirements<\/h5>\n

      How to evaluate the quality of an SRS; discuss embedding tests into an SRS<\/p>\n

      Behavioral testing in the absence of requirements.<\/td>\n

      		Notes<\/td>\nPaper proposal due<\/p>\n

      Requirements QA assigned<\/td>\n<\/tr>\n

      5<\/td>\n10\/18<\/td>\n\n
      QA in Designs<\/h5>\n

      Ways to measure the effectiveness of design; Design reliability (e.g., through components and re-use); error processing and security assurance processing<\/td>\n

      		Notes<\/td>\nDesign QA assigned<\/td>\n<\/tr>\n
      6<\/td>\n10\/25<\/td>\n\n
      Testing Principles<\/h5>\n

      This class covers the goals and basis for testing.<\/td>\n

      		Notes<\/td>\nTest-driven implementation assigned<\/td>\n<\/tr>\n
      7<\/td>\n11\/1<\/td>\n\n
      Verifying Implementation<\/h5>\n

      Ways to assess the quality of implementations outside of testing; test-driven development<\/td>\n

      		Notes<\/td>\nIntermediate paper due<\/p>\n

      Final paper form assigned<\/td>\n<\/tr>\n

      8<\/td>\n11\/8<\/td>\nUnit Testing<\/span><\/p>\n

      Introduction to unit (part) testing. Techniques of unit testing.<\/td>\n

      		Notes<\/td>\nUnit test assignment<\/td>\n<\/tr>\n
      9<\/td>\n11\/15<\/td>\nTo be determined<\/td>\n<\/td>\n<\/td>\n<\/tr>\n
      10<\/td>\n11\/22<\/td>\n\n
      Post-unit Testing\u00a0 I<\/h5>\n

      Regression, interface, integration, system, acceptance and installation testing.<\/td>\n

      		Notes<\/td>\n<\/td>\n<\/tr>\n
      11<\/td>\n11\/29<\/td>\nPost-unit Testing\u00a0 II<\/span><\/td>\nNotes<\/td>\n<\/td>\n<\/tr>\n
      12<\/td>\n12\/6<\/td>\n\n
      QA in Maintenance<\/h5>\n

      Refactoring<\/p>\n

      Principles of maintenance<\/p>\n

      Maintenance quality techniques; refactoring as a maintenance and quality tool.<\/td>\n

      		<\/td>\n<\/td>\n<\/tr>\n
      13<\/td>\n12\/13<\/td>\nPresentations<\/td>\nNotes<\/td>\nFinal paper due<\/td>\n<\/tr>\n
      14<\/td>\n12\/20<\/td>\nTo be determined<\/td>\n<\/td>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
      \n

      Forums — past and present<\/h2>\n

      Spring 2004<\/span>:\u00a0 Group home page: http:\/\/groups.yahoo.com\/group\/773Sp04<\/p>\n

      Summer 2004<\/span>:\u00a0 Group home page:http:\/\/groups.yahoo.com\/group\/773Su04<\/p>\n

      Fall 2004<\/span>: Group home page: http:\/\/groups.yahoo.com\/group\/773F04\/ Group email: 773F04@yahoogroups.com<\/p>\n","protected":false},"excerpt":{"rendered":"

      Last updated November 3, 2004: Last few changes often in red font Background of the Instructor changed if this is red Learning Objectives changed if this is red Contacting Eric Braude changed if this is red Plagiarism Warning changed if this is red Evaluation of Students changed if this is red Policies – Miscellaneous changed […]<\/p>\n","protected":false},"author":2828,"featured_media":0,"parent":22,"menu_order":9,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"_links":{"self":[{"href":"https:\/\/sites.bu.edu\/braude\/wp-json\/wp\/v2\/pages\/66"}],"collection":[{"href":"https:\/\/sites.bu.edu\/braude\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/sites.bu.edu\/braude\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/sites.bu.edu\/braude\/wp-json\/wp\/v2\/users\/2828"}],"replies":[{"embeddable":true,"href":"https:\/\/sites.bu.edu\/braude\/wp-json\/wp\/v2\/comments?post=66"}],"version-history":[{"count":1,"href":"https:\/\/sites.bu.edu\/braude\/wp-json\/wp\/v2\/pages\/66\/revisions"}],"predecessor-version":[{"id":67,"href":"https:\/\/sites.bu.edu\/braude\/wp-json\/wp\/v2\/pages\/66\/revisions\/67"}],"up":[{"embeddable":true,"href":"https:\/\/sites.bu.edu\/braude\/wp-json\/wp\/v2\/pages\/22"}],"wp:attachment":[{"href":"https:\/\/sites.bu.edu\/braude\/wp-json\/wp\/v2\/media?parent=66"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}