6 of
18 relate the requirements of that larger system to functionality of the software and should identify
interfaces between that system and the software.
A block diagram showing the major components of the larger system, interconnections, and external
interfaces can be helpful. This is not a design or architecture picture. It is more to provide context,
especially if your system will interact with external actors. The system you are building should be
shown as a black box. Let the design document present the internals.
This subsection should also describe how the software operates inside various constraints. For
example, these constraints could include
a)
System interfaces (section 2.1.1)
b)
User interfaces (section 2.1.2)
c)
Hardware interfaces (section 2.1.3)
d)
Software interfaces (section 2.1.4)
e)
Communications interfaces (section 2.1.5)
f)
Memory (section 2.1.6)
g)
Operations (section 2.1.7)
h)
Site adaptation requirements (section 2.1.8)
2.1.1 System Interfaces This should list each system interface and identify the functionality of the software to accomplish
the system requirement and the interface description to match the system. These are external
systems that you have to interact with.
Example: For instance, if you are building a business application that interfaces with the existing employee payroll system, what is the API to that system that designer’s will need to use? The application will be implemented in java and it will use Android SDK, Facebook SDK and Google maps SDK. Eclipse will be used as IDE while implementing. MYSQL workbench will also be used as DBMS. Database of the system will be temporarily held in local servers.
