- Before
software
- can be designed
- the software designer must a have firm grasp of its requirements.
- Before
requirements
- can be prescribed
- the requirements engineer must have a firm grasp of the
underlying application domain.
- Therefore we must develop, or there must be available,
- a suitable
domain description.
- In order for the software
- to
satisfy
customers'/users'
expectations
- and be
correct,
- the
domain descriptions
as well as
- the
requirements prescriptions
-
must also be formal.
- The requirements prescription
must be formal so as to
show correctness of software.
- The domain description
must be expressed formally so as
to show that software satisfies customers'/users' expectations
Dines Bjorner
2017-01-12