http://agile.csc.ncsu.edu/iTrust/wiki/ 2009-11-23T14:01:47-05:00 http://agile.csc.ncsu.edu/iTrust/wiki/ http://agile.csc.ncsu.edu/iTrust/wiki/lib/images/favicon.ico text/html 2009-11-02T10:48:52-05:00 http://agile.csc.ncsu.edu/iTrust/wiki/doku.php?id=acceptance_test_plan&rev=1257176932 Here is a set of acceptance test cases for each of the new functionality added to iTrust. A more complete set of tests can be found in the source code, but here is a set of acceptance test cases to be used when grading. UC2 Acceptance Test ID Description Expected Results Actual Results addPublicHealthAgent Preconditions: -> Admin 9000000001 is a registered user of the iTrust system. -> Admin 9000000001 has authenticated successfully. Steps: 1. Admin 9000000001 clicks the “Add PHA… text/html 2009-08-14T10:02:29-05:00 http://agile.csc.ncsu.edu/iTrust/wiki/doku.php?id=design_notes&rev=1250258549 Here are some archetype classes that the system uses. In adding new code, please keep using the appropriate responsibilities for each class type. Action Each JSP uses exactly one Action class. These classes are the ones that integrate all of the other classes together to form the feature. For example, the Action class will take in parameters, validate the information, perform some “business logic” if needed, then pass the information over to the DAO for database interaction. Methods in Ac… text/html 2008-08-12T09:26:37-05:00 http://agile.csc.ncsu.edu/iTrust/wiki/doku.php?id=developing_requirements_sp08&rev=1218547597 UC22: Flow of Events for the Schedule Appointments Use Case 22.1 Precondition: A patient and LHCP are registered users of the iTrust Medical Records system [UC1 and UC2]. The iTrust user has authenticated himself or herself in the iTrust Medical Records system [UC3]. text/html 2009-08-30T12:59:33-05:00 http://agile.csc.ncsu.edu/iTrust/wiki/doku.php?id=home_deployment_instructions&rev=1251651573 Back to start Downloads To install iTrust on your home system, download and install the following packages. Eclipse v3.5 Windows, OS X (Carbon) Unzip the program files to a permanent location JDK v1.5 or above Download the Java JDK and not the JRE package. Also, do not confuse this with the Java EE SDK. Any update for version 1.5 (eg v5) will do; you do not need NetBeans nor the Source Code (though the source can be helpful). Apache Tomcat v5.5.27 Download the core zip, unzip into desi… text/html 2009-06-25T10:15:46-05:00 http://agile.csc.ncsu.edu/iTrust/wiki/doku.php?id=housekeeping&rev=1245939346 Between each semeseter, a bit of effort is needed to clean up the iTrust code and evaluate the state of the project. Among the types of actions are: * Updating automated tests * Fixing or clarifying the document * Discussions of the future of the project * Minor features * Cosmetic changes * Refactoring * Changing technologies (IDE, etc.) text/html 2009-08-14T10:53:40-05:00 http://agile.csc.ncsu.edu/iTrust/wiki/doku.php?id=how_do_i&rev=1250261620 The following page is a set of FAQs that have been put together by past and present CSC 326 TAs and students. Some of these ought to be considered advice, which we encourage you to use with appropriate discernment. If you have something you would like to add or modify, please contact your current TA or an iTrust project admin. text/html 2008-11-07T01:10:09-05:00 http://agile.csc.ncsu.edu/iTrust/wiki/doku.php?id=itrustsecurity&rev=1226038209 Please post your security issue and your name. Andrew Austin, Section 202: - Login as a Patient, then type following url: http://aramis.csc.ncsu.edu:8080/iTrust/auth/patient/survey.jsp?ovID=-1&ovDate=%3Cscript%3Ealert(%22hi%22)%3C/script%3E - Login as Patient, Click “Edit My Demographics” Enter ”><script>alert(“hi”)</script>” as your first name, click “Edit Patient # text/html 2009-09-09T18:02:57-05:00 http://agile.csc.ncsu.edu/iTrust/wiki/doku.php?id=lab_deployment_instructions&rev=1252533777 This tutorial will help you set up iTrust in the lab. Eclipse in the Lab Start Eclipse. The shortcut to Eclipse should be in the Start menu. When Eclipse loads, you will be in the default workspace, similar to the workspace shown below. Setting up Tomcat After Eclipse has started and you are in the default workspace, you should see a project called “Servers” already in the package explorer. This means already has Tomcat set up for this workspace. If, for some reason, you need to se… text/html 2008-04-24T18:52:36-05:00 http://agile.csc.ncsu.edu/iTrust/wiki/doku.php?id=lauren791e&rev=1209077556 Note: This page has been created for Lauren Hayward and Aaron Massey's CSC 791e project. Please do not make revisions or delete. Contact Lauren at ljhaywar@ncsu.edu if you have questions. Lauren's paper notes lauren791enotes ---------- NOTE: This table of contents has been added explicitly because DokuWiki does not have the ability to generate a printable version of its pages. As a result, the automatically generated table of contents does not print. If there are any errors here, … text/html 2008-04-22T23:45:11-05:00 http://agile.csc.ncsu.edu/iTrust/wiki/doku.php?id=lauren791enotes&rev=1208922311 Ideas for Paper.... Transitioning from Use Cases to Traditional Requirements * Asked questions from the book * Removed ambiguity, but described the point of the requirement without giving implementation details * Recorded the context and rationale to maintain that sometimes get lost text/html 2009-08-25T13:53:28-05:00 http://agile.csc.ncsu.edu/iTrust/wiki/doku.php?id=list_of_bugs&rev=1251222808 RESOLVED: Laboratory Procedures NullPointer Found while checking failing HTTPtests -> testInputLabResults in edu.ncsu.csc.itrust.http.LabProceduresTest PROBLEM: On my laptop, MySQL 5.1 and the result set getLong() command return (4294968251) instead of (955) for office visit ID. text/html 2008-11-12T21:52:36-05:00 http://agile.csc.ncsu.edu/iTrust/wiki/doku.php?id=mid_listing&rev=1226544756 MID Listing List all the places you've seen the MID on a page as part of the static or dynamic html as well as all the times you see the MID in the URL. Patient: - <http://localhost:8080/iTrust/auth/patient/viewMyRecords.jsp> - <http://localhost:8080/iTrust/auth/patient/viewPersonnel.jsp?mid=9000000000> - <http://localhost:8080/iTrust/auth/patient/addappointmentrequest.jsp?hintMID=9000000000> - <http://localhost:8080/iTrust/auth/patient/viewOfficeVisit.jsp?ovID=1031> - <http://localh… text/html 2008-02-21T11:35:01-05:00 http://agile.csc.ncsu.edu/iTrust/wiki/doku.php?id=printpage&rev=1203611701 UC23 View Comprehensive Patient Report Use Case 23.1 Precondition: An LHCP and Admin have authenticated themselves in the iTrust Medical Records system [UC2]. 23.2 Main Flow: The LHCP requests a comprehensive patient report for a particular patient [S1]. The Admin can either approve [S2] or reject [E3] the report. Upon approval, the LHCP chooses to view the approved comprehensive patient report [S3] from a list of his/her requests. The events of requesting, approving/rejecting, and viewing… text/html 2009-10-31T19:50:52-05:00 http://agile.csc.ncsu.edu/iTrust/wiki/doku.php?id=requirements&rev=1257033052 Version 18 October 14, 2009 Project Team: You Your Partner/Team Document Authors: Laurie Williams Tao Xie Andy Meneely Lauren Hayward Return to iTrust Homepage Introduction This project involves the development of an application through which doctors can obtain and share essential patient information and can view aggregate patient data. Currently, access to a patient's history regarding previous medical problems, previous surgery, medications, allergies and other factors is ofte… text/html 2009-08-18T16:46:55-05:00 http://agile.csc.ncsu.edu/iTrust/wiki/doku.php?id=roadmap&rev=1250628415 Since the primary source of development is by students, the versions of iTrust are based on semesters. Source Code The source code for iTrust was originally from the CSC 712: Software Reliability and Testing semester project. Since then two types of development have been made: development during semesters with students and development between semesters to refactor and redesign the code. text/html 2008-03-17T19:49:29-05:00 http://agile.csc.ncsu.edu/iTrust/wiki/doku.php?id=sample_raf&rev=1205797769 Date: Project Name: Team Members: “Burn Down” Data Estimate of Hours Remaining Status [Done, Started, Not Started] Iteration 0 Iteration 1 Iteration 2 UC1 UC2 UC4 UC6 UC8 UC9 UC10 Non Func. 4.2 Constraint 5.7 Other items . . . Burn Down Chart (use excel to graph the history of how much more work you feel you have left on the project using data from the above table) text/html 2009-08-17T17:38:58-05:00 http://agile.csc.ncsu.edu/iTrust/wiki/doku.php?id=start&rev=1250545138 Welcome to the iTrust wiki!! iTrust was founded as a class project for Software Engineering at North Carolina State University, and is now maintained by the RealSearch Research Group. iTrust was aimed to teach various testing methods and automatic testing techniques in the curriculum of the course. iTrust is a medical application that provides patients with a means to keep up with their medical history and records as well as communicate with their doctors, including selecting which doctors to b… text/html 2009-01-09T19:11:36-05:00 http://agile.csc.ncsu.edu/iTrust/wiki/doku.php?id=summer08housekeeping&rev=1231546296 Back to main housekeeping page Stuff we did * Try to get rid of the DAOFactory “doubleton”. If anything, remove the DAOFactory.getTestInstance() part and move it into a test util. This should make using the EvilTestConnectionDriver more intuitive to use. * Combine or otherwise organize the test data * Fix the date-sensitive unit tests * Make sure removeCODTrends bug in the sql file is not there * Update the developer notes, no new details, just make sure everything is okay * … text/html 2009-08-13T22:26:47-05:00 http://agile.csc.ncsu.edu/iTrust/wiki/doku.php?id=summer09housekeeping&rev=1250216807 Task Person Status Talk to Trey about getting SVN set up, and the lab Andy & Jason Open Update the lab deployment instructions for Eclipse 3.5 and current lab setup Open Get mock objects started: test utilities, a variety of examples Andy Open Write the mock object tutorial Andy Open Get MySQL, wikis, Bugzilla running on the VCL 326 server Andy Open Look for dead classes, dead JSPs, and dead tables Open... On this note: Check out this cool nugget I found Go find specifi… text/html 2008-03-21T11:46:30-05:00 http://agile.csc.ncsu.edu/iTrust/wiki/doku.php?id=team_project_inspection&rev=1206114390 Below are most of the questions and comments we received during the requirements inspection in lab. UC24 * The survey is assumed to be optional, is that correct? Also, it is assumed to have no expiration date, is that true? * Yes. Yes. * We are assuming that the user cannot view past results, is that ok? * Yes. I have updated UC 9 to reflect this. text/html 2009-08-12T08:34:09-05:00 http://agile.csc.ncsu.edu/iTrust/wiki/doku.php?id=test_data&rev=1250080449 Here is where we keep track of a base set of test data for iTrust. The actual source code has a much more complete set of test data that can be used in different situations, but this is a place where we define a the standard set of test data that all developers start with. text/html 2009-01-12T18:12:33-05:00 http://agile.csc.ncsu.edu/iTrust/wiki/doku.php?id=winter09housekeeping&rev=1231801953 What we did * Removed appointments, appointment requests, and all corresponding artifacts entirely. * Synchronized with the best team's latest manual blackbox test plan. * Anonymized (removed all references to the team members, or their passwords) * Hid err.txt, a file which is required by the MockObject for System.out, away from the developer. * Several HTTPUnit tests had class names which reflected their use case numbers. These were renamed to give a short description of the functi…