Creating the Data Design Model Creating the Interface Design Creating the Control Design
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
Parts
» | Komputasi | Suatu Permulaan
» Quality Focus Process Method Tools
» What is quality? How do we define quality?
» Software Quality Characteristics of a Well-engineered Software
» Software Quality Assurance Activities Formal Technical Reviews
» Types of Software Process Models
» Understanding Systems | Komputasi | Suatu Permulaan
» End-users Understanding People in the Development Effort
» What is documentation? Criteria for Measuring Usability of Documents
» Abstraction Encapsulation Review of Object-oriented Concepts
» Modularity Hierarchy Review of Object-oriented Concepts
» Project Assignment Object-oriented Process Model
» Modeling Activity Unified Modeling Language UML
» UML Baseline Diagrams Unified Modeling Language UML
» Requirements Engineering Concepts | Komputasi | Suatu Permulaan
» Inception Requirements Engineering Tasks
» Elaboration Negotiation Requirements Engineering Tasks
» Specification Validation Requirements Engineering Tasks
» Management Requirements Engineering Tasks
» Scenario Modeling Requirements Analysis and Model
» Requirements Model Validation Checklist
» InvoiceNumber : Numeric Here, an attribute named InvoiceNumber contains a numeric value.
» Ternary association which is a relationship of three or more objects of
» The Analysis Model Analysis Model Validation Checklist
» Requirements Traceability Matrix RTM
» Requirements Metrics | Komputasi | Suatu Permulaan
» The Design Model Design Engineering Concepts
» Describing the Package Diagram Developing the Architectural Design
» Software Architecture Validation Checklist
» Developing the Data Design Model
» Report Design Interface Design
» Forms Design Interface Design
» Basic Component Design Principles Component-level Design Guidelines
» Component Diagram Developing the Software Component
» Project Assignment Design Model Validation Checklist
» Mapping the Design Deliverables to the Requirements Traceability Matrix Design Metrics
» Creating the Data Design Model Creating the Interface Design Creating the Control Design
» Project Assignment Programming Standards and Procedures
» Using Pseudocodes Control Structure Guidelines Documentation Guidelines
» Implementing Packages | Komputasi | Suatu Permulaan
» Abstract Classes Implementing Controllers
» Interfaces Why do we use Interfaces?
» Interface vs. Abstract Class Interface vs. Class Creating Interfaces
» Relationship of an Interface to a Class Inheritance among Interfaces
» Implementing Java Database Connectivity JDBC
» AWT GUI Components Implementing the Graphical User Interface
» Layout Managers Implementing the Graphical User Interface
» Controlling the Version of the Software
» Introduction to Software Testing
» White-Box Testing Techniques Software Test Case Design Methods
» Black-Box Testing Techniques Software Test Case Design Methods
» Testing your Programs | Komputasi | Suatu Permulaan
» Test-driven Development Steps Test-driven Development Methodology
» Testing Java Classes with JUnit
» Testing the System | Komputasi | Suatu Permulaan
» Mapping the Software Testing Deliverable to the RTM Test Metrics
» Project Assignment Software Project Management
» Problem Identification and Definition
» The Project Team Structure Project Responsibility Chart
» Project Work Breakdown Structure WBS
» Work Breakdown Schedule Format
» Size-oriented Metrics- Lines of Codes LOC Function-Oriented Metrics: Function Points FP
» Project Estimations | Komputasi | Suatu Permulaan
» The Risk Table Risk Management
» Risk Identification Checklist Risk Management
» Baseline Software Configuration Tasks
» Writing the Project Plan Project Assignment Case Tools
Show more