Home > Articles > Software Development & Management

  • Print
  • + Share This
This chapter is from the book

1.4 Using Frameworks

When using a framework it is important to first ensure you get a framework that will give you the most reuse within your intended usage objectives. In other words, you want a framework that is well aligned with your needs. You don't want to spend all your time rewriting core elements of the framework—not only will you be getting very little value from the framework but you will also likely introduce difficult-to-debug errors because you don't understand all of the subtleties involved in the interaction between framework parts. In our planet example, if most of your planets have rings or moons, you probably don't want to use the framework we suggested in the example. As always, it is never that easy. Depending on how much effort you put into the development process, you might find a framework for creating arbitrary gravitational bodies that interact (planets, moons, comets, and so on) or discover a novel way to use our example framework to create two planets, one big and one small, and then place the smaller planet into orbit around the bigger one—voila, you now have a planet with a moon.

When looking for a framework to use, you have to realize that frameworks lie between two extremes: class libraries and applications. Although frameworks can be built on class libraries, they supply more than the class library's independent pieces, such as decimal support, time support, or a group of reusable collections. Frameworks that try to cover too much can become class libraries. And, even worse, these overextended frameworks can often create linkages between elements that make the frameworks difficult to use even as class libraries. On the other side of frameworks are applications. This is where frameworks that are too focused (that is, don't have enough extensibility) end up. This is not to say that any one of these solutions is better than another, only that you should pick the right one for your particular problem.

When should you use a framework? When you see the need to create a number of applications or a highly customizable application (because of the broad customer needs) in a particular domain (or domains) and you see that there is a common core of processes and functions, use a framework. The framework normally embodies the part you hate to reinvent every time you write that application, the part you hate to test every time, the part you would rather pay for once and never have to pay for again. Depending on the size and scope of this core, you'll use either a class library or a framework.

Once you've decided to use a framework and have found a suitable one, you need to integrate the use of the framework into your development process. Frameworks are more than pieces that can be reused when implementing your application. Depending on the scope of the framework, it may establish an underlying architecture to which you need to adhere.

A framework also provides a design for a solution to a domain process—such as a business process. You want to use these processes as soon as possible, taking advantage of the framework's work by reusing it. If you wait until you are implementing the code, you may be able to take advantage of certain pieces, but you won't get the greatest reuse—unless you come up with the same design, which is extremely unlikely. The best way to use a framework is to reuse it as soon as possible in your development process.

If you don't have a development process, it will be difficult if not impossible to use a framework. Our experience is that no matter what type of software you are developing, following some type of process, like the Unified Software Development Process [Jacobson 99] or the Extreme Programming (XP) process [Beck 00], greatly increases a project's chance for success.

The most effective way to use a framework is to add mapping steps to each step in your development process. This mapping involves stopping and taking a look at what the framework provides. If you are developing requirements, look for matching requirements. If you are designing your application, align your design with framework design elements. The key is that you must explicitly incorporate and enforce the mapping process—it is much too easy to skip the mapping step, especially if this is the first time using a framework. The most benefit is gained from a framework if you can map early (see the Map Early, Map Often pattern, Section 9.2). If you map at the requirements level, not only will you be able to reuse the use cases but also the analysis, design, implementation, and testing will have already been done for you. For example, if you are building currency conversion support into your application, your requirements are likely to include the abilities to convert currencies, to have the exchange rate vary daily, and to use different exchange rates for hard currency versus traveler's checks. In the IBM SanFrancisco framework [Monday 99], these requirements, stated more generically, are directly supported by the framework: establishing exchange rates via date or period and supporting exchange rate tables for whatever the user wants to define. We can map from those requirements to the framework requirements and start the reuse at this highest level.

While mapping is key to using a framework, it is also the bane of framework use. You need to know what there is to map to (see the Just Learn It pattern, Section 9.1). You are trying to deliver a product, so you don't have infinite time for the mapping stages. You map to what you know about and what you've discovered so far. How much time can you spend learning and discovering? You should spend as much time as you can up front—before you start using the framework. There's probably a core you have to learn (which the framework documentation should identify); after that you can grow your knowledge over time. Even if you don't understand the entire framework up front and you miss something you could have reused, you will still benefit from the things you did reuse.

You can also use a framework as an example. To support mapping, a framework should provide end-to-end documentation and development artifacts. This level of documentation, if done correctly, gives you, in essence, an in-depth case study of one way to approach a domain through all phases of development, including the patterns used as the framework was developed. Often these patterns can be used completely independently of the framework, especially if they have been truly captured as patterns.

  • + 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.

Overview


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.

Surveys

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.

Newsletters

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.

Security


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

Children


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

Marketing


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.

Choice/Opt-out


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.

Links


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