INTRODUCTIONPROJECT OVERVIEWPROJECT SCOPEREFERENCESPRODUCT/PROJECT or BUSINESS DEPENDANCIESROLES AND RESPONSIBILITIESSoftware Development PlanASSUMPTIONSGROUP DEPENDENCIESCONSTRAINTSRISK IDENTIFICATIONESTIMATESEFFORTCOSTSSIZE OF DELIVERABLESSIZE OF NON-DELIVERABLESPROJECT PLAN DELIVERABLESPROJECT LIFE-CYCLEPROJECT SCHEDULE(s)PROJECT ACTIVITIESSCHEDULES AND MILESTONESCRITICAL COMPUTER RESOURCESFACILITIES AND TOOLSSOFTWARE CONFIGURATION MANAGEMENT PLANSOFTWARE QUALITY ASSURANCE PLANCOMMUNICATION PLANTEST PLANEND USER SUPPORT PLANSOFTWARE PROJECT TRACKING & OVERSIGHTAPPROVALSAPPENDIX 1: DEFINITIONSFilename: Feasibility Report Page 1 Last modified: 09/12/00Version: V.1.0 Printed: 09/14/00CS 501- Software EngineeringLegal Data Markup SoftwareRelease (V.1.0)Feasibility ReportVersion (1.0)Key Stakeholders/Organizations:Project Sponsors:Professor Thomas Bruce, Professor William ArmsFilename: Feasibility Report Page 2 Last modified: 09/12/00Version: V.1.0 Printed: 09/14/00Document Change History LogVersion#ChangeRequest#Description of changes to thisdocumentDateApprovedSection(s) of Project Plan affected.1.00 0 Initial Version 09/13/2000 AllFilename: Feasibility Report Page 3 Last modified: 09/12/00Version: V.1.0 Printed: 09/14/00Table of Contents1. INTRODUCTION....................................................................................................... 41.1 PROJECT OVERVIEW .............................................................................................................................41.2 PROJECT SCOPE ......................................................................................................................................41.3 REFERENCES.............................................................................................................................................41.4 PRODUCT/PROJECT or BUSINESS DEPENDANCIES.......................................................................41.5 ROLES AND RESPONSIBILITIES ..........................................................................................................52. SOFTWARE DEVELOPMENT PLAN ....................................................................... 62.1 ASSUMPTIONS ..........................................................................................................................................62.2 DEPENDENCIES ........................................................................................................................................62.3 CONSTRAINTS...........................................................................................................................................62.4 RISK IDENTIFICATION...........................................................................................................................62.5 ESTIMATES................................................................................................................................................62.5.1 EFFORT ................................................................................................................................................62.5.2 COSTS...................................................................................................................................................62.5.3 SIZE OF DELIVERABLES ..................................................................................................................62.5.4 SIZE OF NON-DELIVERABLES.........................................................................................................62.6 PROJECT PLAN DELIVERABLES.........................................................................................................72.7 PROJECT LIFE-CYCLE ...........................................................................................................................72.8 PROJECT SCHEDULE(s)..........................................................................................................................72.8.1 PROJECT ACTIVITIES .......................................................................................................................72.8.2 SCHEDULES AND MILESTONES .....................................................................................................73. CRITICAL COMPUTER RESOURCES..................................................................... 74. FACILITIES AND TOOLS......................................................................................... 75. SOFTWARE CONFIGURATION MANAGEMENT PLAN ......................................... 76. SOFTWARE QUALITY ASSURANCE PLAN .......................................................... 87. COMMUNICATION PLAN......................................................................................... 88. TEST PLAN .............................................................................................................. 89. END USER SUPPORT PLAN................................................................................... 810. SOFTWARE PROJECT TRACKING & OVERSIGHT............................................ 811. APPROVALS ......................................................................................................... 8APPENDICES ................................................................................................................. 8APPENDIX 1: DEFINITIONS .............................................................................................................................9Filename: Feasibility Report Page 4 Last modified: 09/12/00Version: V.1.0 Printed: 09/14/001 INTRODUCTION1.1 PROJECT OVERVIEWCornell’s Legal Information Institute (LII) currently has software that converts the US Code from formattedASCII input provided by the US House of Representatives into HTML. However, this software does nothandle some of the features very well and as desired, cannot convert the “raw” input into XML. ProfessorBill Arms was contacted by the LII to help in the implementation of this technical aspect. Consequently, thisproposal was suggested as one of the projects for the Software Engineering course, CS 501.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 the USHouse of Representatives. The XML version will follow a DTD that we will create. The design should bedone in such a way as to guarantee (so far as is
View Full Document
Unlocking...