Tutorial#02 Functional and nonfunctional requirements
In this tutorial, you will do some tutorial exercises on software requirements, functional requirements and non-functional requirements. You will also have a class discussion on why software projects fail so often.
You will also submit your project team membership, team name and team leader.
* * *
5 Comments
Sorry, the comment form is closed at this time.
Please go to plbpc013.ouhk.edu.hk to get the tutorial and discussion questions.
IEEE Spectrum September 2005 Issue has a feature article on the issue why software fails (http://www.spectrum.ieee.org/sep05/1685).
Why do software projects fail so often?
* Unrealistic or unarticulated project goals
* Inaccurate estimates of needed resources
* Badly defined system requirements
* Poor reporting of the project’s status
* Unmanaged risks
* Poor communication among customers, developers, and users
* Use of immature technology
* Inability to handle the project’s complexity
* Sloppy development practices
* Poor project management
* Stakeholder politics
* Commercial pressures
Hi Steven!
Confuse with separate the functional and non-functional requirements.
“Functional requirements describe the interactions between the system and its environment independent of its implementation.” (Page 125 of the textbook)
“Non-functional requirements describe aspects of the system that are not directly related to the functional behavior of the system. Non-functional requirements include a broad variety of requirements that apply to many different aspects of the system, from usability to performance.” (Page 126 of the textbook)
We will have more discussions on these two concepts on Lecture #4.
I’ll pay more attention on the coming Lecture