Hot answers tagged

3

The definition of ‘functional requirement’ is that it essentially specifies something the system should do. The definition for a non-functional requirement is that it essentially specifies how the system should behave and that it is a constraint upon the systems behaviour. One could also think of non-functional requirements as quality attributes for of a ...


3

There are some major red flags here. You're only going to any testing after development is completely done? If this is development of a single feature, that's fine. If this is for an entire sprint worth of data, that's dangerous. You do not want to wait two weeks before sending a bug report to a developer. When I was developing I could barely remember what ...


2

How are you the only QA guy going to test the work of 10 developers? You will be flooded with work, teach the developers to test! :) This is important, because you will be taking shortcuts under pressure. This could lead to lower quality then before there was a QA guy, because the developers think they have to test less since they now have a dedicated ...


2

What you have description is typical of a 'waterfall' approach to software design. There are some circumstances where this is appropriate, for example the y2k bug and I have been on such projects. However most development today is done with a more modern, typically 'Agile' process. I would suggest that you consider the following Agile process: devs and ...


1

IMHO most obvious hole in your process is missing bug tracker. Get one free, like TRAC. It includes wiki for technical documentation. Every feature should start as a bug in bug tracker. Get developers write whatever thoughts they wave to bug and/or wiki pages linked, so few months later you will be able to recall what assumptions developers made when ...



Only top voted, non community-wiki answers of a minimum length are eligible