SWIM-Suite Final Product Demo Team members: Abhishek Bindiganavile Robert Greenberg Sedat Ozer Jay Takle Swimming Meet Management Software
Motivation - Write about swim meets
Requirements - Requirements
Class Diagram - Class Diagram
Software Architecture - Used a MVC architecture pattern. - Isolates the application logic from the user(Separation of concern). - Advantages: Independent development, testing and maintenance.
Subsystem Decomposition - 3 layered system with 7 subsystems - Higher cohesion and minimum coupling possible.
Hardware/software Mapping
Testing - Write about the test cases
Team Responsibilities Jay Takle: Requirements Analysis. Abhishek Bindiganavile: System Designing. Sedat Ozer: Algorithm Designing. Robert Greenberg: Testing. - Each member was allotted at least one sub-system to code and write at least one document throughout the process. - Helped in recognizing individual strengths.
Project Status & Demo - Write about what you will show at the demo