Scribd
Upload
5 views1 page

Activities

The document outlines two activities for creating and managing a Profile class with properties such as profileId, name, password, dob, and phone. It specifies the need for a service layer to handle operations like saving and deleting profiles, ensuring loose coupling and the use of design patterns for multiple implementations. Additionally, it requires the implementation of a login method that validates profileId and password, along with corresponding test cases for functionality and error handling.

Uploaded by

Suresh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
5 views1 page

Activities

The document outlines two activities for creating and managing a Profile class with properties such as profileId, name, password, dob, and phone. It specifies the need for a service layer to handle operations like saving and deleting profiles, ensuring loose coupling and the use of design patterns for multiple implementations. Additionally, it requires the implementation of a login method that validates profileId and password, along with corresponding test cases for functionality and error handling.

Uploaded by

Suresh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

Activity 1

Create a Profile that will have the following properties: profileId, name, password, dob, phone.

Use the layered architecture and in the service layer you must be able to perform following operations

1. save
2. delete

Maintain the Profile in a Collection framework in the service layer.

Write the test cases for save, delete and also for not saving the duplicate profile.

Design the classes & interfaces accordingly, write the code such that it must be loosely coupled apply
appropriate design patterns so that the client must able to get the multiple implementation of the
service layer without changing the code

Activity 2

To the existing Profile activity provide a login method in the service layer which must accept profileId &
password on a valid profileId and password it must return the Profile else throw a checked exception

Ensure you have a test case to pass profileId and password that expects Profile on those inputs or assert
the error messages you are expecting when profileId or password is wrong.

You might also like