AI Summary
[DOCUMENT_TYPE: concept_preview]
**What This Document Is**
This document is a Feasibility Evidence Description (FED) – a critical component in the early stages of a software engineering project. Specifically, it details the feasibility analysis for a “Mission Science Information and Data Management System” developed by Team 06 at the University of Southern California (USC) as part of the CSCI 577 Software Engineering course. The FED serves as a comprehensive assessment of whether the proposed system is viable from technical, operational, and economic perspectives. It represents a key deliverable demonstrating the team’s due diligence before proceeding further into development.
**Why This Document Matters**
This resource is invaluable for students studying software engineering, systems analysis, or project management. It’s particularly useful for those learning about the software development lifecycle and the importance of upfront planning and risk assessment. Individuals involved in similar team-based software projects will find the structure and approach outlined within highly beneficial. Understanding the contents of a FED can also be helpful for stakeholders evaluating the potential of a new software system before significant investment is made.
**Common Limitations or Challenges**
This FED focuses on the *feasibility* of the project, meaning it doesn’t delve into the detailed design specifications, code implementation, or user interface elements of the “Mission Science” system. It doesn’t provide a complete blueprint for building the software, but rather a justification for *whether* building it is a sensible course of action. It represents a snapshot in time (October 2011) and reflects the team’s understanding of the project requirements and available technologies at that specific point.
**What This Document Provides**
* A structured assessment of the project’s feasibility across multiple dimensions.
* A version history tracking changes and rationales throughout the analysis process.
* Detailed tables outlining evaluation criteria for various system attributes.
* Evidence supporting the selection of a specific software development model.
* Analysis of potential implementation strategies and associated costs.
* Consideration of market trends and the product lifecycle.
* A comprehensive table of contents for easy navigation.