G7 patient record system

4,029 views

Published on

Published in: Education, Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
4,029
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
145
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

G7 patient record system

  1. 1. Al-Zaytoonah University of Jordan Faculty of Science and Information Technology Department of Software Engineering Patient record system By GAITH AMER RAMMAHA ALAAMAHMOUDAl-ZOUBI ZAID ALIGHANAYEM Supervised by DR. MOHAMAD LAFIA GRADUATION PROJECT SUBMITTED IN PARTIAL FULFILMENT OF HEREQUIREMENTS FOR THE DEGREE OF BSC IN SOFTWARE ENGINEERING Month Year (May 2013) i
  2. 2. ii
  3. 3. Abstract A brief discussion about the overall project, and must be up to one page length AcknowledgmentHere you write your personal messages to the people you would like to thank.The recommendation here is: All members can write one general acknowledgment If one chooses to write an acknowledgement, then all must write his/her own dedication. iii
  4. 4. 1 CHAPTER ONE: INTRODUCTION1.1 BackgroundIn our project we will try making it easy to anyone who involved in the medical category, like adoctor, hospital, pharmacy even the patient himself, to check the patients condition in a site thathave the record of all the disease, allergies, medicine (that he having or had) and the blood typethat can help the patient in any hospital he go so he get recover easily and fast.When any one of the category want show the records he have to enter the site and login andsearch to the exact patient by his name or the national number, then the doctor for example cansee or update the patient data (record) about the condition that he responsible of it.Through our site the people who involved can save time, money and treating the patient more quicklyand known more information to help him easily.1.2 Literature Review Well, in our project the idea never get done by any one so we research for something Similar, about a clinic that have a website to prove the info about the Disease and the Medicine, and their project was not that useful for the community so we developed the idea to become more productive. 1
  5. 5. 1.3 Business Model1.3.1Business NeedsPatient record is built to solve some problems that may face the patient when he goes to arandom hospital or clinic for treatment that don’t have patient record. Using our site the doctorwho responsible of the patient will be able to see what the patient records of diseases, info andcontact the Guardian of him. In this way we can save the money, effort and time for the hospitalor clinic and the patient.After the doctor see the patient info online and find out what he is suffering, the doctor should beable to change and update the patient record and what medicine need , so the pharmacy give thepatient the right medicine or for future condition .The site offers a way to the patient and doctor can be contact or a doctor to another 24/7, anydoctor, pharmacy or anyone involved with the medical category can access the site by hismedical number to see any records of an any patient that he need to see, in the other hand theregular person (patient) can access the site to only see his records.1.3.2Business EnvironmentDef:Business environment encompasses all those factors that affect a companysoperations, and includes customers, competitors, stakeholders, suppliers, industry trends,regulations, other government activities, social and economic factors and technologicaldevelopments.In our project there are:Tools:Microsoft Project Professional 2010 Plus IBM Rational Rose 2007 Adobe Dreamweaver cs5 or cs6 My SQL server 2008 Adobe Photoshop cs5 Microsoft Visio 2010 Microsoft PowerPoint 2010 2
  6. 6. *Microsoft Project Professional 2010 plus: Because we make a Gantt chart and we makefeasibility study of the project.*IBM Rational Rose 2007: Because we analysis the project by this tools and make a design ofthe project.*Adobe Dreamweaver: Because we to build and design the website and use the PHP languageand design interface. *My SQL Server: because store, insert and import the data in the server.*Adobe Photoshop cs5: to design the picture in the web.*Microsoft Visio 2010: Because we drawing charts of our project as a context diagram and statechart diagram.*Microsoft PowerPoint 2010: Because we drawing charts of our project as a context diagramand state chart diagram and to presentation.Environment: 1- Windows 8 2- CPU: Core i3 Second Generation 3.3 GHz Speed 3
  7. 7. 3- RAM: 8 Giga DDR3 4- HD: 500GB1.3.2.1 Software Context Diagram Fig (1.1) Software context diagram1.3.2.2 System Scope The idea of the project consists the Medical Records of the Patient (MRP), which has three major interfaces:  Interface of admin where the admin give the privileges for users.  Interface for a Patient to see his Medical Records.  Interface of Medical staff where they can change and update thedata and for the patient. 4
  8. 8. 1.3.3Stakeholder AnalysisStakeholder name Stakeholder represent RoleAdmin Who administrate the system He hasprivileges to edit the whole data in the website.Doctor Who update the data He change and update the Record Patient.Patient Who utilize the website See his recordPharmacist Update the drug data (Limited ) Change the drug section in the patient record.Medical tester Update the tests section Change and update Medical tests (Limited) section onlyRadiology Update the Radiology picture Change and update Radiology (Limited) section only Table (1.1) Stakeholder analysis1.3.4System Vision Document1.3.4.1 Objectives - Conversion the Record Patient system from manual and paper to electronic to keep up with the modernity, - Storage the records data so that Information will be available always. - So can all any Patient get his records anywhere any time.1.3.4.2 Benefits 5
  9. 9. 1. Minimize time and effort. 2. Minimize errors. 3. Speed in giving results. 4. Facilitate data storing. 5. Reduce the number of Patients. 6. Reduce the pressure on admin and all stakeholders. 7. Saving money. 8. Provide security.1.3.4.3 Capabilities 1. Reduce thetimeittakesin terms ofthe presence ofthepatients fileelectronicallyandminimizetheeffortto obtain the file. 2. Reduce errors that result from not patients arrange files through the system we will process the order of the files on the system 3.Data storage byofficialsonthedatabaseof the systemwithease. 4. Save money by havingthe patientsfileonthesystemand does not neednew testsastheyexist on thesystem. 5.Provides security and safety of the data, Available through for all Patients and all medical staff (doctors, hospital ... etc.).1.3.5Project Management1.3.5.1 Project Iteration and ScheduleTask Mode Task Name Duration Start Finish Predecessors Resource Names 6
  10. 10. Manually 0 StartScheduled daysAuto 12 InceptionScheduled daysAuto 12 Iteration I1Scheduled daysAuto Business 7 daysScheduled ModelingManually Define 2 days 1 GaithScheduled Business Needs EvaluateManually Existing 2 days 5 AlaaScheduled InfrastructureManually Stakeholder 2 days 6 ZaidScheduled AnalysisManually Define Vision 1 day 7 GaithScheduled DocumentManually Business Modeling 0 days 8 Alaa;Gaith;ZaidScheduled ReportAuto Project 5 daysScheduled ManagementManually Define Project 1 day 9 GaithScheduled & System ScopeManually Project & 2 days 11 AlaaScheduled Iteration ScheduleManually Define Risks 2 days 12 ZaidScheduled & Feasibility study ProjectManually Management 0 days 13 Alaa;Gaith;ZaidScheduled ReportAuto Environment 5 daysScheduledManually Select 1 day 6 AlaaScheduled Development Tools SelectManually Development 2 days 9 ZaidScheduled ProcessManually Select 1 day 6 AlaaScheduled Support ServicesManually Environment 0 days 17 Alaa;Gaith;ZaidScheduled ReportAuto 31 ElaborationScheduled days Define SupportManually Services 2 days 6 AlaaScheduled Architecture DesignManually Define 2 days 21 Alaa;Gaith;Zaid 7
  11. 11. Scheduled System/Software Architectural DesignAuto 31 Iteration E1Scheduled daysAuto 14 RequirementScheduled daysManually Gathering 3 days 22 GaithScheduled Requirements DefineManually Functional 2 days 25 AlaaScheduled Requirements Define Non-Manually Functional 2 days 25 ZaidScheduled RequirementsManually Requirement 0 days 27 Alaa;Gaith;ZaidScheduled ReportAuto System 9 days AlaaScheduled ModelsManually Use Case 2 days 26 AlaaScheduled ModelManually Domain 2 days 30 AlaaScheduled Class Model Use CasesManually Descriptions 3 days 30 ZaidScheduled "Scenarios" Activity &Manually System Sequence 2 days 32 ZaidScheduled Models User Interface-Manually Navigational Paths 2 days 33 GaithScheduled and Screen Mock- upsManually State chart Model 2 days 31 GaithScheduledManually System 0 days 35 Alaa;Gaith;ZaidScheduled Models ReportAuto 31 DesignScheduled daysAuto Services 1 dayScheduled support designManually Software 1 dayScheduled architecture design DetailsAuto Design "Use Case 7 daysScheduled Realization"Manually 3 days 33 Zaid 8
  12. 12. Scheduled Communication ModelManually Design 2 days 41 AlaaScheduled Class ModelManually Package 1 day 42 GaithScheduled ModelManually State chart Model 1 day 43 GaithScheduledManually Details 0 days 43 Alaa;Gaith;ZaidScheduled Design ReportAuto Database 5 daysScheduled DesignManually Entity 1 day 45 AlaaScheduled Relationship Model System &Manually User Interfaces 2 days 47 GaithScheduled Design SystemManually Controls & Security 2 days 48 ZaidScheduled DesignManually Design 0 days 49 Alaa;Gaith;ZaidScheduled Activities ReportAuto Iteration E2 1 dayScheduledAuto Integration E1 & 1 day Gaith;Alaa;ZaidScheduled E2Auto Iteration E3 1 dayScheduledAuto Integration E1 & 1 dayScheduled E2 & E3Manually 30 ConstructionScheduled daysAuto 10 Iteration C1Scheduled daysAuto E1 Code 10Scheduled Generation days Generate Design ClassManually Model to Specific 1 day 50 AlaaScheduled Programming Language Generate Design ClassManually Model to Specific 1 day 50 AlaaScheduled Database LanguageManually Writing 7 days 58;59 Gaith;ZaidScheduled Programming 9
  13. 13. AlgorithmsManually Algorithms 2 days 60 Gaith;ZaidScheduled Unit TestingManually C1 Working 0 days 59;58 Alaa;Gaith;ZaidScheduled PrototypeAuto Iteration C2 1 dayScheduledAuto Integration 1 dayScheduled Testing C1 & C2Auto Iteration C3 1 dayScheduled IntegrationAuto Testing C1 & C2 & 1 day?Scheduled C3Auto End 0 days 62Scheduled Fig (1.2) Gantt chart1.3.5.2 Project Financial Feasibility and Risk AnalysisProject Financial FeasibilityThe goal of project is to Ease and a speed, to get to all Patient records more flexible and to makethe system more efficient and easy to use for other users. In addition: Reduce the number of the employees. Reduce the cost of traveling to the user. More protection and safety.Risk analysisWhen we talk about risk analysis, we have to know what is the meaning is of risk analysis.Risk analysis: Clinical and administrative activities undertaken to identify, evaluate, to reducethe risk of loss to the organization itself. Activities include the process of making and carryingout decisions that will prevent or minimize clinical, business, and operational risks.Now the risks of this project, as follows: 10
  14. 14. Securing the communication between the home computer to the user and the central server is also a problem. Sometimes the internet is not available for the user. Some people do not like or do not know the use of the Internet.Risk Description Potential impact on Likelihood of Difficulty of timely Overall threat project occurrence anticipation (high,medium,low) (high,medium,low) (high,medium,low) (high,medium,low)Users can not high medium medium highaccess to thesystemUsers can not high medium high highenter dataUsers can not use medium low low mediuma computer savvy 1.3.6Development Environment 1.3.6.1 Development Tools and Support Services IBM Rational Rose 2007: 11
  15. 15. 1- Build software architecture that supports change with a common platform that facilitateseasy roundtrip engineering and synchronization of models and code.2- Accelerate implementation and facilitate maintenance of a service-oriented architecture(SOA) solution, such as a web service, with tools and process guidance. 3- Use UML to ensure the numerous stakeholders within your software developmentprojects are continuously communicating, and use defined specifications to jumpstartdevelopment. 4- Gain insight into distributed projects and tighter control of shared information.Adobe Dreamweaver cs5 :Adobe Dreamweaver CS5 is a program used to develop Websites in terms of design. Thereare many sites online that were made from Dreamweaver. Its become a bit of a staple in theindustry, and the new CS5 version is no exception.Just as is the case with most every program though, there are pros and cons to consider whendeciding whether the cost of CS5 is worth if for your particular needs and interests.Pros:-1-PopularityCS5 and Dreamweaver in general, are quite widespread across the Internet. This means thatthere is a lot of knowledge out there on the program. There are entire communities ofindividuals devoted to Dreamweaver and CS5. This allows you to go on to thosecommunities and ask questions about the program there and get a quick response. So this is amajor advantage Dreamweaver and CS5 has over other programs that might not be as wellknown.The familiarity of the program will also make it easier to find anyone nearby who mightknow of it and any kind of help you might get whether official or unofficial is more likelysince the program is so well known.-2-Complete ManagementDreamweaver isnt just a tool for developing a single page. It can also develop entirewebsites, integrating them all together with a variety of different integrating tools. This cutsdown on the amount of extra work you have to do, or the extra tools and programs you may 12
  16. 16. need. Dreamweaver CS5 allows you to use all these different tools together in a singleprogram.-3-Speed and IntegrationThe CS5 update for Dreamweaver, which came out in April of 2010, is also known forhaving good speed and web integration. Working with images on the web is easier than inprevious versions. The speed at which the program is capable of working has also been muchimproved.CS5 also integrates well with the rest of the Adobe suite, making it easier to go back andforth between different programs for more total control over various procedures on yourcomputer, such as desktop publishing. My SQL server 2008:1- A parent Data Encryption. The ability to encrypt an entire database.2- Backup Encryption. Executed at backup time to prevent tampering.3- External Key Management. Storing Keys separate from the data.4- Auditing. Monitoring of data access.5- Data Compression. Fact Table size reduction and improved performance.6- Resource Governor. Restrict users or groups from consuming high levels or resources.7- Hot Plug CPU. Add CPUs on the fly.8- Performance Studio. Collection of performance monitoring tools...etc...Adobe Photoshop cs5:1- Image editing and additions anddinette gratedorpictures.2- Also add text.3- And Web Design.Microsoft Visio 2010:1- Simplify complexity with a diverse set of intuitive, professional diagramming tools2- Bring your diagrams to life with dynamic, data-driven visuals.3- Share interactive, refreshable, data-linked diagrams with others via their Web browsers.Microsoft project Professional 2010 plus:1- Easily plan & manage your projects with intuitive controls and flexible team tools to help your organization deliver the intended business value.2- Be efficient and prioritize by aggregating everyday work, project tasks, important details, and timelines in a visually rich and contextual interface. 13
  17. 17. 3- Manage anywhere with tools to keep you connected with your team and on top of your projects while you’re on the go. 4- Deliver effective presentations that offer immediate insight into task planning, resource allocation, cost efficiencies, and the many important details of your projects etc…….. Microsoft PowerPoint 2010: 1- Manage presentations with tools that save time and simplify your work. 2- Create extraordinary presentations. 3- Work together more successfully. 4- Access and share your content from more places. 1.3.6.2 System Development ProcessThe Rational Unified Process (RUP) is an iterative software development process framework created bythe Rational Software Corporation, a division of IBM since 2003.RUP is not a single concreteprescriptive process, but rather an adaptable process framework, intended to be tailored by thedevelopment organizations and software project teams that will select the elements of the process that areappropriate for their needs. RUP is a specific implementation of the Unified Process. Fig (1.3) System development process2 CHAPTER TWO: REQUIREMENTS 14
  18. 18. The project requirements phase is one of the most important parts of your project and especially project. Working on a software project, you should use Software Engineering techniques in this phase. Requirements are prepared by communicating with your customer which is in general your advisor.2.1 Gathering Requirements Interview method: Interviewing is an important method for collecting data on information system requirement. An information gathering way represents a directed conversation with a specific purpose that uses question-and-answer format we met some of the staff working in the medical department of electronic. Questionnaires: have advantages over some other types of surveys in that they are cheap, do not require as much effort from the questioner as verbal or telephone surveys, and often have standardized answers that make it simple to compile data. However, such standardized answers may frustrate users. Questionnaires are also sharply limited by the fact that respondents must be able to read the questions and respond to them.2.2 System Problem StatementThe old system was a traditional where was dealing with the documents manually, but now hasbecome a web application where all users of the system can interact with the system which aims tofacilitating of interaction and saving both time and effort.In the old system, the record of patient was an available for one hospital or clinic but now all themedical staff in country can access to his record, the current system facilitate a retrieval and access tothe data, unlike what was in the old system, the current system provides the possibility of see itwhere ever you are, this system also decrease an effort placed on the patient, who was doing aregistration in ever hospital manually.2.3 Functional, Non-Functional Requirements and System Constraints 15
  19. 19. Functional Requirements:Functional requirements are actions which the system does on behalf of the user, also it used to expressthe behavior of a system by specifying both the input and output conditions that are expected to finalresult. Functions of users :I. Administrator- Maintain patient employee info- Search patient- Search employee- Login- Log out- Change passwordII. Doctor- Search patient-change all the data of the patient record- Login- Log out- Change passwordIII. Pharmacist-Search patient-Maintain druginfo- Login- Log out- Change passwordIV. Patient- View his patient’s history record- Login- Log out- Change passwordV. Medical tester- Search patient-Maintain Medical info tests section only. 16
  20. 20. - Login- Log out- Change passwordV. Radiology- Search patient-Maintain Radiology info section only.- Login- Log out- Change passwordNon-Functional Requirements:Non- functional requirements are conditions and constraints which the program must conform, andthe following list summarized non-functional quality attributes of a program: UsabilityWhere the system must be easy to use and any user can interact with it. ReliabilityWhere the system works correctly without any problems or errors. EfficiencyWhere the system executes all operations in a shorter time. AvailabilityThe system must be available when the user need it at any time and can get access to theWebsite. SecurityIn the security there is a special user name and password for each user of the system and each userhas certain privileges. 17
  21. 21. System constraints:1. Financial barriers through, difficulty to pay money.2. Unqualified medical staff.3. Weak planning and management between pharmacist and doctor.2.4 System Models2.4.1Use Case Model searchDoctor searchMedicaltester searchPatient <<include>> <<include>> <<include>> <<include>> searchRadiology <<include>> Admin login <<include>> searchPharmacist <<include>> <<include>> logout changeProfile maintlenAllUser 18
  22. 22. <<include>> logout <<include>> X-rayChange <<include>> <<include>> logout login login drugchange RadiologyPharmacist <<include>> <<include>> <<extend>> <<extend>> changeProfile changeProfile forgot password forgot password 19
  23. 23. <<include>> <<include>> logout <<include>> <<include>> login Medicaltester <<include>> changeProfile <<include>> login Patient <<extend>> <<extend>> changemedicaltester showAlltheprofiles forgot password forgot password <<include>> <<include>> logout Doctor login <<include>> <<extend>> chengePatientrecord forgot password changeProfile2.4.2Domain Class ModelDomain class:The class diagram is the main building block of object oriented modeling. It is used both for generalconceptual modeling of the systematic of the application, and for detailed modeling translating the modelsinto programming code. Class diagrams can also be used for data modeling. The classes in a classdiagram represent both the main objects and or interactions in the application and the objects to beprogrammed. In the class diagram these classes are represented with boxes which contain three parts: A class with three sections:1-The upper part holds the name of the class2-The middle part contains the attributes of the class 20
  24. 24. 3-The bottom part gives the methods or operations the class can take or undertakeIn the design of a system, a number of classes are identified and grouped together in a class diagramwhich helps to determine the static relations between those objects. With detailed modeling, the classes ofthe conceptual design are often split into a number of subclasses.In order to further describe the behavior of systems, these class diagrams can be complemented by statediagram or UML state machine. Also instead of class diagrams Object role modeling can be used if youjust want to model the classes and their relationships 21
  25. 25. 2.4.3Use Cases Descriptions "Scenarios"A Use Case Scenario is a description that illustrates, step by step, how a user is intending to use asystem, essentially capturing the system behavior from the users point of view. A use case scenario 22
  26. 26. can include stories, examples, and drawings. Use cases are extremely useful for describing theproblem domain in unambiguous terms and for communicating with the potential users of a system.Use Case Name: loginScenario: Login to SystemTriggering Event: User wants to login to the websiteBrief Description: User must be a member in user databaseActors: Admin , Doctor, Pharmacist, Patient , Medical tester , RadiologyRelated use case LogoutStakeholders: Admin , Doctor, Pharmacist, Patient , Medical tester , RadiologyPreconditions: User database exists and Username, password and user type are correct.Post conditions: Login to the webFlow of Event: Actor System 1. User enters information. 2. Verify user information. 3-login to the webException 1.1 If incorrect data (user name, password, user type) deny access to the userConditions: account and display error massage. 1.2 If account is block, display error message. Table (2. ) User login scenario 23
  27. 27. Use Case Name: Logout.Scenario: Logout from SystemTriggering Event: User wants to logout from websiteBrief Description: User want to logoutActors: Admin , Doctor, Pharmacist, Patient , Medical tester , RadiologyRelated use case:Stakeholders: Admin , Doctor, Pharmacist, Patient , Medical tester , RadiologyPreconditions: Login to the webPost conditions: Exit web.Flow of Event: Actor System 1. Select logout button 2. Exit from the system.Exception Conditions: Table (2. ) Logout scenario 24
  28. 28. Use Case Name: Change PasswordScenario: Change PasswordTriggering Event: user wants to change passwordBrief Description:Actors: Admin , Doctor, Pharmacist, Patient , Medical tester , RadiologyRelated use case:Stakeholders: Admin , Doctor, Pharmacist, Patient , Medical tester , RadiologyPreconditions: User writes the old password and then the new password is correct.Post conditions: The password changed successfullyFlow of Event: Actor System 1. User enter the old password 2. verify the old password 4. system save the new 3. user enter new password and retype it password to databaseException 1.1 If incorrect data (password) deny access to the user account and display error massage.Conditions: 1.2 If account is block, display error message. Table (2. ) change password scenario Use Case Name: Forget Password Scenario: User forget his passwordTriggering Event: user wants to recover him passwordBrief Description: User forget him password and want to recover it by send him password in him e-mail Actors: Admin , Doctor, Pharmacist, Patient , Medical tester , Radiology Related use case: Stakeholders: Admin , Doctor, Pharmacist, Patient , Medical tester , Radiology Preconditions: Post conditions: The password has been sent to user e-mail Flow of Event: Actor System 1. User enter him e-mail 2. verify the e-mail has been founded And send the password to him e-mail Exception 1.1 the e-mail is incorrect Conditions: 1.2 the e-mail is not found in database 25
  29. 29. Table (2. ) forget Password scenarioUse Case Name: Create Account EmployeeScenario: Admin add anEmployee to the databaseTriggering Event: Admin wants to add a new Employee to the databaseBrief Description:Actors: AdminRelated use case:Stakeholders: Admin , Doctor, Pharmacist, Medical tester , RadiologyPreconditions: admin must existPost conditions: New Employee object must existFlow of Event: Actor System 1. Enter new Employee information 2. Create new Employee, display information 3.Create new Employee, display informationException 1.1 if the Employee found in the database, then give a messageConditions: Table (2.5) Insert Employee scenarioUse Case Name: Verify Account AdminScenario: Admin verify account to the databaseTriggering Event: Admin wants to verify account to the databaseBrief Description:Actors: AdminRelated use case:Stakeholders: AdminPreconditions: admin must existPost conditions: Admin object must existFlow of Event: Actor System 1. Enter Admin information 2.Admin display 26
  30. 30. informationException 1.1 if the Employee found in the database, then give a messageConditions: Table (2.6) Verify Account scenarioUse Case Name: Delete EmployeeScenario: Admin delete anEmployee from databaseTriggering Event: Admin wants to add a new Employee and Candidates to the databaseBrief Description:Actors: AdminRelated use case:Stakeholders: Admin , Doctor, Pharmacist, Medical tester , RadiologyPreconditions: Employee must existPost conditions: Employee information must not existFlow of Event: Actor System 1. A Election officer filter the user and delete 2. System retrieve all these Employee Employee from DB 3.DeleteEmployee informationException 1.1 if the admin not found in the database, then give a messageConditions: Table (2.7) Delete Employee scenarioUse Case Name: Edit EmployeeinformationScenario: Admin edit anEmployee information databaseTriggering Event: User information needs to be updatedBrief Description:Actors: AdminRelated use case:Stakeholders: Admin , Doctor, Pharmacist, Medical tester , RadiologyPreconditions: admin existsPost conditions: Employee exist 27
  31. 31. Flow of Event: Actor System 1. Enter Employee update 2 .Update Employee informationExceptionConditions: Table (2.8) Edit Employee scenarioUse Case Name: Create Account PatientScenario: Admin add a Patient to the databaseTriggering Event: Admin wants to add a new Patient to the databaseBrief Description:Actors: AdminRelated use case:Stakeholders: Admin , PatientPreconditions: admin must existPost conditions: New Patient object must existFlow of Event: Actor System 1. Enter new Patient information 2. Create new Patient, display information 3.Create new Patient, display informationException 1.1 if the Patient found in the database, then give a messageConditions: Table (2.9) Insert Patient scenarioUse Case Name: Verify Account AdminScenario: Admin verify account to the databaseTriggering Event: Admin wants to verify account to the databaseBrief Description:Actors: Admin 28
  32. 32. Related use case:Stakeholders: AdminPreconditions: admin must existPost conditions: Admin object must existFlow of Event: Actor System 1. Enter Admin information 2.Admin display informationException 1.1 if the Patient found in the database, then give a messageConditions: Table (2.10) Verify Account scenarioUse Case Name: Delete PatientScenario: Admin delete a Patient from databaseTriggering Event: Admin wants to add a new Patient and Candidates to the databaseBrief Description:Actors: AdminRelated use case:Stakeholders: Admin , PatientPreconditions: Patient must existPost conditions: Employee information must not existFlow of Event: Actor System 1. A Election officer filter the user and delete 2. System retrieve all these Patient Patient from DB 3.Delete Patient informationException 1.1 if the admin not found in the database, then give a messageConditions: Table (2.11) Delete Patient scenarioUse Case Name: Edit Patient informationScenario: Admin edit a Patient information databaseTriggering Event: User information needs to be updated 29
  33. 33. Brief Description:Actors: AdminRelated use case:Stakeholders: Admin , PatientPreconditions: admin existsPost conditions: Employee existFlow of Event: Actor System 1. Enter Patient update 2 .Update Patient informationExceptionConditions: Table (2.12) Edit Patient scenarioUse Case Name: SearchPatientinformationScenario: Admin search Patient informationTriggering Event: Admin search Patient informationBrief Description:Actors: AdminRelated use case:Stakeholders: Admin , PatientPreconditions: Admin must exist Patient information must existPost conditions: NoneFlow of Event: Actor System 1. Enter Patient information 2.Find and display Patient informationException 1.1 if admin not found, then give a messageConditions: 1.2 if Patient not matches, then give a message Table (2.13) Search Patient scenarioUse Case Name: Search Employee informationScenario: Admin search Employee information 30
  34. 34. Triggering Event: Admin search Employee informationBrief Description:Actors: AdminRelated use case:Stakeholders: Admin , Doctor, Pharmacist, Medical tester , RadiologyPreconditions: Admin must exist Employee information must existPost conditions: NoneFlow of Event: Actor System 1. Enter Employee information 2. Find and display Employee informationException 1.1 if admin not found, then give a messageConditions: 1.2 if Employee not matches, then give a message Table (2.14) Search Employee scenarioUse Case Name: View Employee informationScenario: Admin view Employee informationTriggering Event: Admin view EmployeeinformationBrief Description:Actors: AdminRelated use case: Doctor, Pharmacist, Medical tester , RadiologyStakeholders: Admin , Doctor, Pharmacist, Medical tester , RadiologyPreconditions: Admin must exist Employee information must existPost conditions: NoneFlow of Event: Actor System 1. Enter Employee information 2. Find and display Employee informationException 1.1 if admin not found, then give a messageConditions: 1.2 if Employee not matches, then give a message Table (2. 5) viewEmployeescenario 31
  35. 35. Use Case Name: Show Patient tableScenario: Admin show the Patient oftableTriggering Event:Brief Description:Actors: AdminRelated use case:Stakeholders: AdminPreconditions:Post conditions:Flow of Event: Actor System 1. Admin asked system 2. System retrieve all Patient data about Patient tableExceptionConditions: Table (2.16) Show Patient table scenarioUse Case Name: Show Employee tableScenario: Admin show the Employee of tableTriggering Event:Brief Description:Actors: AdminStakeholders: AdminRelated use case:Preconditions:Post conditions:Flow of Event: Actor System 1. Admin asked 2. System retrieve system about all Employee data Employee tableExceptionConditions: Table (2.17) Show Employee table scenario 32
  36. 36. Use Case Name: Admin add advertise Scenario: Admin Add advertise to DBTriggering Event:Brief Description: Actors: Admin Related use case: Stakeholders: Admin Preconditions: -------- Post conditions: advertise add to DB Flow of Event: Actor System 1. Admin add an advertise 2. Add the new advertise information to DB Exception 1.1 advertise information not completed Conditions: Table (2.18) Admin add ads scenarioUse Case Name: Admin advertise deletesScenario: Admin delete a Candidate from databaseTriggering Event:Brief Description:Actors: AdminRelated use case:Stakeholders: Admin , CandidatePreconditions: Ads must existPost conditions: Advertise information must not existFlow of Event: Actor System 1. delete advertise information 2. System retrieve all advertise from DB 3.Delete advertise informationException 1.1Conditions: Table (2.19) Admin ads deletes scenario 33
  37. 37. Use Case Name: Insert DrugScenario: Insert Drug informationTriggering Event:Brief Description:Actors: PharmacistRelated use case:Stakeholders: PharmacistPreconditions: Drug must existPost conditions: Drug information must not existFlow of Event: Actor System 1. delete Drug information 2. delete Drug informationException 2.1 if the PharmacistConditions: not found in the database, then give a message Table (2.20) Insert drug scenarioUse Case Name: Delete DrugScenario: Delete DrugTriggering Event: Pharmacist wants to Drug delete from databaseBrief Description:Actors: PharmacistRelated use case:Stakeholders: PharmacistPreconditions:Post conditions: Drug createdFlow of Event: Actor System 1. enter new Drug information 2.Create Drug record and display informationExceptionConditions: Table (2.21) Insert drug scenario 34
  38. 38. Use Case Name: Edit DrugScenario: Edit Drug informationTriggering Event: Drug information needs to be updatedBrief Description:Actors: PharmacistRelated use case:Stakeholders: PharmacistPreconditions: pharmacist existsPost conditions: Drug user existsFlow of Event: Actor System 1. Enter Drug update 2. Update Drug informationExceptionConditions: Table (2.22) Insert drug scenarioUse Case Name: Search DrugScenario: Pharmacist Search Drug informationTriggering Event:Brief Description:Actors: PharmacistRelated use case:Stakeholders: PharmacistPreconditions: Drug must existPost conditions: NoneFlow of Event: Actor System 1. Search Drug 2. Search DrugException 1. if Drug not found, then give a messageConditions: Table (2.23) Insert drug scenario 35
  39. 39. Use Case Name: Insert diseaseScenario: Insert disease informationTriggering Event:Brief Description:Actors: DoctorRelated use case:Stakeholders: Patient ,DoctorPreconditions:Post conditions: DiseasecreatedFlow of Event: Actor System 1. enter diseaseinformation 2.Create disease record and display informationExceptionConditions: Table (2.24) Insert new disease scenarioUse Case Name: Delete diseaseScenario: Delete disease informationTriggering Event: Doctor wants to disease delete from databaseBrief Description:Actors: DoctorRelated use case:Stakeholders: Patient ,DoctorPreconditions: disease must existPost conditions: disease information must not existFlow of Event: Actor System 1. Delete disease information 1. Delete disease informationExceptionConditions: Table (2.25) Insert disease scenario 36
  40. 40. Use Case Name: Edit diseaseScenario: Edit disease informationTriggering Event: Disease information needs to be updatedBrief Description:Actors: DoctorRelated use case:Stakeholders: Patient ,DoctorPreconditions: Disease must existPost conditions: Disease user existsFlow of Event: Actor System 1. Enter disease update 2. Update disease informationExceptionConditions: Table (2.26) Edit disease scenarioUse Case Name: View history patientScenario: Patient&Employee view history patientsTriggering Event: Disease information needs to be updatedBrief Description:Actors: Patient , EmployeeRelated use case:Stakeholders: Patient , EmployeePreconditions: patient must existPost conditions: NoneFlow of Event: Actor System 1. view history patient information 2. View history patient information.Exception 1. if patient&Employee not found, then give a messageConditions: Table (2.27) View history patient scenario 37
  41. 41. 2.4.4Activity & System Sequence Models  System activity model:Is used to display the sequence of activities and show the workflow from a start point to the finishpoint detailing the many decision paths that exist in the progression of events contained in theactivity.  System sequence model:Is a kind of interaction diagram that shows how processes operate with one another and in whatorder, it is a construct of a message sequence chart, and it shows object interactions arranged in timesequence. It depicts the objects and classes involved in the scenario and the sequence of messagesexchanged between the objects needed to carry out the functionality of the scenario. 38
  42. 42. user system error message [ not ok ]user enter info verify user [ ok ] login to the web 39
  43. 43. admin systemselect logout button Exit from the system 40
  44. 44. patient systemEnter Patient information Find and display Patient information Pharmacist systemdelete Druginformation delete Drug information 41
  45. 45. 3 CHAPTER THREE: DESIGN3.1 Architecture and Deployment environment Design(Network environment)3.2 Software Architecture Design3.3 Sequence Models Show your details design by giving up to 3 examples of your cases here, and add the rest to your appendix section (don’t print it out just keep it available with your softcopy of the project under (Appendix A: Expanded Sequence Models) section. 42
  46. 46. 3.4 Design Class Model3.5 Design package model (optional)3.6 Design the database3.6.1Design Entity-Relationship Model3.7 Design the system and user interfaces3.8 Design the system security4 CHAPTER FOUR: IMPLEMENTATION4.1 Generate Design class model to specific programming language syntax Show the code for each of cases you have shown in the previous chapter (section 3.3: sequence models)4.2 Generate Entity-Relationship model to SQL script Show the SQL script OR the screen shot for your tables- if you have used GUI - for each of cases you have shown in the previous chapter ( section 3.3: sequence models) 43
  47. 47. 4.3 Building your code This is your software program, and must be in your project CD)5 CHAPTER FIVE: TESTING5.1 Unit Testing5.1.1Set cases test You have to show where you used the requirement in your design as well as in your implementation by conducting a test for the full system and showing the input / process / output procedures within design and implementation stages) 44
  48. 48. 5.2 Integration Testing5.3 Other testing (optional) (Performance Testing, Acceptance Testing, GUI Testing,)6 CONCLUSIONS AND FUTURE WORK6.1 Conclusion6.2 Future work 45
  49. 49. ReferencesUse either APA or MLA bibliography style for citation 46
  50. 50. 7 Appendices7.1 Appendix AAny supporting documents 47
  51. 51. 7.2 Appendix BAny supporting documents 48
  52. 52. Table of ContentsAbstract .......................................................................................................................................... iiiAcknowledgment ........................................................................................................................... iiiTable of Contents ...........................................................................Error! Bookmark not defined.List of Figures ................................................................................Error! Bookmark not defined.List of Tables .................................................................................Error! Bookmark not defined.1 CHAPTER ONE: INTRODUCTION ..................................................................................... 1 1.1 Background ...................................................................................................................... 1 1.2 Literature Review ............................................................................................................. 1 1.3 Business Model ................................................................................................................ 2 1.3.1 Business Needs ......................................................................................................... 2 1.3.2 Business Environment .............................................................................................. 2 1.3.3 Stakeholder Analysis ................................................................................................ 5 1.3.4 System Vision Document ......................................................................................... 5 1.3.5 Project Management ................................................................................................. 6 1.3.6 Development Environment ..................................................................................... 112 CHAPTER TWO: REQUIREMENTS ................................................................................. 14 2.1 Gathering Requirements ................................................................................................. 15 2.2 System Problem Statement ............................................................................................ 15 2.3 Functional, Non-Functional Requirements and System Constraints ............................. 15 2.4 System Models ............................................................................................................... 18 2.4.1 Use Case Model ...................................................................................................... 18 2.4.2 Domain Class Model............................................................................................... 20 2.4.3 Use Cases Descriptions "Scenarios" ....................................................................... 22 2.4.4 Activity & System Sequence Models ..................................................................... 38 2.4.5 Statechart Model (optional) .....................................Error! Bookmark not defined.3 CHAPTER THREE: DESIGN .............................................................................................. 42 3.1 Architecture and Deployment environment Design ....................................................... 42 3.2 Software Architecture Design ........................................................................................ 42 3.3 Sequence Models............................................................................................................ 42 3.4 Design Class Model ....................................................................................................... 43 3.5 Design package model ( optional) .................................................................................. 43 3.6 Design the database ........................................................................................................ 43 3.6.1 Design Entity-Relationship Model ......................................................................... 43 49
  53. 53. 3.7 Design the system and user interfaces............................................................................ 43 3.8 Design the system security ............................................................................................. 434 CHAPTER FOUR: IMPLEMENTATION ........................................................................... 43 4.1 Generate Design class model to specific programming language syntax ...................... 43 4.2 Generate Entity-Relationship model to SQL script........................................................ 43 4.3 Building your code ......................................................................................................... 445 CHAPTER FIVE: TESTING ................................................................................................ 44 5.1 Unit Testing .................................................................................................................... 44 5.1.1 Set cases test ........................................................................................................... 44 5.2 Integration Testing ......................................................................................................... 45 5.3 Other Testing( optional) ................................................................................................. 456 CONCLUSIONS AND FUTURE WORK ........................................................................... 45 6.1 Conclusion...................................................................................................................... 45 6.2 Future work .................................................................................................................... 45References ..................................................................................................................................... 467 Appendices ............................................................................................................................ 47 7.1 Appendix A .................................................................................................................... 47 7.2 Appendix B .................................................................................................................... 48 50

×