Deprecated: Non-static method rgbOptions::rgb_init() should not be called statically in /home/domai125/public_html/ on line 783

Deprecated: Non-static method rgbOptions::rgb_install() should not be called statically in /home/domai125/public_html/ on line 80

Notice: Undefined variable: curent in /home/domai125/public_html/ on line 97

Warning: Cannot modify header information - headers already sent by (output started at /home/domai125/public_html/ in /home/domai125/public_html/ on line 36
Functional at Artieda 2011



Requisite of System: they detail the functions and the restrictions of the system, being known as specification of system requirements. The point to serve of contract between the purchaser must be necessary and the desenvolvedor. Technician of senior level is directed for the professionals and controlling of projects, but could be used for the controlling of the customer, final suppliers and users. Specification of software project: abstract description of the project of software, adding more details to the specification of system requirements. It is directed to the implementation, being written for the software engineers who will develop the system. The system requirements normally are classified as functional, not-functionaries or of domain. It is important to remember that the requirements must specify what is for being made and not it as will be made.

20 Functional: they describe what a system must make in reply to a specific stimulaton. Of this form, they specify the behavior of entrance and exit of a system. Not-Functionary: they describe the performance or restrictions of the system that affects the development and the project. They can include some categories, as: security, trustworthiness, environment, implementation, people, among others (STSC, 2003). The functional requirements not-functionaries can in accordance with appear the necessity of the users, either had the alterations in the current law that affects the system, either for restrictions in the budget, new function to be played by software, an enterprise strategy, as to launch the product anticipatedly to take care of to a demand of the market or some another condition that compels an intervention in the course of the project. Figure 2 shows to a type of classification of the types of requirements not-functionaries that can appear (SOMMERVILLE, 2003): Figure 2: Classification of requirements not-functionaries Source: Sommerville, 2003 Of domain: they can be requisite functionaries or not-functionaries and are derived from the domain of the application, reflecting characteristic of this domain, that is, they are not gotten from the necessities of the users of the system.

This entry is filed under News. And tagged with . You can follow any responses to this entry through RSS 2.0. Both comments and pings are currently closed.

Comments are currently closed.

© 2012-2024 Artieda 2011 All Rights Reserved