internship report

Recommendations

Info

2.4. USE CASES 9 pre-conditions: none basic flow of events: The laboratory information system (LIS) validates incoming test result messages by examinating the content of the message. It then generates an application acknowledgement or application error message and sends it back to the data manager through the remote gateway interface. post-conditions: none alternatives: none 2.4.5 Use Case: Send Acknowledgement Message initiator: data manager involved actors: ˆ remote gateway interface ˆ laboratory information system included use cases: ˆ update measurement transfer status table ˆ log system information pre-conditions: none basic flow of events: The remote gateway interface transports the test result message to the laboratory information system (LIS). The laboratory information system has to validate the message and sends back an Application Acknowledgement (AA) or Application Error (AE) message through the remote gateway interface. The data manager listens on a socket for these incoming AA or AE messages, which are not time critical, and has to respond to them with an acknowledgement message. post-conditions: none alternatives: none 2.4.6 Use Case: Update Measurement Transfer Status Table initiator: data manager involved actors: ˆ SQL7 database
2.4. USE CASES 10 included use cases: none pre-conditions: none basic flow of events: The measurement transfer status table provides all necessary information to track the status of a test result message. Therefor each time a message has been sent or an acknowledgement message has been received, the measurement transfer status table will be updated with flag and timestamp information. If there has been an error acknowledgement, a comment that describes the kind of the error will be inserted. post-conditions: none alternatives: none 2.4.7 Use Case: Log System Information initiator: data manager involved actors: ˆ remote gateway interface ˆ laboratory information system ˆ SQL7 database included use cases: none pre-conditions: none basic flow of events: The log system information use case will provide the possibility to track all important status and error information in a log file. Each part of the system has to write detailed information in the log file if an exception occured in order to make it possible to fix the problem. The log file will also include the information that a message has been sent or received successfully. post-conditions: none alternatives: none 2.4.8 Use Case: Check Send Message Thread Timeout initiator: data manager involved actors: none included use cases: none pre-conditions: none basic flow of events:
Page 1 and 2: David Vogler University of Applied
Page 3 and 4: CONTENTS ii 3.2.3 Communication Pro
Page 5 and 6: CONTENTS iv C.1.4 DBSession.java .
Page 7 and 8: 1.2. PROJECT PLAN 2 1.2 Project Pla
Page 9 and 10: Chapter 2 Analyze System 2.1 System
Page 11 and 12: 2.3. CONTEXT DIAGRAM 6 2.3 Context
Page 13: 2.4. USE CASES 8 2.4.3 Use Case: Se
Page 17 and 18: 2.4. USE CASES 12 Lists of test res
Page 19 and 20: 3.2. NATURE OF COMMUNICATION LINK 1
Page 21 and 22: Chapter 4 Design 4.1 Send Message C
Page 23 and 24: 4.2. RECEIVE MESSAGE SERVER 18 4.2
Page 25 and 26: 4.4. DATABASE MODIFICATIONS 20 Figu
Page 27 and 28: Chapter 5 Implementation 5.1 XML Pa
Page 29 and 30: Chapter 6 Test Strategy 6.1 Gateway
Page 31 and 32: 6.4. PERFORM A TEST RUN 26 normal f
Page 33 and 34: 6.4. PERFORM A TEST RUN 28 6.4.2 Pr
Page 35 and 36: 6.4. PERFORM A TEST RUN 30 Figure 6
Page 37 and 38: 6.4. PERFORM A TEST RUN 32 Figure 6
Page 39 and 40: List of Figures 1.1 System Overview
Page 41 and 42: Appendix B Package ncv.gatewayif Pa
Page 43 and 44: B.1. CLASSES 38 B.1 Classes B.1.1 C
Page 45 and 46: B.1. CLASSES 40 ˆ stop public fina
Page 47 and 48: B.1. CLASSES 42 - Usage * returns t
Page 49 and 50: B.1. CLASSES 44 Constructors ˆ DBS
Page 51 and 52: B.1. CLASSES 46 - Usage * update fl
Page 53 and 54: B.1. CLASSES 48 Constructors ˆ Err
Page 55 and 56: B.1. CLASSES 50 Methods inherited f
Page 57 and 58: B.1. CLASSES 52 ˆ run public void
Page 59 and 60: B.1. CLASSES 54 Constructors ˆ MAS
Page 61 and 62: B.1. CLASSES 56 Declaration public
Page 63 and 64: B.1. CLASSES 58 ˆ iterator public
Page 65 and 66:
B.1. CLASSES 60 Constructors ˆ Not
Page 67 and 68:
B.1. CLASSES 62 B.1.13 Class RecvMe
Page 69 and 70:
B.1. CLASSES 64 ˆ setPriority publ
Page 71 and 72:
B.1. CLASSES 66 ˆ setPriority publ
Page 73 and 74:
B.1. CLASSES 68 B.1.16 Class Timer
Page 75 and 76:
B.1. CLASSES 70 Declaration public
Page 77 and 78:
Appendix C Listings C.1 Java Code C
Page 79 and 80:
C.1. JAVA CODE 74 4 * @version $Rev
Page 81 and 82:
C.1. JAVA CODE 76 116 ErrorMessageL
Page 83 and 84:
C.1. JAVA CODE 78 228 try { 230 sle
Page 85 and 86:
C.1. JAVA CODE 80 98 /** returns na
Page 87 and 88:
C.1. JAVA CODE 82 210 /** returns t
Page 89 and 90:
C.1. JAVA CODE 84 14 * Handles conn
Page 91 and 92:
C.1. JAVA CODE 86 126 } catch (SQLE
Page 93 and 94:
C.1. JAVA CODE 88 238 return true;
Page 95 and 96:
C.1. JAVA CODE 90 350 public ErrorM
Page 97 and 98:
C.1. JAVA CODE 92 462 /** get Messa
Page 99 and 100:
C.1. JAVA CODE 94 44 /** returns th
Page 101 and 102:
C.1. JAVA CODE 96 74 } } 76 } // en
Page 103 and 104:
C.1. JAVA CODE 98 108 e. printStack
Page 105 and 106:
C.1. JAVA CODE 100 220 || responseC
Page 107 and 108:
C.1. JAVA CODE 102 332 try { sendSo
Page 109 and 110:
C.1. JAVA CODE 104 50 if (C.get(Cal
Page 111 and 112:
C.1. JAVA CODE 106 56 msg.setFrom(f
Page 113 and 114:
C.1. JAVA CODE 108 78 } 80 /** retu
Page 115 and 116:
C.1. JAVA CODE 110 94 96 System.out
Page 117 and 118:
C.1. JAVA CODE 112 timeStamp = Misc
Page 119 and 120:
C.1. JAVA CODE 114 itemChild.append
Page 121 and 122:
C.1. JAVA CODE 116 item.appendChild
Page 123 and 124:
C.1. JAVA CODE 118 item.appendChild
Page 125 and 126:
C.1. JAVA CODE 120 itemChild = doc.
Page 127 and 128:
C.1. JAVA CODE 122 34 public synchr
Page 129 and 130:
C.1. JAVA CODE 124 84 } public XMLM
Page 131 and 132:
C.3. CONFIGURATION FILES 126 16 set
show all

internship report

Create successful ePaper yourself

Delete template?

Save as template?