This project will simulate the process and deliverables for a typical software development project and go through the major steps of the software development life cycle. This will give you real experience in each stage, from planning, requirements gathering, system design, implementation, and testing. The point is to develop and describe a project in such a way that it feels real, that it presents a system that could very well exist and provides documentation that all stakeholders could understand and work with. You will use UML diagrams, wireframes, text descriptions, and graphs to create your deliverables. You will not be required to develop any code or create a product, only the supporting documentation.

First, select one of the following possible scenarios

A mobile application that will compete with the latest games on a tablet platform

A website for a bank that allows customers to manage their finances

An air traffic control suite that will be utilized by a major metropolitan airport for routing and management of airplane traffic

Next, you will create a number of documentation deliverables that will reflect the scenario you chose. This scenario will be used for Parts 2 and 3 as well. These deliverables will combine together to create your software development project report. Each deliverable should take a minimum of one page. Include citations throughout, as necessary. Part I deliverables are as follows

Product Overview A description of the overall product being developed, along with related information, such as the market, competitors, and constraints. Notes: This is written in paragraph form, perhaps with a chart to support your claims if necessary. Define what you want to build in a very broad sense and why you would want to build it. Start thinking here about tasks and features that customers and user s expect with this system.

Stakeholder Overview Identify the stakeholders and their desires. Determine objectives, possible conflicts, and rank importance of certain aspects (cost, functionality, etc.) to each stakeholder. Notes: Works best in table format listing each party involved, how much say they have, how much time they can devote, how critical they are, etc.. You may choose a ranking system for such things as long as you define it.

Requirements Analysis Create a list of at least ten (10) system requirements. Notes: Define in very clear, detailed terms what your system does. You will want requirements that are both functional and non-functional. Requirements may be dependent on other requirements or grouped into subsets.