Feasibility Evidence Description (FED)

Transcription

1 Feasibility Evidence Description (FED) LEMA Pilot School Integrated Scheduling System Team No. 12 Name Primary Role Secondary Role David Wiggins Project Manager Developer Aakash Shah Prototyper Developer Kushalpreet Kaur Developer Developer Thammanoon Kawinfruangfukul Tester Developer Eunyoung Hwang Architect Developer Louis Demaria IIV&V Developer Mark Villanueva QFP Developer Sangik Park Developer Developer 02/09/2012 FED_RDCP_S12b_T12_V5.1.doc i Version Date: 02/09/2012

2 Version History Date Author Version Changes made Rationale 09/30/11 A.S. & N.A /12/11 A.S /17/11 A.S /24/11 A.S. 2.1 Introduction & Risk Assessment Introduction and Risk Assessment Entire document completed Elaborated on Business Case and fixed other bugs 11/21/11 A.S. 3 Risk Assessment Updated First draft of the risk analysis of the project Completed the Win-Win negotiations and updating the doc accordingly. After initial evaluations, a draft of the completed document Updated the document with all the feedback from the ARB sessions At the end of the foundations phase, the risks have been evaluated and updated in the FED. 12/05/11 A.S. 4.0 Business Case updated At the end of the DCR ARB, after incorporating the feedbacks, the Business case has been updated to reflect the same. 02/03/12 D.W. 5.0 Updated team members, risks, and feasibility analysis Rebase-line for cs577b 02/09/12 D.W. 5.1 Updated tables 6 and 8 Re-baseline of CRs FED_RDCP_S12b_T12_V5.1.doc ii Version Date: 02/09/2012

3 Table of Contents Feasibility Evidence Description (FED)...i Version History... ii Table of Contents... iii Table of Tables...iv Table of Figures... v..a.1. Introduction A.1.1 Purpose of the FED Document A.1.2 Status of the FED Document A.2. Business Case Analysis A.2.1 Cost Analysis Personnel Costs Hardware and Software Costs A.1.1 Benefit Analysis ROI Analysis A.2. Architecture Feasibility A.2.1 Level of Service Feasibility A.2.2 Capability Feasibility A.2.3 Evolutionary Feasibility A.3. Process Feasibility A.4. Risk Assessment A.5. NDI/NCS Interoperability Analysis A.5.1 Introduction COTS / GOTS / ROTS / Open Source / NCS Connectors Legacy System A.5.2 System Structure A.5.3 Evaluation Summary FED_RDCP_S12b_T12_V5.1.doc iii Version Date: 02/09/2012

4 Table of Tables Table 1: Personnel Costs... 2 Table 2: Hardware and Software Costs... 3 Table 3: Benefits of LEMA Scheduling System... 3 Table 4: ROI Analysis... 4 Table 5: Level of Service Feasibility... 5 Table 6: Capability Requirements and Their Feasibility Evidence... 5 Table 7: Rationales for Selecting Architected Agile Model... 9 Table 8: Requirement Prioritization Table 9: Risk Assessment Table 10: NDI Products Listing Table 11: NDI Evaluation FED_RDCP_S12b_T12_V5.1.doc iv Version Date: 02/09/2012

5 Table of Figures Figure 1: ROI Analysis Graph... 4 FED_RDCP_S12b_T12_V5.1.doc v Version Date: 02/09/2012

6 ..A.1. Introduction..A.1.1 Purpose of the FED Document The purpose of the Feasibility Evidence Description Document is to analyze the feasibility of the current project at every stage, calculate and present the risks at the stage to all the critical success stakeholders, and to record risk mitigation plans. We evaluate the business case of the project, architecture and process feasibilities. We also evaluate NDI/NCS interoperability evidence and document it here. Each version of this document is evaluated at the anchor points and a decision is made to either move ahead with the project or not...a.1.2 Status of the FED Document The FED has been updated to reflect changes in the projects risks and design decisions since the team reformed and re-baselined the system design. FED_RDCP_S12b_T12_V5.1.doc 1 Version Date: 02/09/2012

7 ..A.2. Business Case Analysis..A.2.1 Cost Analysis All of the expected benefits of this project are intangible and focus mainly on saving time, improving efficiency, and providing the students a college like atmosphere to grow in. Thus cost analysis is focused on trying to map these intangibles to some expected results Personnel Costs All personnel costs assume that the project will run for two semesters. Table 1: Personnel Costs Activities Time Spent (Hours) Weekly Meeting with the developers 2*24 = 48 hours Review meetings at the developer site 4*8 = 32 hours Initial Start-up meetings to clarify project details 2*2 = 4 hours Gather different details required by the developers 1*24 = 24 hours Training (getting trained and helping the students) 72 hours Total Costs 190 hours Total costs ($50/hour basis) $9500 The rationale for the above costs is that every week the clients spend about an hour (2 clients, thus 2 hours) for a yearlong (24 week) project. All the review meetings such as Win-Win negotiations, Architecture Review Board meetings, etc. add up to 32 hours of the clients time (4 hours * 8 times). This also includes time to travel to and from the school. The development team had about 2 meetings at the clients site spending about 4 hours of the clients time to get started on to the project. (2 clients 1 hour * 2 times) Sometimes, the clients can be requested certain data, such as a list of all constraints, norms, Regulations, etc. and that may take up to 24 hours of the client s time overall. Training costs for the Head Scheduler training for a week 40 hours. For all students we will need to have a 2 hour session for each class for two weeks. Thus 16 hours of the teachers (2 teachers) implying 32 hours will be consumed in the same Hardware and Software Costs Since our clients are running a non-profit organization to educate young minds, there are no FED_RDCP_S12b_T12_V5.1.doc 2 Version Date: 02/09/2012

8 related hardware costs or software costs. Since we are going to deploy this system online, the only acceptable costs are the deployment costs of about $42 per year (36 $3.5 per month at godaddy.com). There are the following sites available for free hosting and low cost hosting: Table 2: Hardware and Software Costs Type Cost Rationale Software Deployment costs $42/year It is the maximum cost that could come in to play when we have to eventually put the web site online and buy web space. MySQL DB - It is a freely available database technology. Symfony PHP web development platform FET the Scheduling COTS product - Open source development platform for PHP websites. - Open source under the GNU developer license...a.1.1 Benefit Analysis Benefits of this project are on two different levels. Time and efforts saved are one such benefit that come directly and will be mapped clearly. Another benefit that will be seen in the course of time is student transition into college life and their general high school level growth in order to prepare them for their college life ahead. Table 3: Benefits of LEMA Scheduling System Current activities & resources used % Reduce Time Saved (Hours/Year) Scheduling Uses SIS, Columbia and 50%(150 efforts on the part of the APSCS 2 hours/ hours/year months each year (plus few days for the hours) next semester) Student counseling through paper-based forms and counselor checking and approving the same Total Total Cost Saved ($50 an hour) 30%(for the counselor) 30 hours/year 180 hours/year $9,000/year FED_RDCP_S12b_T12_V5.1.doc 3 Version Date: 02/09/2012

9 2.3 ROI Analysis Calculating the return on investment of time, effort, and money incurred by the clients gives us a good idea as to what the clients must expect from the project. The cost per year has been identified as $250 which is for maintenance plus $42 as the web hosting charges per year. The maintenance fees are expected to grow 10% annually. Year Cost($) Benefit (Effort Saved)($) Table 4: ROI Analysis Cumulative Cost($) Cumulative Benefit($) ROI Figure 1: ROI Analysis Graph What this graph tells us is that the clients will be able to break even within a year of their investment. Also, it is a linear graph which tells that the benefits grow linearly with time and that is always a win-win situation for the clients. FED_RDCP_S12b_T12_V5.1.doc 4 Version Date: 02/09/2012

10 ..A.2. Architecture Feasibility..A.2.1 Level of Service Feasibility Table 5: Level of Service Feasibility Level of Service Requirement LOS-1: User Interface must be friendly and intuitive. Product Satisfaction Product Strategies: By using prototyping on the same we can make sure that it is in sync with the client requirements. Process Strategies: Testing with the kids directly and showing them a working prototype and getting first hand feedback from the users to improve the system. Analysis: Keeping the above two in mind, we will ensure that the system will be clean and easy for everyone to be able to work with...a.2.2 Capability Feasibility Table 6: Capability Requirements and Their Feasibility Evidence Capability Requirement CR-1: Provide online application for students subject registration Product Satisfaction HTML/CSS/PHP/MySQL backend/symfony framework Content is displayed through a webpage developed on the framework. The technology chosen is made for web development. FED_RDCP_S12b_T12_V5.1.doc 5 Version Date: 02/09/2012

11 CR 2: Provide Administration access to lock in certain classes. COTS - FET Available as a part of the COTS found CR - 3 Authentication to the system HTML/CSS/PHP/MySQL backend/symfony framework This is a simple DB query to fetch the data. CR 4 Integration with family accountability system REST client in PHP REST is built in to PHP. Capable of common functions such as GET, POST, DELETE, CR - 5 Student records to the counselor HTML/CSS/PHP/MySQL backend/symfony framework Content is displayed through a webpage developed on the framework. The technology chosen is made for web development. CR - 6 Scheduling System COTS - FET COTS enables this functionality for us FED_RDCP_S12b_T12_V5.1.doc 6 Version Date: 02/09/2012

12 CR - 7 Information about the progress of a particular student CR 8 Ability of students to see how many more credits they need to complete a particular grade CR 9 Teachers are assigned a particular course section by the scheduler CR 10 Ability to view alternate schedules HTML/CSS/PHP/MySQL backend/symfony framework Simple via DB operations and intuitive UI Needs prototyping to confirm feasibility. HTML/CSS/PHP/MySQL backend/symfony framework Content is displayed through a webpage developed on the framework. The technology chosen is made for web development. COTS - FET The COTS enables this as soon as we change any other constraint or lock in a class. CR 11 Student to see the GPA for various Cal States, CSU and other universities CR 12 LAUSD constraints HTML/CSS/PHP/MySQL backend/symfony framework Simple via DB operations and intuitive UI Needs prototyping to confirm feasibility. HTML/CSS/PHP/MySQL backend/symfony framework Simple via DB operations and intuitive UI Needs prototyping to confirm feasibility. FED_RDCP_S12b_T12_V5.1.doc 7 Version Date: 02/09/2012

13 CR 13 Database to contain student details, course details and teachers details CR 14 Provide team04 with teacher course list, student course list and/or overall course list. MySQL backend Simple DB operations. REST client in PHP REST is built in to PHP. Capable of common functions such as GET, POST, DELETE,..A.2.3 Evolutionary Feasibility The evolutionary requirements that have been identified are not going to be worked upon in this project as they are now a part of the other project group s requirement lists. (They had overlapped earlier). Thus there are no evolutionary requirements listed here. FED_RDCP_S12b_T12_V5.1.doc 8 Version Date: 02/09/2012

14 ..A.3. Process Feasibility We are using the architected agile methodology for this project. We are also using a NDI, which is available free of cost, but which offers just about 30% of the required functionality. Table 7: Rationales for Selecting Architected Agile Model Criteria Size, Complexity Change Rate % /Month Criticality NDI Support Org/Personnel Capability Key Stage I Activities : Incremental Definition Key Stage II Activities: Incremental Development, Operations Time per Build; Time per Increment Rationales The size and complexity of the project is medium to high. Though since we have got an NDI to perform the most complex piece scheduling we can say that complexity is about medium. Size is a bit of a concern and we need effective prioritization to be able to control that. Since now we have had multiple iterations with the clients on the requirements of the projects, the majority of the requirements are frozen. Some specific details that are still unclear have been asked for. In any case, we expected change rate to be lower than 5%/month. Medium. The project is important from student profiling and scheduling though it is not a critical system that would need continuous maintenance. It is more of a once built and done kind of a system. Though impact of the system is still very high. We shall be using a NDI FET for scheduling. Other than that we shall use MySQL, PHP, Symfony technologies to develop the entire website for the clients. There are 2-3 team members that have some experience with PHP. David is very comfortable with HTML, CSS, PHP in order to design views. Also mostly everyone is familiar with databases and MySQL. Since student profiling is something that is needed sooner than later, a majority of the focus of the first iteration will be on that part of the system. Also it lays the foundations for all details that a scheduler system will need from Student/Teacher/Course input. The next stage is mainly integrating the NDI FET with the database (will be done via exporting and importing CSV files). This is going to be the next important deliverable of the system. Time Per build: about 4 5 weeks for each iteration will be sufficient. The schedule is enough to complete the required system and then we can get continuous feedback from the client as well. Time per Increment: We may use 2-3 months, according to the schedule of the course 577 a/b, it's more safe to arrange FED_RDCP_S12b_T12_V5.1.doc 9 Version Date: 02/09/2012

15 enough time to update and fix the defects. The improvement of low priority requirements should also be considered. Table 8: Requirement Prioritization Priority Requirements References Increment # M Provide online application for students subject CR 1 1 registration M Provide Administration access to lock in certain classes. CR 2 2 M Authentication to the system CR 3 1 M Integration with family accountability system CR 4 2 M Student records to the counselor CR 5 1 M Scheduling System CR 6 2 M Information about the progress of a particular student CR 7 2 S Ability of students to see how many more credits they CR 8 3 need to complete a particular grade M Teachers are assigned a particular course section by the CR 9 1 scheduler M Ability to override the current scheduling system CR 10 2 S Student to see the GPA for various Cal States, CSU and CR 11 3 other universities M LAUSD constraints CR 12 2 M Database to contain student details, course details and CR 13 1 teachers details M Provide team04 with teacher course list, student course CR list and/or overall course list. FED_RDCP_S12b_T12_V5.1.doc 10 Version Date: 02/09/2012

16 ..A.4. Risk Assessment All possible risks to the project have been identified and documented below. These are all the risks at the current point in time. A risk mitigation plan(s) for each one of them has also been identified. Table 9: Risk Assessment Risks Integration of the new system with system being developed by team 4 Import of Legacy System data into our system Since we changed project languages recently, we have yet to prototype the interface from PHP to C in order to talk to the COTS. Some of our developers have little to no experience with PHP and Web development on a framework such as Symfony and the schedule needed to accommodate a learning curve may be too much. Potential Magnitude Risk Exposure Probability Loss Risk Exposure Risk Mitigations Collaborate and work with team 4 to ensure that there are no incompatibilities Use.csv file format for import; as a backup, create pages (UI) for manual entry Aakash is tackling this right now in order to hopefully see complications ASAP. We re doing a number of simple prototypes now in order to see that Symfony is not an incredibly complex framework to learn and use. If those prototypes go poorly we will have to consider reverting back to ASP. FED_RDCP_S12b_T12_V5.1.doc 11 Version Date: 02/09/2012

17 ..A.5. NDI/NCS Interoperability Analysis..A.5.1 Introduction COTS / GOTS / ROTS / Open Source / NCS Table 10: NDI Products Listing NDI/NCS Products FET Free Timetabling Software Purposes To create a schedule given a set of students, teachers, activities and other constraints Connectors - MySQL - PHP connector to connect the MySQL Database to the Symfony framework business layer. - MySQL DB query - CSV file convertor to give inputs to the FET system via CSV files Legacy System There is no need here as the connector between the legacy systems and our new system are the people themselves. (Manual data entry will be done to connect the legacy systems to our new system)...a.5.2 System Structure See OCD for details regarding the System Structure...A.5.3 Evaluation Summary We looked up multiple NDI s offered and finalized FET as the one to use. Basically what we were looking for in every NDI was its flexibility for rules, and also its cost. Most of the COTS came high on costs and very little rule flexibility. FET, was a free software that does give us a large base of constraints to use. Thus FET was chosen eventually as the COTS for our system. Table 11: NDI Evaluation NDI Usages Comments FED_RDCP_S12b_T12_V5.1.doc 12 Version Date: 02/09/2012

18 FET Free Timetabling Software UntisExpress 2012 Mimosa s Scheduling Software Free Edition As a scheduling system with ability to enter constraints As a scheduling system with ability to enter constraints As a scheduling system with ability to enter constraints Free, comfortable to use (i.e. user friendly), and also comes with a wide variety of constraints that can be used. It comes with a cost of 334 USD + a maintenance cost of 100 USD per year. Also the number of constraints that can be used in this system are lower than that offered by FET. It is free, though has much lower functionality than its non-free version. Also it offers more functionality than is required and is a lot more complicated to use than FET. FED_RDCP_S12b_T12_V5.1.doc 13 Version Date: 02/09/2012