Just another WordPress weblog

Functional requirements:
Describe the interactions between the system and its

environment independent from implementation

Nonfunctional requirements:
User visible aspects of the system not directly related to

functional behavior.

Constraints (”Pseudo requirements”): Imposed by the client or the environment in which the system operates

• Functionality: Clear Function in Model.
  
• Usability: Malty of use and easy to use (user view).
  
• Performance: Mainly we mean time.
  
• Dependability:
  
  • Reliability: Trust in model that can do its function any time.
    
  • Robustness: Model can capable of overload of not.
    
  • Safety: of using system under most probable environment.
    
• Supportability: Effort and time to maintain and support (developer view).
  
  • Adaptability: Change function usage.
    
  • Maintainability: Change request.
    
• And OTHER
  

1.B.1-What is usually not in the requirements?



System structure, implementation technology

    Development methodology

    Development environment

    Implementation language

    Reusability

*It is desirable that none of the above are constrained by the client. Fight for it!

Don’t accept any of this constrains until customer have very strong reason.