One basic aspect of IT project management is understanding the different requirements of a system. There are two types, which are both critical when implementing a successful IT project, functional and non-functional requirements.
Senior Project Manager, Søren Pedersen has defined both functional and non-functional requirements, so you can get a basic understanding of the difference between the two.
Functional requirements define what the system does, i.e. user interface, business processes, calculations, input, output etc.
Non-functional requirements define under which conditions the system will function, i.e. performance, service level, supportability, scalability, security etc.
When doing system implementations, you’ll need to have both functional and non-functional requirements specified – in detail.
It may well be that all requested system functionality has been implemented as specified, but system response times are unacceptable slow. Or the system can only comprehend 100 concurrent users, while 300 concurrent users are expected.
Or the system response time is easily met, while some basic calculations or presentation in the Graphical User Interface (GUI) are missing.
In this way, both functional and non-functional requirements are necessary and supplement each other.
Often when doing system implementations, we prepare a joint customer-contractor/vendor project plan/schedule, including tasks related to both functional and non-functional requirements. This will give the customer a good and overview and insight into dependencies, constraints and implementation progress.
Implementing an IT project into any business or organization can be complex and difficult and requires stringent processes and...
Whenever, I hear this, I get sad. And I hear it far too often. Unfortunately, many organizations have never got the desired ROI from their automation...