WelcomeOur ClientDr. Timoth C. LedermanProfessor of Computer ScienceSiena College
2
Code Shark Solutions Detailed Design
AgendaIntroductionOur ModelProblem DefinitionRequirements InventoryData DesignTest PlanPrototype screens/demoWhat is next?
3
Code Shark Solutions Detailed Design
IntroductionOur Team
Daniel RotondoCo-Team Leader
Ryan GodfreyCo-Team Leader
Kurt GreinerLead Programmer
Rebecca WilsonInformation Specialist
Akeem ShirleyDatabase
Administrator
Brittany LintelmanDocumentarian
4
Code Shark Solutions Detailed Design
AgendaIntroductionOur ModelProblem DefinitionRequirements InventoryData DesignTest PlanPrototype screens/demoWhat is next?
5
Code Shark Solutions Detailed Design
AgendaIntroductionOur ModelProblem DefinitionRequirements InventoryData DesignTest PlanPrototype screens/demoWhat is next?
7
Code Shark Solutions Detailed Design
ROSES Problem DefinitionSite lacks functionality
Inconsistent menuNo Search feature
Is not aesthetically pleasing
8
Code Shark Solutions Detailed Design
AgendaIntroductionOur ModelProblem DefinitionRequirements InventoryData DesignTest PlanPrototype screens/demoWhat is next?
9
Code Shark Solutions Detailed Design
Functional RequirementsView WebsiteWill be able to view all pages the client requires.Will be able to click links to this year’s team pages, Siena
College Homepage, Siena Computer Science website, Siena School of Science website, Siena Career Center website.
Calendar will open to the current date.Will be able to select a date to display to.Will have a consistent menu system.
10
Code Shark Solutions Detailed Design
Functional RequirementsSearchWill be able to search by student name, team name, course
year.Will be able to select Student Name, Team Name, or Course
Year from the displayed results.Will be able view page for a student, software team, team
year.Will resize photos of teams and individuals to stay
proportional given a static width.Will be able to print the result pages for Students and TeamsWill be able to click link to view all teams or all course years.
11
Code Shark Solutions Detailed Design
Non-Functional RequirementsSystem must be:
Aesthetically pleasing
Easily navigableEasily maintainable
for instructorEasily modifiable
12
Code Shark Solutions Detailed Design
AgendaIntroductionOur ModelProblem DefinitionRequirements InventoryData DesignTest PlanPrototype screens/demoWhat is next?
13
Code Shark Solutions Detailed Design
Data DictionaryLists all data entities and variable with in a
system
Used to help understand items in the database
14
Code Shark Solutions Detailed Design
MS Access 2007 Relationships Diagram
Provides a visual representation of the database.
Shows tables, fields, and relationships between tables.
16
Code Shark Solutions Detailed Design
Entity-Relationship (ER) Diagram
18
Code Shark Solutions Detailed Design
Provides a graphical representation of entities of a database and their relationships to each other.
Consists of entities, attributes, and relationships.
EntitiesDisplayed as rectangles.Represent a table in the database.AttributesDisplayed as ovals.Represent data associated with entity or
relationship.
Entity-Relationship (ER) Diagram
19
Code Shark Solutions Detailed Design
RelationshipsDisplayed as diamondsRepresent relationship between two entitiesOne-to-OneOne-to-ManyMany-to-Many
Database Relational Schema
21
Code Shark Solutions Detailed Design
Different way to show table organization.Shows primary and foreign keys.
Student(studentID, firstName, lastName, picture, resume, teamLeaderFall, teamLeaderSpring, teamName) Team(teamName, acronym, clientID, siteLink, fallYear, springYear, projectName, projectAcronym, demo, song, teamPic) Client(clientID, firstName, lastName, title, organization) Speaker(firstName, lastName, talkDate, subject, degree, title1, title2, employer1,employer2, employer1City, employer2City, employer1State, employer2State,employer1URL, employer2URL, presentation, talkSemester, talkYear)
AgendaIntroductionOur ModelProblem DefinitionRequirements InventoryData DesignTest PlanPrototype screens/demoWhat is next?
22
Code Shark Solutions Detailed Design
Test PlanDocuments the strategy used to test
Ensures that the Functional and Non-Functional Requirements are met
Includes all of the following: unit testing, integration testing, system testing, and acceptance testing
23
Code Shark Solutions Detailed Design
Our StrategyBreak the project in to units
Ensure the units work properly alone
Make sure the units interact correctly
Test that the whole system functions as expected
Guarantee that all Functional and Non-functional requirements are met
24
Code Shark Solutions Detailed Design
Unit Test Excerpt
25
Code Shark Solutions Detailed Design
Search By Student NameUnit 2.1To search for a particular student by their name
Test Cases
Pass/ Fail
Status
Test Number
DescriptionAction to
perform test (input)
Steps to be Executed
State Before Test Expected resultObserved
resultComments
Tested By
Test Date
2.1.0Navigate to Software Engineering Site
N/AOpen a web browser and go to the site
Browsers default page
Software Engineering Site
2.2.0Navigate to Search page
N/AClick on the "Seach" menu item in the main menu
Software Engineering Home Page
Search Page
2.3.0Click in the Student Name edit field
N/AMove cursor to the search criteria box
Empty Search Page fields
Cursor is in the Student Name box
2.4.0 Type in a name N/ACursor must be in Student Name box
Empty Student Name box
Student Name box has input
2.5.0Click the Search Button
N/AStudent Name Box must have input
Search Page Results Page
2.6.0Choose Correct Student from the List of Results
N/AOn the Results Page
Results Page Student's Information Page
2.7.0
Click on the links to view different information about the student
N/ABe on the Information Page
Information PageDesired information is displayed
2.8.0Repeat Unit 2.1 for all required browsers
F = Unit Summary 0% passing 0 passed Date of last test =
Integration TestingBrings together units that have been tested
individually
Ensures that all units work together properly
Code Shark Solutions Detailed Design 26
Acceptance TestingMakes sure that all functional and non-functional
requirements are met
Makes sure product passes unit testing, integration testing, and full system testing
Will be documented in the next stage of our model
Code Shark Solutions Detailed Design 27
AgendaIntroductionOur ModelProblem DefinitionRequirements InventoryData DesignTest PlanPrototype screens/demoWhat is next?
28
Code Shark Solutions Detailed Design
Prototype Screens/DemoScreen shots of our current work in progress
Allows client and guests to view work more visually
Screens/Demo are conceptual and subject to change
29
Code Shark Solutions Detailed Design
Detailed Design Prototype
34
Code Shark Solutions Detailed Design
http://oraserv.cs.siena.edu/~perm_css/dd/home.php
AgendaIntroductionOur ModelProblem DefinitionRequirements InventoryData DesignTest PlanPrototype screens/demoWhat is next?
35
Code Shark Solutions Detailed Design