Faculty of Science, Engineering and Computing
CI7260 Software Quality Engineering Assessment Compendium
Assessment in CI7260 will be 90% coursework, which is a mix of an individual research report (40%) and a group project in software development (50%), and 10% for demonstration.
The summary table below gives the key assessment points and dates, and the following pages of the booklet contain the assessment briefs.
| In-course assessment | Type | Weight | Set date | Due date | Marker | Initial Feedback | Return date |
| Research report Group Project Demo | 40% 50% 10% | 09/03/20 09/03/20 09/03/20 | 06/04/20 30/04/20 30/04/20 | (JD)/(SK) (AS)/(JK)/ (SK) (AS)/(JK)/ (SK)* | 20/04/20 15/05/20 15/05/20 | 27/04/20 22/05/20 22/05/20 | |
| Examination | 0% |
* Prof S. Khaddaj (SK), Prof J. Dehmeshki (JD), Dr A. Shihab (AS), Dr J. Kiruthika (JK),
Module Learning Outcomes are assessed in in the research report, practical report and demo:
| LEARNING OUTCOME | ASSESSMENT STRATEGY |
| Compare, evaluate the concepts and terms defined in software quality assurance, the tools and the metrics together with related industrial standards for software evaluation throughout the software development lifecycle. | Individual research report to include a comparison and evaluation of software quality assurance factors, software project demonstration and presentation. |
| Analyze the benefits and pitfalls of applying software quality assurance and testing plans in different software development contexts. | Individual research report to include details analysis of practical testing plans, software project demonstration and presentation. |
| Critically evaluate the issues related to multi-layered architectures for web-based infrastructures suitable for developing and deploying web applications, , and produce the design elements of the project | Individual research report to include a discussion Server-side Infrastructure and Architectural aspects of Coursework. UML design as part of the project software development. |
| Apply and use markup languages, scripting languages, and document object models for the development of Client-side components of Web Applications. Create and consume Web Services and APIs | Client-side components and Technical and Architectural aspects of the software project development, demonstration and presentation. |
| Apply Database Access, Object-Relational-Mapping (ORM) and Model-View-Controller (MVC) frameworks and techniques for developing Server-side components of Web Applications. | Server-side components of the software project development, demonstration and presentation. |
| Develop software quality assurance and testing strategies, including security and usability aspects, and plans for given web development projects, and develop a demonstration system that utilizes appropriate tools and techniques. | Software project development, demonstration and presentation, including security and usability aspects. |
Faculty of Science, Engineering and Computing
Assessment Form
Module: CI7260 Setter: SK
Title of Assignment: Individual report & Group Development
Module weighting: 90%
Module Learning Outcomes assessed in this piece of coursework
- Compare, evaluate the concepts and terms defined in software quality assurance, the tools and the metrics together with related industrial standards for software evaluation throughout the software development lifecycle.
- Analyze the benefits and pitfalls of applying software quality assurance and testing plans in different software development contexts.
- Critically evaluate the issues related to multi-layered architectures for web-based infrastructures suitable for developing and deploying web applications, , and produce the design elements of the project
- Apply and use markup languages, scripting languages, and document object models for the development of Client-side components of Web Applications. Create and consume Web Services and APIs
- Apply Database Access, Object-Relational-Mapping (ORM) and Model-View-Controller (MVC) frameworks and techniques for developing Server-side components of Web Applications.
- Develop software quality assurance and testing strategies, including security and usability aspects, and plans for given web development projects, and develop a demonstration system that utilizes appropriate tools and techniques.
Assignment Brief and assessment criteria (these will be discussed within a formally timetabled class)
1. Assignment Brief: Given a scenario of a software development project, you will develop your understanding of quality management within a team as well as an individual. The individual report will review the theories and practices in software quality management while the group development will demonstrate the practices in software development with awareness of quality assurance, both in the context of software development lifecycle.
Assessment scenario
You are working for a company that specialises in bespoke software development. The company has been asked by a recruitment agency to develop an application that would enable job-seekers to fill their CV online in a structured way. The application would enable the agency to search the CVs to find job-seekers with a particular qualification, skill or experience.
One of your company’s analyst has interviewed several people in the agency in order to come up with a database design that captures the sort of data the agency would like in the job-seekers’ CV. He then went on to implement the design in MySQL in order to build a prototype application to test the design. However, before he could do this he suddenly left the company and left no documentation.
Your manager has decided to allocate a small team of programmers to build the prototype based on using MySQL database, and make sure all documentations are up-to-date. You are one of the members of this team. She has advised you that it would be a good idea to create a new database design in order to understand it better. She has also advised you that you should investigate and evaluate any software engineering tools that could help you with this and similar future projects.
You have been asked to produce a report (required content is specified below) and work in a team to prepare a demo & presentation for the client.
Your team will be developing a prototype that would
- Enable job-seekers to enter and edit their CV online
- Enable agency employees to search for job-seekers with a particular qualification, skill or experience
- Calculate Halstead’s volume on your code and present it to stake holders for KPIs.
How realistic is this exercise?
This exercise tries to simulate, as far as possible, what could happen on a real project. However, there are some obvious aspects of this exercise that will not make it completely realistic. These can be either positive or negative. The main positive ones are:
- One can learn more by having more time to reflect in this type of exercise than on a typical commercial project
- You can make assumptions about the project that may not be realistic on a commercial project (e.g. about the client, users, requirements) – this will give you more scope to be creative
The negative once are
- You will miss out on some important type of experience of working on a commercial project, e.g. company politics, interaction with a real client, serious consequences of making poor decisions
You should now proceed as follows
- Form teams of several students (you will be getting help with this from the module leader – it should be based on a shared interest to learn about a particular IDE, programming language(s) and the choice of modules during the exercise period)
- Discuss the experience of the members of the team in the following areas
- Programming
- Specific programming languages and environments
- Web development
- The tools listed above or more
- Choose a team leader – preferably the most experienced team member
- Plan your project in terms of the following stages
- Identify specific tools and languages to be used on your project (this could change later)
- Decide what hardware you will use (consider the limitations of using the university workstations and servers – would using laptops or home workstations be a better choice?)
- Create an Entity-Relationship model
- Create a copy of the MySQL database on your chosen server
- Develop a prototype that would enable job-seekers to enter data and generate a CV (e.g. in PDF or Word format)
- Develop a prototype that would enable the agency to search for job seekers using the following criteria
- Job or Sector (they want to work in) preference
- Minimum education level
- Minimum number of GCSE passes
- Specific educational qualification
- Specific professional qualification
- Specific skill
- Specific experience
- Write and submit an individual report (you may confer with other students but must not copy – see below details of what is required)
- Produce group project documentation
- Prepare and carry out demo / presentation ( see below details of what is required)
- Execute the plan including your Gantt Chart, and other Software Quality Assurance Documentations
- Calculate Halstead’s volume on your code for software metrics measurement purpose
Individual Report Content
The report should contain the following:
- Brief summary of the software engineering tools used in development including IDE, frameworks, and software quality assurance tools.
- Discussion of related software quality assurance theories and practices related to the project development
- Critical review of the software quality assurance tools and techniques used in the development and real practice experiences in the overall software development lifecycle.
- Discussion on future work if the project goes beyond the level defined in the coursework specification.
The Report should:
- Follow a logical Structure (Abstract, Preface, Main body, Conclusions, References )
- All sources should be acknowledged and fully referenced, including URLs etc. where appropriate
- Any quotations (from other sources) should be clearly marked as such, and referenced
- Be of publishable quality
Report presentation guideline and template are on CANVAS in “Unit 1 – Introduction to Software Quality”
Group Project Documentation
The Documentation should contain the following:
- Project schedule document
- Requirements Specification Documents
- Software Design Document
- System Implementation Plan
- SQA Plan
- Risk Management
- Testing documents Unit testing, black box testing usability testing performance testing
- SQA Test Case Report
- Calculate Halstead’s volume calculation
- Zipped source code
Group project preparation materials and templates are available on CANVAS in “Unit 1 – Introduction to Software Quality”
Planning the coursework
Please can each group complete one form and hand it in to the module leader.
| Group number | |
| Group members | |
| Team leader | |
| Experience of Programming Specific programming languages and environments Web development Software tools (please see the list in the coursework specs | |
| Software development tools and languages considered | |
| Environment to be used for the development and demo |
2. Feedback (including details of how and where feedback will be provided)
You will receive the feedback electronically using the feedback form (check the summary table for deadlines)
- Marking scheme: Individual Report
Student Name: K No.: Marker:
Project Summary ( /10)
| ** | VG | G | F | P | VP |
| Overview of project aims and final outcomes | |||||
| Summary of software engineering tools | |||||
| Summary of software quality assurance work involved |
Critical Review on SQ Theories and techniques ( /10)
| ** | VG | G | F | P | VP |
| Related software quality theories and critical review | |||||
| Related software quality techniques and critical review |
Reflections on SQA practices ( /10)
| ** | VG | G | F | P | VP |
| Reflections on chosen SQA tools | |||||
| Reflections on SQA practices/techniques | |||||
| Discussions on future work |
Presentation ( /10)
| ** | VG | G | F | P | VP |
| Overall structure and format | |||||
| Presentation | |||||
| Referencing and citation |
Further Comments
Overall mark ( /40)
** VG: Very Good, G: Good, F: Fair, P: Poor, VP: Very Poor
(II) Marking scheme: Group Work
Student Name: K No.: Marker:
Design, Development and SQA practice ( /30)
| ** | VG | G | F | P | VP |
| Requirement and design documentations | |||||
| Development functionality completeness | |||||
| Quality assurance practices |
Documentation Submitted Electronically ( /10)
| ** | VG | G | F | P | VP |
| Completeness of documentation | |||||
| Quality of the documentations |
Presentation ( /10)
| ** | VG | G | F | P | VP |
| Overall structure and format | |||||
| Presentation | |||||
| Referencing and citation |
Further Comments
Overall mark ( /50)
** VG: Very Good, G: Good, F: Fair, P: Poor, VP: Very Poor
Faculty of Science, Engineering and Computing
Assessment Form
Module: CI7260 Setter: SK
Title of Assignment: Demo
Module weighting: 10%
Submission details: During the demonstration you will be asked to show a working prototype of your program, which should demonstrate good knowledge of software construction and software quality.
Module Learning Outcomes assessed in this piece of coursework
- Develop a demonstration system that utilizes appropriate tools and techniques in different software processes to achieve overall high quality in software development.
Assignment Brief and assessment criteria (these will be discussed within a formally timetabled class)
- Assignment Brief: Demonstrating the implementation part of your work.
- Feedback (including details of how and where feedback will be provided)
You will receive the feedback electronically using the feedback form (check the summary table for deadlines)
Marking scheme
Demo/presentation
| ** | VG | G | F | P | VP |
| Quality: all working as expected | |||||
| Presentation | |||||
| Questions handling | |||||
| Teamwork in presentation |
Overall mark ( /10)
** VG: Very Good, G: Good, F: Fair, P: Poor, VP: Very Poor
The post CI7260 Software Quality Engineering Assessment Compendium appeared first on My Assignment Online.