Business Case Analysis Assumptions People are willing to use an electronic system for collaboration Increased collaboration improves research Stakeholders (Who) Initiatives (What) Value Propositions (Why) Beneficiaries (For Whom) Developers PTS marketing team PTS research team Web master Database administrator Develop System Market the project and get people to sign up. Promoting success stories. Collect statistics on injuries Train the web master. Increase research collaborations between members of PTS. Improve education and research. Reduce number of injuries for children. Reduce the burden on hospitals and clinics. Members of PTS The medical field Children Parents Hospitals, Clinics, Society Cost Developer Personnel Training (Developers, Webmaster) Maintenance Infrastructure expenses (e.g. Web Hosting/Server) Benefits Number of members’ published papers Hours that each member spend for researching
Analysis: By using these kinds of strategies we can use test-based developing to reduce downtime. For example we can simulate the system to examine its performance in different situation and queries. Capability Feasibility Table : Capability Requirements and Their Feasibility Evidence Capability Requirement Product Satisfaction CR-1: Custom searchable database populated from PubMed Software/Technology used: Use algorithms for pulling information through PubMed API, Use MySQL database with powerful search procedures. Feasibility Evidence: Our application and PubMed should Talk to each other smartly and also the database should be fully optimized. CR-2: Search by keyword, MESH term, author Software/Technology used: Using key-based search algorithm to search among database base. Feasibility Evidence: The algorithms should work properly. This means that the result of query should be related to the MESH terms. Referred use case diagram: UC-3, UC-13, UC-14, UC-15 CR-3: Search member directory Software/Technology used: Using a SQL search procedure to search user database. Feasibility Evidence: Providing accurate search result. CR-4: User profile page with list of personal MESH interests, articles, CV Software/Technology used: GUI developing Tools, PHP, HTML, MySQL Feasibility Evidence: This page should be user-friendly and give the members an accurate perspective of other members’ publications and researches. Referred use case diagram: UC-8, UC-12 CR-5: Discussion board (posting/responding to topics) Software/Technology used: Discussion Board COTS Feasibility Evidence: The COTS should be fully integrated with other modules in the system. Referred use case diagram: UC-4, UC-5, UC-6 CR-6: Private messaging system (send/receive/history) Software/Technology used: Messaging COTS Feasibility Evidence: The COTS should be fully integrated with other modules in the system. Referred use case diagram: UC-9, UC-10, UC-11 CR-7: Personal list Software/Technology used: JavaScript Feasibility Evidence: Cross-Browser diagram that give the users a visual perspective of other members’ collaborations. Referred use case diagram: UC-7
Risk Assessment Table 9: Risk Assessment Risks Risk Exposure Risk Mitigations Potential Magnitude Probability Loss Risk Exposure Inability to connect with PubMed 8 5 40 Test PubMed API and Alert System If COTS products which we choose do not meet the needs of the users. 4 7 28 Get client and board feedback, COTS assessment, Prototyping COTS cannot talk to each other 2 3 6 COTS assessment, Test Demo versions, Prototyping Staffing availability (database manager, moderator) 4 4 16 Get client and board feedback, Business Case Analysis Lack of developer skills 3 5 15 Training, Consider other programming language Current host database size limitation 2 3 6 Estimate Database size, Work with limitation, Consider other host services Response time does not meet target 6 3 18 Consider Solr, Lucene solutions, Prototyping