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 centers around the NDI'NCS (likely a system name) 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 requirements, architecture, and potential implementation strategies. It’s a formal report outlining the team’s findings regarding the feasibility of building the proposed system.
Why This Document Matters
This report is invaluable for students studying software engineering, systems analysis, and project management. It’s particularly relevant for those learning about requirements engineering, system architecture, and risk assessment. Individuals preparing for system design reviews or needing to understand the process of validating a project’s feasibility will find this resource beneficial. It showcases a real-world application of theoretical concepts, demonstrating how feasibility is determined and documented in a professional setting. Understanding the structure and content of a FED is crucial for anyone involved in the early stages of software development.
Common Limitations or Challenges
This FED focuses specifically on the feasibility aspects of the NDI'NCS system. It does *not* contain detailed code, implementation plans, or user manuals. It’s a high-level assessment and doesn’t delve into the specifics of coding or testing. The document represents a snapshot in time – the findings are based on information available as of December 3rd, 2011, and may not reflect subsequent changes or updates to the project. It also doesn’t provide a complete solution, but rather an evaluation of whether a solution is realistically achievable.
What This Document Provides
* A version history tracking changes and rationales for updates to the FED.
* A comprehensive table of contents outlining the scope of the feasibility assessment.
* Tables detailing requirement prioritization and evaluation criteria.
* An analysis of the selected architectural approach and its justification.
* Evidence related to the feasibility of specific system capabilities.
* An overview of the level of service implementation strategy.
* A record of the team members and their roles within the project.
