Feasibility Evidence Description (FED)

Transcription

1 Feasibility Evidence Description (FED) SWIM MEET SIGNUP Team 03 Member Name Role Archan Dutta Project Manager, Life Cycle Planner Deepanshu Suneja Software Architect, Developer Jenny Greer IIV and V, Quality Focal Point Rasleen Sahni Feasibility Analyst, Developer Swasti Sharma Operational Concepts Engineer Vibhanshu Sharma Software Prototyper 10/16/2017

2 Feasibility Evidence Description (FED) for Architected Agile Template Version x.x IICSMSw_FED_Architected Agile_Template.doc ii Version Date: 08/17/12

3 Feasibility Evidence Description (FED) for Architected Agile Template Version x.x Version History Date Author Version Changes made Rationale 08/20/05 RS 1.0 Original template for use developing Swim Meet Signup Website Initial draft for DC Package IICSMSw_FED_Architected Agile_Template.doc iii Version Date: 08/17/12

4 Feasibility Evidence Description (FED) for Architected Agile Template Version x.x Table of Contents Feasibility Evidence Description (FED)...i Version History... iii Table of Contents...iv Table of Tables... v Table of Figures...vi 1. Introduction... Error! Bookmark not defined. 1.1 Purpose of the FED Document... Error! Bookmark not defined. 1.2 Status of the FED Document... Error! Bookmark not defined. 2. Business Case Analysis Cost Analysis Benefit Analysis... Error! Bookmark not defined. 2.3 ROI Analysis Architecture Feasibility Level of Service Feasibility... Error! Bookmark not defined. 3.2 Capability Feasibility... Error! Bookmark not defined. 3.3 Evolutionary Feasibility... Error! Bookmark not defined. 4. Process Feasibility Risk Assessment NDI/NCS Interoperability Analysis Introduction Evaluation Summary IICSMSw_FED_Architected Agile_Template.doc iv Version Date: 08/17/12

5 Feasibility Evidence Description (FED) for Architected Agile Template Version x.x Table of Tables Table 1: Program Model... 3 Table 2: Hardware and Software Cost... Error! Bookmark not defined. Table 3: Benefits of xxx System... Error! Bookmark not defined. Table 4: ROI Analysis... Error! Bookmark not defined. Table 5: Level of Service Feasibility... Error! Bookmark not defined. Table 6: Capability Requirements and Their Feasibility Evidence... Error! Bookmark not defined. Table 7: Evolutionary Requirements and Their Feasibility Evidence... Error! Bookmark not defined. Table 8: Rationales for Selecting Architected Agile Model... 8 Table 9: Risk Assessment... Error! Bookmark not defined. Table 10: NDI Products Listing... Error! Bookmark not defined. Table 11: NDI Evaluation IICSMSw_FED_Architected Agile_Template.doc v Version Date: 08/17/12

6 Feasibility Evidence Description (FED) for Architected Agile Template Version x.x Table of Figures Figure 1: ROI Analysis Graph... Error! Bookmark not defined.

7 1. Introduction 1.1 Purpose of the FED Document The purpose of the Feasibility Evidence Description evidence is to that the development project is feasible and to show that the other artifacts are consistent and compatible, in the sense that: Satisfaction of all the requirements specified in the SSRD will result in satisfaction of the Win-Win agreements made by the success-critical stakeholders, for all of the operational scenarios and goals (benefits, ROI, etc.) specified in the OCD. Demonstrate the compatibility and consistency of these elements in ensuring, with high probability, the feasibility of accomplishing the desired goals both product-wise and project-wise. Encourage the development to regularly analyze the risk of the development project and prepare for risk mitigation and risk management plan. The Feasibility Evidence Document (FED) provides a throughout analysis documenting the feasibility of the SwimMeetSignUp project to be completed according to schedule and budget constraints. Our conclusions are drawn from the different types of analysis presented in the following sections: Business Case, Architecture Feasibility, Process Feasibility, Risk Assessment and NDI/NCS Interoperability Analysis. 1.2 Status of the FED Document The status of this FED is currently at the version number 1.0, which will be submitted along with Foundations Commitment Package. This version will be reviewed with the necessary stakeholders and if there are no changes to be made, the latest version of this document will be delivered to the client. IICSMSw_FED_Architected Agile_Template.doc 1 Version Date: 08/17/12

8 2. Business Case Analysis Table 1: Program Model Assumptions 1. The developer should have access to the database of registration ids of the members. 2. The pdf format should be the same for different months. 3. The users are technically sound to operate the website on all devices. Stakeholder (Who is accountable for the information) Initiatives (What to do to realize benefits) Value Propositions (Benefits i.e. Why) Beneficiaries (Who derives value) 1. Coach 2. Parent 3. Treasurer/Maintainer 4. Developer 1. Develop the system 2. Maintain the system 3. Elicitate requirements 4. Negotiate with the client 5. Assign tasks 6. Test different technologies. 1. Reduce incorrect event signups by the parents 2. Easy filter and signup events by the parents. 3. Easy access to total cost generated by signed up events. 4. Easy 1. Children 2. Coach 3. Parents 4. Treasurer Cost (Cost factors) Server Deployment Cost. Cost for planning and developing the software (in hours). There is no Hardware and Software Cost in this project. Maintenance Cost Benefits (Key performance indicators- KPIs) The Head Coach will spend less time dealing with incorrect signups and creating reports; thus, increasing the productivity in other areas of work Parents signup correctly: Parents can easily signup using the website as they can only see events there kid is eligible for. Mobile devices can also be used as website is mobile responsive Treasurer can track the total revenue generated for each swim meet. IICSMSw_FED_Architected Agile_Template.doc 2 Version Date: 08/17/12

9 2.1 Cost Analysis Personnel Costs Table 2: Personnel Costs Activities Time Spent(Hours) Total Time Available (12 weeks) Exploration Phase Client Meetings (2 hours*1 week*1 person) Win Win Session 1 (2 hours * 1 person) Valuation and Foundation Phase Win Win Session 2 (2 hours* 1 person) Weekly Discussion Remote Meetings (1 hour*3 weeks*1 person) ARB (2 hours* 2 times * 1 person) Development, Foundations, Operations Phase Weekly Process Meetings (1hour*6 weeks*1 person) Handover Activities (2 hours* 6 weeks * 1 person) TRR (1 hours* 1 person) CCD (1 hours * 1 person) Total time spent 2 hours 2 hours 2 hours 3 hours 4 hours 6 hours 12 hours 1 hour 1 hour 33 hours Hardware and Software Costs Table 3: Hardware and Software Costs Type Cost Rationale Windows Free Development operating system Apache PDFBox Free PDF library MySQL Free Database Apache TOMCAT server Free Server IICSMSw_FED_Architected Agile_Template.doc 3 Version Date: 08/17/12

10 Adobe Photoshop Free Photo editing Tool 2.2 Benefit Analysis Current activities & resources used Event Signup Parent Sign-ups for the event online Change Signed Up Events Parent can change the event online his kid is signed up for View and Edit Final Report Head Coach can view and edit the final report and print in pdf/csv format Maintain Records Table 4: Benefits of SwimMeetSignUp System Current System (Hours/Year) Proposed System (Hours/Year) % Reduce Time Saved (Hours/Year) 83.3% % % 58 Head Coach maintains the 24 2 records using file systems 91.6% 22 Total ROI Analysis Table 5: ROI Analysis Year Cost Benefit Cumulative Cumulative (Effort Saved) Cost Benefit ROI IICSMSw_FED_Architected Agile_Template.doc 4 Version Date: 08/17/12

11 Figure 1: ROI Analysis Graph IICSMSw_FED_Architected Agile_Template.doc 5 Version Date: 08/17/12

12 3. Architecture Feasibility Level of Service Feasibility Table 6: Level of Service Satisfiability Evidence Level of Service Win Condition Rationale LOS-1: The system shall be mobile responsive. Use HTML media queries to define screen styling for different mobile screens and achieving mobile responsiveness. Table 7: Level of Service Implementation Strategy Level of Service Win Condition LOS-1: The system shall be mobile responsive. Product Satisfaction Product Strategies: Bootstrap, HTML, CSS Process Strategies: Develop a prototype to produce a mobile responsive website using HTML media queries and Bootstrap features. Analysis: Use Bootstrap and CSS to create a mobile responsive website Capability Feasibility Table 8: Capability Feasibility Evidence Capability Requirement CR-1: PDF extraction CR-2: Login CR-3: View total cost Product Satisfaction Software/Technology used: Apache PDFBox Feasibility Evidence: Develop a prototype to implement PDF extraction using PDFBox jar package to extract all the important information line by line from the PDF. Referred use case diagram: Software/Technology used: MySQL-PHP Connector Feasibility Evidence: Develop a prototype to login to the system and authenticate the login details with the login credentials stored in MySQL database. Referred use case diagram: Software/Technology used: MySQL-PHP Connector IICSMSw_FED_Architected Agile_Template.doc 6 Version Date: 08/17/12

13 CR-4: Display eligible events CR-5: Close signups after deadline CR-6: Review event signup information before printing as a pdf/csv. CR-7: Edit signed-up events before deadline CR-8: PDF and CSV file generation Feasibility Evidence: Develop a prototype to display the total cost the parent is supposed to pay for the signed-up events. Referred use case diagram: Software/Technology used: MySQL-PHP Connector Feasibility Evidence: Develop a prototype to implement the filter functionality and display only those events for which the parent s kid is eligible Referred use case diagram: Software/Technology used: MySQL-PHP Connector Feasibility Evidence: Develop a prototype which only allows event signup before the deadline. Referred use case diagram: Software/Technology used: MySQL-PHP Connector Feasibility Evidence: Develop a prototype to implement the function of reviewing all the signed-up events information by fetching data from MySQL database and displaying it on the website. Referred use case diagram: Software/Technology used: Angular JS and MySQL Feasibility Evidence: Develop a prototype to make changes in the signed up events and store the edited information in the database. Referred use case diagram: Software/Technology used: MySQL, Angular JS Feasibility Evidence: Develop a prototype to fetch the information from MySQL and store it in a PDF and CSV format using MySQL database and Angular JS. Referred use case diagram: Evolutionary Feasibility At the time of this draft, no evolutionary requirements are negotiated. IICSMSw_FED_Architected Agile_Template.doc 7 Version Date: 08/17/12

14 4. Process Feasibility Table 9: Requirement Prioritization Priority Requirements Increment # Must have Events Extraction from PDF 1 Must have Extraction of payee information from PDF 1 Must have System should be mobile responsive 1 Must have Easy to use user interface 1 Must have Report Generation 1 Should have Keep track of best times of all kids 2 Must have Event Signup 1 Must have View and Edit Reports 1 Table 10: Rationales for Selecting Architected Agile Model Criteria Importance Project Status Rationales 30 % of NDI/NCS features 3 3 All of NDIs (PHP, AngularJS, Apache PDFbox) are being used for the development. Single NDI/NCS 1 1 More than one NDI is used for development Unique/ inflexible business process 1 1 The business process is not unique. It is specific to a swimming organization and has little flexibility Need control over upgrade / maintenance 2 1 Maintenance is required. Small upgrades might be required Rapid deployment 3 3 It is a one semester project and therefore requires rapid deployment Critical on compatibility 2 3 Since, all of NDIs are used, they must be compatible with each other Internet connection independence Need high level of services / performance 3 3 The website requires internet connection to be accessed. 2 2 The website requires web browsers and must run on desktop/laptop/mobile devices Need high security 1 1 Security is required to keep records safe. This is done IICSMSw_FED_Architected Agile_Template.doc 8 Version Date: 08/17/12

15 through MySQL and proper authentication Asynchronous communication 2 2 System requires Asynchronous communication Be accessed from anywhere 3 3 The system will be on the server and must be accessible from remote locations via the Internet Critical on mass schedule constraints 3 3 Since, time period is short, the project has several schedule constraints Lack of personnel capability 2 2 Members have some experience in web development but still unaware of some processes required for the development Require little upfront costs 4 4 Most NDIs are free Require low total cost of ownership 3 3 The system will be owned by Arcadia Riptides Swim Club Not-so-powerful local machines and will increase their profits 2 1 The website is not performing complex computations and therefore does not require powerful machines IICSMSw_FED_Architected Agile_Template.doc 9 Version Date: 08/17/12

16 5. Risk Assessment Table 11: Risk Assessment Risk Exposure Risks Potential Probability Risk Risk Mitigations Magnitude Loss Exposure Information extraction from PDF Research tools/technologies and procedures for PDF extraction Easy to use UI/UX for the endusers A lot depends on what PDF that being provided, the format of which is fixed. 2- Run Prototype on a PDF to see if it works Develop prototypes for the UI and get feedback from the users on the UI Develop prototype which can extract information from various expected types of PDFs. IICSMSw_FED_Architected Agile_Template.doc 10 Version Date: 08/17/12

17 6. NDI/NCS Interoperability Analysis 6.1 Introduction We chose NDI products based on what we need during the development. For our project, we used Apache PDFBox as development tool/library to extract the relevant information from the PDF and show up the events on the website. MySQL database is used to store information and generate final reports having all the data. AngularJS is used to manipulate and display the relevant data on the website. Apache Tomcat is used as the server and PHP is used for back-end work (server-side scripting) COTS / GOTS / ROTS / Open Source / NCS Table 12: NDI/NCS Products Listing NDI/NCS Products Apache PDFbox PHP MySQL AngularJS Purposes Extract Information from the Swimming Meet pdf. Server-Side Scripting Database to store information of events and kids Frontend Framework along with HTML and CSS Connectors Table 13: NDI/NCS Products Listing Connector PHP/ApachePDFbox MySQLi Purposes PHP code that enables connection between PHP and ApachePDFbox. It is a.dll file available in PHP extensions to facilitate connection between PHP and MySQL Server Legacy System The Arcadia Riptides Swim-Meet Signup website does not need to be used in conjunction with a legacy system or an existing website. 6.2 Evaluation Summary Table 14: NDI Evaluation NDI Usages Comments IICSMSw_FED_Architected Agile_Template.doc 11 Version Date: 08/17/12

18 Apache PDFBox PDF Extraction An open source Java library used to parse and extract text information from the PDF PHP Server-Side Scripting/Backend Awesome Backend language to use because: Quick and easy language for web development Large community, widely used. It works well with databases, file systems, images, et cetera. MySQL Database Relational Database suitable for storing Kid s information and Event Information. It is also easy to use with PHP. AngularJS Frontend Frontend framework to complement HTML and CSS and allow better UI/UX IICSMSw_FED_Architected Agile_Template.doc 12 Version Date: 08/17/12