R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

56
R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/ 10

Transcript of R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Page 1: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

R.O.S.E.S.

Preliminary Design

Presented By:Code Shark Solutions

12/8/10

Page 2: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

WelcomeOur ClientDr. Timoth C. LedermanProfessor of Computer ScienceSiena College

2Code Shark Solutions

Page 3: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

AgendaIntroductionProblem DefinitionRequirements InventoryUsage Case Narratives UML Diagrams & Website MapData Flow DiagramsData DictionaryTestingPrototype screensWhat is next?

3Code Shark Solutions

Page 4: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

IntroductionOur TeamKurt GreinerTeam Leader

Daniel RotondoWebmaster

Ryan GodfreyLead Programmer

Rebecca WilsonInformation Specialist

Akeem ShirleyDatabase

Administrator

Brittany LintelmanDocumentarian

4Code Shark Solutions

Page 5: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

AgendaIntroductionProblem DefinitionRequirements InventoryUsage Case Narratives UML Diagrams & Website MapData Flow DiagramsData DictionaryTestingPrototype screensWhat is next?

5Code Shark Solutions

Page 6: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

ROSES Problem DefinitionSite lacks functionality

Inconsistent menuNo Search feature

Is not aesthetically pleasing

6Code Shark Solutions

Page 7: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

AgendaIntroductionProblem DefinitionRequirements InventoryUsage Case Narratives UML Diagrams & Website MapData Flow DiagramsData DictionaryTestingPrototype screensWhat is next?

7Code Shark Solutions

Page 8: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Functional RequirementsGeneral User:

View WebsiteSearch

8Code Shark Solutions

Page 9: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Non-Functional RequirementsSystem must be:

Aesthetically pleasingEasily navigableEasily maintainableEasily modifiableStable

9Code Shark Solutions

Page 10: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

AgendaIntroductionProblem DefinitionRequirements InventoryUsage Case Narratives UML Diagrams & Website MapData Flow DiagramsData DictionaryTestingPrototype screensWhat is next?

10Code Shark Solutions

Page 11: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Usage Case Narratives

11

•Tells a story for each of the users describing their interaction with the system

•Also explains the abilities each user has for interacting with the system

Code Shark Solutions

Page 12: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

System UsersCourse InstructorGeneral User

StudentsRecommendersFuture EmployerFamily/FriendsAlumni

12Code Shark Solutions

Page 13: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Course InstructorSite Administrator

Can add to and edit all parts of the websiteUse the website as a reference

13Code Shark Solutions

Page 14: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

StudentsMakes use of the website’s calendar and links

for both sections of the course.

Uses the past teams’ websites and documents as a reference point.

14Code Shark Solutions

Page 15: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

RecommenderCan search for specific Software Engineering

students and gain access to their resume, picture, class, and information related to their Software Engineering course.

15Code Shark Solutions

Page 16: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Future EmployerNavigate website with ease

Use the search function to find prospective employees

16Code Shark Solutions

Page 17: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Family/FriendsCan search for Software Engineering

Students to view the talents and accomplishments of their family and friends.

17Code Shark Solutions

Page 18: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

AlumniCan search for themselves or other students

to view past achievements for reminiscent purposes or in the chance of being interviewed by an alumnus this can also serve as a reference.

18Code Shark Solutions

Page 19: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

AgendaIntroductionProblem DefinitionRequirements InventoryUsage Case Narratives UML Diagrams & Website MapData Flow DiagramsData DictionaryTestingPrototype screensWhat is next?

19Code Shark Solutions

Page 20: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

UML Use Case Diagram

Used to show how users interact with system.Users or ‘Actors’ interact through ‘Uses’Lines are drawn to demonstrate a

relationship

20Code Shark Solutions

Page 21: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

UML Use Case Legend

21Code Shark Solutions

Page 22: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

UML Use Case Diagram

22Code Shark Solutions

Page 23: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

UML Deployment Diagram

23

Show devices and execution environments for a system

Shows protocols for interaction with the system

Code Shark Solutions

Page 24: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

UML Deployment Diagram

24Code Shark Solutions

Page 25: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Website Map Legend

25Code Shark Solutions

Page 26: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Website Map

26Code Shark Solutions

Page 27: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

AgendaIntroductionProblem DefinitionRequirements InventoryUsage Case Narratives UML Diagrams & Website MapData Flow DiagramsData DictionaryTestingPrototype screensWhat is next?

27Code Shark Solutions

Page 28: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Data Flow DiagramsUsed to show the movement of data throughout

systemActs as visual aid to demonstrate how system

works

Context Diagram - The highest and most general representation of data flow

Level 0 – Shows the major processes of the systemLevel 1 – Shows in-depth the look at one useLevel 2 – Decomposes each process

28Code Shark Solutions

Page 29: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Context Diagram

29

Highest, most general level of data flow in our system.

Shows interactions between users, databases, and website

Code Shark Solutions

Page 30: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Level 0 Diagram

30

Shows major processes of the system.

Code Shark Solutions

Page 31: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Level 1 Diagram

31

Shows data flow of one of the main uses; viewing the website.

Code Shark Solutions

Page 32: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Level 2 Diagram

32

Decomposes the main process of the system; searching.

Code Shark Solutions

Page 33: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

AgendaIntroductionProblem DefinitionRequirements InventoryUsage Case Narratives UML Diagrams & Website MapData Flow DiagramsData DictionaryTestingPrototype screensWhat is next?

33Code Shark Solutions

Page 34: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Data DictionaryLists all data entities and variable with in a

system

Used to help understand items in the database

34Code Shark Solutions

Page 35: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Data Dictionary Excerpt

35Code Shark Solutions

Page 36: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

AgendaIntroductionProblem DefinitionRequirements InventoryUsage Case Narratives UML Diagrams & Website MapData Flow DiagramsData DictionaryTestingPrototype screensWhat is next?

36Code Shark Solutions

Page 37: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Test PlanDocuments the strategy used

Ensures that the Functional Requirements are met

Includes all of the following: unit testing, integration testing, system testing, and acceptance testing.

37Code Shark Solutions

Page 38: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

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

38Code Shark Solutions

Page 39: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Unit Test Excerpt

39Code Shark Solutions

Page 40: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

AgendaIntroductionProblem DefinitionRequirements InventoryUsage Case Narratives UML Diagrams & Website MapData Flow DiagramsData DictionaryTestingPrototype screensWhat is next?

40Code Shark Solutions

Page 41: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Prototype ScreensScreen shots of our current work in progress

Allows client and guests to work more visually

Screens are conceptual and subject to change

41Code Shark Solutions

Page 42: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Current Menus

42Code Shark Solutions

Page 43: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

New Main Menu

43Code Shark Solutions

Page 44: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

New Sub-menu

44Code Shark Solutions

Page 45: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Old Calendar

45Code Shark Solutions

Page 46: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

New Calendar

46Code Shark Solutions

Page 47: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

New Functionality: Search

47Code Shark Solutions

Page 48: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Search Results

48Code Shark Solutions

Page 49: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Student Result Page

49Code Shark Solutions

Page 50: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Year Results Page

50Code Shark Solutions

Page 51: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Mobile VersionSmart phones and other mobile devices are

becoming increasingly popular.Student will always need to see what’s due in

Software Engineering at any given moment. Many websites will not display properly on

mobile devices

Code Shark Solutions 51

Page 52: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Mobile Screenshots

Code Shark Solutions 52

Page 53: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Mobile Screenshots cont.

Code Shark Solutions 53

Page 54: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

AgendaIntroductionProblem DefinitionRequirements InventoryUsage Case Narratives UML Diagrams & Website MapData Flow DiagramsData DictionaryTestingPrototype screensWhat is next?

54Code Shark Solutions

Page 55: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

What’s Next?2010 – DONE!

2011:

55Code Shark Solutions

Page 56: R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.

Thank You!Questions?

Comments?

Have a nice Holiday Season!

56Code Shark Solutions