Case Study 2: Instrumentation Software
-
Upload
junaid-lodhi -
Category
Education
-
view
34 -
download
0
Transcript of Case Study 2: Instrumentation Software
![Page 1: Case Study 2: Instrumentation Software](https://reader036.fdocuments.us/reader036/viewer/2022062503/58d149291a28ab455d8b68fb/html5/thumbnails/1.jpg)
CASE STUDY #2
Instrumentation software
Group 2
![Page 2: Case Study 2: Instrumentation Software](https://reader036.fdocuments.us/reader036/viewer/2022062503/58d149291a28ab455d8b68fb/html5/thumbnails/2.jpg)
Tektronix Oscilloscope
![Page 3: Case Study 2: Instrumentation Software](https://reader036.fdocuments.us/reader036/viewer/2022062503/58d149291a28ab455d8b68fb/html5/thumbnails/3.jpg)
Oscilloscopes
Evolution of oscilloscopes
Applications: Maintenance of electronic equipments Analyzing automation ignition systems, testing
sensors and output signals Display waveform of heartbeat as ECG
![Page 4: Case Study 2: Instrumentation Software](https://reader036.fdocuments.us/reader036/viewer/2022062503/58d149291a28ab455d8b68fb/html5/thumbnails/4.jpg)
Problems
Little reuse across oscilloscope products Different products are built differ Introduction of new hardware/UI would require
software redesign from scratch Custom products were built for specialized markets
Performance problems because software could not be easily reconfigured
![Page 5: Case Study 2: Instrumentation Software](https://reader036.fdocuments.us/reader036/viewer/2022062503/58d149291a28ab455d8b68fb/html5/thumbnails/5.jpg)
The purpose of this project was to develop a reusable software architecture to be shared among a number of new oscilloscope products. The result of that work was a domain-specific software architecture that formed the basis of the next generation of oscilloscopes.The goal of the project was to develop an architecture framework for oscilloscope that address H/w & UI requirements and reconfigurable software.
![Page 6: Case Study 2: Instrumentation Software](https://reader036.fdocuments.us/reader036/viewer/2022062503/58d149291a28ab455d8b68fb/html5/thumbnails/6.jpg)
Soln #1: Object Oriented Approach
![Page 7: Case Study 2: Instrumentation Software](https://reader036.fdocuments.us/reader036/viewer/2022062503/58d149291a28ab455d8b68fb/html5/thumbnails/7.jpg)
Soln #1
Drawbacks No overall model could be established
data types were identified but there was no overall model that explained the types fit together
It is cumbersome to partition the functionality
Confusion about division of functionality
Confusion about which objects are allowed to interact with user
![Page 8: Case Study 2: Instrumentation Software](https://reader036.fdocuments.us/reader036/viewer/2022062503/58d149291a28ab455d8b68fb/html5/thumbnails/8.jpg)
Soln #2: Layered Approach
![Page 9: Case Study 2: Instrumentation Software](https://reader036.fdocuments.us/reader036/viewer/2022062503/58d149291a28ab455d8b68fb/html5/thumbnails/9.jpg)
Soln #2
Drawbacks wrong model for the application domain
boundaries of abstraction enforced by the layers conflicted with the needs for interaction among various functions
![Page 10: Case Study 2: Instrumentation Software](https://reader036.fdocuments.us/reader036/viewer/2022062503/58d149291a28ab455d8b68fb/html5/thumbnails/10.jpg)
Soln #3: Pipes and Filters
Oscilloscope functions were viewed as incremental transformers of data:
![Page 11: Case Study 2: Instrumentation Software](https://reader036.fdocuments.us/reader036/viewer/2022062503/58d149291a28ab455d8b68fb/html5/thumbnails/11.jpg)
Soln #3
Advantages: Functions are no longer isolated into separate
partitions
Data flow nature of signal processing is reflected
Allows intermingling and substitution of software and hardware components
Disadvantages: Does not enable the user to interact with the system
![Page 12: Case Study 2: Instrumentation Software](https://reader036.fdocuments.us/reader036/viewer/2022062503/58d149291a28ab455d8b68fb/html5/thumbnails/12.jpg)
Modified Pipes and Filters