1. CS/SWE 421 Project Overview Dan Fleck

2. Project Overview Team Formation Team Formation - just to get an idea of who you are and what you want to do Detailed Project Statement - More explanation of the project. I want you to think about it, understand the implications and start to “sell” the project idea to management (me)  Real World - Used as a 10 minute presentation to your boss/client/potential investors to sell the project and get resources ($$ and people)

3. Project Overview Software Requirements Spec (SRS) - Gives detailed requirements and use cases.  Real world - used to validate your understanding of the project with stakeholders. Also during the process you will gain a much deeper understanding of the project High level analysis - Diagrams help explain more information about the project  Real world - same as SRS

4. Project Overview Detailed Analysis Detailed Analysis - low level design/implementation information (not done in this class)  Real world - used by development/test teams to create a plan to build the software. Also helps minimize changes during development Implementation - Not done in this class  Real world - includes coding, unit testing, fixing,

5. Project Overview Testing - Test cases written to explain how to test all aspects of your software.  Real world - test cases are used to help all testers know what to test and also by other parties (developers, quality assurance, management, customers) to validate that everything is being tested thoroughly Deployment - Not done in this class  Real world - includes training and user documentation, delivery and installation, support (help desk), etc…