Home > Articles > Software Development & Management > Object Technology

  • Print
  • + Share This
Like this article? We recommend

Like this article? We recommend

Software Plasticity: An Architectural Attribute

Modifiability is the architectural quality attribute most related to plasticity. A modifiable architecture is one for which future changes don't have far-reaching consequences. The plasticity requirements in this article are simply that we should be able to open some Java code, create some additional logging detail, and then apply a bug fix to the area.

Figure 2 illustrates the idea of two developers working on two different products. Bug reports come in from the field and both programmers have to try to deduce an appropriate fix. Let's assume that both have access to the fielded system. The two programmers have a good idea which Java class has the problem, but the Java class in question has insufficient logging data to determine the exact problem. How can the programmers determine what to do? To answer this question, let's look a little more closely at the area of in-field debugging and the code in question.

Figure 2

Figure 2 Two programmers—only one of whom is using plastic software.

In-field Debugging and AOP

Network management tends to feature transactions such as reading a block of data from the network or modifying a table in a device. For our in-field debugging mechanism to work, we need close cooperation with the end user. Let's say that a specific transaction has failed. We get the user to repeat the operation after we've dropped in our interception code. The interception code has the necessary logging detail that will tell us exactly the nature of the problem.

Peeking at the Java Code

In the Java code examples for this article, the topmost layer of Figure 1 is represented by a class called ApplicationLayerRequestData:

public class ApplicationLayerRequestData {
  public static void main(String argv[]) {
    ApplicationLayerRequestData appLayerReqData = new

public void readData(String argv[]) {
    RequestNetworkData someData = new RequestNetworkData(argv);

The ApplicationLayerRequestData has a main method that calls into the middle layer of Figure 1 by instantiating an object of the class RequestNetworkData and invoking its collectNetworkData() method. Let's have a look at that method:

public void collectNetworkData(String argv[])
    final String host = argv[0];
    final String port = argv[1];
    final int WAIT_TIME = 10000;
    final int MS_DIVIDEND = 1000;

    // Lots of Java DMK code here

    SnmpVarBindList vbList =
      dispatchRequest(list, session, host, port, WAIT_TIME);

The collectNetworkData() method calls into Java DMK via the dispatchRequest method to retrieve some SNMP data from a selected device. The selected device is specified on the command line of the program and must be accompanied by a UDP port number (the standard SNMP port is 161).

Once we've collected the network data, we use it for some purpose, such as updating a device in the network. The latter is handled by calling the ApplicationLayerRequestData method writeData(). This completes the transaction started when we read the network data.

Putting It All Together

In the previous section, we saw a transaction that reads data from a designated network device and uses this data to update either that device or another one. This is the network-management process called configuration, whereby some change is introduced to the network. In this case, the update method does little more than print a message to screen. However, for the moment I want to focus on the data that we've read from the device.

Very often, network managers execute complex transactional configuration procedures against their networks. Typically, this process involves a combination of steps:

  1. Reading data from the network.
  2. Supplying some additional operational data.
  3. Updating the configuration of one more devices in the network.
  4. Retrieving some network data to verify the change(s).

The first two steps dictate the success of the overall operation. If the data supplied to the update software (in step 3) is inaccurate, the configuration change may fail. Often, the failure is very difficult to track down. Dozens of data items may be involved, the value of one of which may cause a downstream failure. So we need a way of looking at the configuration data before the network update occurs. This is where we make use of the magic of AOP and AspectWerkz to intercept the code after steps 1 and 2.

Intercepting the Network Update Operation

We want to intercept the operation of the class ApplicationLayerRequestData between the following two method calls:


When we've acquired our data, we want to be able to see it prior to using it to update the network. Part of the collectNetworkData() method writes the required data to a file called networkData.txt. In an operational scheme, this data might be stored in a database table or in an internal data structure. Whatever the location, we want to be able to look at this data!

The method collectNetworkData contains code that captures the data to file as follows:

try {
BufferedWriter out = new BufferedWriter(new FileWriter("networkData.txt"));
out.write(vbList.varBindListToString(), 0, vbList.varBindListToString().length());
} catch (IOException e)

We want to see the contents of the file networkData.txt prior to calling the method ApplicationLayerRequestData.writeData(). This can be achieved elegantly by creating an AOP aspect class called MyAspect.java. This class contains a method called beforeNetworkUpdate() that gets called prior to the update method as required:

public class MyAspect {
public void beforeNetworkUpdate(JoinPoint joinPoint) {
System.out.println("Before Network Update - fasten your seatbelt!");

To orchestrate the interception of ApplicationLayerRequestData.readData(), we employ an XML file called aop.xml:

<system id="AspectWerkzExample">
    <aspect class="MyAspect">
        <pointcut name="greetMethod" expression="execution(* ApplicationLayerRequestData.writeData(..))"/>
        <advice name="beforeNetworkUpdate" type="before" bind-to="greetMethod"/>
        <advice name="afterNetworkUpdate" type="after" bind-to="greetMethod"/>

In aop.xml, I've defined a pointcut called greetMethod that is used to intercept the ApplicationLayerRequestData.writeData() method. The pointcut includes two advice items that correspond to two methods in the MyAspect class: beforeNetworkUpdate() and afterNetworkUpdate().

Don't worry if this seems very complicated; we just want to break into the execution of the readData() method.

Building and Running the Code

The following commands are used to compile the Java files and execute the program. The program parameters are shown as myPCIPAddress and 161. You need to replace the first of these with an IP address or DNS name that matches your own network setup. You'll also need copies of Java DMK and AspectWerkz. (See the "Resources" section at the end of this article for links.)

javac RFC1213_MIBOidTable.java
javac RequestNetworkData.java
javac ApplicationLayerRequestData.java
javac MyAspect.java

aspectwerkz -Daspectwerkz.definition.file=aop.xml ApplicationLayerRequestData myPCIPAddress 161

Running the program on my PC results in the following data:

AspectWerkz - INFO - Pre-processor org.codehaus.aspectwerkz.transform.AspectWerkzPreProcessor loaded and initialized
SyncManager::dispatchRequest: Sending getRequest to SNMP agent on myLaptopPC at port 161

[Object ID : (Syntax : String)
Value : Hardware: x86 Family 6 Model 6 Stepping 10 AT/AT COMPATIBLE - Software: Windows NT Version 4.0
Object ID : (Syntax : Integer32)
Value : 1, Object ID : (Syntax : Counter32)
Value : 653, Object ID : (Syntax : Gauge32)
Value : 10000000]
Hello World from ApplicationLayerRequestData.readData()!

Before Network Update - fasten your seatbelt!  (********----- INTERCEPTION
Object ID : (Syntax : String)
Value : Hardware: x86 Family 6 Model 6 Stepping 10 AT/AT COMPATIBLE - Software: Windows NT Version 4.0
Object ID : (Syntax : Integer32)
Value : 1
Object ID : (Syntax : Counter32)
Value : 653
Object ID : (Syntax : Gauge32)
Value : 10000000

Hello World from ApplicationLayerRequestData.writeData()!
After Network Update - we've crossed the Rubicon

The line marked INTERCEPTION indicates the point at which we've intercepted the program. At this point, we echo the configuration data as required. To achieve this goal, we would have to drop in the MyAspect class file and the aop.xml file. Then the target class must be executed again.

The use of AOP has enabled us to extract data from legacy code and even to modify its operation. This is what I mean by software plasticity.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020