CSE 4701 Project-1 Semester Project Requirements Prof. Steven A. Demurjian Computer Science & Engineering Department The University of Connecticut 191 Auditorium Road, Box U-155 Storrs, CT (860) Important Note: When ing Questions, Please Include All s of your Entire Team so that David and I can do a GROUP Response to your .

CSE 4701 Project-2 Phase II Due Dates n Optional Intermediate Due Date - 11:59pm 4/13 l Your Team Should get ½ or more Screens Completed l 16 in n Project Phase II: Application D & D l Thursday, April 30, 11:59p, with as needed Demos n Individual Self Assessments to l Due Friday May 1, 11:59p

CSE 4701 Project-3 Other Team1 Screens Posted

CSE 4701 Project-4 Other Team1 Screens Posted

CSE 4701 Project-5 validator.php

CSE 4701 Project-6 register.php

CSE 4701 Project-7 Development Strategy for Phase II n Two Team Members Focusing on Web Screens n One Person Focusing on Database Query Support l Design/Implement Screen l Provide Relevant Query/Queries for Screen n Repeat Process for all 16 screens – Core Functionality n Reports – Additional Functionality l One Report Screen with 10 Possible Reports l Start on after you complete Core Functionality l Utilize the Same Process l Separate Screen for Each report to: à Input Values for Screen/Display Results l See Samples on Next 3 slides

CSE 4701 Project-8 Sample Reporting Screens

CSE 4701 Project-9 Sample Reporting Screens

CSE 4701 Project-10 Sample Reporting Screens

CSE 4701 Project-11 Project Domain n Design, Develop, and Test the Information System for UConnJobSearch.com l monster.com clone l Bleeding Edge of Capabilities and Features n Three Phases l Thursday, March 4 à Finalize Groups for the Project l Project Phase I: Database Design à Friday, March 13, 11:59pm (EER to Relational Design) l Project Phase II: Application D & D à Thursday, April 30, 11:59p, with as needed Demos

CSE 4701 Project-12 Project Requirements n Team Project - Discussion Between Teams Allowed if you are Helping with DB Configuration, Programming Question, etc., NOT Joint Design/Development! n Implementation Languages/Platform l MySQL Workbench, php, html/css l Eclipse PHP or Aptana Studio 3 – To be Decided l See bullet item 3 of Phase I Project Document n UConnJobSearch.com Overview/Other Sample Screens l Strongly Encouraged to Enhance/Extend l Documentation of Proposed Enhancements n Should Work on Chrome and Explorer

CSE 4701 Project-13 Web Client Job Seeker REST php API Web Client Job Poster MySQL Front half contains API (Java calls) that hide DB interactions from Client Back half is the implementation of the classes that contains code to open the database connection, perform a query, collect results, etc. Connect and Interact with MySQL Clients and Software Architecture

CSE 4701 Project-14 Project Requirements n Phase I Report l Will Provide Sample l Submit to HuskyCT n Phase II: l Project File loadable into IDE l.sql File with Tuples for Testing l User Manual l Individual Contribution/Self Assessment à Individual: Requires a Log à Self Assessment: Overall Teamwork l See Phase II Assignment Requirements n Final Demo – TBD if a Team’s code Won’t Run

CSE 4701 Project-15 Phase I Project Requirements n Given Common EER Design n 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 n All Team Members MUST Participate in This Process n Due Date: Friday, March 13, 11:59pm

CSE 4701 Project-16 EER for UConnJobSearch - Part 1

CSE 4701 Project-17 EER for UConnJobSearch - Part 2

CSE 4701 Project-18 Explaining Phase I Project Requirements Examine EER and Make Sure Everything Makes Sense (A) Set of Assumptions in regards to the EER diagram à Resume needs a new ResumeID as a primary key, since using RLastName as a primary key doesn’t work à Posters working for Companies is really a 1-to-n relationship, not 1-to-1, since Companies should be able to have multiple posters. (B) A Relational Schema From the Entity Relationship Model by applying the transformation algorithm à Present Solution by Algorithm Step 1, 2, 3, etc. à USER (UName, UState, UPasswd, UFName, ULName, UStreet1, UStreet2, UCity, UZip, U , UPhone, UFax, UCell, UHomepage)

CSE 4701 Project-19 Explaining Phase I Project Requirements (C) The Set of Functional Dependencies Used to Evaluate If the Resulting Schema is BCNF or 3NF à Primary Key = UName  UName  UState, UPasswd, UFName, ULName, UStreet1, UStreet2, UCity, UZip, U , UPhone, UFax, UCell, UHomepage (D) The Normalization Process (If Necessary) That Transforms the Relational Schema to a Relational Schema in BCNF or 3NF à Review one Table at a time à There are Multi-Valued Attributes ….

CSE 4701 Project-20 Phase II Project Requirements n Design! Design! Design! n Development! Development! Development! n Objectives of Phase II l Organize your Team à Database Creation and Maintenance à DB API (Middle Layer) Development – REST API à GUIs for Customers and Employees – html/css

CSE 4701 Project-21 First Step - Organize your Team n Choose Teams n Organize Teams Effectively - Objectives l Allow Team Members to Work in Parallel l Must Come to Agreement w.r.t. Common Software l Arrive at a Working Plan l Set Achievable Milestones/Deadlines for Team n Assigning Responsibilities: l 1 Person - Database Creation and Maintenance (early) Shifts to GUI/Report Screens/Capabilities l 1 Person – REST API - Server Development l 1 Person - GUIs

CSE 4701 Project-22 Project Overview of Capabilities n Briefly, Let’s Review the Entire Process n Figures 1 to 16 n The Figures are Mock-Ups l You can Deviate and Customize Depending on your Approach l Need to Maintain Content and NOT Look-and-Feel n Note – see also link below for html based Mockups l mpleProjectScreens.docx

CSE 4701 Project-23 UConn’s Job Search Database Phase I: The Login Process

CSE 4701 Project-24 UConn’s Job Search Database Phase I: Error During Logon

CSE 4701 Project-25 Phase I: Registration

CSE 4701 Project-26 UConn’s Job Search Database Phase I: Various Error Messages

CSE 4701 Project-27 Welcome to UConn’s Job Search Database Phase I: Main User Screen after Logon

CSE 4701 Project-28 Search Uconn’s Job Search Database Phase I: Searching for Appropriate Jobs

CSE 4701 Project-29 Applications: Welcome to Uconn’s Job Search Database Phase I: Search Results

CSE 4701 Project-30 Resume: Welcome to Uconn’s Job Search Database Attach Resume Browse Phase I:

CSE 4701 Project-31 Resume: Welcome to Uconn’s Job Search Database Phase I: Updating Education Data

CSE 4701 Project-32 Resume: Welcome to Uconn’s Job Search Database Phase I: Adding a New Degree

CSE 4701 Project-33 Resume: Welcome to Uconn’s Job Search Database Phase I: Updating Experiences

CSE 4701 Project-34 Resume: Welcome to Uconn’s Job Search Database Phase I: Entering New Experiences

CSE 4701 Project-35 Resume: Welcome to Uconn’s Job Search Database Phase I: Defining your Skills

CSE 4701 Project-36 Phase I: Updating Profile Data

CSE 4701 Project-37 Job Detail: Uconn’s Job Search Database Phase I: Details on an Available Position

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

CSE 4701 Project-39 Other Sample UConnJobSearch Screens n In this first sample, the front end is HTML/Javascript GUI where each page is dynamically generated by the PHP in the applications layer in Mozilla. n In this second sample, the client layer is written using HTML, CSS and Javascript which is in explorer.

CSE 4701 Project-40 First Sample

CSE 4701 Project-41 First Sample

CSE 4701 Project-42 First Sample

CSE 4701 Project-43 First Sample

CSE 4701 Project-44 First Sample

CSE 4701 Project-45 First Sample

CSE 4701 Project-46 First Sample

CSE 4701 Project-47 Second Sample

CSE 4701 Project-48 Second Sample

CSE 4701 Project-49 Second Sample

CSE 4701 Project-50 Second Sample

CSE 4701 Project-51 Second Sample

CSE 4701 Project-52 Second Sample

CSE 4701 Project-53 Second Sample

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

CSE 4701 Project-55 Main Menu Sample Reports from CT Insurance Dept.

CSE 4701 Project-56 Sample Reports from CT Insurance Dept.

CSE 4701 Project-57 Sample Reports from CT Insurance Dept.

CSE 4701 Project-58 GUI from CSE255 Spring 2003 Project

CSE 4701 Project-59 GUI from CSE255 Spring 2003 Project

CSE 4701 Project-60 GUI from CSE255 Spring 2003 Project

CSE 4701 Project-61 GUI from CSE255 Spring 2003 Project

CSE 4701 Project-62 GUI from CSE255 Spring 2003 Project

CSE 4701 Project-63 GUI from CSE255 Spring 2003 Project

CSE 4701 Project-64 GUI from CSE255 Spring 2003 Project