Welcome
C.S.S. is a team consisting of dedicated and determined problem solvers.
Our team is extremely diverse in several technological fields.
We'll take a bite out of your problem!
Click on a person's face to find out more about them
Daniel Rotondo
SE I - Webmaster, SE II - Co-Team Leader
Brittany Lintelman
Documentarian
Akeem Shirley
Database Administrator
Ryan Godfrey
SE I - Lead Programmer, SE II - Co-Team Leader
Rebecca Wilson
Informatin Specialist
Kurt Greiner
SE I - Team Leader, SE II - Lead Programmer
Current Status - Acceptance Test
Software Plan: Define client's problem after continuous weekly meetings with the client to establish the goal. The Software Plan outlines the problem and the current solution as decided by Code Shark Solutions and the client.
Requirements - Specifications: All possible requirements of the system to be developed are captured in this phase. Requirements are set of functionalities and constraints that the end-user (who will be using the system) expects from the system.
Preliminary Design: Before a starting for actual coding, it is highly important to understand what we are going to create and what it should look like? The requirement specifications from first phase are studied in this phase and system design is prepared. System Design helps in specifying hardware and system requirements and also helps in defining overall system architecture. The system design specifications serve as input for the next phase of the model.
Detailed Design: On receiving system design documents, the work is divided in modules/units and actual coding is started. The system is first developed and all goals and requirements are met.
Acceptance Test: Software from the implementation step is tested for it's functionalities and tested to check if the system behaves as per the specifications. After successfully testing the software, it is delivered to the customer.
Documents
Software Plan |
 .pdf | |
 .htm |
Software Plan Presentation |
 .ppt | |
.htm |
Requirements - Specification |
.pdf | |
.htm |
Requirement Specifications Presentation |
.ppt | |
.htm |
Preliminary Design |
.pdf | |
.htm |
Preliminary Design Presentation |
.ppt | |
.htm |
Detailed Design |
.pdf | |
.htm |
Detailed Design Presentation |
.ppt | |
.htm |
Acceptance Test |
.pdf | |
.htm |
Acceptance Test Appendix D: Source Code |
.pdf | |
.htm |
Acceptance Test Presentation |
.ppt | |
.htm |
Client Notes
Meeting Date |
Document |
|---|---|
Tuesday Sept. 16th |
Client Meeting #1 .pdf |
Thursday Sept. 16th |
Client Meeting #2 .pdf |
Tuesday Sept. 21rd |
Client Meeting #3 .pdf |
Tuesday Sept. 28th |
Client Meeting #4 .pdf |
Thursday Sept. 30th |
Client Meeting #5 .pdf |
Tuesday Oct. 5th |
Client Meeting #6 .pdf |
Tuesday Oct. 19th |
Client Meeting #7 .pdf |
Thursday Oct. 21st |
Client Meeting #8 .pdf |
Tuesday Nov. 2nd |
Client Meeting #9 .pdf |
Tuesday Nov. 9th |
Client Meeting #10 .pdf |
Thursday Nov. 11th |
Client Meeting #11 .pdf |
Tuesday Nov. 30th |
Client Meeting #12 .pdf |
Monday Jan. 1st |
Client Meeting #13 .pdf |
Monday Feb. 21st |
Client Meeting #14 .pdf |
Monday April 11th |
Client Meeting #15 .pdf |
Team Notes
Meeting Date |
Document |
|---|---|
Wednesday Sept. 15th |
Team Meeting #1 .pdf |
Sunday Sept. 19th |
Team Meeting #2 .pdf |
Wednesday Sept. 22rd |
Team Meeting #3 .pdf |
Wednesday Sept. 29th |
Team Meeting #4 .pdf |
Tuesday Oct. 5th |
Team Meeting #5 .pdf |
Wednesday Oct. 6th |
Team Meeting #6 .pdf |
Tuesday Nov. 9th |
Team Meeting #7 .pdf |
Sunday Nov. 14th |
Team Meeting #8 .pdf |
Monday Nov. 15th |
Team Meeting #9 .pdf |
Wednesday Nov. 17th |
Team Meeting #10 .pdf |
Monday Nov. 29th |
Team Meeting #11 .pdf |
Preliminary Design prototype: PD Demo Home
Detailed Design prototype: DD Demo Home
Acceptance Test prototype: AT Demo Home
.wmv
.mov
.avi
.rtfAkeem Shirley
Database Administrator
Akeem will be responsible for all of our team's databases.
Resume - .pdf
Email - aj15shir@siena.edu
Brittany Lintelman
Documentarian
Brittany will be responsible for all of our team's documents and notes.
Resume - .pdf
Email - bn15lint@siena.edu
Daniel Rotondo
Software Engineering II - Co-Team Leader
Daniel is responsibile for organizing and managing the project and his team members.
Software Engineering I - Webmaster
Daniel will be in charge of the team's website along with any web development for the project.
Resume - .pdf
Email - dm30roto@siena.edu
For more info about Daniel Rotondo, please visit: www.droto.net
Kurt Greiner
Software Engineering II - Lead Programmer
Kurt's main responsibility is to help create the underlying architecture of the software project.
Software Engineering I - Team Leader
Kurt's responsibility is to organize meetings and the rest of the team.
Resume - .pdf
Email - kc13grei@siena.edu
Rebecca Wilson
Information Specialist
Rebecca will manage the team's notes from meetings and make them presentable to the client.
Resume - .pdf
Email - ra03wils@siena.edu
Ryan Godfrey
Software Engineering II - Co-Team Leader
Ryan's responsibility is organize and manage the project and team members.
Software Engineering I - Lead Programmer
Ryan's responsibility is to create the underlying architecture of the software project.
Resume - .pdf
Email - rd02godf@siena.edu