Consultant’s Analysis Report on Enterprise Systems
Information Technology Architectures
The purpose of this outline is to discuss the development of this document titled Consultant’s Analysis Report on Enterprise Systems. As the project progresses, it will discuss many different areas of the enterprise system. Basically, this will provide the basic outline from week to week before finally having enough information to deliver the finalized portion throughout each section of the document. There will be times when more research is needed in a particular field than others, but the appropriate amount of time will be spent to ensure that deliverables meet the requirements needed.
About the Company
The company, Medicare Associates of America, is a company of more than one thousand five hundred people in a call center environment who work to provide Medicare Insurance to senior citizens who have reached the age of sixty-five (65). The corporate headquarters is located in Austin, Texas and have two other sister buildings located in Logan, Utah and Nashville, Tennessee. Their database consists of more than 3,500,000 customers who use their services and receive a call volume of nearly 40,000 calls per day.
The developer has requested that some architecture requirements be listed before the process goes any further. The developer suggests that Windows XP or Windows 7 would be the ideal operating system requirement. It is also suggested that the system uses domain technology. For design, a tool to have on board would be the capability to use a virtual machine, but not be limited to just this. For security, reputable security protocols should be configured into the system. For hardware, the minimal specifications needed would include an Intel dual core processor (1.5GHZ or higher). Significant hard drive space will be needed to install the system with an uninterruptable power supply. Finally, a printer for printing reports can be optionally added as well as a USB Flash Drive to store data backups.
Client and Server distributed systems
The customer server model is crucial to circulated frameworks. It is a reaction to the restrictions exhibited by the customary centralized server customer host model, in which a solitary centralized server gives imparted information access to numerous moronic terminals. The customer server model is likewise a reaction to the neighborhood (LAN) model, in which numerous separated frameworks get to a document server that gives no handling force.
Customer server building design gives joining of information and benefits and permits customers to be segregated from innate complexities, for example, correspondence conventions. The effortlessness of the customer server structural planning, permits customers to make changes that are directed to the suitable server. These appeals are made as exchanges. Customer exchanges are frequently SQL or PL/SQL methodology and capacities that get to individual databases and administrations.
Shared model system
An alternate sort of dispersed framework is a shared model, which expects to spread the computational load over numerous customer machines to help with the workload as opposed to having the assets on a server. The ruin to this model is that middle-ware for it is still in its outset. The greater part of P2P frameworks have been close to home frameworks, for example, your home system. However there is expanding utilization of P2P systems in business. P2P systems, portrayed by dematerialized system architectures permit any of the machines on the system to house the asset, and alternate machines on the system can get to it.
The last building design considered was an appropriated item construction modeling. With this type of structural engineering in place, there is no refinement between the customer and the server. This means that every gadget gives administration to the greater part of alternate gadgets on the system. To fulfill this, the kind of middle-ware utilized is called an article appeal dealer (Sphere). This middle-ware is in charge of making sure that there is a typical dialect among the distinctive gadgets. This model has a few preferences to consider on the off chance that you want to become faster and more efficient. It is extremely adaptable so you can include assets as required, and you can design it to be alterable, which permits you to relocate protests over the system effortlessly.
Concerning the picked system, I chose a client/ server construction modeling in light of the fact that it being used by Medicare Associates of America upon their system. It permits them to be versatile, which encourages a positive outlook when we need to rearrange the room. Now that assets are set up, they don’t need to move their machines with them. Therefore the additional work of planning a P2P or a dispersed item construction modeling would be difficult to get regard without critical legitimization.
The client server model will suit the needs of my system because it will allow the resources to be on the Virtual PCs where each client can access the appropriate tables and manage the database information from their client. Furthermore, this allows Management to have a current common operating picture of all of the Virtual PCs that we use. By having a common operating system, management can make timely and accurate decisions on where to focus the call volume and resources at their disposal or if they need to request assistance from our Loss Mitigation or operation support teams.
The number of personnel that should be required is greater or equal to a minimum of one thousand five hundred users. Authenticated users have a time limit for access typically four months. Depending on the role of the user, there may be different security access that will either be more restricted or less secure. A supervisor ranking and higher will always have open access to the system to ensure that the rights of other users are granted or denied as needed. (Coulouris, 2012)
Training Requirements for Staff
For System Software and Hardware Installation:
- 4 Week Training Provided (Required): Must have Bachelor’s Degree in IT Field or 8 years of job related experience.
System maintenance and modification:
- 6 Week Training Program (Required): Associate’s Degree preferred or 4 years of job related experience.
- Training Required: Personnel must have a Bachelor’s degree in an Information Technology or 8 years of job related experience.
|Enterprise ApprovalWeek 1||Enterprise system concepts have been approved by management and the project is authorized to proceed to detailed requirements definition.|
|Requirements ReviewWeek 1||Requirements specifications are complete, correct, approved and suitable for input to design.|
|Preliminary Design ReviewWeek 1 – Week 2||The enterprise system design satisfies all enterprise system requirements, is approved and is suitable for input into the detailed design process.|
|Critical Design ReviewWeek 2||Detailed designs fully implement the enterprise system architecture, are approved and are suitable for input into the enterprise system.|
|Test Plan ReviewWeek 2 (End)||Test plans are adequate for the testing of all enterprise system features, are approved and are suitable for input to the development of test cases and test procedures.|
|Test Readiness Review Week 3||Developed and unit tested software has been passed by the test team and is suitable for input into integration testing.|
|System Test ReviewWeek 3 – Week 4||The enterprise system has passed system testing and is suitable for input into acceptance testing.|
|Operational Readiness ReviewWeek 4||The enterprise system has passed acceptance testing and is suitable for deployment in its target production environment.|
|Product OperationalWeek 5||The enterprise system is in use in its target operational environment.|
Final Analysis and Recommendations
Coulouris, G. (2012). Distributed Systems: Concepts and Design, Fifth Edition. Pearson Custom Publishing.
Teach-ICT (n.d) 3.Why Use a Distributed Database? Retrieved on 4-12-15 from http://www.teach-ict.com/as_a2_ict_new/ocr/A2_G063/334_applications_ict/distributed_database/miniweb/pg3.htm
Burns, A (January 2015) Securing Health Information. Retrieved on 4-19-15 from http://computingnow.computer.org/cms/Computer.org/ComputingNow/issues/2015/04/mit2015010023.pdf
Emmerich, W (1997) Distributed System Principles. Retrieved on 4-19-15 from http://www0.cs.ucl.ac.uk/staff/ucacwxe/lectures/ds98-99/dsee3.pdf
Chambers and Associates (2015) Milestone. Retrieved on 4-26-15 from http://www.chambers.com.au/glossary/milestone.php
EventHelix (2015) Resource Allocation Patterns. Distributed Resource Allocation. Retrieved on 4-27-15 from http://www.eventhelix.com/realtimemantra/patterns/resourceallocationpatterns.htm#Distributed Resource Allocation