1 / 30

Team P5T Presentation, Proposal, and Paper Program Permissions Tool

Team P5T Presentation, Proposal, and Paper Program Permissions Tool. Richard Laughlin Alexander Kelley James Fitzgerald Jacob Siegel. Sponsor: Nathan Claes, PhD US Veterans Affairs : Center of Excellence for Suicide Prevention. *Agenda. Project Background Scope and Requirements

Samuel
Download Presentation

Team P5T Presentation, Proposal, and Paper Program Permissions Tool

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Team P5T Presentation, Proposal, and Paper Program Permissions Tool Richard Laughlin Alexander Kelley James Fitzgerald Jacob Siegel Sponsor: Nathan Claes, PhD US Veterans Affairs : Center of Excellence for Suicide Prevention

  2. *Agenda • Project Background • Scope and Requirements • Process Methodology • Design • Testing and Risks • Future Plans • Reflection • Questions

  3. Project Background • Program Tracking • Program Status • Storage of related documents • Reviews and Approval Tracking • Webcrawler • Grants • Citations

  4. Scope & Requirements

  5. Scope • Web application that tracks research programs, their artifacts, and archives all content for auditing purposes. • Web crawler that finds citations and grants, updating the web application automatically.

  6. Requirements Elicitation • Started with given project description • Met several times to ask for clarifications and to break down into individual requirements.

  7. Requirements • Technology Requirements • Functional Requirements • Security Requirements • FIPS 197 • Accessibility Requirements • Section 508

  8. Technology * Required

  9. Process Methodology

  10. Process Model • Spiral / Evolutionary Prototyping • Frequent prototypes for sponsor evaluation • Frequent risk analysis • Generate different paths to reach “win condition”

  11. Release Schedule

  12. R1 Schedule Goal: Minimize risk of errors in requirements elicitation.

  13. R2 Schedule Goal: Minimize risk from lack of expertise in building data mining tools.

  14. R3 Schedule Goal: Incorporate sponsor feedback.

  15. Metrics Product Metrics • System Response Time • Query Response Time • Comment Density Future • Crawler Speed • Links / Crawled Page Process Metrics • Δ Worked Hours • Δ Risk • Time Between Cycles • Time / Phase / Week

  16. Design

  17. Design Process • Incrementally and Iteratively adjusted during each release.

  18. Database • Simplified • Typing Specifications Researcher -First Name -Middle Initial -Last Name -Primary Affiliation -Title -Phone -E-mail -Secondary Affiliation(s) -Title(s) -Phone(s) -E-mail(s) +Related Products +Related Grants

  19. Database

  20. UML

  21. Crawler

  22. UI Design

  23. Testing & Risks

  24. Risks

  25. Testing • User acceptance testing • UI • Main program features

  26. Current Status • R1 has been delivered to the sponsor. • R2 has been completed and the results have been used to adjust the risk assessment. • R3 is currently in-progress.

  27. Future Plans • Finish web client development. • Design and build web crawler • Finds citations and grants

  28. What Went Well? • Good team communication • Good rapport with sponsor • Completed most of the client requirements in two cycles

  29. What Went Poorly? • Minor schedule slide • Artificial deadlines • Some environment setup problems • Delay with VM setup • MS SQL issues • Metric collection / usage issues.

  30. Questions?

More Related