Define Non-functional requirements

Projects are never initiated with the purpose of doing the non-functional stuff but many projects are being hit hard by not respecting and planning the large amount of resources that is often required.

The non-functional scope elements consist of both technical – and project oriented deliverables.

Non-functional technical deliverables in software project are e.g. requirements related to security, performance, device compatibility etc. Non-functional project deliverables consist of e.g requirements related to reporting and project management procedures, stakeholder management, testing, training and documentation

The bigger the project the more resources need  to allocated to non-functional deliverables There are surveys indicating that non-functional tasks including testing often takes up  more than 50% of total time in projects and up to 65% in big projects (Jones, 2007, Estimating Software Costs, Bringing realism to estimating, Mc Graw Hill)


Non-functional requirements (project) may include:

  • Establishment of project infrastructure 
  • Project management
  • Testing
  • Training
  • Data migration
  • Documentation
  • Stakeholder management
  • Organizational implementation
  • Contracts and Vendor selection
  • Development of methods required in the project
  • Hand-over to operations
  • Establishment of support setup 


Non-functional requirements (technical/solution) 

  • Performance and Availability
  • Scalability
  • Security
  • License / payment solutions
  • User administration
  • Establishment of infrastructure and  technical environments
  • Build and deployment procedures
  • Help functions and – content
  • Data integration framework
  • Browser, OS and device compatibility