ELEC5618 Software Quality Engineering Page 1 of 4 Assignment 1 School of Electrical and Information Engineering Instructions • Complete deliverables described in the laboratory slides each week. • A ZIP file of the deliverables to be submitted on Canvas. • Please submit individually. • Submission due by Week 6, Sunday 18 April 2021 at 11:59pm. Assessment There are six components that make up the submission for the assignment, each containing one or two documents. Submissions will be assessed against the requirements for each week as described in the laboratory slides. The marks for the six components are weighted equally. A chosen project is the basis of the assignment. The progression of activities during the weeks leading up to submission follows that which is required to implement a software quality plan. Page 2 of 4 ELEC5618 Software Quality Engineering Assignment 1 Deliverables Each week there are a number of activities to be completed which are described in the laboratory slides. The final submission will be a ZIP file of these folders to be uploaded to Canvas. The outcomes from these activities are to be saved into folders with names as indicated in the laboratory slides. The following is a summary of the activities to be completed. The headings cross reference the sections in the laboratory slides that contain the complete details of the activities. The tables describe the documents which are required and the folder were they should be placed. Lab 2.1 Team Formation and Operating Principles Lab 2.2 Select an Open-Source Project Teamwork is a skill that is becoming more important in corporate environments. A company typically needs a person with skills in a specific area, but on top of that, someone that is capable of integrating in an already existing team and contribute to its success. Folder Documents 02 meeting policy Document describing the policy to organize team meetings. Lab 2.3 Structure of the Product and Quality Mechanisms The objective of this activity is to understand the level of quality assurance present in the project that has been chosen. This is not only restricted to unit testing, but includes also testing strategies, regressions, documentation, quality plan, reviews, and inspections. Folder Documents 03 project description Brief document titled Project Description, with information about the project One-page document titled Initial Quality Assurance Mechanisms describing the presence/absence of the following elements in the project. Lab 3.1 QA Items Present in the Project Lab 3.2 Compare QA Measures Encountered in the Project The objective of these activities is to further understand the project that has been chosen. This includes the main functionalities, the software architecture, and main data structures. Once a better understanding of the project is obtained, the further objective is to consider potential defects that must be avoided and what measures that could be put in place to ensure that they are detected before it is released. Page 3 of 4 ELEC5618 Software Quality Engineering Assignment 1 Folder Documents 04 initial qa mechanisms A document that includes a list of the main functionalities, a diagram of the software architecture and a list of the main data structures One page document that describes one of the potential defects and what measure can be used to detect it. Lab 4.1 Sections of the SQP for the Project Lab 4.2 Review Sections of the SQP for the Project The objective for this activity is to write parts of a Software Quality Plan (SQP) for the chosen project. There are two topics to be covered: Management (Organization, Tasks, Roles and responsibilities, Quality assurance estimated resources) and Documentation (Purpose, Minimum documentation requirements, Other documentation). Folder Documents 05 sqp section A document describing your presented version of your software quality plan for your project. Also, please attach your pre-lab document containing your selected section of the software quality plan. Lab 5.1 Write SRS and Use Cases for the Project Lab 5.2 Refine Functional Requirements and Use Cases for the Project The objective for this activity is to look at the Software Requirement Specification (SRS). Look at how requirements can be described in a concise and unambiguous way and how use cases can be used to describe requirements. Folder Documents 06 srs use cases A document describing two requirements for your project. A document describing two use cases for your project. Page 4 of 4 ELEC5618 Software Quality Engineering Assignment 1 Lab 6.1 Prepare a Checklist of the Items to Verify in a Fagan Inspection Lab 6.2 Apply Checklist and Static Verification to the Project Source Code The objective for this activity is to use the method described by Fagan to inspect the source code in your project. The check list provided in the paper by Fagan can be adapted to your project. This check list will then be applied to some of the source code in your project and the results documented. Folder Documents 07_fagan A no more than two-page document that has three sections: the result of the check list on parts of the code, a list of aspects of the inspection that were missing, and a summary of anomalies detected by static verification.
欢迎咨询51作业君
