fssa-batch3 / fssa-batch3/sec_a_gowtham.sathyamoorthy__corejava_project_2
User module | Register Feature
- Dominant language
- Java
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
### Attributes
- [ ] name
- [ ] email
- [ ] password
- [ ] phone no
### Validation
- [ ] validateUser()
- [ ] validateEmail()
- [ ] validatePassword()
- [ ] validateName()
### Validation Tests:
- [ ] testvalidateUser()
- [ ] testvalidateEmail()
- [ ] testvalidatePassword()
- [ ] testvalidateName()
###DAO:
- [ ] createUser()
###Service:
- [ ] registerUser()
### Service Tests:
TestRegisterFeature
- [ ] testRegisterSuccess()
###Estimation:
- [ ] 10 hrs
#Turbo Trip
[Milestones](https://github.com/fssa-batch3/sec_a_gowtham.sathyamoorthy__corejava_project_2/milestones)
###ERDIAGRAM
[](https://freeimage.host/i/HpQ4rMu)
### Flow:
```mermaid
flowchart TD
A[Start]
B[Display Registration Form]
C[User Fills out Form]
D[Validate Input]
E{Validation Successful?}
F[Save User Data]
G[Registration Successful]
H[Display Error Messages]
I[End]
A --> B
B --> C
C --> D
D --> E
E -- Yes --> F
F --> G
E -- No --> H
H --> B
H --> I
G --> I
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the ER diagram and the registration flow, then trace the planned validateUser(), validateEmail(), validatePassword(), validateName(), createUser(), and registerUser() entry points in the project. Done means registration stores name, email, password, and phone data, validates the listed fields, and includes the specified validation and TestRegisterFeature tests for successful registration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authentication, backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100