Comments on: Tutorial#02 Functional and nonfunctional requirements http://www.stevenchoy.com/mt356f/tutorial02/ Archiving the teaching of MT356F from September 2006 to May 2007 Thu, 8 Jan 2009 11:32:52 +0000 http://wordpress.org/?v=2.0.4 by: ching_lam68 http://www.stevenchoy.com/mt356f/tutorial02/#comment-12 Tue, 03 Oct 2006 13:53:32 +0000 http://www.stevenchoy.com/mt356f/tutorial02/#comment-12 I'll pay more attention on the coming Lecture :-) I’ll pay more attention on the coming Lecture :-)

]]> by: Steven Choy http://www.stevenchoy.com/mt356f/tutorial02/#comment-11 Tue, 03 Oct 2006 01:40:34 +0000 http://www.stevenchoy.com/mt356f/tutorial02/#comment-11 "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. “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.

]]> by: ching_lam68 http://www.stevenchoy.com/mt356f/tutorial02/#comment-10 Fri, 29 Sep 2006 07:23:24 +0000 http://www.stevenchoy.com/mt356f/tutorial02/#comment-10 Hi Steven! Confuse with separate the functional and non-functional requirements. Hi Steven!
Confuse with separate the functional and non-functional requirements.

]]> by: Steven Choy http://www.stevenchoy.com/mt356f/tutorial02/#comment-9 Wed, 27 Sep 2006 09:36:18 +0000 http://www.stevenchoy.com/mt356f/tutorial02/#comment-9 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 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

]]> by: Steven Choy http://www.stevenchoy.com/mt356f/tutorial02/#comment-7 Tue, 26 Sep 2006 02:20:53 +0000 http://www.stevenchoy.com/mt356f/tutorial02/#comment-7 Please go to <a href="http://plbpc013.ouhk.edu.hk/mt356f/" rel="nofollow">plbpc013.ouhk.edu.hk</a> to get the tutorial and discussion questions. Please go to plbpc013.ouhk.edu.hk to get the tutorial and discussion questions.

]]>