Inspirational Qoutes fOr yOu

If you don't like something, change it; if you can't change it, change the way you think about it.

- Mary Engelbreit

Thursday, February 19, 2009

Activity4a_SE1

Question:
Among the many nonfunctional requirements that can be included in a specification are those related to safety and reliability. How can we demonstrate that these requirements are testable? How can we demonstrate the reliability of a system that is required never to fail?


Non-functional requirements are requirements that specify criteria that can be used to judge the operation of a system, rather than specific behaviors. This should be contrasted with functional requirements that specify specific behavior or functions. In general, functional requirements define what a system is supposed to do whereas non-functional requirements define how a system is supposed to be. Non-functional requirements are often called qualities of a system. http://en.wikipedia.org/wiki/Non-functional_requirement

From the definition above, Non-functional requirements are the most critical factor in the success of your project. Without including it in your specification, your system will not be reliable enough and not secured to use.

In the question of how can we demonstrate that these requirements are testable? Is the same way of answering of how we can demonstrate the reliability of the system? The answer is to fully document both the functional and non-functional requirements. Both play different rules but of the same weight, I guess, because without the presence of one of the requirements in your system, it will definitely not work. Maybe that’s the main reason why functional and non-functional are included in developing a system because both are important in the completion of a project.

The main factor to consider in doing it is to have a better understanding of the performance your system and the usability of your system. One needs to study and have knowledge in documenting these requirements because without any knowledge of how it should be gathered or start with is useless. One needs to have a better and deep understanding about it. How can one or your group test your system without having it studied furthered?

The reliability and safety of you system depend on who develop the system. Who gathers the data needed and who list the requirements of the system. The group must have a root analysis in everything they do. It’s very important especially when you want your system to be on its peak when it will be implemented.

No comments:

Post a Comment