Customer Management System

Customer Management System ------------------------------------------- Our business is mainly focused on customers who are having multiple skills. We need to track users with their gender, skills and education. While registering any user, they have to specify their gender, latest education and all known skills. User should be able to edit their info. Administrators can able to search and delete any user info. In our project, There are Two types of users. 1. Customer (or) end user 2. Administrator Customer can register/edit/view his info. Administrator can search/view/edit/delete any customer info. Mater Tables: ------------------ CREATE TABLE GENDERS(ID INT, NAME VARCHAR(10), CONSTRAINT G1 PRIMARY KEY(ID)); INSERT INTO GENDERS VALUES(1, 'MALE'); INSERT INTO GENDERS VALUES(2, 'FEMALE'); CREATE TABLE SKILLS (ID INT, NAME VARCHAR(90),CONSTRAINT S1 PRIMARY KEY(ID)); INSERT INTO SKILLS VALUES(1, 'C'); INSERT INTO SKILLS VALUES(2, 'C++'); INSERT INTO SKILLS VALUES(3, 'JAVA'); INSERT INTO SKILLS VALUES(4, 'ORACLE'); CREATE TABLE EDUCATIONS(ID INT, NAME VARCHAR(90), CONSTRAINT E1 PRIMARY KEY(ID)); INSERT INTO EDUCATIONS VALUES(1, 'MCA'); INSERT INTO EDUCATIONS VALUES(2, 'BE'); INSERT INTO EDUCATIONS VALUES(3, 'ME'); INSERT INTO EDUCATIONS VALUES(4, 'MBA'); Transaction Tables ------------------------- CREATE TABLE USERS (ID INT, FIRST_NAME VARCHAR(90), LAST_NAME VARCHAR(90), AGE INT, EMAIL VARCHAR(90),GENDER_ID INT,EDUCATION_ID INT,USERNAME VARCHAR(90), PASSWORD VARCHAR(90),CONSTRAINT U1 PRIMARY KEY(ID),CONSTRAINT U2 FOREIGN KEY(GENDER_ID) REFERENCES GENDERS(ID),CONSTRAINT U3 FOREIGN KEY(EDUCATION_ID) REFERENCES EDUCATIONS(ID)); CREATE TABLE USERS_SKILLS(ID INT, USER_ID INT, SKILL_ID INT, CONSTRAINT US1 PRIMARY KEY(ID), CONSTRAINT US2 FOREIGN KEY(USER_ID) REFERENCES USERS(ID), CONSTRAINT US3 FOREIGN KEY(SKILL_ID) REFERENCES SKILLS(ID)); CREATE SEQUENCE USERS_SKILLS_SEQ INCREMENT BY 1 START WITH 1 List of use cases ---------------------- 1. User Registration 2. User Login 3. Viewing User Registration info. 4. Editing User registration info. 5. Administrator Search In every use case, 1. View, Controller, Service, DAO layers separately should develop. 2. Wherever test cases required there and all test cases should be developed? 3. It should be with current industry standards 4. Development should be in with Spring WEB MVC (4.x) and Hibernate (4.x). 5. Class diagram required for every usecase.