Feasibility Evidence Description (FED)

Transcription

1 Feasibility Evidence Description (FED) BlackProfessionals.net Website Team No.6 Tian Xiang Tan Jhih-Sheng Cai Aril Alok Jain Pablo Ochoa Jeng-Tsung Tsai Sadeem Alsudais Po-Hsuan Yang Project Manager System/Software Architect Requirements Engineer Prototyper Operational Concept Engineer IIV & V Life Cycle Planner <11/25/2014>

2 Feasibility Evidence Description (FED) for Architected Agile Template Version 3.0 Version History Date Author Version Changes made Rationale 09/20/ /25/ /07/ /11/ /18/ /23/ /02/20 14 TX 1.0 l Create the first version of FED. l Add risk assessment. l Add Cost analysis l Add NDI/NCS Interoperability Analysis TX 1.1 l Refine the risk assessment. TX 2.0 TX 2.1 TX 2.2 TX 3.0 TX 3.1 l Modify the risk assessment, business analysis l Refine the Process Feasibility l Modify the benefit analysis l Refine the architecture feasibility. l Modify the document based on the feedback from IIV & V and ARB. l Refine the business analysis and architecture feasibility l Update the ROI analysis due to the feed back in ARB. l To fit CS577a course content l More risks are found in the team meeting. l More risks are found. l After communicating with clients, more details are known. l More information are collected, we can make more decision. l More information is gotten from the client. l Some factors are not considered previously. l Some parts in the document are not consistency with other documents. l More win conditions has been added. l Decision on architecture has been made. l Add pessimistic estimation in ROI analysis. ii

3 Feasibility Evidence Description (FED) for Architected Agile Template Version 3.0 Table of Contents Feasibility Evidence Description (FED)... i Version History... ii Table of Contents... iii Table of Tables... iv Table of Figures... v 1 Introduction Purpose of the FED Document Status of the FED Document Business Case Analysis Cost Analysis Personnel Costs Hardware and Software Costs Benefit Analysis ROI Analysis Architecture Feasibility Level of Service Feasibility Capability Feasibility Evolutionary Feasibility Process Feasibility Risk Assessment NDI/NCS Interoperability Analysis Introduction COTS / GOTS / ROTS / Open Source / NCS Connectors Legacy System Evaluation Summary iii

4 Feasibility Evidence Description (FED) for Architected Agile Template Version 3.0 Table of Tables Table 1: Personnel Costs... 8 Table 2: Hardware and Software Costs... 9 Table 3: Benefits of BlackProfessionals.net Table 4: ROI Analysis Table 5: Level of Service Feasibility Table 6: Capability Requirements and Their Feasibility Evidence Table 7: Rationales for Selecting Architected Agile Model Table 8: Risk Assessment Table 9: NDI Products Listing Table 10: NDI Evaluation iv

5 Table of Figures Figure 1: Program Model of Blackprofessioanls.net... 7 Figure 2: ROI Analysis Graph... 12

6 Feasibility Evidence Description (FED) 1 Introduction 1.1 Purpose of the FED Document The Feasibility Evidence Description of the website BlackProfessional.net is written to prove that the requirements of the project can be met. It provides the stakeholders in the project with the business case analysis of the website, the assessment of the risks that the team faces while developing and the NDI/NCS Interoperability analysis. The document also helps the stakeholders to determine whether the project should enter the next phase of development or not. 1.2 Status of the FED Document For now, our project is in the foundation phase, and we have refined the business case analysis, risk assessment and the architecture feasibility analysis. l A more detailed ROI analysis is provided. l The risk of time constraint is removed. l CG-8 and CG-9 is added. l Refine the LOS feasibility analysis. FED_FCP_F14_Team06_V3.0.doc 6 Version Date: 12/7/2014

7 2 Business Case Analysis Figure 1: Program Model of Blackprofessioanls.net Assumptions (Under what Business assumptions will this model be true) People feel more comfortable connecting to other people from same community People/Companies find it difficult to search for professionals based on ethnicity and culture Stakeholders Initiatives Value Propositions Beneficiaries Developers: Team 06 Acquirer: Prentice Parr Cost Hardware to host server Fee for web hosting services Maintenance Marketing Develop a new platform for connecting professionals based on ethnicity Marketing: Search Engine Optimization, Social Network Marketing, Academia Marketing, Marketing to Corporations Increase engagement experience of black professionals online Easier ways to connect with other black professionals Easier ways for recruiters to connect to black professionals Students Professionals Companies Benefits Create a more engaging environment. Metrics: the number of users who continuously use our website for a sufficiently long time (One year). Increase the number of prominent presence in professional domain. Metrics: the number of prominent in professional domain in our website. Increased employment numbers. Metrics: The number of people who get hired from our website. Decrease head hunting time. Metrics: The difference between the average time that used by the headhunters to hire people from our website and the average time they used to hire people before using the website. Decrease the time for job search. 7

8 Metrics: The difference between the average time that used by the students to search for a job from our website and the average time they used to search a job before using the website. Improved professional growth of people belonging to African-American community. Metrics: The number of professional people who belong to African-American. 2.1 Cost Analysis Since our team decide to use Ruby on Rails, PostgreSQL to develop the website and may deploy it on the AWS when finished. Therefore, the client doesn t need to spend money during the development. The client needs to spend at least 2 hours for regular client meeting. 2.2 Personnel Costs Development Period (24 weeks) Activities Table 1: Personnel Costs Time Spent (Hours) Exploration Phase: Time Invested (CSCI577a, 2 weeks) Client: Meeting via , phone, and other channels [(Client 7.5 Interaction * 1 * 3hours + Win Win Negotiation * 1 * 2.5 hours + 1 regular client meeting * 2hours) * 1 people] Client Representatives: Meeting via , phone, and other 0.5 channels Valuation and Foundations Phases: Time Invested (CSCI577a, 7 weeks) Client: Meeting via , phone, and other channels [( hour/week * 7) * 1 people] Client Representatives: Meeting via , phone, and other 16 channels [(7 regular client meetings * 2hours + Win Win Negotiation * 1 * 2hours) * 1 people] Architecture Review Board [(2 times * 2 hours) * 1 people] 4 Development and Operation Phases: Time Invested (CS577b, 12 weeks) Client: Meeting via , phone, and other channels [0.5hr/week 6 * 12week * 1 people] Maintainer: Meeting via , phone, and other channels 0 Architecture Review Boards and Core Capability Drive-through 4.5 session [1.5hr * 3 * 1 people] Deployment of system in operation phase and training 0 - Installation & Deployment 8

9 - Training & Support Total 42 Maintenance Period (1 year) Maintenance [1hr/week * 52] 52 Total Hardware and Software Costs Table 2: Hardware and Software Costs Type Product Name Cost Rationale Development Software Linked in API $0 (Linkedin API Allow our website can assess the License) users profile on Linked in. Software Adsense $0 Allow the advertisement displayed on our website. Software Rails $0 (MIT License) The framework for the system. Software Ruby $0 (Ruby License) Software PostgreSQL $0 (PostgreSQL The DBMS for the system. License) Software Phusion Passenger $0 (Apache HTTP Server. License) Software Apache $0 (2-Clause BSDlike license) HTTP Server. Hardware Heroku $0 The cloud application platform to deploy and test the system. Production Software Linked in API $0 Allow our website can assess the Software Adsense $0 users profile on Linked in. Allow the advertisement displayed on our website. Software Rails $0 The framework for the system. Software PostgreSQL $0 The DBMS for the system. Software Phusion Passenger $0 HTTP Server. Software Apache $0 HTTP Server. Hardware Amazon Service (m1.medium) Web $134 per year. The cloud application platform to deploy the system. 2.4 Benefit Analysis 9

10 Since the system serves to the public, we cannot get an exact number of users. Therefore, we estimate that there are 5,000 users in our system in 2016, 90% of them are students and 10% of them are hunters, companies, and organizations. Table 3: Benefits of BlackProfessionals.net Current activities & resources used % Reduce Time Saved (Hours/Year) The time to find the people with the same background Black people [5,000people * 0.5hour * 0.3reduction] The time to search the jobs for the black people Students and recent grade students [4,500people * 2hour * 0.3reduction] 30 2,700 The time to recruit the black people Head hunters, companies, organizations [500people * 2hour * 0.3reduction] Total 3, ROI Analysis Table 4: ROI Analysis For Optimistic Estimation: Year Cost Benefit Cumulative Cumulative (Effort Saved) Cost Benefit ROI 2015 $1, $0.00 $1, $ $53, $47, $54, $47, $59, $71, $113, $118, $66, $108, $180, $227, For Pessimistic Estimation: Year Cost Benefit Cumulative Cumulative (Effort Saved) Cost Benefit ROI 2015 $1, $0.00 $1, $ $53, $2, $54, $59, $4, $113, $66, $6, $180, Explanation for Cost: We calculate the effort paid by the client during the development (42hours * the average salary in America $15 per hour = $630) and the effort for managing the system in future (52hours per year * the average salary in America $15 per hour = $780 per year). Moreover, we also calculate the money spend in deploying the 10

11 project ($134 per year) and the money used to update the system. And here we assume that the client will hire 3 people to update the system in 3 months per year. That is $53, per year (the average salary for a ruby programmer is about $70,943 per year, see reference) and we assume that there is a 10% increment each year after For year 2015, since we deliver the system in May, therefore, we calculate the effort that client spent in the development ($630), the maintaining effort for half a year ($780 / 2 = $390) and the cost of deploying the system for half a year ($134 / 2 = $62), that is $1082. Reference (the average salary for ruby programmer): mmer/salary Explanation for the number of users: The number of users significantly affect the income of the website. There are some factors in consideration when we give this estimation. The first one is that though the develop team will deliver the system next year, the client may still need to spend some time in marketing, finding the resources for the website (for example, invite the companies and head hunters to use the website.). Therefore, even though the website is delivered in 2015, there may be few users since there are not so many resources, thus we assume that 0 users in The second factor is the competition from other similar websites. Since there some similar websites in the market, such as black career network, users have more choices. We assume that 40% of the users will use our website. The third factor is the growth of users for a social network. The number of users in Linkedin doubled every year from 2009 to 2011, and increased by 1.5 from 2011 to Therefore, we believe that the growth rate of users from 0 to 1.0 for our website is reasonable, here we take the 0.5 growth rate and we assume that there will be a 5% increment in the growth rate. The forth factor is the number of black students in the college. According to the statistics from and we know that there are about 30million students in the colleges all over the USA, about 1/3 of them attend 2-year college and 2/3 of them attend 4-year and about 15% of them are black students. That is about 1.5 million black student graduate from the college each year. Based on the factors listed above, for a optimistic estimation, we assume that 1% of the black students will try to use the websites designed for the black students in the market to and due the competition from the other similar websites from the market, we assume that 1/3 of them will use our website. Therefore, we estimate that there are 0, 5,000 7,500, 11,438 users for year from 2015 to For a pessimistic estimation, we assume that 0.1% black students will use the similar websites, and 20% of them will use our website, that is 0, 300, 485, 686 users from year 2015 to Explanation for Benefit: For the benefit, we calculate the income from the advertisement. Based on the information from we estimate the income from AdSense is about $20 per day 11

12 if there is 1,000-page view ($0.02 for per page view). And based on the information from It says that 40% of Linkedin user will check Linkedin everyday, and the average time of a user spend on Linkedin every month is 17 minutes, here we assume that 30% users in our website will each day and will open 4 pages (2 homepage, 1 group page, 1 message page). Moreover, we also estimate that $0.25 per click for an advertisement and we assume that there is1%users will click the advertisement. That is (5,000 people * 0.3 * 4 * $ ,000 people * 0.3 * 0.01 * 0.25) * 365 days = $52, Besides, we also calculate the income from selling the banner advertisement in our website, and it will earn about $1 per day for us if there is 1,000 page view and we assume that there is a 5% increment for this income every year. That is 365 days * (5,000 people * 0.2 * 4 page view / 1000) = $2, for the year 2016 and $1.05 per day for year 2017 so on and so forth. Figure 2: ROI Analysis Graph Year Optimistic ROI Pessmistic ROI 12

13 3 Architecture Feasibility 3.1 Level of Service Feasibility Table 5: Level of Service Feasibility Level of Service Requirement LOS-1: The system shall return search results at most 5 seconds Product Satisfaction Product Strategies: We will use Apache + Phusion Passenger to handle the concurrency requests from the users. Moreover, we use some optimization techniques in PostgreSQL, such as EXPLAIN, Batch Insertion to improve the performance of the DBMS. Process Strategies: When we test the system, we will generate a large number of mock data in our database system. Then use Load Tester LITE to simulate a group of users use the search engine at the same time to see whether the result can be returned in 5 seconds. Analysis: The time of returning result depends on a lot of factors, such as the number of the request at the same time, the scale of the data, the connection speed of the network. But basically, on a machine which has 512M memory, 1GHz Cell II CPU and 7200 RPM disk, PostgreSQL can return the a single search result for a large table which has one million rows and 40 columns within less than 100ms. Plus the calculation of recommendation engine in our system and the time spend on transferring the data, we can return the result in less than 5 seconds as long as the connection of the network is not very slow. Moreover, if we do more optimization and deploy our system on a more powerful machine, the performance can be better. 3.2 Capability Feasibility Reference (in Chinese): Table 6: Capability Requirements and Their Feasibility Evidence Capability Requirement CR-1: Profile management: The system is capable of creating a Product Satisfaction Software/Technology used: Ruby on Rails, Linkedin API, PostgreSQL 13

14 profile for users, allowing them to maintain the profile by adding/ updating/ deleting information. CR-2 Messaging: The system is capable of allowing users to send/receive messages to/from other users in BlackProfessionals.net. CR-3 Recommendation Engine: The system is capable of providing some recommendations for connection, showing on the side of a page so that users can easily connect to those who share the same background with them. CR-4 Search and Connect: The system is capable of allowing users to search people in BlackProfessionals.net, to connect with other users, and to connect with (join) a group. CR-5 Social Feed: The system is capable of allowing users to see an update, involving status changes, new connections, and new posts (of an article, pictures or a video). Users can also see others updates, and can comment on an update. CR-6 Invitation: The system is capable of allowing users to invite their contact in LinkedIn or in account, and to invite friends in the network to join a group. CR-7 Advertising: The system is capable of showing advertisement from schools as well as companies, using Google AdSense API. CR-8 Group Formation: The Feasibility Evidence: The prototype shows that we can use Linkedin API to import the data from Linkedin. After that we can use the program written in Ruby to execute the command from users to manage the data in database. Referred use case diagram: UC-3, UC-4, UC-5 Software/Technology used: Ruby on Rails, PostgreSQL Feasibility Evidence: We can use the program written in Ruby to execute the command from users to search the data in database, and return to the users, display them on the web pages. Referred use case diagram: UC-6, UC-7 Software/Technology used: Ruby on Rails, PostgreSQL Feasibility Evidence: We can get the data from the PostgreSQL using the program written in Ruby at first, and then use the weighted_recommendation algorithm to analyze the data, and then return the most similar result to the user. Referred use case diagram: UC-8 Software/Technology used: Ruby on Rails, PostgreSQL Feasibility Evidence: We can write the program in Ruby to search and update the relationship of user data in the DBMS. Referred use case diagram: UC-9, UC-10, UC-11, UC-12, UC-13, UC-14 Software/Technology used: Ruby on Rails, PostgreSQL Feasibility Evidence: We can write the program in Ruby to search and manage the social feed in the DBMS. Referred use case diagram: UC-24, UC-25, UC-26 Software/Technology used: Ruby on Rails, PostgreSQL, Linkedin API Feasibility Evidence: We can write the program, which uses the Linkedin API to see the users friends in Linkedin, and then the system can send an invitation through if the user wants. Referred use case diagram: UC-21, UC-22, UC-23 Software/Technology used: Ruby on Rails, Adsense Feasibility Evidence: A space on our website pages will be reserved for the advertisement using Adsense, and Google will display the advertisement on the page. Referred use case diagram: UC-15 Software/Technology used: Ruby on Rails, PostgreSQL 14

15 system is capable of allowing users to create groups; group creator serves as the manager, who can accept joining request. CR-9 Recommendation Letter: The system is capable of allowing users to write, to review, to accept and to reject recommendation letters. Feasibility Evidence: We can write the program to manage the group in our system and its data in the DBMS. Referred use case diagram: UC-18, UC-19, UC-20 Software/Technology used: Ruby on Rails, PostgreSQL Feasibility Evidence: We can write the program in Ruby to allow the users who are in connection with the user to write recommendation letters. Referred use case diagram: UC-16, UC Evolutionary Feasibility No evolutionary requirements are recorded in win book yet. 15

16 Feasibility Evidence Description (FED) 4 Process Feasibility Table 7: Rationales for Selecting Architected Agile Model Criteria Importance Project Status Rationales 30 % of NDI/NCS features Although we can use some NDI/NCS, such as AdSense for some part in our website. Most of the functionality is needed 0 0 to be developed by us. Single NDI/NCS There is no such a NDI/NCS 0 0 that can fulfill the requirements of our system. Unique/ inflexible business process The client briefly defines how the system would be; however, they are open to discussions Need control over upgrade / maintenance Rapid deployment Critical on compatibility 3 1 Internet connection independence Need high level of services / performance Need high security Asynchronous communication Be accessed from anywhere Critical on mass schedule constraints 0 1 with the development team. The system needed to be maintained and added more features to it in the future. We will deploy the system at the end of next semester when we deliver it. We don t need to rush to deploy the system on the server. User need to access the Internet, so that they can access our website. The requirements mention that the search result should be returned in 5 seconds. Since the website records the users data including some private information. Thus, we need a high security. Our website should be able to handle the asynchronous communication from different users. The users can access our website as long as they can access to the Internet. The system will be deployed at the end of next semester. FED_FCP_F14_Team06_V3.0.doc 16 Version Date: 12/7/2014

17 Lack of personnel capability Require little upfront costs Require low total cost of ownership Not-so-powerful local machines The development team members have learned related knowledge to develop the system. During the development period, no money is required for the project. The client just need to pay about $134 per year to keep the website running. The user can use a not-sopowerful machine to visit our website as long as the machine can run a browser program. 17

18 Feasibility Evidence Description (FED) 5 Risk Assessment Table 8: Risk Assessment Risks Similar Products in the market already: The BlackJob.com and the BlackCareerNetwork.com are similar to what we are going to develop, although these websites are not operating now, the competence may be inevitable. Risk Exposure Potential Probability Magnitude Loss Risk Exposure System Maintenance And upgrade: The maintainer for the website has not been determined yet Risk Mitigations Upgrade the system frequently after deploying based on the feedback of the users. If the client insist maintaining the website by himself, then he need to spend some time in learning the web technologies. Budget: Since the system we will deliver next semester has only simple features, the client may not be able to spend enough money on it (about several ten thousand dollars each year according to the ROI analysis) to make the website more engaging and provide a better user experience for users It is hard to upgrade the system; the client needs to hire someone to do it. Find some investors who are interested in the project and ask them to fund the project. FED_FCP_F14_Team06_V3.0.doc 18 Version Date: 12/7/2014

19 6 NDI/NCS Interoperability Analysis 6.1 Introduction 6.2 COTS / GOTS / ROTS / Open Source / NCS Table 9: NDI Products Listing NDI/NCS Products Rails PostgreSQL Phusion Passenger Apache LinkedIn (Ruby) AdSense Purposes The framework of back-end of the website. The DBMS for the website. The application server for the project. The http server for the project. To get user s profile from LinkedIn To display advertisement on our website. 6.3 Connectors In this project, we use Ruby/PostgreSQL connector to enable the Ruby web application to retrieve and query data from the database. 6.4 Legacy System Client does not have an existing system. 6.5 Evaluation Summary Rails PostgreSQL Table 10: NDI Evaluation NDI Usages Comments The framework of backend Positive Point: Easy to use of the website. Negative Point: Need to design very carefully to obtain The DBMS for the website. scalability. Positive Point: Easy to use and improve its performance. Phusion Passenger The application server for the project. Negative Point: No negative point Positive Point: Easy to configure, and it is supported 19

20 and updated. Apache LinkedIn (ruby) AdSense The http server for the project. To get user s profile from LinkedIn To display advertisement on our website. Negative Point: No negative Point. Positive Point: Fast, reliable Negative Point: No negative point. Positive Point: Easy to use. Negative Point: None. Positive Point: Easy to use. Negative Point: Cannot control which advertisement to be displayed. 20