Semester Project Requirements

1
Semester Project Requirements
Prof. Steven A. Demurjian Computer Science
Engineering Department The University of
Connecticut 191 Auditorium Road, Box
U-155 Storrs, CT 06269-3155
steve_at_engr.uconn.edu http//www.engr.uconn.edu/st
eve (860) 486 - 4818
Important Note When Emailing Questions, Please
Include All Emails of your Entire Team so that
Derek and I can do a GROUP Response to your email.
2
Project Domain

• Design, Develop, and Test the Information System
  for UConnJobSearch.com
• monster.com clone
• Bleeding Edge of Capabilities and Features
• Three Phases
• I Conceptual Design and the Requirements
  Analysis
• October 23, 2007 Phase I Report Due
• II Database Design requirements (ER -
  Relational)
• October 30, 2007 Phase II Report Due
• III Application Design and Development
• December 4, Phase III Final Report Due

3
Project Requirements

• Team Project - Discussion Between Teams Allowed
  if you are Helping with DB Configuration,
  Programming Question, etc., NOT Joint
  Design/Development!
• Implementation Languages/Platform
• MySQL, Dynamic html, JSP, Javascript/PHP
• See bullet item 3 of Phase I Project Document
• UConnJobSearch.com Specification Generic
• Strongly Encouraged to Enhance/Extend
• Documentation of Proposed Enhancements
• Must Keep Team Busy for Entire Semester!

4
Clients and Software Architecture
Connect and Interact with any DBMS
Personal Oracle
Web Client Customer
Query Program API
MS Access
Java Client Employee
MySQL
Back half is the implementation of the classes
that contains code to open the database
connection, perform a query, collect results,
etc.
Front half contains API (Java calls) that hide DB
interactions from Client
5
Project Requirements

• Phase I, II, and III Report
• Major Design/Development Decisions/Justification
• For Each Phase
• Electronic and Hardcopy
• Phase III Individual Contribution/Self
  Assessment
• Individual Requires a Log
• Self Assessment Overall Teamwork
• See Web for Requirements
• Final Demo December 4, 5, and 6 (time DBA)
• Professional Presentation (PPT) and Demo
• All Team Members MUST Participate

6
Phase I Project Requirements

• Conceptual design is a Combination of
  Requirements Analysis, Software Engineering, and
  Database Design
• UML-Based Design
• Use-case Diagrams Focus on Actors and
• Use-Cases (Functional Requirements)
• EER Design
• Capture Entities and Relationships via EER
• Database Content Requirements
• Screen Mock-ups for Job Posters
• All Team Members MUST Participate in Requirements
  and Must Identify Diagram(s) that they Constructed

7
Other Phase I Advice

• Requirements in Specification may not be Complete
• Indicate what the General Categories of Data are
  without Providing Details
• They Need to be Enhanced/Extended
• Changes Must be Documented and Submitted
• Utilize Tools
• UML Various Free Products
• ER - Visio, Aqua Design Studio, Powerpoint, etc.

8
Phase II Project Requirements

• Given Common EER Design
• Relational Database Design By
• (A) Set of Assumptions in regards to the EER
  diagram
• (B) A Relational Schema From the Entity
  Relationship Model by applying the
  transformation algorithm
• (C) The Set of Functional Dependencies Used to
  Evaluate If the Resulting Schema is BCNF or 3NF
• (D) The Normalization Process (If Necessary) That
  Transforms the Relational Schema to a
  Relational Schema in BCNF or 3NF
• All Team Members MUST Participate in This Process
• Due Date October 30th

9
Phase III Project Requirements

• Design! Design! Design!
• Development! Development! Development!
• Objectives of Phase III
• Organize your Team
• Database Creation and Maintenance
• DB API (Middle Layer) Development
• GUIs for Customers and Employees
• Finalize your Technologies
• DB to Use
• Middle Layer (C, Java, etc.)
• GUIs (Applications vs. html vs. 4GL)

10
First Step - Organize your Team

• Choose Teams
• Organize Teams Effectively - Objectives
• Allow Team Members to Work in Parallel
• Must Come to Agreement w.r.t. Common Software
• Arrive at a Working Plan
• Set Achievable Milestones/Deadlines for Team
• Assigning Responsibilities
• 1 Person - Database Creation and Maintenance
• 1 Person Server (Middle Layer) Development
• 1 Person - GUIs

11
Phase I Requirements/Specification

• Briefly, Lets Review the Entire Process
• Figures 1 to 16
• The Figures are Mock-Ups
• You can Deviate and Customize Depending on your
  Approach
• Need to Maintain Content and NOT Look-and-Feel
• Additionally, Need to Specify Mock-ups for Job
  Posters as Part of Phase I

12
Phase I The Login Process
13
Phase I Error During Logon
14
Phase I Registration
15
Phase I Various Error Messages
16
Phase I Main User Screen after Logon
17
Phase I Searching for Appropriate Jobs
18
Phase I Search Results
19
Phase I
20
Phase I Updating Education Data
21
Phase I Adding a New Degree
22
Phase I Updating Experiences
23
Phase I Entering New Experiences
24
Phase I Defining your Skills
25
Phase I Updating Profile Data
26
Phase I Details on an Available Position
27
GUIs (Applications vs. html vs. 4GL)

• Recall Five Programs
• Login Programs
• Query Program
• Registration Program
• Traveler/Automobile Profile Update Program
• Reservation Program
• Objective - Structure Four Programs (APIs) into
  Two or More GUIs
• Customer GUI - Reserve Cars, Change Profile, etc.
• Clerk GUI - Pickup/Drop-off/Upgrade
• Management GUI - Reports
• You Must Define the Scope and Capability of Each
  GUI that is Then Realized

28
Sample Java GUIs from CT Insurance Dept.
29
Sample Java GUIs from CT Insurance Dept.
30
Sample MS Access GUIs
31
Web Pages from CSE293 Project
32
MS Access Data Entry/Display Screens
33
Sample Reports from CT Insurance Dept.
Main Menu
34
Sample Reports from CT Insurance Dept.
35
Sample Reports from CT Insurance Dept.
36
GUI from CSE255 Spring 2003 Project
37
GUI from CSE255 Spring 2003 Project
38
GUI from CSE255 Spring 2003 Project
39
GUI from CSE255 Spring 2003 Project
40
GUI from CSE255 Spring 2003 Project
41
GUI from CSE255 Spring 2003 Project
42
GUI from CSE255 Spring 2003 Project
43
Final Thoughts

• Phase III Report (see 6 Bullet Items)
• Purpose, Tasks, System Requirements, Revisions to
  Phases I and II
• Problems Found and Solutions
• System Architecture and Choices
• Conclusion, Assessment, Evaluation
• Team Member Contributions
• SQL DDL, Source Code, DB Instances, Screen Shots
• Demos on in December for Each Team (1/2 hour)