Post on 17-Dec-2015
Preliminary Design: Smart SchedulingClient: Dr. Robert Yoder
2
Welcome
Dr. Robert Yoder (client)Head of the Computer Science Department at Siena College
Dr. Timoth LedermanOur Professor
3
Agenda
• Software Engineering Team
• Restatement of Problem
• Project Progression
• User Case Narratives
• UML Diagram
• Framework Map
• Data Flow Diagrams
• Requirements Inventory
• Testing
• Data Dictionary
• Prototype Screens
• What’s Next
• Questions
4
Empire Unlimited
•Thomas Mottola – Team Leader
•Jason Czajkowski – Lead Systems Administrator
•Meghan Servello – Organizational Information Manager
•Brian Maxwell – Lead Software Developer
•Jonathan Smith – Information Analysis Manager
•Collin Lefeber - Webmaster
5
Agenda
• Software Engineering Team
• Restatement of Problem
• Project Progression
• User Case Narratives
• UML Diagram
• Framework Map
• Data Flow Diagrams
• Requirements Inventory
• Testing
• Data Dictionary
• Prototype Screens
• What’s Next
• Questions
6
The Problem
• Scheduling classrooms, labs, courses, and professors.
• Currently scheduling is done in a cumbersome fashion.
• Lack of a self-checking system.
• There are constraints set by Siena College.
• Schedules can be difficult to read.
7
Examples
8
Agenda
• Software Engineering Team
• Restatement of Problem
• Project Progression
• User Case Narratives
• UML Diagram
• Framework Map
• Data Flow Diagrams
• Requirements Inventory
• Testing
• Data Dictionary
• Prototype Screens
• What’s Next
• Questions
9
Project Progression
10
Agenda
• Software Engineering Team
• Restatement of Problem
• Project Progression
• User Case Narratives
• UML Diagram
• Framework Map
• Data Flow Diagrams
• Requirements Inventory
• Testing
• Data Dictionary
• Prototype Screens
• What’s Next
• Questions
11
User Case Narratives
What’s Provided:
• Description of how each user interacts with the system.
• Description of a specific users goal when interacting with the system.
12
User Case Narratives – Course Coordinator
• Log in via username / password
• Assign classrooms, courses, and faculty
• Class Modification
• Access to previous schedules
• View reports
13
User Case Narratives - Faculty
• Log in via username / password
• View schedules
• View reports
• Apply Filters
• Add office hours unique to the faculty member
14
User Case Narratives – General User
• View schedules
• View reports
• Apply Filters
15
Agenda
• Software Engineering Team
• Restatement of Problem
• Project Progression
• User Case Narratives
• UML Diagram
• Framework Map
• Data Flow Diagrams
• Requirements Inventory
• Testing
• Data Dictionary
• Prototype Screens
• What’s Next
• Questions
16
UML Diagram - Legend
17
UML Diagram – Use Case Diagram
Agenda
18
UML Deployment Diagram
19
Agenda
• Software Engineering Team
• Restatement of Problem
• Project Progression
• User Case Narratives
• UML Diagram
• Framework Map
• Data Flow Diagrams
• Requirements Inventory
• Testing
• Data Dictionary
• Prototype Screens
• What’s Next
• Questions
20
Framework Map
21
Framework Map
22
Framework Map
23
Agenda
• Software Engineering Team
• Restatement of Problem
• Project Progression
• User Case Narratives
• UML Diagram
• Framework Map
• Data Flow Diagrams
• Requirements Inventory
• Testing
• Data Dictionary
• Prototype Screens
• What’s Next
• Questions
24
Data Flow Diagram - Overview
• Provide representation of data flow
• Provide representation of data manipulation
• “Top Down” view of the system
25
Data Flow Diagram - Legend
Entities/Sources/Sinks
Processes
Stores
The Flows
26
Data Flow Diagram – Context
27
Data Flow Diagram – Level 0
28
Data Flow Diagram – Level 1
29
Data Flow Diagram – Level 2
30
Agenda• Software Engineering Team
• Restatement of Problem
• Project Progression
• User Case Narratives
• UML Diagram
• Framework Map
• Data Flow Diagrams
• Requirements Inventory
• Testing
• Data Dictionary
• Prototype Screens
• What’s Next
• Questions
31
Functional Requirements Inventory
• Web based
• Able to run on all popular web browsers
• Login system to differentiate between users
• Reports will be easily viewable
32
F. R. I. – Course Coordinator
• Find common time slots in schedule
• Modify the schedule
• Add new classes
• Create faculty accounts
• View the schedule (filtering available)
33
F. R. I. – Faculty
• Add office hours specific to the faculty member
• View and print room reports
• View the schedule (filtering available)
34
F. R. I. – General User
• View and print room reports
• View the current schedule (filtering available)
35
Non-Functional Requirements
The system will be…
• easily maintained
• stable
• viewable on multiple browsers
• efficient
• user friendly and easy to use
36
Agenda
• Software Engineering Team
• Restatement of Problem
• Project Progression
• User Case Narratives
• UML Diagram
• Framework Map
• Data Flow Diagrams
• Requirements Inventory
• Testing
• Data Dictionary
• Prototype Screens
• What’s Next
• Questions
37
Testing
Units:
• Add Faculty member
• Authenticate
• Update Class
38
Testing
• Acceptance Criteria : Determined by F.R.I.
• Testing Environment
• Testing Process:
• Unit
• Module
• As a whole
39
Testing
40
Testing
41
Testing
42
Testing
43
Agenda
• Software Engineering Team
• Restatement of Problem
• Project Progression
• User Case Narratives
• UML Diagram
• Framework Map
• Data Flow Diagrams
• Requirements Inventory
• Testing
• Data Dictionary
• Prototype Screens
• What’s Next
• Questions
44
Data Dictionary
KEY:
• Data Name
• Applicable To
• Data Type
• Data Size
• Description
• Acceptable Input
• Correct Example of Input
• Notes
45
Data Dictionary
46
Agenda
• Software Engineering Team
• Restatement of Problem
• Project Progression
• User Case Narratives
• UML Diagram
• Framework Map
• Data Flow Diagrams
• Requirements Inventory
• Testing
• Data Dictionary
• Prototype Screens
• What’s Next
• Questions
47
Prototype – Login View
48
Prototype – Login View with Errors
49
Prototype – Schedule Day View
50
Prototype – Schedule Day View with filter
51
Prototype – Schedule Day View with all filters
52
Prototype – Schedule Week View
53
Prototype – Schedule List View
54
Prototype – Schedule List View with quick editing
55
Prototype – Schedule List View sorting example
56
Prototype – Resource CRUD View
57
Prototype – View Resource CRUD View
58
Agenda
• Software Engineering Team
• Restatement of Problem
• Project Progression
• User Case Narratives
• UML Diagram
• Framework Map
• Data Flow Diagrams
• Requirements Inventory
• Testing
• Data Dictionary
• Prototype Screens
• What’s Next
• Questions
59
What’s Next
60
The End
Thank you.
Questions or Comments?