Every software team will experience some sort of problem as they move through the system. These may be technical issues, issues with working with other departments, etc.
A Process Pattern describes a process related problem that is encountered during software engineering work, identifies the environment in which the problem occurs, and suggests one or more solutions to the problem.
A basic template for these describing a process pattern is below:
- Pattern Name – give is a meaningful name
- Forces – the environment in which the pattern exists and may affect the solution
- Type –
- Stage – associated with the framework activity
- Task Pattern – which work task or action
- Phase Pattern – the sequence of the framework
- Initial Context – Conditions which this process applies
- Problem – the actual problem
- Solution – to the problem
- Resulting Context – what will it be like once the solution is in place
- Related Patterns – is this similar to other issues?
- Known uses and examples
Software Process Structure was originally found on Access 2 Learn