Creating the Data Design Model Creating the Interface Design Creating the Control Design

J.E.D.I

4.11 Exercises

4.11.1 Creating the Data Design Model

1. Create the Data Design Model of the Coach Information System. • Create the static view of the persistent classes. • Model the dynamic behavior of the persistent classes which includes initialization, create, read, update and delete. 2. Create the Data Design Model of the Squad Team Maintenance System. • Create the static view of the persistent classes. • Model the dynamic behavior of the persistent classes which includes initialization, create, read, update and delete.

4.11.2 Creating the Interface Design

1. Design the Report Layouts of the following, and use the standards as defined in this chapter. • List of Members by Status • List of Members who will be moving on or graduating next year • List of members who have not yet paid their renewal fee 2. Redesign the Application Form that accommodate the additional athlete information that the club owners want. Use the standards as defined in this chapter. 3. Refine the screen design of the Athlete Screen as shown in to include additional information needed by the club owners. • Create a new screen prototype. • Define the screen as a class. • Model the behavior of the screen. 4. Create the screen design and dialog design of the Coach Information System. • Create the screen prototype. • Define the screen as a class. • Model the behavior of the screen. 5. Create the screen design and dialog design of the Squad and Team Maintenance System. • Create a the screen prototypes. • Define the screens as classes. • Model the behavior of the screen.

4.11.3 Creating the Control Design

1. Refine the control classes of the Coach Information System. • Refine and redefine the control classes. Software Engineering 201 J.E.D.I • Model the behavior of the control classes with the screen and persistent classes. • Model the component using the component diagram. 2. Refine the control classes of the Squad Team Maintenance. • Refine and redefine the control classes. • Model the behavior of the control classes with the screen and persistent classes. • Model the component using the component diagram. 3. Define the component diagram of the software • Refine the software architecture by repackaging the classes. • Define the component diagram of each package in the software architecture.

4.12 Project Assignment