Software Engineering Project Assignment 7 Group 3 IT-201

Proposal: Develop and deliver Engineering Logistical Support Information System.  Database drive web application  Coast Guard wide.  HQ established matrices.

Current state: Each unit tracks port services, weapons training, and engineering functions in their own way. Negatives:  Matrices do not always match HQ desired.  Information loss.  Non-transparent.  Inefficient.

Current records: Paper copy. Logs. s Verbal

Current records (cont.): Negatives:  Records get lost.  Supervisor not always aware of what personnel are doing.  CG HQ not fully aware of funding, personnel, AFC budget, and MILCON budget use.

Desired state: CG wide system – totally transparent. Uniform system  Reduced training of reporting personnel. Better use of annual CG budget. Better use of manpower. Better use of Military Construction Funding.

Desired records: Web forms for data collection. Databases for information storage. Webpage reports.

Deliverables: List of matrices for all facets of the proposed system arrived at by sampling 15% of Coast Guard duty Station’s. Preliminary system specifications once matrices are approved by CG. Interactive Model of system for user review. Beta test at Coast Guard HQ and two East and two West coast Station’s. Revise system after two month beta test. Final system role out to 10% of CG

Development team: Program Manager: Paul Sanger. Lead information data mining: Valerie Dazey. Lead modeling and simulation: Jonathan White. Lead Software development: Robert Mackey.

Tasks: Valerie’s group: determine adequate matrices. Robert’s group: write preliminary software specifications with PM utilizing customer input. Jonathan’s group: create module of user interface working with Robert to ensure front and back end functionality. Paul: hire contractor for installation of beta test gear. Robert send group members to install, train, and support units during initial two weeks of beta test. Paul: Arrange Beta test debrief site all leads and customer representative evaluate feedback. Robert’s group: revise system for final rollout.

Budget: Initial budget for system is $225, for data-mining, simulation, beta testing, revision, and software delivery. Implementation if accepted is to roll out in four phases each comprising 25% of the Coast Guards units. Lifecycle cost, if system is accepted, is expected to be $1M for 10 years.

Budget breakdown: $30k data-mining. $50k modeling simulation. $60k beta software development. $10k revision meetings. $75k final software development.

Timeline: From contract date: 2-month: Data-mining matrices report submittal. 2.5-months: CG acceptance of matrices. 5-months: Working model delivers to CG for evaluation. 6-months: Milestone A (PM needs to authorize further development)-CG feedback submitted. 9-months: Beta type delivered.

Timeline (cont.): 11-months: Milestone B (PM needs to authorize initial production)-CG feedback submitted. 16-months: Software delivered to CG. 17-months: Milestone (PM need to authorize initial full rate production/installation) 22-months: Initial 25% of CG units online. 28-months: If CG authorizes 2nd quarter of CG units online. 32-months: If CG authorizes 3rd quarter of CG units online. 36-months: If CG authorizes entire CG online.