Since its foundation, HSG has been a leader in Business Rule Management Systems Training and Consulting services by way of the Blaze Advisor Rule Engine.  Over the years we have provided such services to many of the worlds largest corporations and government institutions whose respective backgrounds include credit card processing, banking, insurance, health and medicine and more, much more.  Such training and consulting services have included:

Create a wrapper object model in either Java, .NET or XML

Identify and catalog business rules

Develop a rule architecture within Blaze Advisor that isolates rule repositories as they relate to functionality and corporate policies

Configure, develop and implement a variety of interfaces to the rule engine from disparate systems ranging from mainframe applications written in Cobol to UNIX/Windows applications using Enterprise Java Beans, Windows Services, Web Services, Fat Clients, Java Messaging Services and Web Applications.

Review and update code to boost efficiency either by way of

    Removing functions calls within conditional statements

    Ensuring that database calls are essential or can be rearchitected in some other manner

    Employing the rete algorithm where necessary

    Paring down extensively large class models

    Deploying such appliations in multi-threaded systems

·         ...

Call us if you:

    are in need of Blaze Advisor Expertise
    are developing SMEs in Blaze
    want to speak directly with an expert (no placement agencies)
    want an affordable alternative to FICO
    want to work with an industry leader

There has been and continues to be a plethora of observational studies by different researchers in the publishing industry focused on how e-books have affected hard-copy book sales. Evidence from these studies has indicated that there is a significant and monumental shift away from hard-copy books to e-books.[1]These findings precipitate fears that hard-copy books might become more expensive in the near future as they begin to be less available.  This scenario could escalate to the point where only collectors of hard-copy books are willing to pay the high price for ownership.

The founder of Amazon, Jeff Bezos, made a statement in July 2010 that sales of digital books had significantly outstripped U.S. sales of hard-copy. He claimed that Amazon had sold 143 digital books for its e-reader, the Kindle, for every 100 hard-back books over the past three months. The pace of this change was unprecedented;  Amazon said that in the four weeks of June 2010, the rate of sales had reached 180 e-books for every 100 hard-backs sold. Bezos said sales of the Kindle and e-books had reached a "tipping point", with five authors including Steig Larsson, the writer of Girl with a Dragon Tattoo, and Stephenie Meyer, who penned the Twilight series, each selling more than 500,000 digital books.[2] Earlier in July 2010, Hachette said that James Patterson had sold 1.1m e-books to date.

According to a report made by Publishers Weekly, for the first quarter of 2011, e-book sales were up 159.8%; netting sales of $233.1 million. Although adult hard-cover and mass market paperback hard-copies had continued to sell, posting gains in March, all the print segments had declined for the first quarter with the nine mass market houses that report sales. Their findings revealed a 23.4% sales decline, and that children’s paper-back publishers had also declined by 24.1%.[3] E-book sales easily out-distanced mass market paperback sales in the first quarter of 2011 with mass market sales of hard-copy books falling to $123.3 million compared to e-books’ $233.1 million in sales.

According to .net sales report by the March Association of American Publishers (AAP) which collected data and statistics from 1,189 publishers, the adult e-Book sales were $282.3 million in comparison to adult hard-cover book sales which counted $229.6 million during the first quarter of 2012. During the same period in 2011, eBooks revenues were $220.4 million.[4] These reports indicate a disconcerting diminishing demand for hard-copy books.

It is hard not to wonder how current technology would have altered the events surrounding the tragic death of John F. Kennedy. On the afternoon of November 22, 1963, shots rang out in Dallas, TX, taking the life of JFK, one of the most beloved Americans. Given the same circumstances today, surely the advances in IT alone, would have drastically changed the outcome of that horrible day. Would the government have recognized that there was a viable threat looming over JFK? Would local and government agencies have been more prepared for a possible assassination attempt? Would the assortment of everyday communication devices assisted in the prevention of the assassination, not to mention, provided greater resources into the investigation? With all that the IT world has to offer today, how would it have altered the JFK tragedy?

As many conspiracy theories have rocked the foundation of the official story presented by government agencies, realization of the expansive nature of technology provides equal consideration as to how the event would have been changed had this technology been available during the time of the shooting. There were T.V. cameras, home 8mm recorders, even single shot-hand held cameras snapping away as the car caravan approached. Yet, there remains little documentation of the shooting and even less information pertaining to the precautions taken by officials prior to JFK's arrival. Theorists consider these possibilities along with how the world would have turned out had the great John F. Kennedynever been assassinated on that day.

Millions of people experienced the frustration and failures of the Obamacare website when it first launched. Because the code for the back end is not open source, the exact technicalities of the initial failings are tricky to determine. Many curious programmers and web designers have had time to examine the open source coding on the front end, however, leading to reasonable conclusions about the nature of the overall difficulties.

Lack of End to End Collaboration
The website was developed with multiple contractors for the front-end and back-end functions. The site also needed to be integrated with insurance companies, IRS servers, Homeland Security servers, and the Department of Veterans Affairs, all of whom had their own legacy systems. The large number of parties involved and the complex nature of the various components naturally complicated the testing and integration of each portion of the project.

The errors displayed, and occasionally the lack thereof, indicated an absence of coordination between the parties developing the separate components. A failed sign up attempt, for instance, often resulted in a page that displayed the header but had no content or failure message. A look at end user requests revealed that the database was unavailable. Clearly, the coding for the front end did not include errors for failures on the back end.

Bloat and the Abundance of Minor Issues
Obviously, numerous bugs were also an issue. The system required users to create passwords that included numbers, for example, but failed to disclose that on the form and in subsequent failure messages, leaving users baffled. In another issue, one of the pages intended to ask users to please wait or call instead, but the message and the phone information were accidentally commented out in the code.

While the front-end design has been cleared of blame for the most serious failures, bloat in the code did contribute to the early difficulties users experienced. The site design was heavy with Javascript and CSS files, and it was peppered with small coding errors that became particularly troublesome when users faced bottlenecks in traffic. Frequent typos throughout the code proved to be an additional embarrassment and were another indication of a troubled development process.

NoSQL Database
The NoSQL database is intended to allow for scalability and flexibility in the architecture of projects that will use it. This made NoSQL a logical choice for the health insurance exchange website. The newness of the technology, however, means personnel with expertise can be elusive. Database-related missteps were more likely the result of a lack of experienced administrators than with the technology itself. The choice of the NoSQL database was thus another complication in the development, but did not itself cause the failures.

Another factor of consequence is that the website was built with both agile and waterfall methodology elements. With agile methods for the front end and the waterfall methodology for the back end, streamlining was naturally going to suffer further difficulties. The disparate contractors, varied methods of software development, and an unrealistically short project time line all contributed to the coding failures of the website.