Object Modelling

Collins car tracking software prototype validation

Name

Institutional Affiliation

Object-oriented design models are often complex and challenging since they require technical expertise something that most people are not conversant with. It is therefore critical to carry out an in-depth research or analysis on this subject in order to augment our understanding on the concepts of object oriented design models. It is therefore critical to assess all the important concepts of object oriented programming in order to ensure that the concepts have been understood in full and that they are also easily understandable in a way that enhances and makes it easier for the users. This study will particularly assess the Collins car parking system by validating the system design through the development of a prototype for at least one subsystem that has been chosen for the case study. In so doing, the research will aim to unravel how the system designs for the prototypes can be validated in order to ensure that the system is working not only according to the specified standards but also in an effective manner. The study will further aim to validate the designs through the construction of a prototype and further convert the design diagrams into program codes. Furthermore, the study will prepare for project documentation through the development of a lucid presentation that will reflect on the practices that have been developed for this study and further improve on the designs that have been proposed for this study in order to bring out the needed result. The study will culminate with an identification of the three most important use cases for the subsystems and also the development of the communication diagrams or sequence diagrams for the use of these cases in a way that will ensure that they have been properly developed and that their functionalities have also been enhanced in order to bring out the desired results.

Prototype is an effective an efficient way of augment the understanding of the Collins car tracking software and further making it easier to validate the various requirements of the system at an early stage in a way that will promote the development of the software. This study will particularly develop an approach that will make it easier to develop the requirement models for the Collins car tracking system with the various OCL requirements into prototypes that are easily executable in a way that they also have functions of invariant constraints and also the multiplicity of the car tracking system design.

Sequence communication diagram

The analysis of the semantics of the preconditions and the post conditions that have made it easier to execute the operations of the prototype as a sequence for the primitive actions which first of all assess the preconditions of the system. They then enforce the post conditions that are required for transferring the system from the pre-state to the post-state in a step and step.

The actions that are primitive are the basic causes of manipulation in the state of the system through the development of the object diagram including finding the links and also the objects and further enhancing the removal and creation of links and objects in order to check the different set of attributes in the values of the system (Aristides, 2006). Based on the approach, there is a development of a tool that makes it easier to automate the generation of the prototypes as well as the analysis. This therefore implies that there will be a development of the tools that are needed in order to enhance the effectiveness of the Collins car tracking system in a way that that will make it easier to operate the system and further make it easier to use it.

In the beginning of the development of the software, it is critical to define and capture the requirements of the system since they are often cause difficulties for the engineers that are constructing the software. As a result of the gap that is got between the designers and the customers in the understanding of the system and the requirements thereof. Prototyping is therefore an efficient way of closing the gap and further validating the requirements of the customers in order to improve the overall customer experience. This will further go a long way in ensuring that the customer experience for the Collins car tracking system is improved and that it meets all the needs and the requirements that are needed for the development of the system. The main purpose for building the prototype should be to ensure that the Collins car tracking software is enhanced (Unhelkar, 2005).

Some of the purposes for the development of the Collins car tracking systems include the following. One of the purposes is to ensure that the requirements that are needed in order to validate the Collins car tracking software are validated through the demonstration of the prototypes for the customers that have been targeted by the system (Yang & EI-Haik, 2008). In addition, it is also imperative to ensure that the proper understanding of all the requirements that are needed in the system. In addition, it is also critical to ensure that there are proper implementers and designers for the Collins car tracking software.

In addition, it will also be used to test how the system is working and whether or not it working effectively. In so doing, the system developers are able to detect the deviations that are in the Collins car tracking software and further make the necessary corrections that are needed in order to enhance the effectiveness of the software.

In addition, it is also critical to cope with the changing requirements for the software in a better way in order to ensure that it is working in a proper manner and in the most effective manner. Moreover, it is also critical to ensure that any changes are done in a proper manner and to further ensure that the changes have been accounted for and that they also have been developed effectively in a way that will ensure that they have also been incorporated in all the tools of the system and that they are also easily understandable by all the users of the system.

The development of the prototype for the system takes into consideration the time and also the effort of the Collins car tracking software. It will therefore be critical to develop a prototype that will be generated automatically from the different requirement specifications. It is a palpable fact that the requirement model will be executed entirely and it is therefore a challenging and important problem to deal with. This is because of the apparent fact that it proposes a way of ensuring that the requirement models are enable us to explore the parts of the model are executable. It also allows us to generate a prototype without the need for the development of a design that is detailed (Unhelkar, 2005).

The UML model of requirements are defined and used through an approach that uses case driven specifications and requirements for analysis and modeling. Based on that work, this study will present a tool that will be developed for the automatic generation of prototypes and also the analysis of the Collins car tracking software. AutoPA 3.0 will be the tool that will be used for the development and enhancement of the Collins car tracking software (Aristides, 2006). It is a tool that is used to transform the UML model of the requirements into a prototype that is easily executable.

The system requirement model is a conceptual model class that uses a case model. The conceptual class of the model will represent the various concepts of the domains in the Collins car tracking software such as the use of classes and the relations with the associations. Unlike a class in a design class model, the class is a conceptual model of class that does not have a definite method. The conceptual diagrams of the class in addition to the annotation assertions impose the constraints on the states of the system that are easily allowable.

Each fragments of the expression of the OCL for instance the sub-expressions and the corresponding AST sub-tree. The OCL expressions are then translated into the explicit semantics of the corresponding primitive actions that are needs for the development of the system (Yang & EI-Haik, 2008).

The OCL and the UML models that can be prepared for the general case of the UML tools for instance the files that are needed for the development of the system and further enhance the tools that are also needed for the system. The UML and the OCL met models and then transforms each of the cases through the cases of the primitive actions. Other necessary functions that is needed for the tools for the prototypes such as the generation of the extra primitive actions and further through the processing of different posts that are needed for the system (Yang & EI-Haik, 2008).

In addition, it is also enhanced through generating the declarations of the different prototypes that are needed for the development of the system. In addition, it will also be used to generate the use case handlers and further enhance the implementation of the interface of the GUI interface in a way that interferes with the prototypes that have already been implemented.

Object-oriented Methods

Many claims have been made about the object-oriented paradigm. These claims include: Dawson and Swatman262

1. Ease of understanding object-oriented models due to a consistent underlying representation throughout the development process

2. The ability to model the behavior of objects (encapsulation of data and process)

3. Ease of modification and extensibility of object-oriented models.

4. Ease of reuse of object components from previously designed systems

5. superior data abstraction facilities including inheritance and polymorphism

When we study object-oriented methods in requirements engineering, our interest is in how experienced analysts and developers actually use such methods in “real-world” system specification. We also need to consider whether the benefits of reuse, abstraction and reduction in complexity outweigh any difficulties in using object-oriented methods.

Object-oriented systems development life cycles are usually based on non-linear cycles such as the spiral model. Henderson-Sellers reflects the conventional wisdom of the object-oriented community in stating that object-oriented analysis provides an accurate picture of a real world situation, object-oriented design supports good software engineering design and the goal of a good object-oriented method is the “seamless” transition between the analysis and design phases (Aristides, 2006).

Further, it is generally agreed within the object-oriented world that one of the strengths of object-oriented methods is that complexity is reduced because the concept of an object remains the same throughout the development process from analysis to implementation and flow of control is modeled as interactions between objects.

In this program of research, we open these key assertions to question and seek persuasive empirical evidence (for or against) that is grounded in the professional use of object-orientated methods on a commercial scale and in a commercial setting.

In an object-oriented modeling process, several models are usually produced. These models can be loosely categorized as either static models or dynamic models. Static models describe objects, their characteristics and the relationships between them. Some common models are class and object diagrams component notation and templates object. Models, class cards, hierarchies and collaborations, object/class models object and layer models and structural models.

Dynamic models define states of objects, state transitions, message passing and event handling. Some common dynamic models are state transition and event diagrams, state diagrams, object charts, interaction diagrams, rules, object communication models and dynamic models using event chains and collaborative diagrams. Sequencing is often modeled using use cases defining typical user interaction with the system.

The sub system or the Collins car tracking system will be used to track all the vehicles in order to foster the security of the vehicles and further enhance the tracking of vehicles in an effective and efficient way (Yang & EI-Haik, 2008). In addition, they will also be used to improve the operations of the vehicles by making it easier for the vehicles to operate smoothly and to further ensure that they can be used safely without the fear for theft. This in turn will improve the operation of the drivers as well as improve the overall business of the vehicles.

In conclusion, it is evident that object oriented programming is a challenging, complex and complicated field. The technicality surrounding this field is complex and this therefore implies that there are intricacies surrounding the field that are difficult for the readers to easily comprehend. The study nonetheless made concerted efforts to unravel how the validation of the Collins car tracking system can be done but there is need to conduct more research in order to solve some of the gaps in the literature.

References

Aristides, D. (2006). Verification, Validation and Testing in Software Engineering. New York, NY: IGI Global.

Unhelkar, B. (2005). Verification and Validation for Quality of UML 2.0 Models. New York, NY: John Wiley & Sons.

Yang, K., & EI-Haik, B. (2008). Design for Six Sigma: Design Validation. New York, NY: McGraw Hill Professional.

Compatible vehicles

Collins car tracking software