[Main]

Requirements for the Software Project

1. Write a problem statement: A problem statement is a general description of your project that anyone can understand.
2. Write Requirements for your project: Write up general requirements for your project in the form of Specific Scenarios and non-functional requirements. Scenarios help communicate the functionality of your system to others, so that they may reach a level of understanding so that you and they can rectify and elaborate the requirements further. This phase requires your ability to communicate with others and translate their often verbal requirements onto legible English.
3. Analysis Phase: After all the requirements have been gathered, perform an analysis.
4. For this course, you need to implement a three tier architecture.
   1. Data Model E-R Diagrams.
   2. Business Services Analysis for every Scenarios.
5. Implementation Phase:
   1. Write the SQL and execute them on a database.
   2. Implement the Business Services
   3. Unit Test your services by going through specific scenarios.
   4. Now start implementing your User Interface.
6. Verify that every scenario in your requirements has been met.
7. Write your final document to submit as your project. Your project must contain:
   1. Problem Statement
   2. Requirements
   3. E-R Diagram with a Data Dictionary
   4. Business Service Analysis with documentation explaining your services
   5. SQL Statements for your database
   6. Source code for the implementation of your Business Services.
   7. Source Code for your Unit Tests
   8. Source Code for your Presentation Tier.
8. Demonstrate your project.