CS 425 – F ALL 09 C ORY L EHAN T IM M EYER J ARROD C APPS J ONATHAN B RIDGES F INAL P RESENTATION

P ROJECT O UTLINE CS Team Neurotic 2 Cognitive Dissonance Reduction in Neural Networks

Participants CS Team Neurotic 3 Manager Dr. Fujinoki Manager Dr. Fujinoki Client/User Dr. Watson Client/User Dr. Watson Members Tim Meyer Jarrod Capps Jonathan Bridges Members Tim Meyer Jarrod Capps Jonathan Bridges Team Leader Cory Lehan Team Leader Cory Lehan

Team Roles CS Team Neurotic 4 Team Leader Customer Interface Support Cory Lehan Test Manager Process Manager Tim Meyer Implementation Manager Plan Manager Jarrod Capps Design Manager Quality Manager Jonathan Bridges

Ethical Considerations CS Team Neurotic 5 Client Relations  Bi-weekly meetings at client’s discretion. Individual Accomplishments  Author and Co-author tags. Academic Awareness  Put forth best effort, due to the sharing of a group grade.

Background Cognitive Dissonance  A cognition can be a belief or attitude a person holds.  Dissonance occurs when cognitions contradict each other.  Very uncomfortable feeling in humans. 6 CS Team Neurotic Responsibility Cognition 2 Cognition 1 BeliefDissonance Reduction occurs to reduce the unpleasant feeling.

Background CS Team Neurotic 7 Neural Networks  Two main groups: A.I. & Cognitive Modeling. Artificial Intelligence with Neural Networks  Problem solving.  Pattern recognition.  Can be trained or learn. Cognitive Modeling in Neural Networks  Models biological neural systems.  Heavy use of mathematical models.

Background CS Team Neurotic 8 Neural Network for this project  Concerned with modeling, not problem solving.  Based off the Consonance Model from “Connectionist Models of Social Reasoning And Social Behavior”.  Will attempt to simulate dissonance reduction.

Background CS Team Neurotic 9 The Consonance Model.  Cognitions  Two nodes at polar ends.  Resistance to change  Nodes contain an activation level.  Firing rate of neuron.  Represents direction and strength of the attitude or belief (the cognition) Cognition

Background CS Team Neurotic 10 The Consonance Model.  Cognitions are connected through their nodes bi-directionally.  Connections are weighted positively or negatively.  Cognitions are related positively or negatively Cognition 2Cognition 1

R EQUIREMENTS CS Team Neurotic 11

Hardware Environment CS Team Neurotic 12 What They Are  Windows Environment (XP, Vista, 7)  Minimum disk storage ~50mb  1 GHz Pentium III, or greater, processor. How We Know  Based off requirements of similar software the client runs.

Software Requirements CS Team Neurotic 13 Requirements Gathering  Repeated meetings with the client.  Use Cases  Interface Mock-up to gather features for.

Software Requirements CS Team Neurotic 14 Feature Priority List  Generated from gathering phase.  Priority assigned based off client need, and risk assessment.  Estimates are conservative, and based off previous experience. PriorityItem#Description Est. (days) Very High Neural network components with attributes- 1 Cognitions, Nodes2 2 Connections2 3 Update algorithm for iterations4 4 Neural network creation wizard3 Feature Priority List Example:

Software Requirements CS Team Neurotic 15 Key Features  User created neural network.  Ability to load/save past creations.  Ability to edit properties of a created neural network.  Start/Pause the neural network simulation.  Graphical representation of the neural network.  Graph output of dissonance.

D EVELOPMENT E NVIRONMENT CS Team Neurotic 16

Programming Language CS Team Neurotic 17 What is it?  Java Why?  Helpful Neural Network books with Java.  JFreeChart and JOGL Java libraries.  Java SWING provides interface creation.

Libraries CS Team Neurotic 18 JFreeChart  Allows dynamically created charts.  Meets requirements based off tested code in High-Fidelity prototype. JOGL (Java OpenGL)  Allows the graphical representation of the neural network.  Certain it meets required needs based off previous experience.

Software Tools CS Team Neurotic 19 Subversion  Used with all documents and code. NetBeansIDE  Java support.  JUnit  Subversion support. Doxygen  For generating software reference documentation.

Coding & Documentation Standards CS Team Neurotic 20 Code Comments  Javadoc style comments Indentation  Standard 4 space “hanging paragraph” style. Naming  Camel Casing (e.g. camelCasing)  Noun phrases for class names.  Verb phrases for method names.

D EVELOPMENT P LAN CS Team Neurotic 21

Software Engineering Methodology CS Team Neurotic 22 Based off certain agile “Best Practices”  Customer Involvement  Test Before Code  Code Review and Refactor  Stand-up Meetings  Problem Solving with Patterns

Developed in iterations. Gather RequirementsDesign - System StructureIncremental DevelopmentSystem TestingReview & Release Software Process CS Team Neurotic 23

Software Process CS Team Neurotic 24 Incremental Development  Begins by converting features to tasks. Design Implementation & Unit Testing System Testing Review Feature-to- Task

Software Process CS Team Neurotic 25 Reasons for Process Choice  Adaptability to changing requirements.  Iterative nature gives an early working build.  Allows for a lot of testing.  Keeps client involved through iteration reviews.

Risk Analysis CS Team Neurotic 26 R ISK M ITIGATION T ACTIC Dissonance reduction algorithm doesn’t work. Design pseudo-code of algorithm. Priority of first iteration. Interface and Graph Output don’t interact with one another correctly. Extensive documentation purchased on JFreeChart. Implemented chart in high-fidelity prototype. No working product early enough for client to begin research. The first iteration will contain only the bare and highest-priority items.

Project Plan CS Team Neurotic 27 Iteration #1 – Very High Priority Features

Project Plan CS Team Neurotic 28 Iteration #2 – High Priority Features

Project Plan CS Team Neurotic 29 Iteration #3 – Moderate Priority Features

Project Plan CS Team Neurotic 30 Iteration #4 – Low Priority Features (Optional)

Testing Plan CS Team Neurotic 31 Testing will be done in 3 phases:  Phase 1: Functionality Testing. Done by individual programmer.  Phase 2: Requirements testing. Done by majority of the team including Client.  Phase 3: Final testing of Program. Done by the majority of the team. Unit testing will be done in all Phases.

D ESIGN CS Team Neurotic 32

CS Team Neurotic 33 Static class diagram of system structure Observer Pattern Displays are updated when new data is available. Allows dynamic addition or remove of observing displays. Singleton Pattern Only one instance of the network data can exist. Gives a global access point to the data.

Graphics CS Team Neurotic 34 Displays the Neural Network in a graphical, user-friendly way Takes mouse input for easily modifying the network Tasks are divided into separate classes for expandability

Algorithm CS Team Neurotic 35 Current algorithms are rather simple  Formulas contained in texts Client may need more advanced algorithms  Dynamic connection weights are desired  Both client and team will work together to develop a more advanced algorithm to simulate these changes

Algorithm CS Team Neurotic 36 Pseudo-code created of simple dissonance reduction algorithm, and calculating consonance/dissonance. calculateConsonance { float consonance; for(... Node i) { for(... Connection j) { consonance += Node[i].con[j].weight * Node[i].activation * Node[j].activation; } Sample of calculating consonance:

P ROTOTYPE D EMO CS Team Neurotic 37

Questions? CS Team Neurotic 38 Cory Lehan Tim Meyer Jarrod Capps Jonathan Bridges