next up previous
Next: Software Use Case model Up: Introduction Previous: Software Interfaces

Major constraints

Any business or product line constraints that will impact the manner in which the software is to be developed, designed, implemented or tested are noted here.

Performance constraints
Specified here constraints like

Design constraints

Specify here the constraints about the development tools and software packages available. For example, the RDA project must use VB and ASP.

Assumptions and Dependencies

List each of the factors that affect the requirements stated in this ARS. These factors are not design constraints on the software but are, rather, those assumptions that any changes to these assumptions can affect the requirements. For example, an assumption might be that a specific development system would be available on the some hardware designated for your project. The .NET on the SE lab is classic real example. Or, that the old system would be available for testing. (RDA project).

If, in fact, these resource were not available, the SRS would then have to be changed accordingly.

Special Restrictions and Limitations
Special issues which impact the specification, design, or implementation of the software are noted here.

Course-Project constraints
In few of our projects, the application can not run as stand alone, therefore there is a major constraint on a real live demo of the product. In this case specify here what is needed to be done for maximum live demo and testing.


next up previous
Next: Software Use Case model Up: Introduction Previous: Software Interfaces
Eliezer Kaplansky 2002-12-25