Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community for help and clear up your study doubts
Discover the best universities in your country according to Docsity users
Free resources
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
Material Type: Project; Class: Survey of Energy and Power for a Sustainable Future; Subject: Aerospace and Mechanical Engineering; University: University of Southern California; Term: Spring 2005;
Typology: Study Guides, Projects, Research
1 / 40
This page cannot be seen from the preview
Don't miss anything!
Jewel Ward
Project Manager: Maxim Krivokon Developer: Bo Lee Developer: Genesan Kim Developer: Vu Nguyen IV&Ver: Shing-Cheung Chan IV&Ver: Marie Chi IV&Ver: Kristine Guevara qkd2cl-861710-3353391-frd-rlca-s05b-t07-v4-3-doc.doc Version Date: 2/9/
Feasibility Rationale Description (FRD) Version no 4. 3
Date Author Version Changes made 10/10/04 Hui-Hsien Chi v1. Initial draft 10/18/04 Hui-Hsien Chi v1. Correct some grammar mistakes Change section 2.1.4 and 2.1. Add one more risk in section 4 10/24/04 Hui-Hsien Chi v2. Change section 2.1.5 and 2.2. Modified and clarified the risk in section 4 Add section 2.2.5 and 2.2. 11/14/04 Hui-Hsien Chi v3. Change section 2. Change section 3. Section 4, add contingency plan for risks Change section 5 11/29/04 Hui-Hsien Chi V3. Modify section 2. Modify section 4 12/05/04 Hui-Hsien Chi V3. Add COCOMO to estimate requirement for section 3. Add COTS table on section 5. Modify section 2.1. Modify section 2.2 to match OCD, SSAD, and SSRD 1/24/05 Genesan Kim V4. Modified section 2. Added stakeholder concurrence table in section 2. 1/25/05 Genesan Kim V4. Modified section 3. 1/30/05 Genesan Kim V4. Modified section 4 to update current risks 2/2/05 Genesan Kim V4. Modified section 2.1, added new ROI graph qkd2cl-861710-3353391-frd-rlca-s05b-t07-v4-3-doc.doc ii
Feasibility Rationale Description (FRD) Version no 4. 3 qkd2cl-861710-3353391-frd-rlca-s05b-t07-v4-3-doc.doc iv
A.1. Introduction A.1.1 Purpose of the Feasibility Rationale Description Document The purpose of this document is to rationalize development decision of the Data Mining of Digital Library Usage Data application. It shall ensure that all the system elements have been demonstrated satisfying the success-critical stakeholders in the OCD and LCP, meeting the requirements described in the SSRD, and using the specified architecture defined in the SSAD. The FRD represents that the life cycle process will: -Satisfy the requirements -Support the operational concept -Match the budgets and schedules The target audiences of the FRD are stakeholders described in OCD, and the people in the Architecture Review Board (ARB). A.1.2 References MBASE Guidelines version 2.4. http://cse.usc.edu/classes/cs577a_2004/guidelines/MBASE_Guidelines_v2.4.1.pdf MBASE Version 2.4.1 Templates for FRD (version 1a) http://cse.usc.edu/classes/cs577a_2004/guidelines/MBASEtemplates/ FRD_Templatev1a.doc “Data Mining of Digital Library Usage Data” Project Description http://sunset.usc.edu/classes/cs577a_2004/projects/description/project7.htm MBASE Electronic Process Guide http://cse.usc.edu/research/MBASE/EPG USC Copyright Agreement http://cse.usc.edu/classes/cs577a_2004/forms/CopyrightAgreementV1.html Fall 2004 CS 577a Project #7 Description http://sunset.usc.edu/classes/cs577a_2004/projects/description/project7.htm qkd2cl-861710-3353391-frd-rlca-s05b-t07-v4-3-doc.doc 1
Fall 2004 CS 577a Project #7 LCO portion of OCD http://seacliff.usc.edu/~team7/LCO/OCD_LCD_F04a_T 07 _V02.0.doc Fall 2004 CS 577a Project #7 Prototype for LCO http://seacliff.usc.edu/~team7/LCO/Prototypes/Prorotype_LCO_F04a_T 0 7_V01.0.doc Fall 2004 CS 577a Project #7 Prototype for SSRD http://seacliff.usc.edu/~team7/LCO/SSRD_LCO_F04a_T 0 7.doc Fall 2004 CS 577a Project #7 Prototype for SSAD http://seacliff.usc.edu/~team7/LCO/SSAD_LCO_F04a_T 0 7.doc Fall 2004 CS 577a Project #7 Prototype for LCP http://seacliff.usc.edu/~team7/LCO/LCP_LCO_F04a_T 0 7.doc Fall 2003 CS 577a Project # 3 LCO portion of FRD http://ebase.usc.edu/eservices/cs577a_2003/team 03 a/LCO/FRD_LCO_F03a_T 03 .pdf Fall 2003 CS 577a Project # 8 LCO portion of FRD http://ebase.usc.edu/eservices/cs577a_2003/team 08 a/LCO/FRD_LCO_F03a_T 08 .pdf Fall 2003 CS 577a Project # 11 LCO portion of FRD http://ebase.usc.edu/eservices/cs577a_2003/team 11 a/LCO/FRD_LCO_F03a_T 11 .pdf Fall 2003 CS 577a Project # 17 LCO portion of FRD http://ebase.usc.edu/eservices/cs577a_2003/team 17 a/LCO/FRD_LCO_F03a_T 17 .pdf Fall 2003 CS 577a Project # 32 LCO portion of FRD http://ebase.usc.edu/eservices/cs577a_2003/team 32 a/LCO/FRD_LCO_F03a_T 32 .pdf USC Information Services Division http://www.usc.edu/isd/about/about.html Dr. Bollen, Johan presentations http://www.cs.odu.edu~jbollen/presentations/facstaff_02_28_03.pdf http://www.cs.odu.edu/~jbollen/presentations/ecdl02.pdf http://www.cs.odu.edu/~jbollen/presentations/aisti04.pdf A.1.3 Change Summary -Clarified the risks base on the ARB comments. -Gave more specific contents of project benefit -Changed the document to approach the change of OCD, SSRD, and SSAD. -Changed the document to consist the priorities, process and resources. -Modified the product features. qkd2cl-861710-3353391-frd-rlca-s05b-t07-v4-3-doc.doc 2
Total personnel costs = $ The detail information of the personnel time cost is described in the [LCP 5.2]. In addition, this system is going to be developed using the existing software and hardware that belong to USC ISD/USC CES. Thus, the cost of software and hardware should not be an issue of this project. This relates to our win condition of the WinWin Negotiation building the project with no budget, coding the system in-house, and using open-source/ freeware. Hardware costs: Development team will use personal workstations and computing facilities provided by the USC Information Services Division. The proposed application is standalone and therefore does not require hosting facilities to be tested. Total hardware costs = $ Software costs: Project will use the following open source components which are available at no cost: SQLite, H3Viewer, Open Motif. The following free open source development tools will be used: gcc, make, autoconf etc. Project management will be done using software tools licenses for which are provided with no cost as part of the class: Rational Rose, Microsoft Project. Total software costs = $ Facilities: Development team will use USC campus facilities for team meetings, and other development activities. Total facilities cost = $0; Total development costs = Personnel costs + Hardware costs + Software costs + Facilities costs = $ 2.1.2 Transition Cost The proposed system will be a brand new system developed for analyzing usage log and generating reports of usage log analysis. Thus, training time is one of the transition cost to be incurred in this project. The system will also use open-source, so there is no transition cost of COTS licenses. The system will not purchase any equipment because it is going to use existing equipment in USC library. The following is a breakdown of all costs that are a part of the transition process. Training Costs: Trainer preparation time = 4 hours. Since training preparation will be done by the development team, cost = $0. Client will be trained as an administrator of the system, and will be given instructions on how to analyze log data using the system and distribute results of qkd2cl-861710-3353391-frd-rlca-s05b-t07-v4-3-doc.doc 4
the analysis to regular users. Client training time = 4 hours; Average client salary = $35 per hour. Therefore cost = 4 * $35 = $140. Library staff users will be trained on how to visualize analyzed data received from the admin using the system. Number of users = 5; Training time = 4 hours; Average salary = $25 per hour. Thus, cost = 5 * 4 * 25 = $500. Maintainer training time = 4 hours; Average maintainer salary = $30 per hour. Cost = 4 * $30 = $120. Total training costs = $140 + $500 + $120 = $ Data preparation: The system will use the log data provided by existing Digital Archive system. This data is provided as part of normal functioning of the DA system and therefore does not incur any costs. Data preparation costs = $0; COTS licenses: Proposed system uses only open source and free components. COTS licenses costs = $ Operational readiness testing: This testing will be done by the client through comprehensive evaluation of major functionality of the system. Estimated testing time = 2 hours; Average client’s salary = $35. Cost = 2 * 35 = $70. Total testing costs = $ Site preparation: The proposed system is a standalone application which can be installed on any workstation running Mac OS X, which does not require any special preparations Site preparation costs = $ Facilities preparation: Proposed system does not require use of any specialized facilities. Facility preparation costs = $ Equipment purchase: The developed system will be installed on existing Digital Library equipment and also on personal workstation of the client, therefore no equipment will be purchased. Equipment cost: = $ Total transition cost = $760 + $70 = $ qkd2cl-861710-3353391-frd-rlca-s05b-t07-v4-3-doc.doc 5
and 5 Library employees, and it will make updating of Library Collections more efficient. Currently there is no automated system that helps Library employees to make decisions on which collections are important, which new areas of interest are emerging and which items could be removed from the collection, since they are not being used. Currently 5 Library employees spend 5 hours per week for maintaining and developing digital collections. Also the Digital Archive manager spends 10 hours per month of her time for manual usage log analysis and coordination of development efforts of Library staff. Average salary of Library staff is $25 per hour. Average salary of Library project manager is $35 per hour. Thus current costs per year are = 5 * 5 * 48 * 25 + 10 * 12 * 35 = $34200 per year. The proposed system will make this process more efficient in the following way: each of 5 library employees now will have to spend only 3 hours per week evaluating results of usage data analysis and making decisions on collection updates. Digital Archive manager will use the developed system to produce usage analysis data and will spend 5 hours per month doing that. Thus improved cost will be = 5 * 3 * 48 * $25 + 5 * 12 * $35 = $20100 per year. Thus savings = $14100 per year. Total cost of the system = Development cost + Transition cost = $6300 + $830 = $7130. Maintenance cost = $7200. Table 1 : < Return on Investment > 1st year 2nd year 3rd year 4th year 5th year Costs saved $0 $ 14100 $ 14100 $ 14100 $ 14100 Cumulative costs saved
Cost of the system
Cumulative costs of the system
qkd2cl-861710-3353391-frd-rlca-s05b-t07-v4-3-doc.doc 7
Return on Investment (^0) **-0.
-0. 0
0 1 2 3 4 5 Number of Years ROI Figure 1 – Return on Investment A.2.2 Requirements Satisfaction** This section explains how and why the proposed system will meet the specific architecture of SSAD and satisfy the system requirements of OCD and SSRD. 2.2.1 Operational Concept Satisfaction This section shows how the project satisfies the operational concept which is listed in the [OCD 4]. Below is the list of the concepts from the [OCD 4] Table 2 : < Operational Concept Satisfaction – System Capabilities> Operational Concept C-01:^ Manage Usage Log Data Description The proposed system shall provide a tool or method to import usage data form log file into the local database. The [SSRD 2.1. SR-1] defined the requirement of this system capability. Therefore, it completely satisfies the [OCD 4.3.1 SC-01] Reference OCD 4.3.1 C-01 and SSRD 2.1.1 SR- Operational Concept C-02:^ Log Analysis qkd2cl-861710-3353391-frd-rlca-s05b-t07-v4-3-doc.doc 8
Table 4 : < Project Requirements Satisfaction> Project Requirements PR-1: Limited schedule Requirements Satisfaction Since this project is a part of cs577a course work, there is a limited schedule. The project needs to be implemented in 24 weeks, and it is distributed into four stages of development (inception, elaboration, construction and transition). The [LCP 2] has complete milestone and schedule of the system developing. Also, the [LCP 4] describes the plans of the project. It shows how the project approaches those milestone and schedule. Therefore, these plans and schedule demonstrate the project can be implemented in 24 weeks. The [LCP 2] and [LCP 4.1] completely satisfies the [SSRD 2.1 PR-1] Reference SSRD 2.1 PR-1, LCP 2 and LCP 4 Project Requirements PR-2: No budget Requirements Satisfaction From the Winwin negotiation, one of the win conditions is no budget for this project, and it is also defined in the [SSRD 2. PR-2]. In the [LCP 5.2] and the [FRD 2.1.1], we described why there is no budget in this project. This is due to several reasons, such as no developer cost, no hardware cost, and no software cost. Reference SSRD 2.1 PR-2, LCP 5.2, and FRD 2.1. Project Requirements PR-3:Use MS Project for scheduling and progress tracking Requirements Satisfaction The [LCP 4.2] described the system will use MS project for tracking and planning the project. This completely satisfies the [SSRD 2 PR-3] Reference SSRD 2.1 PR-3 and LCP 4. Project Requirements PR-4: Use GNU compilation tools Requirements Satisfaction The [LCP 4.2] production stage, described the system will use GNU for developing the system. This completely satisfies the [SSRD 2.2 PR-4] Reference SSRD 2.2 PR-3, and LCP 4. Project Requirements PR-5: Use efficient development language with 3d visualization capabilities Requirements Satisfaction In the [LCP 4.2] production stage, it has defined the developed team use C/C++ for coding user interface. This matches the [SSRD 2.2 PR-5]. Reference SSRD 2.2 PR-5, and LCP 4. Project Requirements PR-6: Use UML for modeling and design Requirements Satisfaction The [LCP 4.2] has described the develop team uses Rational Rose for building UML diagram. That shows the team will use qkd2cl-861710-3353391-frd-rlca-s05b-t07-v4-3-doc.doc 10
UML for modeling and design of the project. This completely satisfies the [SSRD 2.2 PR-6]. Reference SSRD 2.2 PR-6 and LCP 4. Project Requirements PR-7: Use free components Requirements Satisfaction The [FRD 5.2] has listed all the open sources that will be used in this system. It satisfies this requirement. Reference SSRD 2.2 PR-7, and FRD 5. Project Requirements PR-8: Target operating system is Mac OS X Requirements Satisfaction The proposed system shall be able to use on Mac OS X. The [LCP 2.2.2] has scheduled the transition preparation which defines that the system will be compiled for UNIX and Mac OS X. Reference SSRD 2.2 PR-8, and LCP 2.2. Project Requirements PR-9: Use visualization component that provides interactive 3d interface. Requirements Satisfaction The result of the usage analysis should be present as 3D hyperbolic view. In the [LCP 4.2], the production stage has described that the develop team will use an open source, H3viewer, to implement the proposed system. Therefore, this plan matches [SSRD 2.2 PR-6] Reference SSRD 2.2 PR-9, and LCP 4. Project Requirements PR-10: Use data storage that does not require maintenance. Requirements Satisfaction The [LCP 4.2] production stage, described the system will use SQLite for storing the data. Also, the [FRD 5.2] has the reason of why we chose this open source for storing the data. This completely satisfies the [SSRD 2.2 PR-10] Reference SSRD 2.2 PR-10 and LCP 3 Project Requirements PR-11: Input data format compatibility Requirements Satisfaction The proposed system should be able to parse the usage data from log file. The [SSAD 3.1.7.1] has defined that the proposed system will provide an interface to import log data, and it can be able to check and parse the data. Reference SSRD 2.2 PR-11, and SSAD 3.1.7. Project Requirements PR-12: Well documented code Requirements Satisfaction There are several peer reviews during the production stage. These reviews have been planned in the [LCP 4.2.2], and the purpose of these reviews are to ensure that the system code is documented and can be approved by the client. These review plans in the [LCP 4.2.2] completely satisfy the [SSRD 2.2 PR- 12] qkd2cl-861710-3353391-frd-rlca-s05b-t07-v4-3-doc.doc 11
Table 5 :
Risks Data structure of DA database is changed Reference
qkd2cl-861710-3353391-frd-rlca-s05b-t07-v4-3-doc.doc 13
Title SR-2: Remove usage data from log files Description The proposed system should be able to remove the data from the local database. The [SSAD 4 .1.7.1.1] has described how the system will delete data from the local database, and also provided the activity of the delect data. Thus, This completely satisfies the [SSRD 3.2.1 SR-2]. Criticality High Technical Issue Need to have existing usage log’s data structure. Cost and Schedule There is no cost, and it is scheduled in the production stage. Dependencies Depends on DA database provide by Digital Library Side Effects The user needs to download log file from Apache server using FTP tool. Risks Data structure of Apache log files is changed Reference
qkd2cl-861710-3353391-frd-rlca-s05b-t07-v4-3-doc.doc 14
