-
The Business Is the Bottleneck
May 16, 2012
-
Problem Solving and Decision Making Processes
May 16, 2012
-
Dealing with Conflict in Project Teams
May 16, 2012
-
4 Easy Questions About How to Prioritize
May 15, 2012
-
An Example of a Project Charter
May 15, 2012
-
The Agile Project Manager - Fail Now as a Strategy
May 15, 2012
-
So What Is Value for Money?
May 14, 2012
-
Post-Agile?
May 14, 2012
-
Navigating the Path to Integration Success
May 14, 2012
-
When Agile Isn’t The Best Thing For The Client
May 13, 2012
A Project Management Primer - Scope - Requirements - Non-Functional Requirements
March 13, 2008 | Author: PM Hut | Filed under: Requirements Management, Scope Management
A Project Management Primer - Scope - Requirements - Non-Functional Requirements (#13 in the Hut A Project Management Primer)
By Nick Jenkins
It is essential to consider other requirements too, these are called “non-functional requirements” which, to my mind, is a bit of an oxymoron. The point however is valid, there are ‘obvious’ requirements that your end-users may not think about it.
Performance: Performance covers areas like responsiveness, throughput and speed of operation. What is the minimum performance that will satisfy your client?
Usability: How “easy-to-use” will the finished product be? For example do you cater for disabled or handicapped users? Generic ease of use should be considered though, more than one product has failed by supplying full functionality with an obscure or convoluted interface.
Reliability: Reliability requirements deal with the continuous availability of the product to users. They should state what availability is necessary and desirable.
Security: In products which deal with confidential or sensitive information, security considerations should be taken into account. Requirements for different levels of access, encryption and protection should be gathered.
Financial: Financial considerations which will determine the success or failure of the project. For example a bank or investor might specify certain financial constraints or covenants which must be satisfied during the project.
Legal: There may be legal requirements that must be met due to the environment in which your product will operate. Consult a legal expert for these.
Operational: There may be a number of day-to-day operational issues that need to be considered. Failure to accommodate these will not delay project launch but may limit or halt its uptake by end-users once it has been launched.
Specialist: There might be special requirements that are dependent upon the nature of the project or the nature of the business. You should considered these separately and state them explicitly in design docs.
Next in the Hut A Project Management Primer:
A Project Management Primer - Scope - Requirements - Stakeholders
Previously in the Hut A Project Management Primer:
A Project Management Primer - Scope - Requirements - Functional Requirements
Nick Jenkins is an IT manager with 10 years experience in software development, project management and software testing. He’s worked in various fields of IT development in Australia, Britain and the USA and occasionally he learned something along the way. Now he lives on the banks of the Swan River in Perth, Western Australia, and he publishes the odd guide to help aspiring IT professionals. Nick’s website can be found at www.nickjenkins.net.
Related Articles
- A Project Management Primer - Scope - Requirements - Functional Requirements
- A Project Management Primer - Scope - Requirements
- A Project Management Primer - Scope - Requirements - Stakeholders
- A Project Management Primer - Scope - Requirements Capture - Introduction
- A Project Management Primer - Scope - Documenting Requirements - Introduction
feel free to leave a comment
Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!
XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
All fields marked with " * " are required.
- Agile Project Management
- Ask the Hut
- Certification
- Change Management
- Communications Management
- Computer Based Information Systems
- Concepts
- Corporate Transformation
- Cost Management
- Critical Chain Project Management
- Delegation
- History
- HR Management
- Implementing Project Management
- Integration Management
- Lessons Learned
- Management
- Miscellaneous
- People Issues
- PMBOK
- PRINCE2
- Procurement Management
- Program Management
- Project Lifecycle Phases
- Project Management Advantages
- Project Management Advantages
- Project Management as a Career
- Project Management Best Practices
- Project Management Charts
- Project Management Definitions
- Project Management Ethics
- Project Management for Beginners
- Project Management Guides
- Project Management Musings
- Project Management Office
- Project Management Proposals
- Project Management Templates
- Project Portfolio Management
- Project Workforce Management
- Quality Management
- Requirements Management
- Risk Management
- Scheduling
- Scope Management
- SCRUM
- Soft Management
- Time Management
- Training
- Uncategorized
1 person has left a comment
[...] A Project Management Primer - Scope - Requirements - Non-Functional Requirements [...]