Home > Articles > Programming > Java

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

This chapter is from the book

Within organizations, there will always be elements related to software development that will remain constant, regardless of the technology and programming languages employed to construct the information systems. Being able to recognize and fine-tune these elements, so they can be applied toward software development efforts, can provide the following long-term benefits:

  • Projects can leverage proven best practices.

  • Projects can be delivered with a greater degree of confidence, reducing risk and costs.

  • Risks involved in a project can be mitigated by employing accepted shared practices.

  • Technical competencies and skills can be developed through practicing consistent approaches.

However, most organizations fail to recognize these benefits. It is essential for organizations to possess internal communication mechanisms that can easily cross-fertilize information and promote best and worst practices across the spectrum of active IT projects. Two organizational frameworks that have proved invaluable in the support for enterprise J2EE software development efforts are Communities of Practices and Technical Centers of Excellence for J2EE Architecture.

Communities of Practice

Communities of Practice is a term used to define a forum of people, who can be extended across an organization, who share a common interest. Communities can exist for multiple topic areas, just like public user groups; the only difference being that their existence must contribute in some manner to the success of the organization.

In most organizations, J2EE solutions need to swiftly proceed from concept to prototype to production, and continue to evolve even after they are deployed. As a result, Communities of Practice need to be involved in developing the most practical, flexible, and efficient approaches for the J2EE software development efforts, especially in the areas that require business analysis, such as project inception and requirements gathering. Communities of Practice will derive best practices and techniques for assisting J2EE software development projects in a manner that will be supported and governed by the culture of an organization.

NOTE

In most cases, the best practical approach is the most culturally supported approach.

Communities can be technical and non-technical in nature. What is important is that they understand how they can contribute to the success of J2EE software solutions.

Non-Technical (End-User) Communities

This community represents the advocates for the end users within an organization, and primarily supports the Requirements and Analysis phases of a J2EE software development methodology. End users, just by the nature of their roles in an organization, do not typically have insight to how information systems are developed. Hence, they will not understand the activities or processes they will be involved in, or the implications of documenting or changing business processes.

This aspect of their interactions with IT projects always consumes their concentration over providing valuable information and knowledge to the business analysts. However, they are the primary information resources for nearly all IT projects.

Business analysts need to apply an investment in educating end-user communities on the Requirements and Analysis phases to ensure they understand the informational value they posses and how they can effectively articulate that information.

Such communities require sponsorship and need to be championed by a well- recognized and respected member of the end-user community. A strong marketing effort is also required to promote its existence, since there is no point in building a Community of Practice if no one knows it exists. It is extremely important for them to gain exposure and be utilized by the organization.

Technical Communities

Technical communities are more prevalent than the non-technical end-user communities within an organization, and are usually composed of representatives from an organization's technical workforce—technical architects, software developers, and testers.

These communities generally exist for technology platforms, development languages, and their respective integrated development environments. Hence, technical communities have established themselves as developing the suite of technology criteria for the deployment of successful information management systems within an organization.

Examples of the concentration of such communities include

  • Programming languages (Java, C++, and Visual Basic)

  • Databases (Oracle, Sybase, DB2, and SQL Server)

  • Technical vendors (Oracle, BEA, Microsoft, and IBM)

There should always be an entity that sets the technical directions and standards within the organization, but the technical community should not be that entity. The mission of technical communities is to develop how those technologies can best be applied or practiced, not by theory, white papers, or technical paraphernalia, but through actual hands-on experience.

By creating and sponsoring technical communities, organizations will over time develop consistent approaches to software development that will possess a high degree of quality and success.

Technical Centers of Excellence—The J2EE Architecture Group

A Center of Excellence is a formalized group of people who are focused on a specific technology or software platform which their organization utilizes in its software development efforts. Their roles are to be experts, practitioners, and mentors on the technology domains they represent. This group must also wear the business hat to continually monitor business drivers that affect them, as well as the areas within an organization that could potentially be affected by the technology they represent.

If your organization is going to transition its software development platform to one that employs the J2EE architecture, there will be an expectation, after the completion of the first few J2EE projects, that subsequent J2EE project efforts become more efficient through the reduction of time, cost, and risk. With major updates occurring to the J2EE architecture almost every six months, a Center of Excellence is the means to realize those goals.

The J2EE Architecture team must collectively define how they are going to publish their information and knowledge to the organization, to ensure that the J2EE value proposition is comprehendible. Hence, they will need to represent technical ideas and the business implications of J2EE solutions, without needing to explain the intricate underlying technology. Business leaders view technical architecture as a winning gamble—an investment today with the optimism it will reap huge benefits in the future.

NOTE

The J2EE Architecture team must learn to talk in relation to user implications, as all technical choices should ultimately be linked back to business strategies and drivers.

The work that the J2EE Architecture team conducts should be in a level of detail that can be achieved within a set timeframe, typically no longer than the duration of the next release of the J2EE specifications. The longer they take to establish compliance on how J2EE solutions should be implemented, the less productive their mission and existence becomes. The litmus test for how successful an organization is with a J2EE Architecture team can easily be measured by the number of projects that adopt J2EE as the platform for the solution and have a successful deployment.

J2EE Architectural Guidance to IT Projects

The biggest payoff of having a J2EE Center of Excellence within your organization is the ability for their members to get involved with J2EE projects right from the beginning, and ensure that a J2EE solution is valid and best suited for the solution domain. At a minimum, it should provide the appropriate technology guidance.

However, the biggest mistake that IT projects make in selecting a platform for their solution architecture is they see both the Requirements and Analysis phases of a software development lifecycle as the building blocks for producing the overall design of the system.

In reality, the role of the Requirements phase is to identify the functionality of the system, not how the functionality will be implemented. The Analysis phase, on the other hand, provides essential information contributing toward an understanding of the solution domain, and not what the solution system will look like—that is the role of the Design phase.

It is also important to note that an IT solution's architecture should not be confused with its design. The focus of the architecture is on how the system will be deployed, and not its granular implementation details. The architecture of a system should capture the elements of design, which provide a clear vision and guidance for the overall design of the system.

The J2EE Architecture Center of Excellence should ensure that when they get involved in projects, the due diligence for the technology solution does not take a J2EE bias. If J2EE is selected as the appropriate platform, they should provide an architectural blueprint for the following:

  • How the J2EE services can be implemented

  • How existing organizational J2EE business components, such as EJBs, JavaServer Pages, and Servlets, can be reused

  • How the system can evolve and scale over time, resisting any stress placed upon it by the business

  • How and who to hire for project augmentation

  • How newly created J2EE business components can be harvested into a central component library

Another area where the J2EE Center of Excellence will be very valuable is in systems integration. J2EE is a relatively new technology platform for most organizations. Although much of an organization's data will have been collected by existing applications, the value will not be in the replacement of these existing systems, but in how they can be interfaced into new J2EE solutions, hence commoditizing their value.

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