The concept of reusability is of foremost importance within any Enterprise-wide IT Initiative. Its promotion is one of the principal means from which ROI is obtained, whether it is through direct re-use or indirect collateral factors such as increased logic centralization, reduced gross "architectural size" and infrastructure footprint, among others.
Although this might seem like a straightforward concept, many Enterprises have neither the governance nor standards required to truly transform reusability into reuse. Without governance and standards, all the effort put into increasing the reusability potential of a software solution is translated into sunken costs and ultimately leverage for taking traditional, tactical, and siloed solution endeavors.
This article aims to give guidance on differentiating reusability from reuse. It will recommend approaches and things to consider to ease the transition from one to the other, with aim on changing hope-driven reuse into proactive reuse.
Reusability and reuse within a single application...
One drawback of using the XP agile method in software development is its underestimation of software quality attribution. These attributes are of main indices of software architecture. In this study, a method is represented for responding to this challenge on the bases of probability theory.
Firstly, the rating matrix is structured on the bases of quality attributions architecture solutions. Each element of this matrix shows a rating for every solution, and the ratings are initialized through the analytic hierarchy process (AHP). Via quality weight implement on the above matrix, a rating vector is created. Each rating vector represents the rate of reaching those quality attributes in a rating matrix.
Because rating vectors have normal probable distribution, their elements' probable density is mostly gathered around the mean. In this study, the probable density of architecture is defined, the appropriateness of a solution in comparison to other solutions is evaluated. The response...
This article is the conclusion of an annotation to the case study from Chapter 7 in Next Generation SOA: A Concise Introduction to Service Technology & Service-Orientation. To read the first part of this article series, click here.
Page 95: "In the last week of May, Robert holds a two-day strategic planning workshop with key thought leaders from the company's IT and business operating units, including executives, managers, architects, and business analysts."
Page 102: "As RYLC begins its transformation journey by automating business processes and introducing SOA, its architects establish reference architecture."
When we have firings, we must recalibrate business and architectural policy. While layoffs will free up cash and can provide a bounce to the stock, the underlying problems will still fester. Clients, employees, and shareholders will view firing people just to cut costs as desperate. Therefore, layoffs must have solutions to fix the firm's problems. We must look at our business...