Implementing a Development Plan

Project Scheduling
Much like the product being developed, project scheduling is completed systematically. Scheduling helps ensure that the project completes on time (remember planning?)

Steps to Schedule a Project

Simplify development activities by breaking them into a well-defined set of tasks. Determine the interdependencies Allocate time to each task Validate the effort by ensuring that there are the right amount of people on the project at any given time Define responsibilities for each team member Define the outcomes for every task Define milestones

Software Quality Assurance (SQA)

Quality of conformance: measures the extent to which the end product conforms to the requirement specifications Quality of design: refers to issues related to design (i.e. it is buggy or the infrastructure is not in place).

SQA Quality Measures

Correctness: to the extent to which a single function conforms to its required function. This is measured by a defect. Reliability: the probability that no defect will occur in a specified environment, during a specified exposure period

A program is reliable only if all of its modules are correct.

SQA Quality Measures

Integrity: Establishes the issue of the capability of the software to withstand security breaches. Threat: Probability of an attack of a particular type within a time span Security: Probability that the attack of a particular type will be overcome. {(1 security) * (1 threat)}

Formal Technical Reviews (FTR)

Reviews are conducted regularly to ensure that the project is continuing in the right direction. Verify quality of conformance and design Ensure the software meets predefined standards Ensure consistency in the development process

A test plan document should be created that defines all tests to be conducted The tests should be designed to detect the degree of conformance The tests should be planned well in advance of the actual testing. The test planner should be familiar with the internal working of the product, as well as the requirements. Tests should be defined at very low (detailed) levels. A testbed must be defined.

Test Planning