Computer management system
Computer management is the process of managing, monitoring and optimizing a computer system for performance, availability, security and/or any base operational requirement.
It is broad term that includes manual and automated administrative processes in the operations of a computer.
Computer management is also known as PC management or desktop management.
Understanding User Resistance and Acceptance during the Implementation of an Order Management System: A Case Study Using the Equity Implementation Model
CaseStudy
Successful implementation of new technologies and systems is vital for sustaining and enhancing the productivity and the competitive position of an organization. However, many implementation efforts fail due to resistance or non-acceptance of new systems by users. This paper presents the details of the implementation of an order management system in a custom furnishing business. Details of changes brought about by the new system in the work environment of users and the resulting user acceptance and resistance behaviors are examined in the light of the user evaluation process proposed by the equity implementation model (EIM). The paper concludes that the findings of the case study support EIM, which provides an understanding of both resistance and acceptance behaviors. EIM also provides an understanding of users’ initial reactions to the implementation as well as their post implementation responses. Such insights can be helpful in developing better strategies for implementing systems and dealing with user resistance.
Functionalities
What is Coupling??
Coupling is the act of joining two things together. In software development, coupling refers to the degree to which software components are dependent upon each other. For instance, in a tightly-coupled architecture, each component and its associated components must be present in order for code to be executed or compiled. In a loosely-coupled architecture, components can remain autonomous and allow middleware software to manage communication between them. In a decoupled architecture, the components can operate completely separately and independently.
In computer science, coupling is considered to be the degree to which each program module relies on other modules, and is also the term used to describe connecting two or more systems. Coupling is broken down into loose coupling, tight coupling, and decoupled. Coupling is also used to describe software as well as systems. Also called dependency.
Coupling between two Functionalities:
In the software engineering coupling is the more important concept that used in not only software field but also used in the personal and daily life. Coupling means interdependence between two modules, people, classes, and component.
High coupling means more and more dependence between two classes and modules. Low coupling means high independence and low dependence. In the above given case study firstly we will define the major functionalities of an computer management system(CMS) where, implemented of the system using new technology using some proper and successful way to integration the modules in an computer management system organization. Lets now we start understand the coupling between two functionalities of an computer management system organization.
Coupling between User Acceptance vs. Resistance to change:
Lets given two functionality derived from the above case study. Suppose that given two functions is the department, component and modules of an computer management system organization, and now we are interested about coupling and interdependent between two functions or modules. For example, when we implement the one computer management system the most important concept and term is user acceptance, and now we are interested about to know how user acceptance modules, classes and department dependent Resistance to change modules.
In the bad design and tight coupling if we change the requirement after rejection of user acceptance, this modules more dependent on the control management system, that means the change in the users acceptance, depend on the change requirement so strongly, that the control management is so complex and very difficult to management these requirement according to the users requirement.
What is cohesion??
In computer programming, cohesion refers to the degree to which the elements inside a module belong together. In one sense, it is a measure of the strength of relationship between the methods and data of a class and some unifying purpose or concept served by that class. In another sense, it is a measure of the strength of relationship between the class’s methods and data themselves.
Cohesion is an ordinal type of measurement and is usually described as “high cohesion” or “low cohesion”. Modules with high cohesion tend to be preferable, because high cohesion is associated with several desirable traits of software including robustness, reliability, reusability, and understandability. In contrast, low cohesion is associated with undesirable traits such as being difficult to maintain, test, reuse, or even understand.
Cohesion is often contrasted with coupling, a different concept. High cohesion often correlates with loose coupling, and vice versa. The software metrics of coupling and cohesion were invented by Larry Constantine in the late 1960s as part of Structured Design, based on characteristics of “good” programming practices that reduced maintenance and modification costs. Structured Design, cohesion and coupling were published in the article Stevens, Myers & Constantine (1974) and the book Yourdon & Constantine (1979); the latter two subsequently became standard terms in software engineering.
Cohesion Between two Functionalities:
In the given case study, the first portion of assignment we should discuss the case study, define the Functionality of the case study and discuss about coupling with two functionality in the high coupling or a bad design.
Now we are interested to know about that cohesion between one or more functionality between modules, classes and organization department. Cohesion concept is totally different against the coupling and is the main and very important concept in the software engineering field, cohesion means in very simple words is that the degree which all elements of the modules, class and elements work together as a fictional unit and give an excepted outcome.
The main and important concept is that high cohesion is good and low cohesion is bad, If we give the examples on high cohesion, good design and more efficient output is that integration.
Integration is the main component and major life cycle parts of software development life cycles.
Before implementation, integration is important component of SDLC, where a lot of modules in the integration parts, now at this steps where all modules depends with one another and working as an unit.
0 comments: