Project Scenario

 New Codington City Council (NCCC) is the client for this project.

 The NCCC is holding a festival to celebrate the union of North Town and South Town
into New Codington, and is opening all of the city’s great attractions to the public.

 The NCCC has requested that Accenture produce a web-based search tool able to find
and register visitors for tourist attractions and festival events.

 The tool should be easy to use and needs to produce a list of matches to a user’s custom
search.
Release- 1 Business Requirements
 Only a Visitor can view the Event Catalog
 A Visitor must have a Visitor Account
 A User becomes a Visitor by creating a Visitor Account in the system.
 A User can only register for a Visitor Account in the system.
 A Visitor must be logged into the system to register for an event
 A Visitor must be logged into the system to unregister from an event
 A Visitor must be logged into the system to change their personal information
 There is no limit to the number of events that a visitor can register for
 A Visitor Name in a Visitor Account cannot be changed once created by the Visitor
 A Visitor can only register for one ticket for an event
 A Visitor can only unregister for events the Visitor is current registered for
 A Visitor can cancel registrations recorded in the system at any time
 No two Visitors can have the same username
Release- 1 Use Case Diagram
Release- 1 Implementation
 EventDAO
 handles and manages event related data
 displaying Event Catalog
 updating Events after visitor registers for event
 checking visitor has already registered for Event or not
 update event database after unregistering event by visitor
 VisitorDAO
 handles and manages visitor related data
 insert visitor details into VISITOR table in database
 searching for visitor details using USERNAME and PASSWORD
 register visitor to specific event and checking about status
 display all the events registered by particular visitor
 update visitor information
 unregister visitor from events
 EventServiceImpl
 service class that implements the EventFacade
 makes event-related data requests to the EventDAO class
 displaying all events from DAO
 identifying all events registered by visitor
 deleting events for visitor
Release- 1 Implementation (Contd.)
 VisitorServiceImpl
 service class that implements the VisitorFacade
 makes visitor-related data requests to the VisitorDAO class
 inserting new visitor
 searching visitor details
 registering user to event
 displaying all registered events
 Unit Testing
 Assembly Testing
 Manual Testing
 User Interface
Release- 1 Flow
 Register Visitor
 Login Visitor
 Update Visitor
 Register Visitor for Event
 Unregister from Event
Release- 2 Business Requirements
 FERS should have a search capability to filter the viewed events.

 FERS should have a sort capability to allow a list of events to be sorted by event name in
the table in ascending or descending order.

 FERS should provide a login screen for the administration and a screen to allow the
ability to add, update, and delete and event from the FERS database.

 FERS must allow users to be able to register for a particular session for an event, not just
the general event itself.
Release- 2 Implementation
 Fixing Defects in UI
 EventDAO
 handles and manages event related data
 displaying Event Catalog
 updating Events after visitor registers for event
 checking visitor has already registered for Event or not
 update event database after unregistering event by visitor
 VisitorDAO
 handles and manages visitor related data
 insert visitor details into VISITOR table in database
 searching for visitor details using USERNAME and PASSWORD
 register visitor to specific event and checking about status
 display all the events registered by particular visitor
 update visitor information
 unregister visitor from events
 EventServiceImpl
 service class that implements the EventFacade
 makes event-related data requests to the EventDAO class
 displaying all events from DAO
 identifying all events registered by visitor
 deleting events for visitor
Release- 2 Implementation(contd.)
 VisitorServiceImpl
 service class that implements the VisitorFacade
 makes visitor-related data requests to the VisitorDAO class
 inserting new visitor
 searching visitor details
 registering user to event
 displaying all registered events
 EventController
 handles all event related activities of new visitor.
 get available events
 delete event
 displaying events
 updating events
 VisitorController
 receiving and handling all visitor related transactions from the User Interface including visitor
account access,visitor account maintenance, and visitor event registration requests..
 Inserting new visitor
 Search Visitor
 Register Visitor to an event
 updating Visitor
Release- 2 Implementation(contd.)
 change password
 unregister event
 search events by name
 search events by name catalog
 show all events in ascending and descending order
 show events catalog by ascending and descending order
 Unit Testing
 Assembly Testing
 Manual Testing
 User Interface
Release- 2 Use Case Diagram
Release- 2 Flow
 View Events
 Search Events
 Sort Events
Thank you!