Nice Place

  A distribution of Computers may serve as a grid for a group or Cluster of Computer Applications. In the Cluster of Computer Applications the Applications are similar in many ways.  The Applications forming the Applications Cluster are distributed across Computers located at different locations. These locations are specified. We cannot talk about any location. Actually, the Cluster of Applications is supported by an arrangement of Computers. This arrangement of Computers is systematized using Distributed Architecture. Applications are scaled or measured. Such measurement is performed to know if an Application can become a  member of a group.  Applications that are measured or scaled to be similar are grouped. The measurement results from careful observations. Statistical analysis is part of such recording of observations.  A huge size of data resulting from statistical analysis of Applications is very attentively studied. The results of such studies unfold many...

Software is a sensitive creation. It is valuable for us. So, we make it secure and protect it. Software security means software protection against unwanted changes. Software carries a risk of being harmed. There is a danger that one may interfere with normal software functioning. Thus, Software may be forced to behave improperly. Normal Software behaviour can change. Such change can occur if unauthorized access to Software is made.  In other words, Software can be affected if someone without permission can have access. If access to Software is without permission, it means there is no approval for such access. A step towards Software Security is to restrict access to  Software. We can say that we can permit access in a controlled manner. Permission is granted to authentic users of the Software. Users who are not authentic are not granted access to the Software. Checking users for Security is called authentication. It is really a verification process. Users are authenticated bef...

The Component Model displays excellent scalability. The scale used in designing the Component Model is highly inclusive and real world oriented. The little details  of the Model are properly and carefully attended. It is again and again ensured that essential working elements are clearly and specifically represented. The Model is based on technologies that makes it easy to realize a trouble free arrangement. This arrangement makes a trouble free design possible. The technologies used are armed with utilities that are easier to translate into a Model. The small details are well matched and give the best. A helpful and friendly Model is the result when accuracy is observed. Measurements have to be perfect. A value product is in the view. Performance follows because the Component Model has its focus on a standardised scale. Resultant transparency really helps,  we must say. The choice of scale used is based on the priorities.  A scale that results in a clear  cut  ...

Software Components seated at different locations are said to be Distributed Components. These Components are arranged in such a way so as to enable communication. In other words, the Distributed arrangement helps communication among Components.    The arrangement that allows Component based communication is based on principled distribution. A Component requiring to communicate sets itself into action. It extends itself. It makes itself effective outside the Component boundary line.  A Component that has extending abilities can be distributed. If a Component is unable to cause effect outside the Component boundary line, it cannot be distributed.  It's true that ordinary Components do not have communication rights. Such Components do not follow philosophy related to distribution. So, these Components are denied communication rights. To sum up, an ordinary Component cannot communicate.  A Component in a distribution starts the linking process. Requirement for comm...

The Component Model has persistence. Persistence property means that the Component Model can survive in difficult conditions.In other words, the Model constantly maintains the working state. The Model is well tested. It is closely monitored. It meets standard requirements. Modellers make sure that the Model works properly. Persistence property gives information about the toughness of the Component Model. The toughness is determined by good response in difficult conditions. The response of a persistent Component is suitable in challenging times.  Persistence means the Component is tireless, fault- tolerant,and secure. Persistence of the Component Model bears justification. The Component Model meets the standards of Component based modelling. Meeting such standards, by extension, means the Model stands for toughness.  Persistence is decided by: Response Time: A Model should be quickly captured by the analysts. It must be sensitive. A sensitive Model can be clearly observed for r...

Sharing helps. Sharing is fun. Sharing brings joy. Sharing gives results. The Component Model is friendly towards Sharing.  It is a practice to Share the Component Model. This practice has been adopted for many reasons. The reasons are good. The Sharing exercise has clearly succeeded.  A model is a small size of preparatory work. First Component Model is prepared and later the Component is developed. The Component is a detail form of the Component Model. The Component Model is shared to: Promote Development: Sharing promotes Component Development. The Model is shared with experts. Experts use their skills. An excellent working Component is the result. Complexity Management: When Model is shared the complexities are very well understood. They are resolved.When complexity goes away, simplicity finds way. Enrich Development: Sharing the Model with experts helps. Experts give their best. With expertise and skill, the Component Development process goes through technological refine...

Software Industry takes pride in developing standard practices. When a model is designed, many of our goals become simple.  The actual design of Software Components is guided by a standard model, i.e., COM ( Component Object Model ). Each and every step of Software Component design refers to the COM model. First the model is constructed. Once the model is in place, the detailed design is started, and the actual software Component is born. Till the end of Component design, and even after, the model of the Component serves the Component development and onward activities. The 'Component Model', or 'Component Object Model' ( COM ) lays stress on: Platform Independence: The model serves the purpose of being neutral to different kinds of systems. This kind of neutrality of COM is very promising. It leads to increased development activity, and thus promotion of software industry's interests. We mean the Component Model is  applicable to a variety of Operating Systems ( OSs...

A 'Component' is a single piece of code. In fact, a Component is a  small coded unit. 'Software Systems' are designed using coding practices. Such 'Software Systems' are made up of many such pieces of 'Components'.  In a 'Software System', a 'Component' has a well-defined role. It is fitted in the 'Software System' to perform that role.  Many 'Components' compose a 'Software System'. The 'Software System' can work successfully only when all the 'Components' ( pieces ) are doing their assigned tasks properly. Faulty 'Components' can be replaced. In a 'Software System', a 'Component' has to participate. A 'Component' has a well-defined function. It  performs when required.  A 'Component' is designed to work on its own.  It is armed with the code that can fulfill the task it is supposed to do. A 'Software System' is powerful. Such a System is empowered by...