What This Document Is
This document is a Feasibility Evidence Description (FED) prepared by Team 06 for CSCI 577 Software Engineering at the University of Southern California. It focuses on the NDI/NCS system (Version 1.6) and represents a critical stage in the software development lifecycle – assessing the viability of proceeding with a project based on gathered evidence. The FED details an analysis of the system’s feasibility across various dimensions, serving as a key deliverable for a Test Readiness Review. It’s a formal report outlining the team’s findings regarding the practicality of implementing the system as defined by its requirements.
Why This Document Matters
This FED is essential for students studying software engineering, particularly those focusing on system design, requirements engineering, and project management. It’s valuable for understanding how to systematically evaluate the feasibility of a software project *before* significant development resources are committed. Individuals preparing for roles in software architecture, quality assurance, or project leadership will find this report insightful. It’s most useful when studying the processes involved in risk assessment, requirements validation, and the transition from conceptual design to implementation. Understanding the structure and content of a FED will help you prepare similar reports in your own projects.
Common Limitations or Challenges
This FED provides a detailed *assessment* of feasibility, but it does not contain the actual source code, detailed design specifications, or implementation plans for the NDI/NCS system. It focuses on the ‘why’ and ‘if’ of the project, not the ‘how’. The document presents evidence-based conclusions, but it doesn’t offer a step-by-step guide to building the system. It also represents a snapshot in time (December 3, 2011) and may not reflect subsequent changes or updates to the project.
What This Document Provides
* A version history tracking changes and rationales throughout the FED’s development.
* A comprehensive table of contents outlining the scope of the feasibility analysis.
* Detailed tables summarizing evaluation criteria related to system attributes and features.
* Evidence supporting the feasibility of various system capabilities and levels of service.
* Analysis of risks and their potential impact on project success.
* Discussion of the architectural model selected for the project and its justification.
* A structured approach to documenting feasibility evidence for a complex software system.
