Due Date: Thursday, February 15, in class -

For the proposal phase of your project you will need to state who is on your team, who is your team leader and who is going to be assigned what responsibilities for your project. Each team will thus submit one proposal. The responsibilities of team members may change over time, but give the initial assignments. You will need to turn in a preliminary Problem Statement/Requirements Definition, and initial Entity-Relationship (ER) Diagram, and an initial set of Use Cases. These are the items 1), 2), and 5) as described in your Phase 1 Design Requirements. Present the elements of your proposal in exactly this order. Again, these are preliminary and I would expect that they will change as you refine what you need to do to implement your project over time.

1) Problem Statement/Requirements Definition. Develop a narrative statement of the needs for this project. Begin with a overview and background description of the organization and enterprise. What is the business operation that you are automating? Next describe what is to be done and what business processes you are focusing on for the project. Your Requirements Statement needs to include the problem scope, what is needed, the application context, and assumptions and performance needs.

2) The Entity-Relationship Model which will provide the mapping to the global schema for your database. Not due in the Proposal Phase , but due in the Phase 1 Design phase you will also build a *simple* Object Model diagram according to the Rumbaugh Methodology discussed in class and shown in notes. Entity-Relationship Modeling is covered in Chapter 2 of your text and in the course notes. Object-Oriented and Object-Relational Databases are covered in Chapters 8 and 9 respectively.

3) A Set of Use Cases: You will need to include a use case diagram and a narrative description of each use case. If use cases are complex, break them down hierarchically into sub-use cases. Use cases are described in the notes. See other links on my web page for more on Use Cases.

4) A filled-in evaluation form from each and every one of your project team.