What This Document Is
This is a Feasibility Evidence Description (FED) – a critical component in the software development lifecycle, specifically within a Software Engineering course (CSCI 577) at the University of Southern California. It represents a detailed analysis undertaken by Team 06 for a project called “Mission Science,” an information and data management system. The FED outlines the viability of the project from a technical, operational, and economic standpoint, serving as a foundational decision point for proceeding with further development. It’s a formal assessment, structured to demonstrate the project’s potential for success.
Why This Document Matters
This document is invaluable for students studying software engineering, systems analysis, or project management. It’s particularly relevant for those learning about requirements engineering, feasibility studies, and the application of agile methodologies. Professionals involved in software development, particularly those in roles requiring risk assessment and project justification, will also find this a useful reference. Understanding the structure and content of a FED is crucial for anyone involved in initiating and planning complex software projects. It provides a blueprint for evaluating project success *before* significant resources are committed.
Common Limitations or Challenges
This FED focuses on the *feasibility* of the “Mission Science” system. It does not contain the actual software code, detailed design specifications, or implementation plans. It’s a high-level assessment, and while it identifies potential challenges, it doesn’t offer solutions to those challenges. Furthermore, the document represents a snapshot in time (October 2011) and may not reflect subsequent changes or updates to the project. It’s a planning document, not a finished product.
What This Document Provides
* A version history tracking changes and rationales for those changes.
* A comprehensive table of contents outlining the scope of the feasibility study.
* Detailed tables presenting evaluation criteria for various project attributes.
* Analysis of requirement prioritization and service level satisfiability.
* Evidence related to the project’s evolutionary feasibility and market trends.
* Considerations regarding hardware and software costs associated with the project.
* An overview of the selected development model and its justification.
