Guideline: Non-Functional Requirements for Existing Systems
Consider these classes of non-functional requirements when evaluating existing systems for fit as candidate services.
Relationships
Main Description
  • Exception Handling - Work to understand how exception handling works today. In batch processing, when exception occurs, the program abnormally terminates and produces a core dump. The programmer is required to look at the core dump and determine what needs to be done. This might not be acceptable. One would need to figure out what needs to be done, for instance, and how to integrate with exception handling framework.
  • Process and Data Distribution - Examine where the data and process are executed. A CICS application running on one machine might send a request to another machine (also known as function shipping in CICS) or it might "remote call" data on another machine. We might consider going directly (JDBC to DB) to the remote machine where the process or data is running, instead of using the connector which goes through the JDBC to DB.
  • Data Availability - If these is a VSAM customer file which requires, say, a 4 hour maintenance window, then we can't support 24/7 customer service. We would need to consider a new storage solution.
  • Authorization/Authentication - Many legacy applications have authorization and authentication mechanisms in the application code. This would require migrating user access management to federated managed environment supported by best practices.
  • Staging Delays - Typically batch programs run once a day in the night. If requirements are to run the program more often, then the schedule program must be modified to change the frequency.