Saturday, June 15, 2019

Introduction to Requirements and Systems Modelling Essay

Introduction to Requirements and Systems Modelling - Essay ExamplePost Conditions The LED keep on masking the updated status of the peeing level received from the sensors. Assumptions It is assumed that the substance abuser has switched on the button of the Tunze Osmolator and checking / viewing LED to know the level of the water. Basic Flow 1. The user of the Tunze Osmolator switches on the machine. 2. The sensor motor activates itself and detects levels of the water in the tank. 3. The sensor sends the information to the arithmetic unit to compare the sensors value with the lower rope value of the tank. 4. Once the value has been compared, the LED would show the information whether the water level is lower than the threshold value A 1. 5. The motor starts itself to increase the level of the water till it reaches to the upper limit of the tank. Alternate Flow A 1. The motor would non start if the water level in the tank is higher than the requisite or lower threshold value of the tank. Conditions Trigging Alternate Flow The alternate flow would only be initiated if the water level in the tank is within the prescribed threshold limits. Note - The use case description format has been taken from the book of the R. S. Pressman. unite Modeling Language (UML) In package engineering, the Unified Modeling Language (UML) is a standardized modeling language that facilitates to create a graphical depiction of the object oriented systems under development. The UML is utilized for specifying, building, visualizing and documenting the software artifacts for the software application is to be developed. The UML adopts a combination of various concepts including the Booch, Object Modeling Technique (OMT) and Object Oriented Software Engineering (OOSE). By utilizing these concepts the UML provides a single platform for describing and modeling the software systems. However, in that respect are various limitations of the UML, as it focuses on software rather than iron ware (Overgaard, Selic and Bock, 2000). In other words, there are many issues in building the UML of the real-time systems include the description of hardware elements, time constraints, communications tasks and network modeling. Many solutions have been developed to reduce these issues and one of the solutions is to build the diagrams in three (3) tier structure of the system. In the first tier the object building and software construction would focus on the software architecture, whereas, the system architecture would focus on the hardware and communications aspects of the system (Lou, 2000). The Tunze Osmolator water level controller system relates to the systems establish on hardware more as compared to the software implementation. As described above, therefore, it can be stated that the implementation of the UML notation is quite difficult for the systems entirely based on hardware, time constraints and communications tasks. As the Tunze Osmolator includes the hardware and com munications tasks, therefore, comparatively the UML notation cannot be as fruitful as for the data-intensive applications or the software applications mostly based on the software. On the other hand, the UML notation can effectively use in various software engineering areas include but are not limited to the enterprise resource planning, banking and accounting services, web based

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.