IT Architectural Considerations Case Study Example | Topics and Well Written Essays - 750 words

IT Architectural Considerations - Case Study ExampleIT Architectural Considerations a. IT characteristics i. Accessibility Accessibility of the centralized gross gross sales and product organization impart be highly restrictive to specific people who will use the schema to play specific roles or downstairstake specific purposes. On the whole, the sales IT manager shall be the head of the organization and so he shall have full entre to the system. All sales departmental heads shall also have access code to the system but they shall not have access to manipulate data put into the system in any way. This is because figures data are very significant for determining the progress of the lodge and need not be tampered with. Finally, accountants and auditors shall have access to the data in the system but shall not have access to operate the system in any way. ii. Availability Since sales, payment and product registration go on in the company on regular basis, the system shall be available for use on regular basis by those who are permitted to have access to it. As often and regularly as sales are made in any department or any branch of the company, payment input shall be made into the system so that the system will have to record the payment and undertake a comprehensive summation at the head office of the sales. iii. Portability One of the most outstanding advantages of the recent technology for the sales and products department is its portability. This is because the framework of the system has been designed to centralize all accounts records of the company. This means that there will not be little fragments of account data to deal with therefore making the system very portable and handy. One aspect of the system that makes it even more portable is the fact that the system will not be accessible to a lot more people. iv. Reliability The system has been designed on the bases of reliability and accuracy. For instance data entered into the sales and payment system cannot be manipulated in any way by any body expect by the senior sales IT officer. This means that the company shall have reliable sales and payment records. The situation whereby some people are likely to embezzle funds will thus be catered for under the system. The company shall there be expectant of financial growth henceforth b. security aspects as they relate to the technology solution i. credential & Authorization Authentication and authorization are important components of any IT system especially when it deals with accounts figures. Wells (1996) explains that authentication tools provide the ability to determine the identity of a party to an interaction and to ensure that a message came from who it claims to have come from. Based on this background, all operators of sales machines have been given registered for a special verification ferment that makes use of thumbprint. Users therefore have to register their thumbprints into the sales machines before they can ac cess it. Without this verification, data recorded into the sales machine will not be recorded by the new IT system. ii. Prevention & Resistance Any technology system that does not focus on prevention and resistance lacks a honorable security basis. For this reason, no matter the authentication and authorization features incorporated into the system, the way must be paved for any security breaches to be prevented all together (Purpura,2002). For this reason, a prevention