Nathan Mikeska Richard Carney Brian Navarro Neil Alfredson

Project Overview Modernize current system Modernize current system ElectronicElectronic Web basedWeb based More efficient for large classesMore efficient for large classes Users Users Chemistry ProfessorsChemistry Professors Chemistry StudentsChemistry Students

Project Overview (cont) Functionality Functionality Arrangement of tilesArrangement of tiles Observation or playback of a submitted arrangementObservation or playback of a submitted arrangement Creation of new sets of tiles and arrangementsCreation of new sets of tiles and arrangements Goal of System Goal of System Students gain a better understanding of the periodic tableStudents gain a better understanding of the periodic table Teachers are given an insight into the thought processes of their studentsTeachers are given an insight into the thought processes of their students

Stakeholders Ms. Wiediger Ms. Wiediger Chemistry Students Chemistry Students Development Team Development Team

Project Organization Project Manager Project Manager Lead UI Designer and Lead Programmer Lead UI Designer and Lead Programmer Lead Designer Lead Designer Lead Quality Assurance Lead Quality Assurance

Project Organization (cont)

Development Process: Lifecycle Model

Development Process Methodologies - Object-oriented modular design Methodologies - Object-oriented modular design Policies - Modules developed and tested by individuals and small groups. - Further testing at group meetings if necessary. - Modules integrated at group meetings. Policies - Modules developed and tested by individuals and small groups. - Further testing at group meetings if necessary. - Modules integrated at group meetings. Standards - Standards -

Development Process (cont.) Tools - Documentation - Word, PowerPoint, Visio - Graphics - MS Paint, GIMP - Coding – NetBeans, Eclipse, JBuilder Tools - Documentation - Word, PowerPoint, Visio - Graphics - MS Paint, GIMP - Coding – NetBeans, Eclipse, JBuilder Version Control - Handled by Lead Programmer - Code stored at secure online location - All previous versions also organized and stored. Version Control - Handled by Lead Programmer - Code stored at secure online location - All previous versions also organized and stored.

Test Plan Module Testing - Done by individual or group that wrote code. - Further testing in group meetings if necessary. Module Testing - Done by individual or group that wrote code. - Further testing in group meetings if necessary. Integration Testing - Done at group meetings by Lead Programmer. - Code writers must be present at meeting. Integration Testing - Done at group meetings by Lead Programmer. - Code writers must be present at meeting. System Testing – Tile Arrangement - Use test cases (record unexpected behavior and examine log files). - Log files become test cases for Playback. System Testing – Tile Arrangement - Use test cases (record unexpected behavior and examine log files). - Log files become test cases for Playback.

Test Plan (cont.) System Testing – Playback - Use test cases generated from Tile Arrangement. - Record and document behavior. System Testing – Playback - Use test cases generated from Tile Arrangement. - Record and document behavior. System Testing – Creation - Make test cases for creating and modifying sets. - After passing Creation test cases, resulting sets will be tested in the other two subsystems. System Testing – Creation - Make test cases for creating and modifying sets. - After passing Creation test cases, resulting sets will be tested in the other two subsystems.

Test Plan (cont.) Acceptance Testing – Students - Tile Arrangement testing. - Will be observed and questioned afterwards. - Log files stored for Client Acceptance Testing. Acceptance Testing – Students - Tile Arrangement testing. - Will be observed and questioned afterwards. - Log files stored for Client Acceptance Testing. Acceptance Testing – Client - Tile Arrangement, Playback, Creation systems. - Tile Arrangement – same tests as students - Playback – use student test results. - Creation – create and modify small sets. - Observe and question afterwards. Acceptance Testing – Client - Tile Arrangement, Playback, Creation systems. - Tile Arrangement – same tests as students - Playback – use student test results. - Creation – create and modify small sets. - Observe and question afterwards.

Efforts and Schedule 6 Categories of Effort 1.Documents 2.Research 3.Implementation 4.Testing 5.Progress Review 6.Graphics Goal: Keep everyone busy but vary the work

Documents Existing Document Revision Contract Prototype Tutorial Full Manual (Developer and User) User Tutorials Logs & Status Reports

Research Java Programming Concepts File Formats Java Swing & Java Applets Mini-Map/Zoom & Grid Structure Simple Pattern Comparison

Implementation Prototype (Framework) Code Cleanup & Fixes Grid Mini-map/Zoom Rule Editor, Tile Editor, Pattern Editor Play Area

Testing System Testing Acceptance Testing Delivery Testing Integration Testing Module Testing

Progress Review Initial Client Demo & Web Site Client Progress Reviews Acceptance Testing Delivery Testing Final Report & Presentation

Graphics Applet Menu Interface Play Area Construction Grid Construction Tiles Playback Icons

Measurements Team Log Reports Team Log Reports Each member of the team will write up a weekly log report Manager Meetings Manager Meetings The project manager will meet with the senior Project Instructor Client Meetings Client Meetings Group meets with our client and talks about progression of project

Risk Management Using Java is the biggest risk we need to consider Using Java is the biggest risk we need to consider This means we will need to consider a learning curve for all group members This means we will need to consider a learning curve for all group members Java drag and drop operations are among the elements that may hinder our progress due to need for research Java drag and drop operations are among the elements that may hinder our progress due to need for research

Risk Management Our risk also includes a number of user interface difficulties we have come across Our risk also includes a number of user interface difficulties we have come across Limited screen spaceLimited screen space Amount of text on each cardAmount of text on each card Grid sizeGrid size Development of solutions to screen space issues (ex. Zoom, Mini-map, ect.)Development of solutions to screen space issues (ex. Zoom, Mini-map, ect.)

Ethical Considerations Security is an ethical consideration of all projects Security is an ethical consideration of all projects The security of the students resultsThe security of the students results Use for submission Use for submission Considerations of read/write privilegesConsiderations of read/write privileges Inform users of access to hard drive Inform users of access to hard drive Do not infect or exploit users Do not infect or exploit users

Ethical Considerations Who can use the system? Who can use the system? This was a decision that we needed to make and we thought about ethical implicationsThis was a decision that we needed to make and we thought about ethical implications No user-logons means we do not restrict to SIUE students and teachers No user-logons means we do not restrict to SIUE students and teachers By using java we allow users of different platforms to use our system (some chemistry professors do not use windows) By using java we allow users of different platforms to use our system (some chemistry professors do not use windows)

QUESTIONS?