Define any pertinent message formatting. Identify any communication standards that will be used, such as FTP or HTTP. Specify any communication security or encryption issues, data transfer rates, and synchronization mechanisms.> SOFTWARE INTERFACE <Describe the connections between this system and other specific software components (name and version), including databases, operating systems, tools, libraries, and integrated commercial components. Identify the data items or messages coming into the system and going out and describe the purpose of each. Describe the services needed and the nature of communications. Refer to documents that describe detailed application programming interface protocols. Identify data that will be shared across software components. If the data sharing mechanism must be implemented in a specific way (for example, use of a global data area in a multitasking operating system), specify this as an implementation constraint.> HARDWARE INTERFACE <Describe the logical and physical characteristics of each interface between the software product and the hardware components of the system. This may include the supported device the nature of the data and control interactions between the software and the hardware, and communication protocols to be used.> FUNCTION/USER SECURITY MATRIX <Define the relationship between each user group (actor) both internal and external, and the functions (or use case) as described in the functional hierarchy or use case descriptions.> These matrixes are important in the phase of your analysis when both the business function model and entity relationship model seem consistent internally. You can use a CRUD matrix to answer the following questions: Do the business functions require the entities that are missing? Are there entities that are not used by any of the functions? <The following symbols represent the level of access by each of the user groups:> C Create R Read U Update D Delete
Define any pertinent message formatting. Identify any communication standards that will be used, such as FTP or HTTP. Specify any communication security or encryption issues, data transfer rates, and synchronization mechanisms.> SOFTWARE INTERFACE <Describe the connections between this system and other specific software components (name and version), including databases, operating systems, tools, libraries, and integrated commercial components. Identify the data items or messages coming into the system and going out and describe the purpose of each. Describe the services needed and the nature of communications. Refer to documents that describe detailed application programming interface protocols. Identify data that will be shared across software components. If the data sharing mechanism must be implemented in a specific way (for example, use of a global data area in a multitasking operating system), specify this as an implementation constraint.> HARDWARE INTERFACE <Describe the logical and physical characteristics of each interface between the software product and the hardware components of the system. This may include the supported device the nature of the data and control interactions between the software and the hardware, and communication protocols to be used.> FUNCTION/USER SECURITY MATRIX <Define the relationship between each user group (actor) both internal and external, and the functions (or use case) as described in the functional hierarchy or use case descriptions.> These matrixes are important in the phase of your analysis when both the business function model and entity relationship model seem consistent internally. You can use a CRUD matrix to answer the following questions: Do the business functions require the entities that are missing? Are there entities that are not used by any of the functions? <The following symbols represent the level of access by each of the user groups:> C Create R Read U Update D Delete
mfr-brd-feb18-2010.docx