2. GAYA Analyzer What Is It All About?

3. GAYA Analyzer Medical Imaging - Gamma Medica Camera

4. GAYA Analyzer Medical Imaging - GE Camera GE camera equipped with IMARAD CZT CZT camera head

5. GAYA Analyzer Medical Imaging - Philips & Siemens Siemens camera equipped with IMARAD CZT

6. GAYA Analyzer Medical Imaging - The Scheme

7. GAYA Analyzer How It Is Done - The Module

8. GAYA Analyzer The Inspection Process 1.Calibration 2.Analysis 3.Find optimal cut 4.Estimate Quality Degradation 1.Calibration 2.Analysis 3.Estimate Quality Degradation 1.Calibration 2.Analysis 3.Find Qualified Criteria

9. GAYA Analyzer Other Functional Requirements The hardware will be delivered to the clients with a software package that allows him to operate and test the modules. This package will include application with limited abilities, and a class library which enables communicating with the hardware.

10. GAYA Analyzer The World We Live In

11. GAYA Analyzer Our Block Diagram

12. GAYA Analyzer Non Functional Requirements  Capacity - Each image is about 0.5Mb in size.  GUI - User-friendly and intuitive, will follow the Orbotech Look & Feel. For every operation that takes more than 5 sec., a progress bar or sand clock will be displayed.  Robustness - The software must handle all exceptions internally, and prompt the user with clear and understandable error messages.  Portability - JDK1.5, VS7.1 + Intel Compiler 9, Windows XP.

13. GAYA Analyzer Non Functional Requirements - cont.  Testability - tools for high-level testing: The software simulator, The hardware SDK, Logger.  Reusability - The API for 2nd level users will be derived from the 1st level API.  Release Requirements - software simulator and application will be delivered as executables, communication and services layers will be delivered as class libraries. In addition, all the documents specified in the course syllabus are required.  Safety - The software has no interaction with the radiation source.

14. GAYA Analyzer Use Case: Acquire Image Description Display the pixels histograms as they change along the testing procedure, and save results to the DB. Frequency: Always. Priority: Mandatory. User levels: 1st Pre-conditions Wafer ID is loaded Parameters sets are defined in the DB. Processing The SDK memory has to be reset. Work mode will be set to histogram. All connected modules' FIFO will be reset. All the modules we wish to receive events from will be set to "events read mode". After the image acquisition timeout, the following steps should be made: Save the histogram results to DB. Set all the connected modules to "normal" mode. Post-conditions Image acquisition is done, and the results are saved to DB. Dependencies Use case ‎3.1.3.1 executed.

15. GAYA Analyzer Use Case: Acquire Image – Process Diagram

16. GAYA Analyzer Use Case: Acquire Image Through API Description The application starts image acquisition process by instructing the relevant modules to start sending events to the hardware SDK. Frequency: Sometimes. Priority: Mandatory. User levels: 1st, 2nd Pre-conditions N/A Processing Same as use case ‎3.1.4.2 (Acquire Image) Post-conditions The modules are in "events read mode", the SDK is acquiring image. Dependencies N/A

17. GAYA Analyzer Use Case: Acquire Image Through API