Software Quality and Process Management
On completion of this module, a student should be able to:
- Select, evaluate and apply standards, tools and techniques for assuring software quality
- Critically review a software development process and identify its ranking in an accepted capability maturity model.
- Critically evaluate an architectural design against accepted quality criteria.
- Select, evaluate and use tools and techniques to successfully manage a large scale software project, including configuration management and version control.
- Estimate the cost and duration of a software project.
The module content is split into the following topics. Each topic lasts for one or two weeks. The lab activities for each are provided in numbered markdown files in the home directory of this repository with the supporting materials in the
exercises/ directory. You should start by cloning this repository into your development workstation. This might be:
- Using the Windows 10 lab computers (download Visual Studio Code from the AppsAnywhere server)
- Using your own laptop computer
- or you might use your Chromebook and clone into an instance of an online IDE such as Goorm. For help with this option you will find a lab called Setup.
You will need to understand the syntax of the ECMA programming language which you will be using to develop your software during this module.
There are two labs to complete and you should aim to get both completed in the first two weeks:
- Templates and Forms
- Dynamic Websites
The extension lab covers the use of advanced async features to reduce the complexity of your code and improve legibility.
2 Test-Driven Development
In this week we will be extending your understanding of ECMA6 by learning how to apply the principles of Test-Driven Development (TDD) when writing code in the ECMA6 programming language. You will be required to complete the TDD Express lab this week. There are two additional labs that you should be attempting if time allows.
- TDD API
- TDD for Browser JS using the MQTT protocol
3 Software Design
At this stage you will have been assigned to an assignment topic and will apply the Domain-Driven Design (DDD) techniques to build a domain model and use this to explore alternative architectures. This will form part of your assignment submission. If you have time you will be able to continue your ECMA6 learning. There are two labs in this section, each taking a week to complete:
- Domain-Driven Design
- Software Architecture
4 Software Architecture
5 Architectural Coupling
- BEA chapter 4: Architectural Coupling
- Domain-Driven Design
- Copy of 09 Acceptance Testing
6 Software Quality
- Week 6 - Software Quality Metrics
- Week 7 - Software quality measurement and indicators
- Week 8 - Software quality metrics and ISO_IEC standard
7 Fitness Functions
- BEA chapter 2: Fitness Functions
- Week 6 - Cyclomatic Complexity
- Copy of 08 Non-Functional Testing
8 Software Development
- Week 9 - Capability Maturity Models
9 Advanced Version Control
- Copy of 07 Advanced Version Control
10 Continuous Integration and Delivery
- BEA chapter 3: Engineering Incremental Change
- Copy of 10 Continuous Integration and Delivery
- Copy of 11 Deploying Code
Stuff to Remove
Removing any content related to agile processes
5 Project Management
- Week 5 - Agile Software Estimation Techniques
- Week 5 - Software Project Cost Estimate Models
- Design model
- Annotated source code
- Test suite
- Branching model
- Process maturity
- Evaluation of agile technique
Start project with a hub and spoke architecture. Each student (team?) contributes a module to this. Perhaps use pubsub MQTT broker? Also can tap into building data?
- System log