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 Software/Technology used: Use algorithms for pulling information database populated from through PubMed API, Use MySQL database with powerful search PubMed 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, Software/Technology used: Using key-based search algorithm to MESH term, author 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 Software/Technology used: Using a SQL search procedure to search directory user database. Feasibility Evidence: Providing accurate search result. CR-4: User profile page Software/Technology used: GUI developing Tools, PHP, HTML, with list of personal MySQL MESH interests, articles, Feasibility Evidence: This page should be user-friendly and give the CV members an accurate perspective of other publications members’ and researches. Referred use case diagram: UC-8, UC-12 CR-5: Discussion board Software/Technology used: Discussion Board COTS (posting/responding to Feasibility Evidence: The COTS should be fully integrated with topics) other modules in the system. Referred use case diagram: UC-4, UC-5, UC-6 CR-6: Private messaging Software/Technology used: Messaging COTS system Feasibility Evidence: The COTS should be fully integrated with (send/receive/history) other modules in the system. Referred use case diagram: UC-9, UC-10, UC-11 CR-7: Personal Software/Technology used: JavaScript list Feasibility Evidence: Cross-Browser diagram that give the users a visual perspective of other collaborations. members’ Referred use case diagram: UC-7
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
FED_FCP_F12a_T01_V1.5.docx