1 INTRODUCTION1.1 PROJECT OVERVIEW1.2 PROJECT SCOPE1.3 REFERENCES1.4 PRODUCT/PROJECT or BUSINESS DEPENDANCIES1.5 ROLES AND RESPONSIBILITIES2 Software Development Plan2.1 ASSUMPTIONS2.2 GROUP DEPENDENCIES2.3 CONSTRAINTS2.4 RISK IDENTIFICATION2.5 ESTIMATES2.5.1 EFFORT2.5.2 COSTS2.5.3 SIZE OF DELIVERABLES2.5.4 SIZE OF NON-DELIVERABLES2.6 PROJECT PLAN DELIVERABLES2.7 PROJECT LIFE-CYCLE2.8 PROJECT SCHEDULE(s)2.8.1 PROJECT ACTIVITIES2.8.2 SCHEDULES AND MILESTONES3 CRITICAL COMPUTER RESOURCES4 FACILITIES AND TOOLS5 SOFTWARE CONFIGURATION MANAGEMENT PLAN6 SOFTWARE QUALITY ASSURANCE PLAN7 COMMUNICATION PLAN8 TEST PLAN9 END USER SUPPORT PLAN10 SOFTWARE PROJECT TRACKING & OVERSIGHT11 APPROVALSAPPENDIX 1: DEFINITIONSCS 501- Software EngineeringLegal Data Markup SoftwareRelease (V.1.0)Feasibility ReportVersion (1.1)Key Stakeholders/Organizations:Project Sponsors: Professor Thomas Bruce, Professor William ArmsFilename: Feasibility Report Page 1 Last modified: 11/27/00Version: V.1.1 Printed: 01/13/19Document Change History LogVersion#ChangeRequest#Description of changes to thisdocumentDateApprovedSection(s) of Project Plan affected.1.00 0 Initial Version 09/13/2000 All1.1 1 Revision for Delivery 11/27/2000 1.1, 5, 6, 8, 9Filename: Feasibility Report Page 2 Last modified: 11/27/00Version: V.1.1 Printed: 01/13/19Table of Contents1 INTRODUCTION 51.1 PROJECT OVERVIEW 51.2 PROJECT SCOPE 51.3 REFERENCES 51.4 PRODUCT/PROJECT or BUSINESS DEPENDANCIES 51.5 ROLES AND RESPONSIBILITIES 62 SOFTWARE DEVELOPMENT PLAN 72.1 ASSUMPTIONS 72.2 GROUP DEPENDENCIES 72.3 CONSTRAINTS 72.4 RISK IDENTIFICATION 72.5 ESTIMATES 72.5.1 EFFORT 72.5.2 COSTS 72.5.3 SIZE OF DELIVERABLES 72.5.4 SIZE OF NON-DELIVERABLES 72.6 PROJECT PLAN DELIVERABLES 72.7 PROJECT LIFE-CYCLE 82.8 PROJECT SCHEDULE(s) 82.8.1 PROJECT ACTIVITIES 82.8.2 SCHEDULES AND MILESTONES 83 CRITICAL COMPUTER RESOURCES 84 FACILITIES AND TOOLS 85 SOFTWARE CONFIGURATION MANAGEMENT PLAN 86 SOFTWARE QUALITY ASSURANCE PLAN 87 COMMUNICATION PLAN 98 TEST PLAN 9Filename: Feasibility Report Page 3 Last modified: 11/27/00Version: V.1.1 Printed: 01/13/199 END USER SUPPORT PLAN 910 SOFTWARE PROJECT TRACKING & OVERSIGHT 911 APPROVALS 9APPENDIX 1: DEFINITIONS 10Filename: Feasibility Report Page 4 Last modified: 11/27/00Version: V.1.1 Printed: 01/13/191 INTRODUCTION1.1 PROJECT OVERVIEWCornell’s Legal Information Institute (LII) currently has software that converts the US Code fromformatted ASCII input provided by the US House of Representatives into HTML. However, this softwaredoes not handle some of the features very well and as desired, cannot convert the “raw” input into XML.Professor Bill Arms was contacted by the LII to help in the implementation of this technical aspect.Consequently, this proposal was suggested as one of the projects for the Software Engineering course, CS501.The objective of the Legal Data Markup Software project is to create a filter that will reliably andaccurately create a structured XML version of the US Code from formatted ASCII input provided by theUS House of Representatives. The XML version will follow a DTD that we will create. The design shouldbe done in such a way as to guarantee (so far as is possible) a usable lifespan of three or more years for thesoftware.The software will be used by Professor Thomas Bruce, the cron daemon, and the American people. Thisfilter will be run in an automated batch-processing environment. Therefore, Professor Bruce will sign offon this project, the cron daemon will interact with the software at run time, and the American people willbe the ultimate users of the product created by the software.The LII will use the software to create a variety of electronic publications: one is their Web version of theCode. Others contemplated include downloadable versions of the Code in Folio Views format or formatsreadable on PDAs. These will make use of the XML version created by our software, and furthertransform it.The project was initiated by Professor Thomas Bruce. 1.2 PROJECT SCOPE- Required: The project will provide software that will convert the US House of Representatives Code inraw ASCII format into XML format for use by Cornell’s Legal Information Institute. The XMLoutput will preserve the layout and structural division of the US Code.- Desired: Additional goals of the project include enabling point in time references and marking updetailed tables to increase the utility of the XML output.1.3 REFERENCESThe following documents are related to the project and have been consulted:- Current version of code for conversion from raw ASCII to HTML.- http://uscode.house.gov/download.htm – US Code related input formats.- http://www.lexum.umontreal.ca/fr/equipes/technologie/dtd/LOIQ.dtd -- Montreal’s DTDs used forlegislative purposes.- http://elj.warwick.ac.uk/jilt/00-2/bruce.html – General background on legislative and legalpublishing.- http://elj.warwick.ac.uk/jilt/00-1/arnold.html – History, motivation, and high-level implementation ofEnAct, a project done in Tasmania similar to this one.1.4 PRODUCT/PROJECT or BUSINESS DEPENDANCIESThis project is not dependent on any other project. The LII intends to use the software to publish US Codein HTML format on their website and store the XML format for later use.Filename: Feasibility Report Page 5 Last modified: 11/27/00Version: V.1.1 Printed: 01/13/191.5 ROLES AND RESPONSIBILITIESName Department ResponsibilityThomas Bruce Legal Information Institute Project SponsorWilliam Arms Computer Science Department Project SponsorAmy Siu Computer Science Department Project ReviewerJu Joh Computer Science Department Student DeveloperSylvia Kwakye Computer Science Department Student DeveloperJason Lee Computer Science Department Student DeveloperNidhi Loyalka Computer Science Department Student DeveloperOmar Mehmood Computer Science Department Student DeveloperCharles Shagong Computer Science Department Student DeveloperBrian Williams Computer Science Department Student DeveloperFilename: Feasibility Report Page 6 Last modified: 11/27/00Version: V.1.1 Printed: 01/13/192 Software Development Plan2.1 ASSUMPTIONS - Given that the project is part of a course requirement, it is assumed that adequate funding is provided.- There exists sufficient time to complete the project.- Since there is no involvement of trade secrets or other
View Full Document
Unlocking...