Strategic advice to leverage new technologies
Technology is at the heart of nearly every enterprise, enabling new business models and strategies, and serving as the catalyst to industry convergence. Leveraging the right technology can improve business outcomes, providing intelligence and insights that help you make more informed and accurate decisions. From finding patterns in data through data science, to curating relevant insights with data analytics, to the predictive abilities and innumerable applications of AI, to solving challenging business problems with ML, NLP, and knowledge graphs, technology has brought decision-making to a more intelligent level. Keep pace with the technology trends, opportunities, applications, and real-world use cases that will move your organization closer to its transformation and business goals.
Insight
It is clear to most people by now that no one methodology will fit every software project. What is not clear is where to go next. If concrete advice can't be given across projects, how are we to find meaningful methodological advice for our projects?
Executive Summary
Beyond Supply Chain Management: Supply Chain Synthesis and Technology
Analysts predict that business-to-business (B2B) sales over the Internet will reach US $500 billion by early next year and $2 trillion or more by 2004. In contrast, business-to-consumer (B2C) e-commerce sales are not expected to reach $400 billion until 2003. Business analysts believe that B2B will cut costs, reinvent supply chains, improve communications, and increase customer satisfaction.
In Sebastian Junger's The Perfect Storm, a fishing boat out of Gloucester, Massachusetts, USA, encounters a storm -- not just any storm, but "the perfect storm" -- and ends up meeting a tragic end. This "perfect storm" was the result of a combination of various meteorological phenomena. Together, these phenomena made it impossible for the fishermen to do their job and bring swordfish back to port.
In this Executive Update, we'll take a look at the latest data from Cutter Consortium's ongoing survey on components/distributed computing and their relationship to component-based application servers. (We used the term component-based application servers on the survey to distinguish it from other application server uses, ranging from hardware servers to HTTP or Web servers.)
Article
Measuring the Software Process
The norm for software development today is to use object-oriented (OO) and component-based technologies -- such as Enterprise JavaBeans (EJB), Java, and Microsoft's C# -- in combination with relational database technology such as DB2 or Oracle 8i.
As Dorothy so aptly pointed out in The Wizard of Oz, "We're not in Kansas anymore, Toto."
Two common metrics for software size are source lines of code and function points. But by no means are these the only units of size; others include objects, modules, programs, components, and frames. Obviously there are scaling relationships between these abstractions. How can you translate one from the other to understand the proportional aspects of one metric to the next? If you knew the size of a major application in source lines of code, is there a way to equate the size using a metric like function points for people who speak that language?