Changes between Version 3 and Version 4 of Vision
- Timestamp:
- 11/01/17 16:48:22 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Vision
v3 v4 130 130 '''1.1 [=#p1.1] Purpose''' 131 131 132 The purpose of this document is to specify and perceive the goals and capabilities of this system. 132 The purpose of this document is to specify and perceive the goals and capabilities of this system. It also states the various constraints which the system will be abide to. This document further leads to clear vision of the software requirements, specification and capabilities which are to be exposed to the development, testing team and end users of the software. 133 133 134 134 '''1.2 [=#p1.2] Scope''' 135 135 136 The system being described provides management of all activities among the hospital staff and the patients. 136 The system being described generally provides management of all activities among the hospital staff and the patients. The system will be used in any hospital, clinic, dispensary or Pathology laboratories in order to get information from the patients and then store that data for future usage. 137 The current system in use is a paper-based system. It is too slow and cannot provide updated lists of patients within a reasonable time frame. The intention of the system is to reduce over-time pay and increase the number of patients that can be treated accurately. Requirements statements in this document are both functional and non-functional. 137 138 138 139 '''1.3 [=#p1.3] Definitions, Acronyms and Abbreviations''' 139 140 141 CFD – Context Flow Diagram 142 DFD – Data Flow Diagram 143 IDE – Integrated Development Environment 144 SQL – Structured Query Language 145 SRS – Software Requirement Specification. 146 GUI - Graphical User Interface 147 140 148 Name: '''System administrator''' 141 149 … … 177 185 178 186 '''2.1 [=#p2.1] Business Opportunity''' 187 The feasibility of the project is analysed in this phase and business proposal is put forth with a very general plan for the project and some cost estimates. During system analysis the feasibility study of the proposed system is to be carried out. This is to ensure that the proposed system is not a burden to the company. For feasibility analysis, some understanding of the major requirements for the system are essential. 179 188 180 189 '''2.2 [=#p2.2] Problem Statement''' 181 182 ||'''Проблемот на''' ||Немање термин за консултации и недостапност на професорите, асистентите и демонстраторите за студентите || 183 ||'''Засега''' ||Студенти на Финки || 184 ||'''Што доведува до''' ||Незадоволство кај студентите, недоразбирање помеѓу студентите и професорите || 185 ||'''Успешно решение би''' ||Да се креира систем кој ќе овозможи 24 часовна комуникација во “реално време“ помеѓу студентите и предавачите, притоа без да се врши оптеретување на корисниците со несоодветни пораки || 190 * Not having computerized all details regarding the patients and the hospital; 191 * Not having good overview what time is convenient for both the patient and the doctor; 192 * Not having scheduled all the services of specialized doctors and emergencies provided by hospital are fully utilized in effective and efficient manner. 193 * If the medical store issues medicines to patients, the stock status of the medical store and vice-versa should be reduced. 194 * It should be able to handle the test reports of patients conducted in the pathology lab of the hospital. 195 * There is not updated inventory, it needs to be updated automatically whenever a transaction is made. 196 * A system where all the records for the patients doesn't exist, these should be kept up to date and kept in a system for historical purposes. 197 186 198 187 199 '''2.3 [=#p2.3] Product Position Statement''' 188 200 189 ||'''За''' ||Тековните студенти и предавачи на Финки || 190 ||'''Кои''' ||Побаруваат едноставен начин за комуникација за било кое време [[br]] 191 Системот за on-line консултации || 192 ||'''Кој''' ||Овозможува комуницирање помеѓу предавачите и студентите во било кое верме без разлика на тоа каде се наоѓаат тие || 193 ||'''За разлика од''' ||Чекањето со часови пред кабинетите и правењето гужви во ходниците || 194 ||'''Нашиот продукт''' ||Е достапен 24/7 и не бара дополнителни трошоци || 201 ||'''For''' ||The current employees and the management of the institution using the system|| 202 ||'''Employees''' ||Need an easy access to the free time available for further appointments and review of patient's record|| 203 ||'''Patients''' ||Can view their own appointments and diagnosis|| 204 ||'''Different than''' ||Paper-based system|| 205 ||'''This product''' ||is available online and does not require additional expenses|| 195 206 196 207 '''3. [=#p3] Stakeholder and User Descriptions''' … … 350 361 '''4.1 [=#p4.1] Product Perspective''' 351 362 352 Овој систем ќе се интегрира како дел од веќе постоечкиот систем за елетронско следење на наставата на ФИНКИ. Ова ги опфаќа системите iknow за електронско запишување на предмети и ecourses за електронско следење на предметите. Неопходно е системите да бидат поврзани. Студентите кои ќе можат да го користат новиот систем се истите кои имаат запишан тековен семестар, студентите кои ќе можат да присуствуваат на консултации се само оние кои го имаат запишано дадениот предмет во тековниот семестар. Сите овие ограничувања и дозволи за пристап можат да бидат поставени во интеракција со постоечките системи. 363 The application will be windows-based, self contained and independent software product. It is necessary all employees and the management of the institution which uses it to have access to it and credentials provided. Only the current employees have access to system as the type of user they are. For instance if a doctor stops working in a hospital, they lose the credentials for the system and can no longer access it. 364 365 The entire project mainly consists of 7 modules, which are 366 1. Admin module 367 2. User module (patient) 368 3. Doctor module 369 4. Nurse module 370 5. Pharmacist module 371 6. Laboratorist module 372 7. Accountant module 353 373 354 374 '''4.2 [=#p4.2] Summary of Capabilities'''