What is an enterprise system is and how can this design support testing processes?
An enterprise system is a compilation of separate but related modulated wares that are integrated with a single cohesive database, with multiple interfaces, to achieve the business purpose of an organization across multiple departments, in an effort to consolidate separate legacy systems and improve overall efficiencies. Enterprise systems are complex by nature but with the right planning and proper execution success can be reached and the benefits to an organization can be immense.
The enterprise system paradigm supports testing processes by offering a wide range of potential test cases for every aspect of an organization, effectively enabling developers and systems engineers to better the system as a whole for the entire enterprise in specific ways. The concept behind enterprise systems is integration through modulation, empowering organizations to perform any function required and change the system on demand and/or based on local need. For example, an accounting module that is functionally sound for US locations will calculate salaries differently than what is required for a European location. Currencies are different, taxes are different, pay scales are different, etc. As such, modified/localized versions of modules allow the organization to deploy localized versions of the accounting module, while still integrating data to the central database. This allows executives from any locale to gain insight into labor trends and costs across the enterprise to make more intelligent decisions on the direction of the company on a global scale. Test cases can be created to compare modules and sub-modules to see which are transferable to other locations of the organizations, and then run in tandem to determine functionality. Since enterprise systems are sold by the module, then allow for some customization on the customers part, the accounting module in general should be transferable to any locale, with some minor modifications to allow for local laws and practices, which saves the company money overall. It is far easier and less expensive to modify an existing module to allow for proper payroll calculations based on local laws, as an example, than it is to have the developer write a completely new module for each location that requires it and then figure out how to integrate that data without having to add too much to the already complex central database. This testing model applies to any aspect of an enterprise system: inventory, human resources, manufacturing, etc, but with different data sets. Having a global infrastructure also allows administrators to tap into collective resources to evaluate and gain feedback on any proposed update/upgrade. Sometimes, asking workers simple questions can eliminate the need for many costly test cases, which when performed in excess can actually result in project failure due to never really gaining momentum and being stuck in procedure or policy, as it were. Sometimes just listening to the users can be an administrators best test case, as long as they are willing to hear what is said and then make sure that the executives buy into the concept.
Have a question? Have a comment? Comment below, let's start a dialog.
~Geek
Integrating Informations Systems Knowledge within an Organization
The first discussion question for my last class went something like this:
"What is the best approach to integrating IS knowledge domain-specific and professional core competency needs with your organization? Why is this approach better than others?"
After reading my fellow classmates responses, and pondering my own perspectives on the question, here is what I came up with as my response:
The theme I see in my classmates responses mirror my own opinions on this topic - the best approach is to evaluate the IS resource to determine its usefulness, or kind of knowledge, and apply the resource based on the needs and goals of the organization. As information systems have evolved into the complex and interconnected platforms of the modern era, more domain specific competencies have emerged, resulting in a need for more specialization from IT professionals. My families business has been scaled down over the past two years due to the economic downturn however we continue to thrive because of my unique understanding of information systems and how they can help us be more efficient with less knowledge workers for our type of business. The reason why we remain successful is because of information systems. Having grown up watching my father and grandfather build the business to what it was after over 60 years (dozens of workers, four locations around the globe, representing more than 100 major brand names for all aspects of construction and hospitality supply), being a part of the downsize effort was sobering. Before the downsize, our core competencies were spread among departments, much like found at any corporation, based on the level of skill and domain specific knowledge. Since I am the systems engineer it is my responsibility to connect the dissimilar and unconnected workers to each other Understanding the core competencies for each position, and its importance to the whole of the company, coupled with my IT experience and system prowess, I was able to create a cohesive environment of wares and solutions that not only integrated all domain-specific workers to the larger whole, but also helped refine our core competencies to what they have evolved into today. A mostly interchangeable workforce that can be effective and efficient across all knowledge bases. As another classmate noted, it would be unconventional to have an IT tech move into the accounting role especially within a larger organization, but in small businesses workers need to have a mix of knowledge because more is required by less. Integrating information systems is the only way to accomplish this with any level of organization and efficiency. Without properly planned and implemented information systems, and skilled workers to use them, most companies would fail before they get going because they could not remain competitive in the market. Staying "lean and mean" in modern business is the only way most companies are still around after the harsh economic downturn and the low cost of technology has enabled them to stay open, as well as pave the way for start-ups to reach a profitable state faster than ever. The trick is to plan, plan, and plan. Going into a information system migration/integration takes careful planning, testing, redesigning, retesting, and finally implementation and maintenance. Trying to integrate the same without a plan almost always results in catastrophic failures.
...damn I love this shit...
Do you have any thoughts on the subject? Or any questions on my contribution? Post a comment, let's discuss.
~Geek
