132k views
3 votes
Which is NOT an example of common application features requirements reuse opportunity?

A. User authentication and security requirements are often the same across systems. For example, the systems might have a common requirement that all products must have a single sign-on using Active Directory for user authentication.
B. Business applications aften contain common functionality for which requirements-and perhaps even full implementations-can be reused. Possibilities include search operations, printing, file operations, user profiles, undo/redo, and text formatting
C. The same core set of requirements is used even though there might be some detailed requirement and/or user interface design differences based on the platform. Examples include applications that run on both Mac and Windows or on both iOS and Android
D. Often business processes are common across organizations and need to be commonly supported by software. Many institutions maintain a set of business process descriptions that are reused across IT projects.

User Pakage
by
7.2k points

1 Answer

5 votes

The option that is NOT an example of common application features requirements reuse opportunity is A. User authentication and security requirements are often the same across systems.

The option that is NOT an example of common application features requirements reuse opportunity is A. User authentication and security requirements are often the same across systems. This is because user authentication and security requirements may vary depending on the specific system and its security protocols. Therefore, they are not always reusable across different systems.

User SirFartALot
by
7.6k points