Review

Project: My Sweet Home Document: Development Guide Approved by: Faculty



1. INTRODUCTION .............................................................................................................. 4

2. EXISTING SCENARIO ...................................................................................................... 4

3. CUSTOMER REQUIREMENT SPECIFICATION .................................................................. 4

4. FUNCTIONAL REQUIREMENT SPECIFICATION: ............................................................. 4

4.1. GUEST CAN VIEW COMPANY‟S INFORMATION ................................................................................ 4

4.1.1. Description ................................................................................................................ 4

4.1.2. Functional Requirement ............................................................................................. 4

4.2. GUEST CAN LOGIN AS EMPLOYEE OR ADMIN ................................................................................ 4

4.2.1. Description ................................................................................................................ 4

4.2.2. Functional Requirement ............................................................................................. 4

4.3. EMPLOYEE CAN EDIT THEIR PROFILE INFORMATION ....................................................................... 5

4.3.1. Description ................................................................................................................ 5

4.3.2. Functional Requirement ............................................................................................. 5

4.4. SEARCHING ........................................................................................................................ 5

4.4.1. Description ................................................................................................................ 5

4.4.2. Functional Requirements ............................................................................................ 5

4.5. EMPLOYEE CAN VIEW DETAILS OF EVENT..................................................................................... 5

4.5.1. Description ................................................................................................................ 5

4.5.2. Functional Requirements ............................................................................................ 5

4.6. EMPLOYEE CAN SEND REQUEST TO REGISTER EVENT ...................................................................... 5

4.6.1. Description ................................................................................................................ 5

4.6.2. Functional Requirement ............................................................................................. 5

4.7. EMPLOYEE CAN CANCEL THE EVENT REGISTER .............................................................................. 5

4.7.1. Description ................................................................................................................ 5

4.7.2. Functional Requirements ............................................................................................ 6

4.8. EMPLOYEE CAN MAKE COMMENT ............................................................................................... 6

4.8.1. Description ................................................................................................................ 6

4.8.2. Functional Requirements ............................................................................................ 6

4.9. EMPLOYEE CAN VIEW ANOTHER EMPLOYEE‟S INFORMATION .............................................................. 6

4.9.1. Description ................................................................................................................ 6

4.9.2. Functional Requirements ............................................................................................ 6

4.10. EMPLOYEE CAN PROPOSES THE NEW EVENT .............................................................................. 6

4.10.1. Description ................................................................................................................ 6

4.10.2. Functional Requirements ............................................................................................ 6

4.11. EMPLOYEE CAN VIEW FAQS ................................................................................................. 6

4.11.1. Description ................................................................................................................ 6

4.11.2. Functional Requirements ............................................................................................ 6

4.12. SUPPORTING ................................................................................................................... 6

4.12.1. Description ................................................................................................................ 6

4.12.2. Functional Requirements ............................................................................................ 6

4.13. SYSTEM REMINDS BIRTHDAY ................................................................................................ 7

4.13.1. Description ................................................................................................................ 7

4.13.2. Functional Requirement ............................................................................................. 7

4.14. SYSTEM PUBLISHES UPCOMING EVENTS ................................................................................... 7

4.14.1. Description ................................................................................................................ 7

4.14.2. Functional Requirements ............................................................................................ 7

4.15. SYSTEM PUBLISHES THE WINNER OF EVENT .............................................................................. 7

4.15.1. Description ................................................................................................................ 7

4.15.2. Functional Requirement ............................................................................................. 7

4.16. SYSTEM ACCEPTS/DECLINE THE EVENT REGISTER ....................................................................... 7

4.16.1. Description ................................................................................................................ 7

4.16.2. Functional Requirement ............................................................................................. 7

4.17. ADMINISTRATOR CAN MANAGE ACCOUNT ................................................................................. 7

4.17.1. Description ................................................................................................................ 7

4.17.2. Functional Requirement ............................................................................................. 7

4.18. ADMINISTRATOR CAN MANAGE EVENTS ................................................................................... 7



Project Team: 01 Prepared by: All members Page 1 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



4.18.1. Description ................................................................................................................ 7

4.18.2. Functional Requirement ............................................................................................. 7

4.19. ADMINISTRATOR CAN CANCEL EVENTS .................................................................................... 8

4.19.1. Description ................................................................................................................ 8

4.19.2. Functional Requirement ............................................................................................. 8

4.20. ADMINISTRATOR CAN ACCEPT/DECLINE THE EVENTS WHICH ARE PROPOSED BY THE EMPLOYEE............... 8

4.20.1. Description ................................................................................................................ 8

4.20.2. Functional Requirement ............................................................................................. 8

4.21. ADMINISTRATOR CAN MANAGE THE TYPE OF EVENT .................................................................... 8

4.21.1. Description ................................................................................................................ 8

4.21.2. Functional Requirement ............................................................................................. 8

4.22. ADMINISTRATOR CAN MANAGE THE PRIZES OF EVENT.................................................................. 8

4.22.1. Description ................................................................................................................ 8

4.22.2. Functional Requirement ............................................................................................. 8

4.23. ADMINISTRATOR CAN UPDATE THE WINNER OF GAME.................................................................. 8

4.23.1. Description ................................................................................................................ 8

4.23.2. Functional Requirement ............................................................................................. 8

4.24. MANAGE FAQS ................................................................................................................ 8

4.24.1. Description ................................................................................................................ 8

4.24.2. Functional Requirements ............................................................................................ 8

4.25. MANAGE COMPANY‟S INFORMATION ....................................................................................... 8

4.25.1. Description ................................................................................................................ 8

4.25.2. Functional Requirements ............................................................................................ 9

4.26. MANAGE EMPLOYEE „S COMMENT ........................................................................................... 9

4.26.1. Description ................................................................................................................ 9

4.26.2. Functional Requirements ............................................................................................ 9

5. SYSTEM REQUIREMENTS ................................................................................................ 9

5.1. HARDWARE ........................................................................................................................ 9

5.1.1. Web Server ............................................................................................................... 9

5.1.2. Client ........................................................................................................................ 9

5.2. SOFTWARE ......................................................................................................................... 9

5.2.1. Web Server ............................................................................................................... 9

5.2.2. Client ........................................................................................................................ 9

6. DEVELOPMENT SOFTWARE ............................................................................................. 9

7. TECHNOLOGY.................................................................................................................. 9

8. USE CASE ...................................................................................................................... 11

8.1. GUEST ............................................................................................................................ 11

8.1.1. View ....................................................................................................................... 11

8.1.2. Login ...................................................................................................................... 12

8.1.3. Forgot Password ...................................................................................................... 13

8.2. EMPLOYEE ........................................................................................................................ 14

8.2.1. Search .................................................................................................................... 14

8.2.2. Process Event .......................................................................................................... 16

8.2.2.1. View Details of Event ............................................................................................ 16

8.2.2.2. Register Event...................................................................................................... 17

8.2.2.3. Cancel Event Register ........................................................................................... 18

8.2.3. View Another Employee‟s Information ....................................................................... 19

8.2.4. Propose New Events ................................................................................................ 19

8.2.5. View FAQs............................................................................................................... 21

8.2.6. Support ................................................................................................................... 22

8.3. MANAGE PROFILE ............................................................................................................... 23

8.4. ADMINISTRATOR ................................................................................................................ 25

8.4.1. Search .................................................................................................................... 25

8.4.2. Manage event ......................................................................................................... 26

8.4.2.1. View list of event .................................................................................................. 26

8.4.2.2. View event details ................................................................................................ 27



Project Team: 01 Prepared by: All members Page 2 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



8.4.2.3. Create event ........................................................................................................ 28

8.4.2.4. Update event ....................................................................................................... 30

8.4.2.5. Cancel event ........................................................................................................ 31

8.4.2.6. Create prize ......................................................................................................... 32

8.4.2.7. Update winner ..................................................................................................... 33

8.4.3. Manage proposed event ........................................................................................... 35

8.4.3.1. View list of proposed event ................................................................................... 35

8.4.3.2. View proposed event details.................................................................................. 36

8.4.3.3. Accept/decline proposed event .............................................................................. 37

8.4.4. Manage Account ...................................................................................................... 38

8.4.4.1. View list of accounts ............................................................................................. 39

8.4.4.1.1. View account details ............................................................................................. 40

8.4.4.2. Set administrator .................................................................................................. 41

8.4.4.3. Create account ..................................................................................................... 41

8.4.4.4. Block/Unblock account ......................................................................................... 42

8.4.5. Manage company information .................................................................................. 43

8.4.5.1. View company information .................................................................................... 43

8.4.5.2. Create company information ................................................................................. 44

8.4.5.3. Update company information ................................................................................ 45

8.4.5.4. Delete company information ................................................................................. 46

8.4.6. Manage FAQ ........................................................................................................... 48

8.4.6.1. View list of FAQs .................................................................................................. 48

8.4.6.2. View FAQ details .................................................................................................. 49

8.4.6.3. Create FAQ .......................................................................................................... 50

8.4.6.4. Update FAQ ......................................................................................................... 51

8.4.6.5. Activate/Inactivate FAQ ........................................................................................ 52

8.4.6.6. Publish FAQs ........................................................................................................ 53

8.4.7. Manage comments .................................................................................................. 54

8.4.7.1. View list of comments ........................................................................................... 54

8.4.7.2. Delete comments ................................................................................................. 55

8.4.8. Manage event type .................................................................................................. 56

8.4.8.1. View list of event type .......................................................................................... 56

8.4.8.2. View event type details ......................................................................................... 57

8.4.8.3. Create event type ................................................................................................. 58

8.4.8.4. Update event type ................................................................................................ 59

8.4.8.5. Delete event type ................................................................................................. 60

8.5. SYSTEM ........................................................................................................................... 61

8.5.1. Remind Birthday ...................................................................................................... 61

8.5.2. Accept Register Event Request ................................................................................. 62

8.5.3. Publish Upcoming Event ........................................................................................... 63

8.5.4. Publish The Winners of Event ................................................................................... 64

9. ENTITY RELATIONSHIP DIAGRAM (ERD) .................................................................... 65

9.1. CONCEPTUAL .................................................................................................................... 65

9.2. LOGICAL .......................................................................................................................... 66

10. ENTITY-ATTRIBUTE ................................................................................................... 66

10.1. FAQ ........................................................................................................................... 66

10.2. COMPANY INFORMATION .................................................................................................. 66

10.3. USER ........................................................................................................................... 67

10.4. COMMENT..................................................................................................................... 67

10.5. PRIZE .......................................................................................................................... 67

10.6. EVENT ......................................................................................................................... 68

10.7. EVENT TYPE .................................................................................................................. 68

10.8. EVENT REGISTER ............................................................................................................ 68

11. TASKSHEET ................................................................................................................ 69









Project Team: 01 Prepared by: All members Page 3 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty





1. Introduction

Blue Pumpkin is a marketing agent of an internet marketing company, who provides different services

such as dial-up services, the broadband services, etc., . They want to build a website for the

interactive and entertainment purpose of the Employees.



2. Existing Scenario

There are many employees work for Blue Pumpkin; they often move out to contact customers or to

seek for new customers. Therefore they don‟t have much time to meet, relax or play together. To

accomplish that, the manager wants to create website application, which will be a new space where

all employees can join not only for entertainment, but also for events, meetings, and other work

wherever they are.



3. Customer Requirement Specification

This website can perform the following tasks:

- User will login as admin or employee.

- If user is admin, he will have the authority to create and delete the profile of an employee.

- The admin will have the permission to accept the participation request based on the

requirement.

- If user is employee, he/she will be able to send their request for the participation in any of the

events and view detail of any events.

- The employee can propose new event to the manager to make closet employee together.

- To encourage employees and to build a friendly rapport in the company, the manager started

conducting games and distributing the prizes.

- The website home page should have the details of the upcoming events such as meetings,

games…

- This home page should also include the winners details of the events conducted recently.

- The website also has a reminder which will remind about the users birthday.

- The website contains the FAQs, have contact and support page where the details be display.



4. Functional Requirement Specification:

A. Guest

4.1. Guest can view company’s information



4.1.1. Description

Display the company‟s information.



4.1.2. Functional Requirement

REQ - 01. Display the company‟s information.

4.2. Guest can login as Employee or Admin



4.2.1. Description

The site will have a page to allow guest to login as Employee or Admin. The system must

distinguish between employee and admin and then redirect to a specific page.



4.2.2. Functional Requirement

REQ - 02. Guests must provide Username and Password to login into the website.

REQ - 03. System must recognize the account‟s type to display the right pages.

REQ - 04. Employees can only access to pages they have permission.

REQ - 05. Admins will be forwarded to administration panel to maintain system.





Project Team: 01 Prepared by: All members Page 4 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



B. Employee

4.3. Employee can edit their profile information

4.3.1. Description

Provide a page to allow employee to:

- View and edit personal information.

- View the events that they have joined



4.3.2. Functional Requirement

REQ - 06. Employees can view and edit their personal information.

REQ - 07. Employees can View the events that they have joined.

4.4. Searching



4.4.1. Description

Provide a page to allow employee to search events by entering keyword(s). The search results

include general information about each event and provide a link where employee can click on

in order to view details.

Employee can view events quickly by selecting items of the list of news events, events with

many participants and so on.



4.4.2. Functional Requirements

REQ - 08. Provide a search engine to search events.

REQ - 09. Search results list general information about each event and provide a link to view

details.

REQ - 10. Provide list of news events, events with many participants and so on, to allow

employee to view the events fast.

4.5. Employee can view details of event

4.5.1. Description

Provide a page to allow employee to view details of event when employee click on “view

detail” of any event.



4.5.2. Functional Requirements

REQ - 11. Employee can view event details such as description, number of participants,

prizes, etc.,

4.6. Employee can send request to register event



4.6.1. Description

When employee views events, provide a link allow employee to send request to register for

the event.



4.6.2. Functional Requirement

REQ - 12. System displays the form that allows employee to send request to register the

event that hasn‟t pass the deadline and that event hasn‟t registered by that user.

4.7. Employee can cancel the event register



4.7.1. Description

Provide a page to allow employee to cancel the registered event, although the system accept

the request or not.









Project Team: 01 Prepared by: All members Page 5 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



4.7.2. Functional Requirements

REQ - 13. Employee can cancel the registered event after the registered event has been

approved and the event deadline is not expired.

4.8. Employee can make comment



4.8.1. Description

Provide a page to allow employees to make a comment about news when they view the

events.



4.8.2. Functional Requirements

REQ - 14. Employee can make the comment

4.9. Employee can view another employee’s information



4.9.1. Description

Provide a page to allow employee to view another employee‟s information:

- Username, email, department.



4.9.2. Functional Requirements

REQ - 15. Employee can view another employee„s information.

4.10. Employee can proposes the new event



4.10.1.Description

Provide a page to allow employee to propose the new event:

- Event‟s name.

- Event‟s content.

- Event‟s purpose, mean.



4.10.2.Functional Requirements

REQ - 16. Employee must provide the information about new events.

4.11. Employee can view FAQs



4.11.1.Description

Provide a page to allow employee to view FAQs.



4.11.2.Functional Requirements

REQ - 17. Employee can view FAQ‟s.

4.12. Supporting



4.12.1.Description

Employee can send supporting request and view the answer.



4.12.2.Functional Requirements

REQ - 18. Employee can view supporting page.

REQ - 19. Employee can send the supporting question.









Project Team: 01 Prepared by: All members Page 6 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



C. System

4.13. System reminds birthday

4.13.1.Description

When employee/administrator logged in, system will notice them about user‟s birthday in this

week.



4.13.2.Functional Requirement

REQ - 20. The system reminds user about the birthday of other user.

4.14. System publishes upcoming events



4.14.1.Description

The system published the new events three days before it will be started.



4.14.2.Functional Requirements

REQ - 21. The system will publish upcoming events in the next 3 days.

4.15. System publishes the winner of event



4.15.1.Description

The system will publish the events winner together with his/her prize.



4.15.2.Functional Requirement

REQ - 22. System publishes winner of recent event on homepage after the event has been

finished for 3 days.

4.16. System accepts/decline the event register



4.16.1.Description

System can accept the employee„s register.



4.16.2.Functional Requirement

REQ - 23. System accepts the registration only if the register date is not end; the number of

participant isn‟t full.

D. Administrator

4.17. Administrator can manage account



4.17.1.Description

System must provide for Administrator a page that allows them to manage accounts such as

create new account, block/unblock account.



4.17.2.Functional Requirement

REQ - 24. Administrator can manage an account.

4.18. Administrator can manage events



4.18.1.Description

System must provide for Administrator a page that allows them to manage events such as

creating, updating event‟s information.



4.18.2.Functional Requirement

REQ - 25. Administrator can create an event

REQ - 26. Administrator can update event information









Project Team: 01 Prepared by: All members Page 7 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



4.19. Administrator can cancel events



4.19.1.Description

Administrator can cancel event if they meet the condition (e.g. the number of participants is

less than one third of the total ones.)



4.19.2.Functional Requirement

REQ - 27. Administrator can cancel event.

4.20. Administrator can accept/decline the events which are proposed by the employee



4.20.1.Description

Administrator can choose to accept or decline the proposed event



4.20.2.Functional Requirement

REQ - 28. Administrator can accept or decline proposed event

REQ - 29. System will automatically display the upcoming approved events.

4.21. Administrator can manage the type of event



4.21.1.Description

Administrator can create news, update or delete event type



4.21.2.Functional Requirement

REQ - 30. Administrator must provide event type information

REQ - 31. Administrator can update or delete event type

4.22. Administrator can manage the prizes of event



4.22.1.Description

Provide a page to allow administrator to manage the prizes of event such as inserts, deletes,

and updates the prizes of game.



4.22.2.Functional Requirement

REQ - 32. Administrator can manage the prizes of event.

4.23. Administrator can update the winner of game.



4.23.1.Description

When an event ends, or has a winner, administrator must update the winner of the event



4.23.2.Functional Requirement

REQ - 33. Administrator must provide the winner to system updating.

4.24. Manage FAQs



4.24.1.Description

System must provide to user (employee and guest) a page which displays frequently

questions and answers. Administrator can add, modify or delete these.



4.24.2.Functional Requirements

REQ - 34. All users can view FAQs page.

REQ - 35. Administrator can add, modify,publish or delete these.

4.25. Manage company’s information

4.25.1.Description

Provide a page to allow admin to update company‟s information.









Project Team: 01 Prepared by: All members Page 8 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



4.25.2.Functional Requirements

REQ - 36. Admin manage company‟s information.

4.26. Manage employee ‘s comment



4.26.1.Description

Provide a page to allow admin to be able to view the employee‟s comment, and delete the

comments.



4.26.2.Functional Requirements

REQ - 37. Admin manage employee„s comment.



5. System Requirements

5.1. Hardware



5.1.1. Web Server

Processor Dual Core or higher.

Memory 1G RAM or greater.

Modem/ADSL Connecting to internet 24/7



5.1.2. Client

Processor Dual Core or higher.

Memory 1G RAM or greater.

Monitor Super VGA (800x600) or higher resolution with >256 colors.

Pointing Device Mouse or compatible pointing device.

Modem/ADSL Speed: 2mbps



5.2. Software



5.2.1. Web Server

Operation System Windows XP / 7

Browser Internet Explorer 7.0 or higher.

Database Microsoft SQL Server 2005 SP1

Software Java SDK 1.6 u22

Server Jboss Application Server 5.1.0 GA



5.2.2. Client

Operation System Windows Vista or later.

Browser Internet Explorer 7.0 or higher.



6. Development Software

 Net Beans 6.7.1

 Java SDK 1.6 u17

 Microsoft SQL Server 2005 SP1

 Internet Explorer 7.0

 Jboss 4.0





7. Technology

 JavaEE5

 JSP, Servlet

 HTML

 EJB3





Project Team: 01 Prepared by: All members Page 9 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty









REVIEW 2









Project Team: 01 Prepared by: All members Page 10 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty





8. Use case

8.1. Guest

class GUEST









VIEW









LOGIN





GUEST

(from Actors)







GET PASSWORD









8.1.1. View

Author Ao Hoang Hung

Use Case Name View

Actors Guest

Description Guest wants view information of company

Requirements n/a

Pre-conditions n/a

Post-conditions Success: Redirect to “About Us” page

Fail: n/a

Basic flow Actor Actions: System Responses:

1. Actor clicks “About Us” link on “Home 2. System redirects to “About Us” page

page” and display table format contain:

- 2 column:

* Column 1: Information

* Column 2: Value

Alternative n/a n/a

Exception n/a n/a









Project Team: 01 Prepared by: All members Page 11 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty









8.1.2. Login

Author Ao Hoang Hung

Use Case Name Login

Actors Guest

Description Guest wants to login to website as a Employee or Admin

Requirements n/a

Pre-conditions n/a

Post-conditions Success: Redirect to Employee‟s home page or Admin‟s home page

Fail: Refill information.

Basic flow Guest Actions: System Responses:

1. Click „Login‟ link.

2. System redirects Login form with the

following control:

- „Username‟ text field

- „Password‟ password field

- „Login‟ button

-„Cancel‟ button

-„Forgot Your Password‟ link

3. Guest inputs Username and Password.

- Provide username in „Username‟ text field

- Provide password in „Password‟ password

field

4. Click the Login button. 5. System checks the information and

[Alternative 1] [Alternative 2] authority. .[Exception 1]

6. System redirects to Actor‟s Home

page.

Alternative Guest Actions: System Responses:

[Alternative 1] Guest clicks the „Cancel‟ 1. System clears all text field and return

button. blank.

[Alternative 2] Guest clicks „Forgot Your 2. System redirects to „Get Password‟

Password‟ link page



Exception Guest Actions: System Responses:

[Exception 1]Input wrong username or 1. System displayed message to notice

password guest: „Username or Password incorrect.

Please try again‟.

2. System check how many time guest

inputs wrong username or password.

After 3 times, system redirect to „Get

Password‟ page.









Project Team: 01 Prepared by: All members Page 12 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty









8.1.3. Forgot Password

Author Ao Hoang Hung

Use Case Name Forgot Password

Actors Guest

Description Guest wants to get password.

Requirements n/a

Pre-conditions n/a

Post-conditions Success: Display message: “Password re-sent to your email”

Fail: n/a

Basic flow Guest Actions:

1. Guest click „Forgot Your Password‟ link.



2. System redirects to „Get Password‟

page and display form include control:

- „Your e-mail‟ text field.

- „Ok‟ button

- „Cancel‟ button

3.Guest inputs email address.

- Provide email address in „Your e-mail‟

text field.

4. System checks email.

[Exception 1]

5.Guest click „OK‟ button.

[Alternative 1] 6. System redirects to „Forget Password‟

page and display message „Password re-

sent to your email‟

Alternative Guest Actions: System Responses:

[Alternative 1]

Click the „Cancel‟ button. System clears all text field and return

blank.

Exception Guest Actions: System displayed message to notice

[Exception 1] guest:

1. Input wrong email. 1. „Email not exist. Please try

again‟.









Project Team: 01 Prepared by: All members Page 13 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty









8.2. Employee

uc Employee Use Cases









Search









Process ev ent









View another employee's

Employee information









Propse new ev ents









View FAQs

Support









8.2.1. Search

Author Ao Hoang Hung

Use Case Name Search

Actors Employee



Project Team: 01 Prepared by: All members Page 14 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



Description Actor can search events through keyword.

Requirements Actor logged in the website.

Pre-conditions Actor logged in as Employee.

Post-conditions Success: show list of events.

Fail: show Error page.

Basic flow Actor Actions: System Responses:

1. Actor enters keyword to “Search” text field.

2. Actor clicks Search button.

[Alternative 1] 3. System selects events which have

event‟s information that matches

searching information.

[Alternative 1]

4. System displays the list of events

with following information:

 ShortDescription

 Registration event.

 Number of participants.

and one of the controls is displayed:

 Register button if the

registration date is not

expired, the number of

participant is not full, and the

actor has not registered

before.

 Or Cancel button if actor has

registered before, the

registration date is not

expired.

 Or Pending label if the start

date of event started.

 Or AdminCancel label if the

event is canceled by admin.

Alternative flow Actor Actions: System Response:

[Alternative 1]

- There„s no event that match searching - System shows the message for actor:

information. “There is no result match your

searching condition.”

Exception n/a n/a









Project Team: 01 Prepared by: All members Page 15 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



8.2.2. Process Event









8.2.2.1. View Details of Event

Author Ao Hoang Hung

Use Case Name View Details of Event

Actors Employee.

Description Actor can view details of event.

Requirements Actor chooses the event to view.

Pre-conditions Actor logged in as Employee.

Post-conditions Success: show details of chose event.

Fail: show Error page.

Basic flow Actor Actions: System Responses:

1. Actor clicks on “View Detail” link. 2.System selects from database and

displays details of event with

following controls:

 „Title‟ label: event‟s title.

 „FullDescription‟ label:

event‟s full description.

 „StartDate‟ label: start date

of event.

 „EndDate‟ label: end date of

event.

 „RegistrationStart‟ label:

event‟s start date of

registration.

 „RegistrationEnd‟ label:

event‟s end date of

registration.





Project Team: 01 Prepared by: All members Page 16 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



 „NoOfParticipant‟ label: the

number of people can

participate.

 „Joined‟ label: the number of

people registered to

participate in event.

And one of the controls is displayed:

 „Register‟ button if actor

hasn‟t registered before, the

registration date is not

expired and the number of

participant is not full.

 Or „Cancel‟ button if actor

has registered, the

registration date is not

expired.

Alternative flow n/a n/a

Exception n/a n/a









8.2.2.2. Register Event

Author Ao Hoang Hung

Use Case Name Register Event

Actors Employee

Description Actor can register to join in event.

Requirements Actor logged in the website.

Pre-conditions Actor logged as Employee.

Post-conditions Success: show actor‟s history with the event which actor has just registered.

Fail: show Error Page.

Basic flow Actor Actions: System Responses:

1. Actor clicks on „Register‟ button. 2. System checks the condition:

 The registration date of event

is not expired.

 The number of participant is

not full.

[Alternative 1]

3. System redirects to the page and

shows list of events which actor has

just registered with the “Cancel”





Project Team: 01 Prepared by: All members Page 17 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



button for actor to cancel the

registered event.

Alternative flow Actor action: System Responses:

[Alternative 1] System declines that event register

and shows the popup form with the

message:

- The registration date of event is expired. - “Registration date of event is

expired.”

- The number of participant is full. - “The number of participant is full”.



Exception n/a n/a









8.2.2.3. Cancel Event Register

Author Ha Thi Minh Phuong

Use Case Name Cancel Event Register.

Actors Employee

Description Actor can cancel the event register.

Requirements n/a.

Pre-conditions Actor logged in the website as Employee.

Post-conditions Success: show the event‟s history.

Fail: show Error page with the reason why actor cancels event register fail.

Basic flow Actor Actions: System Responses:

1. Actor clicks on “Cancel” button. 2. System checks the information:

 The registration of event is

not expired.

 The number of participant is

not full.

[Alternative 1]

3. System updates event status

register for Actor.

Alternative flow Actor Actions: System Response:

[Alternative 1]

- The registration date is expired. - System shows popup form with

message “The registration date is

expired.”

- The number of participant is full. - System shows popup form with the

message “The number of participant

is full.”



Exception n/a n/a









Project Team: 01 Prepared by: All members Page 18 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty









8.2.3. View Another Employee’s Information

Author Ha Thi Minh Phuong

Use Case Name View Another Employee‟s Information

Actors Employee

Description Actor can view another employee‟s information.

Requirements Actor logged in the website.

Pre-conditions Actor logged in the website as Employee.

Post-conditions Success: show another employee‟s public information.

Fail: show Error page.

Basic flow Actor Actions: System Responses:

1. Actor clicks on Another Employee‟s 2.System selects from database and

Username. displays another employee‟s

information:

 Full name.

 Department

 Email.

 Events he/she joined.

Alternative flow n/a. n/a.

Exception n/a. n/a.









8.2.4. Propose New Events

Author Huynh Khanh Thien vu

Use Case Name Propose New Events

Actors Employee





Project Team: 01 Prepared by: All members Page 19 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



Description Actor proposes new events.

Requirements Actor logged in the website.

Pre-conditions Actor logged in the website as Employee.

Post-conditions Success: show the list of events which are proposed by actor.

Fail: refill information.

Basic flow Actor Actions: System Responses:

1. Actor clicks on Propose New Event button. 2.System redirects to the page and

shows the form for Actor to input

information with the following

control:

 „Title‟ text field.

 „Event type‟ dropdownlist

 „ShortDescription‟ text area.

3. Actor inputs information: name in „Title‟  „Description‟ text area.

text field, event‟s short description in  “Propose” button.

„ShortDescription‟ text area, event‟s detail  “Cancel” button.

description in „Description‟ text area.

4. Actor clicks “Propose” button.

[Alternative 1]



5. System checks input information.

[Exception 1]

6. System inserts into database and

display list of events which are

proposed by actor.

Alternative flow Actor Actions: System Responses:

[Alternative 1]

- Actor clicks “Cancel” button. - System redirects to actor‟s User

panel page.

Exception Actor Actions: System Responses:

[Exception 1] System show message to actor:

-„Title‟ text field is blank - “Event‟s title is not blank.”

- The title‟s length is not between 5 and 255. - “Event‟s title must be between 5 and

- „ShortDescription‟ text area is blank. 255”

- “Event‟s short description is not

- The short description‟s length is not between blank.”

5 or 255. - “Event short description‟s length is

- „Description‟ text area is blank. between 5 and 50”

- “Event‟s description is not blank ”

- The description‟s length is not between 20 - “Event description‟s length is

and 2000. between 20 and 2000”









Project Team: 01 Prepared by: All members Page 20 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty









8.2.5. View FAQs

Author Ha Thi Minh Phuong

Use Case Name View FAQs

Actors Employee

Description View frequently asked questions.

Requirements Actor logged in the website.

Pre-conditions Actor logged in the website as employee.

Post-conditions Success: List FAQs is showed.

Fail: Show Error page.

Basic flow Actor Actions: System Responses:

1. Actor clicks on FAQs link on menu bar. 2. System selects from database, show

the list questions with the general

information and provide the link for

actor to view details of question.

4. System selects from database, show

3. Actor clicks on the question which actor details of question:

wants to view details.  The content of question.

 The answer.

Alternative flow n/a n/a

Exception n/a n/a









Project Team: 01 Prepared by: All members Page 21 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty









8.2.6. Support

Author Ha Thi Minh Phuong

Use Case Name Support

Actors Employee

Description Actor wants to be supported, so actor sends the question.

Requirements Actor logged in the website.

Pre-conditions Actor logged in the website as Employee.

Post-conditions Success: show the question which the actor asked.

Fail: Refill information.

Basic flow Actor Actions: System Responses:

1. Actor clicks on Support link on User panel‟s 2.System redirects to Support page

menu bar. and display the form for Actor to

input information:

 “Content” text area.

 “Send” button.

 “Cancel” button.

2. Actor inputs content of question to

“Content” text area, clicks “Send” button. 3. System checks input data.

[Alternative 1] [Exception 1]



4. System inserts to database and

return the support question‟s history.

Alternative flow Actor Actions: System Responses:

[Alternative 1]

Actor clicks “Cancel” button. System redirects to actor‟s User panel

page.

Exception Actor Actions: System Responses:

[Exception 1] System returns the message to actor:

- “Question‟s content is not blank.

- „Content‟ text field is blank. - “The length of content question is

- The content‟s length is not between 10 and between 10 and 255”

255.









Project Team: 01 Prepared by: All members Page 22 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty









8.3. Manage profile

uc Admin - Employee









Manage Profile



Employee

Admin







Author Ha Thi Minh Phuong

Use Case Name Manage Profile

Actors Employee, Admin

Description Actor can view and edit his/her profile.

Requirements Actor logged in the website.

Pre-conditions Log in as Employee or Admin.

Post-conditions Success: show Profile Page.

Fail: refill information.

Basic flow Actor Actions: System Responses:

1. Actor clicks Actor‟s Username on top of 2. System selects from database,

page. redirects to the page and displays

profile‟s information with following

controls:

 „FullName‟ label: actor‟s full

name.

3. Actor clicks on Edit button.

 „Gender‟ label: actor‟s

gender.

 „Address‟ label: actor‟s

address.

 „Department‟ label: actor‟s

department.

 „Birthday‟ label: actor‟s

birthday.

 „Email‟ label: actor‟s email

address.

4.System redirects to the page and

shows the form for Actor to input new

information with the following





Project Team: 01 Prepared by: All members Page 23 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



control (the controls‟ value are filled

with the data in database):

 „Name‟ text field.

5. Actor edits information needed updating: full  „Password‟ password field.

name in „Name‟, password in „Password‟,

 „ConfirmPassword‟

confirm password in „ConfirmPassword‟,

checks one of two „Gender‟ radio button, password field.

address in „Address‟ text field, department in  Two „Gender‟ radio button

„Department‟ text field, email address in with value: Male, Female.

„Email‟, birthday in „Birthday‟.  „Address‟ text field.

6. Actor clicks “Save” button.  „Department‟ text field.

[Alternative 1]

[Alternative 2]  „Email‟ text field.

 „Birthday‟ calendar control.

 „Save‟ button.

 „Cancel‟ button.



7. System checks input data.

[Exception 1]

8. System updates new information

into database.

9. System redirects to the page to

display the updated profile.

Alternative flow Actor Actions: System Responses:

[Alternative 1]

Actor clicks “Cancel” button. System redirects to Actor‟s

homepage.

Exception Actor Actions: System Responses:

[Exception 1] System displays message to Actor:

- Actor left „Name‟ text field blank. -“The full name can‟t be blank”.

- Full name„s length is not 10 between and 255. - “The full name‟s length must be

- Actor left „Password‟ password field blank. between 10 and 255.”

- Password‟s length is between 6 and 50. - “Password can‟t be blank”.

“Password‟s length must be between

- Actor left „ConfirmPassword‟ text field 6 and 50”.

- “Confirm Password can‟t be blank”.

- Value of „Password‟ and value of -“Password and Confirm Password

„ConfirmPassword‟ are not same. must be same”.

- Actor left „Email‟ text field blank. - “Email address can not be blank”

- Email address is not match regular - “Email is invalid”.

expression: \b[A-Z0-9._%-]+@[A-

Z0-9.-]+\.[A-Z]{2,4}\b. - “Address can not be blank”.

- Actor left „Address‟ text field blank. - “Address‟s length is between 15 and

- Address‟s length is between 5 and 255. 255”

- “Department can not be blank”

- Actor left „Department‟ text field blank. - “Department‟s length is between 5

- Department‟s length is between 5 and 50 and 50”.

- “Birthday‟s year isn‟t more than

- Birthday‟s year is more than 1900. 1990”.









Project Team: 01 Prepared by: All members Page 24 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty









8.4. Administrator

uc Administrator









Search

Manage ev ent



Manage proposed

ev ent









Manage account









Answ er support

Administrator

request









Manage company

information







Manage new s



Manage FAQs









8.4.1. Search

Author Tran The Nhan

Use Case Name Search

Actors Administrator



Project Team: 01 Prepared by: All members Page 25 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



Description Actor can search events through keyword.

Requirements Actor logged in the website.

Pre-conditions Actor logged in as Administrator.

Post-conditions Success: show search result

Fail: show Error page.

Basic flow Actor Actions: System Responses:

1. Actor enters keyword to “Search” text field.

2. Actor clicks Search button.

[Alternative 1] 3. System search database and

displays result in table form

Alternative flow Actor Actions: System Response:

[Alternative 1]

- There„s no event that match searching - System shows the message for actor:

information. “There is no result match your

searching condition.”

Exception n/a n/a





8.4.2. Manage event









8.4.2.1. View list of event

Author Tran The Nhan

Use case name View List of Events

Actors Administrator

Description View List of Events

Requirements n/a

Pre-conditions Logged into the System as Administrator

Post-conditions Success : View List of Events

Fail : connection error, redirect to Admin homepage

Basic flow Actor actions: System response:

1. From „Admin‟ page, actor clicks on to 2. System redirects to „Event

„Manage Events‟ button. management‟ page and display list of

Events in table form:

 Title of event Label

 Event type Label

 ShortDescription Label

 View detail button







Project Team: 01 Prepared by: All members Page 26 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



 Cancel button

 Create prize button

 Update winner button

 Create new event button

Alternative n/a n/a

Exception n/a n/a









8.4.2.2. View event details

Author Tran The Nhan

Use case name View Event Details

Actors Administrator

Description View Event Details

Requirements n/a

Pre-conditions Logged into the System as Administrator

Post-conditions Success: View Event Details

Fail : connection error, redirect to Admin homepage

Basic flow Actor actions: System response:

1. From „Event management‟ page, actor 2. System redirects to „Event Details‟ page

clicks on to a „View details‟ button. and display event information:

 EventID Label

 Title Text field

 EventType Dropdownlist

 ShortDescription HTML Editor

 FullDescription HTML Editor

 NoOfParticipant Text field

 StartRegDate Datetimepicker

 EndRegDate Datetimepicker

 StartDate Datetimepicker

 EndDate Datetimepicker

 isActive checkbox

 Update button

 Cancel button

 Back button

 Create prize button

 Update winner button







Project Team: 01 Prepared by: All members Page 27 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



 View comments

Alternative n/a n/a

Exception n/a n/a









8.4.2.3. Create event

Author Tran The Nhan

Use Case Name Create event

Actors Administrator

Description Administrator want to create a new event

Requirements n/a

Pre-conditions Logged in as administrator

Post-conditions Success: new event created

Fail: Refill information

Basic flow Actor Actions: System Responses:

1. Actor clicks „Create new event‟ button 2. System redirects to create event

page and displays form with the

following control :

 Title Text field

 EventType Dropdownlist

 ShortDescription HTML Editor

 FullDescription HTML Editor

 NoOfParticipant Text field

 StartRegDate Datetimepicker

 EndRegDate Datetimepicker

 StartDate Datetimepicker

 EndDate Datetimepicker

 isActive checkbox

 Create button

 Back button

3. Actor inputs information and clicks on to

Create button. 4. System checks the information

[Alternative 1] [Exception 1]

5. System inserts new event into

database, show message: „Your event

has been created!‟ and then redirects

to „Event management‟ page.

Alternative Actor Actions: System Responses:

[Alternative 1]

1. Actor clicks „Back‟ button. 2. System returns to „Event

management‟ page.



Project Team: 01 Prepared by: All members Page 28 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



Exception Actor Actions: System Responses:

[Exception 1] System displays message to Actor :

1. Actor left title Text field blank 1. „Title cannot be blank‟

2. Actor input Title less than 5 or more than 2. Title must have 5 to 50 characters

50 characters

3. Actor didn‟t choose event type 3. „You must choose event type‟

4. Actor left short description HTML Editor 4. „Short Description cannot be blank‟

blank

5. Actor left full description HTML Editor 5. „Full Description cannot be blank‟

blank

6. Actor input short description less than 5 6. Short Description must have 5 to

or more than 2000 character 100 characters

7. Actor input Title less than 5 or more than 7. Full Description must have 5 to

2000 character 2000 characters

8. Actor left NoOfParticipant Text field blank 8. „NoOfParticipant‟ cannot be blank‟

9. Actor fill letter in NoOfParticipant Text 9. „NoOfParticipant must be numeric‟

field

10. The number actor fill in NoOfParticipant 10. „NoOfParticipant must > 0 and

current date current date

13. Actor choose EndDate StartDate

14. Actor choose StartRegDate StartDate

15. Actor choose EndRegDate StartRegDate

StartRegDate









Project Team: 01 Prepared by: All members Page 29 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



8.4.2.4. Update event

Author Tran The Nhan

Use Case Name Update event

Actors Administrator

Description Administrator want to edit event‟s information

Requirements Event hasn‟t started yet

Pre-conditions Logged in as administrator

Post-conditions Success: event updated

Fail: Refill information

Basic flow Actor Actions: System Responses:

1. In “Event details” page, system

display details , user can input

information in following control:

 Title Text field EventType

Dropdownlist

 ShortDescription HTML Editor

 FullDescription HTML Editor

 NoOfParticipant Text field

 StartRegDate Datetimepicker

 EndRegDate Datetimepicker

 StartDate Datetimepicker

 EndDate Datetimepicker

 Update button

 Back button

 Create prize button

 Update winner button

3. System checks the information

2. Actor inputs information and clicks on to [Exception 1]

Update button. 4. System update selected event into

[Alternative 1] database, show message: „Your event

has been updated!‟ and then redirects

to „Event Details‟ page.

Alternative Actor Actions: System Responses:

[Alternative 1]

1. Actor clicks „Back‟ button. 2. System returns to „Event Details‟

page.

Exception Actor Actions: System Responses:

[Exception 1] System displays message to Actor :

1. Actor left title Text field blank 1. „Title cannot be blank‟

2. Actor input Title less than 5 or more than 2. Title must have 5 to 50 characters

50 characters

3. Actor didn‟t choose event type 3. „You must choose event type‟

4. Actor left short description HTML Editor 4. „Short Description cannot be

blank blank‟

5. Actor left full description HTML Editor 5. „Full Description cannot be blank‟

blank

6. Actor input short description less than 5 6. Short Description must have 5 to

or more than 100 character 100 characters

7. Actor input Title less than 5 or more than 7. Full Description must have 5 to

2000 character 2000 characters

8. Actor left NoOfParticipant Text field blank 8. „NoOfParticipant‟ cannot be blank‟

9. Actor fill letter in NoOfParticipant Text 9. „NoOfParticipant must be numeric‟

field



Project Team: 01 Prepared by: All members Page 30 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



10. The number actor fill in NoOfParticipant 10. „NoOfParticipant must > 0 and

current date current date

13. Actor choose EndDate StartDate

14. Actor choose StartRegDate StartDate

15. Actor choose EndRegDate

StartRegDate StartRegDate









8.4.2.5. Cancel event

Author Tran The Nhan

Use Case Name Cancel event

Actors Administrator

Description Administrator want to cancel selected event

Requirements Event hasn‟t started registering yet

Pre-conditions Logged in as administrator

Event satisfy the conditions to be canceled

Post-conditions Success: event canceled

Fail: event does not meet the conditions.

Basic flow Actor Actions: System Responses:

1. Actor clicks „Cancel event‟ button „Event 2. If true, show alert with message:

Details‟ page “Do you want to cancel this event? “

3. Actor clicks on to Yes button. 4. System update selected event into

[Alternative 1] database, show message: „Your event

has been cancelled!‟ and then redirects

„Event Details‟ page.

Alternative Actor Actions: System Responses:

[Alternative 1]





Project Team: 01 Prepared by: All members Page 31 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



1. Actor clicks „No‟ button. 2. System returns to „Event Details‟

page.

Exception Actor Actions: System Responses:

n/a n/a









8.4.2.6. Create prize

Author Tran The Nhan

Use Case Name Create prize

Actors Administrator

Description Administrator want to create prize for selected event

Requirements Event hasn‟t started registering yet

Pre-conditions Logged in as administrator

Post-conditions Success: prize created

Fail: refill information

Basic flow Actor Actions: System Responses:

1. Actor clicks „Create prize‟ button 2. System redirect to create prize

page. Actor must fill information in

following controls:

 EventID Label

 Title Text field

 ShortDescription HTML Editor

 FullDescription HTML Editor

 Create button

 Back button

3. Actor click „Create‟ button 4. System checks if the information are

[Alternative 1] correct

[Exception 1]

5. System insert new prize to database

, show message: „Create prize

successfully‟ and show message: „Do

you want to create another prize for

this event?‟

6. Actor click „Yes‟ button 7. Show create prize page

[Alternative 2]







Project Team: 01 Prepared by: All members Page 32 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



Alternative Actor Actions: System Responses:

[Alternative 1]

1. Actor clicks „Back‟ button. 2. System returns to „Event Details‟

page.

[Alternative 2]

1. Actor click „No‟ button 2. System returns to „Event Details‟

page

Exception Actor Actions: System Responses:

[Exception 1] System displays message to Actor :

1. Actor left Title blank 1. Title cannot be blank

2. Actor input Title less than 5 or more 2. Title must have 5 to 50

than 50 characters characters

3. Actor didn‟t choose event type 3. „You must choose event type‟

4. Actor left short description HTML 4. „Short Description cannot be

Editor blank blank‟

5. Actor left full description HTML Editor 5. „Full Description cannot be

blank blank‟

6. Actor input short description less 6. Short Description must have 5

than 5 or more than 100 character to 100 characters

7. Actor input Title less than 5 or more 7. Full Description must have 5 to

than 2000 character 2000 characters









8.4.2.7. Update winner

Author Tran The Nhan

Use Case Name Update winner

Actors Administrator

Description Administrator want to update winner for selected event

Requirements Event ended

Pre-conditions Logged in as administrator

Post-conditions Success: winner updated

Fail: refill information

Basic flow Actor Actions: System Responses:

1. Actor clicks „Update winner‟ button 2. System redirect to update winner

page. Actor must fill information in

following controls:

 Username dropdownlist





Project Team: 01 Prepared by: All members Page 33 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



 Prize detail label

 Update button

 Back button

[Exception 1]

3. Actor click „Update‟ button

4. System insert winner to database,

[Alternative 1]

show message : „Update winner

successfully‟

Alternative Actor Actions: System Responses:

[Alternative 1]

1. Actor clicks „Back‟ button. 2. System returns to „Event Details‟

page.

Exception Actor Actions: System Responses:

[Exception 1] System displays message to Actor :

1. Actor didn‟t choose username 2. „You must choose a winner‟









Project Team: 01 Prepared by: All members Page 34 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



8.4.3. Manage proposed event









8.4.3.1. View list of proposed event

Author Huynh Khanh Thien Vu

Use case name View list of proposed events

Actors Administrator

Description View list of proposed events

Requirements n/a

Pre-conditions Logged into the System as Administrator

Post-conditions Success: View list of proposed events

Fail : connection error, redirect to Admin homepage

Basic flow Actor actions: System response:

1. From „Admin‟ page, actor clicks on to 2. System redirects to „Proposed event

„Manage proposed events‟ button. management‟ page and display list of

proposed events in table form:

 Title of event Label

 Event type Label

 isActive Label( Yes or No only )

 View detail button

 Accept button

 Decline button

Alternative n/a n/a

Exception n/a n/a









Project Team: 01 Prepared by: All members Page 35 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty









8.4.3.2. View proposed event details

Author Huynh Khanh Thien Vu

Use case name View proposed event details

Actors Administrator

Description View Event details

Requirements Event is not accepted or declined

Pre-conditions Logged into the System as Administrator

Post-conditions Success: View proposed event details

Basic flow Actor actions: System response:

1. From „Proposed event management‟ 2. System redirects to „Proposed event

page, actor clicks on to a „View details‟ details‟ page and display event

button. information:

 Title Label

 EventType Label

 ShortDescription Label

 FullDescription Label

 NoOfParticipant Label

 Accept button

 Decline button

 Back button

Alternative n/a n/a

Exception n/a n/a









Project Team: 01 Prepared by: All members Page 36 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty









8.4.3.3. Accept/decline proposed event

Author Huynh Khanh Thien Vu

Use Case Name Accept/decline proposed event

Actors Administrator

Description Administrator want to Accept/decline proposed event

Requirements Event is not accepted or declined

Pre-conditions Logged in as administrator

Post-conditions Success: proposed event updated

Fail: redirect to „Proposed event management‟ page

Basic flow Actor Actions: System Responses:

1. Actor clicks „Accept‟ page in „Proposed 2. System update status of event to

event details‟ page database, create new event from

[Alternative 1] proposed event and show message:

[Alternative 2] „Event accepted and created, please

check event list for more detail‟ and

redirect to „Proposed event details‟

page.

Alternative Actor Actions: System Responses:

[Alternative 1]

1. Actor clicks „Decline‟ button. 2. System show message: „Are you

sure you want to decline this event?‟

3. Actor click „Yes‟ button 4. System update event status to

database

[Alternative 2]

1. Actor click „Back‟ button 2. System returns to „Propose event

management‟ page

Exception n/a n/a









Project Team: 01 Prepared by: All members Page 37 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty









8.4.4. Manage Account









Project Team: 01 Prepared by: All members Page 38 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



8.4.4.1. View list of accounts









Author Ha Thi Minh Phuong

Use case name View list of accounts

Actors Administrator

Description View list of all accounts, update account‟s role to “admin” role and block/unblock the

accounts.

Requirements n/a

Pre-conditions Logged into the System as Administrator

Post-conditions Success: show list of all accounts.

Fail: show error page.

Basic flow Actor actions: System response:

1. From „Admin‟ page, actor clicks 2. System redirects to „Account

„Manage accounts‟ button. management‟ page and displays list of

accounts in table form:

 Username Label

 Block button if status of that

account is active or Unblock

button if status of that account is

inactive.

 View detail button

 New Account button

Alternative flow n/a n/a

Exception n/a n/a









Project Team: 01 Prepared by: All members Page 39 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty









8.4.4.1.1. View account details

Author Ha Thi Minh Phuong

Use case name View account Details

Actors Administrator

Description View account Details

Requirements n/a

Pre-conditions Logged into the System as Administrator

Post-conditions Success: View account Details

Fail : connection error, redirect to Admin homepage

Basic flow Actor actions: System response:

1. From „Event management‟ page, actor 2. System redirects to „Event Details‟ page

clicks on to a „View details‟ button. and display event information:

 Username label

 Full name

 Gender

 Birthday

 Phone

 Email

 Address

 isAdmin check box

 Update button

 Back button

Alternative n/a n/a

Exception n/a n/a









Project Team: 01 Prepared by: All members Page 40 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty









8.4.4.2. Set administrator

Author Ha Thi Minh Phuong

Use case name Set administrator

Actors Administrator

Description Set account type to administrator

Requirements Account type is not administrator

Pre-conditions Logged into the System as Administrator

Post-conditions Success: View account Details

Fail : connection error, redirect to Admin homepage

Basic flow Actor actions: System response:

1. Actor check on isAdmin check box, 2. System update account type to

then click „Update‟ button. database and redirect to account details

[Alternative 1] page

Alternative Actor action System response

[Alternative 1]

1. Actor click back button 2. Redirect to account management page

Exception n/a n/a









8.4.4.3. Create account

Author Ha Thi Minh Phuong

Use Case Name Create account

Actors Administrator

Description Administrator wants to create new account for employee.

Requirements Administrator must provide account‟s information.

Pre-conditions Logged in the system as administrator



Project Team: 01 Prepared by: All members Page 41 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



Post-conditions Success: Show detail of account.

Fail: Refill information

Basic flow Actor Actions: System Responses:

1. Actor clicks on “New account” button in 2. System redirects to “Create account”

“Account management” page. page. System displays these following

controls for actor to input:

 „Username‟ text field.

 „Full name‟ text field

 „Department‟ text field

 „Create‟ button

 „Cancel‟ button.

3. Actor inputs information and clicks „Create‟ 4. System checks the information

button [Exception 1]

[Alternative 1] 5. System inserts account into

database with the default password is

123.

Alternative flow Actor Actions: System Responses:

[Alternative 1]

1. Actor clicks „Cancel‟ button. 2. System returns to „Account

management‟ page.

Exception Actor Actions: System Responses:

[Exception 1] System displays message to Actor :

- „Username‟ text field is blank. - “Username‟s account can‟t be blank”

- Username„s length is not between 5 and “Username‟s length must be between 5

50. and 50”









8.4.4.4. Block/Unblock account

Author Ha Thi Minh Phuong.

Use Case Name Block account

Actors Administrator

Description Administrator wants to block/unblock account

Requirements n/a

Pre-conditions Logged in as administrator

Post-conditions Success: list of blocked/Unblocked accounts.

Fail: Show error page.

Basic flow Actor Actions: System Responses:

1. Actor clicks on “Block/Unblock Account” 2. System show popup form: “Are you

button in „Account details‟ page. sure you want to block/unblock this

account?”

3. Actor clicks on “Yes" button 4. System updates selected account‟s



Project Team: 01 Prepared by: All members Page 42 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



[Alternative 1] status into database, show message:

„Account has been updated!‟ and then

redirects to „View List Accounts‟ page

to display the account which has just

blocked/unblocked.

Alternative flow Actor Actions: System Responses:

[Alternative 1]

- Actor clicks „No‟ button - System returns to „View List Accounts‟

page.

Exception n/a n/a









8.4.5. Manage company information









8.4.5.1. View company information

Author Huynh Khanh Thien Vu

Use case name View company information

Actors Administrator

Description View company information

Requirements n/a

Pre-conditions Logged into the System as Administrator

Post-conditions Success: View company information





Project Team: 01 Prepared by: All members Page 43 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



Fail : connection error, redirect to Admin homepage

Basic flow Actor actions: System response:

1. From „Admin‟ page, actor clicks on to 2. System redirects to „Company

„Manage company information‟ button. information management‟ page and

display information in following controls:

 Info text field

 Value text field

 DisplayOrder text field

 isActive checkbox

 „View detail‟ button

 „Delete‟ button

Alternative n/a n/a

Exception n/a n/a









8.4.5.2. Create company information

Author Huynh Khanh Thien Vu

Use Case Name Create company information

Actors Administrator

Description Administrator want to create company information

Requirements n/a

Pre-conditions Logged in as administrator

Post-conditions Success: company information created

Fail: Refill information

Basic flow Actor Actions: System Responses:

1. Actor click on “Create new company 2. System checks if the conditions are

information” button in “Company information satisfied. System redirect to “Create

management” page. company information” page. System

display these following control for user

to input:

 Info text field

 Value text field

 DisplayOrder text field

 isActive checkbox

3. User input information and click „Create‟  „Create‟ button

button  „Back‟ button

[Alternative 1] 4. System checks the information

[Exception 1]

5. System inserts account into

database, show message: „Your



Project Team: 01 Prepared by: All members Page 44 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



company information has been

created!‟ and then redirects to

„Company information management‟

page.

Alternative Actor Actions: System Responses:

[Alternative 1]

1. Actor clicks „Back‟ button. 2. System returns to „Company

information‟ page.

Exception Actor Actions: System Responses:

[Exception 1] System displays message to Actor :

1. Actor left Info blank 1. „Info cannot be blank‟

2. Actor input Info less than 5 or more than 2. „Info‟s length must between 5 and

255 characters 255 characters‟

3. Actor left Value blank

3. „Value cannot be blank‟

4. Actor input Value less than 5 or more

than 2000 characters 4. „Value‟s length must between 5

and 2000 characters‟

5. Actor left DisplayOrder blank 5. „DisplayOrder cannot be blank‟

6. Actor input non-numeric in DisplayOrder 6. „DisplayOrder must be numeric‟









8.4.5.3. Update company information

Author Huynh Khanh Thien Vu

Use Case Name Create company information

Actors Administrator

Description Administrator want to create company information

Requirements Administrator must provide company information

Pre-conditions Logged in as administrator

Post-conditions Success: company information created

Fail: Refill information

Basic flow Actor Actions: System Responses:

1. Actor click on “Create new company 2. System checks if the conditions are

information” button in “Company information satisfied. System redirect to “Create

management” page. company information” page. System

display these following control for user

to input:

 Info text field

 Value text field





Project Team: 01 Prepared by: All members Page 45 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



 DisplayOrder text field

 isActive checkbox

3. User input information and click „Create‟  „Update‟ button

button  „Back‟ button

[Alternative 1] 4. System checks the information

[Exception 1]



5. System inserts account into

database, show message: „Your

company information has been

created!‟ and then redirects to

„Company information management‟

page.

Alternative Actor Actions: System Responses:

[Alternative 1]

1. Actor clicks „Back‟ button. 2. System returns to „Company

information‟ page.

Exception Actor Actions: System Responses:

[Exception 1] System displays message to Actor :

1. Actor left Info blank 1. „Info cannot be blank‟

2. Actor input Info less than 5 or more than 2. „Info‟s length must between 5 and

255 characters 255 characters‟

3. Actor left Value blank

3. „Value cannot be blank‟

4. Actor input Value less than 5 or more

than 2000 characters 4. „Value‟s length must between 5

5. Actor left DisplayOrder blank and 2000 characters‟

6. Actor input non-numeric in DisplayOrder 5. „DisplayOrder cannot be blank‟

6. „DisplayOrder must be numeric‟









8.4.5.4. Delete company information

Author Huynh Khanh Thien Vu

Use Case Name Delete company information

Actors Administrator

Description Administrator want to delete company information

Requirements n/a

Pre-conditions Logged in as administrator

Post-conditions Success: company information deleted





Project Team: 01 Prepared by: All members Page 46 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



Fail: show error page

Basic flow Actor Actions: System Responses:

1. Actor clicks on „Delete‟ button 2. System show message: „Do you

[Alternative 1] want to delete this company

information?‟

[Add later]

3. Actor click „Yes‟ button 4. System deletes company

information in database, shows

message: „Delete successfully‟ and

returns to „company information

management‟ page

[Exception 1]



Alternative Actor Actions: System Responses:

[Alternative 1]

1. Actor clicks „Back‟ button. 2. System returns to „company

information management‟ page.

[Alternative 1]

1. Actor clicks „No‟ button 2. System returns to „company

information management‟ page.



Exception n/a n/a









Project Team: 01 Prepared by: All members Page 47 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



8.4.6. Manage FAQ









8.4.6.1. View list of FAQs

Author Huynh Khanh Thien Vu

Use case name View list of FAQs

Actors Administrator

Description View list of FAQs

Requirements n/a

Pre-conditions Logged into the System as Administrator

Post-conditions Success: View list of FAQs

Fail : connection error, redirect to Admin home page

Basic flow Actor actions: System response:

1. From „Admin‟ page, actor clicks on to 2. System redirects to „FAQs management‟

„Manage FAQs‟ button. page and display list of FAQs in table

form:

 Question label

 Answer label

 View details

 Update button

 Create button

Alternative n/a n/a

Exception n/a n/a









Project Team: 01 Prepared by: All members Page 48 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty









8.4.6.2. View FAQ details

Author Huynh Khanh Thien Vu

Use case name View FAQ details

Actors Administrator

Description View FAQ details

Requirements n/a

Pre-conditions Logged into the System as Administrator

Post-conditions Success: View FAQ details

Fail : connection error, redirect to Admin home page

Basic flow Actor actions: System response:

1. From „FAQs management‟ page, actor 2. System redirects to „FAQ details‟ page

clicks on to a „View details‟ button. and display FAQ information:

 Question label

 Answer text field

 DisplayOrder text field

 Active checkbox

 Publish checkbox

 Update button

 Back button

Alternative n/a n/a

Exception n/a n/a









Project Team: 01 Prepared by: All members Page 49 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



8.4.6.3. Create FAQ

Author Huynh Khanh Thien Vu

Use Case Name Create FAQ

Actors Administrator

Description Administrator want to create FAQ‟s

Requirements n/a

Pre-conditions Logged in as administrator

Post-conditions Success: FAQ created

Fail: Refill information

Basic flow Actor Actions: System Responses:

1. Actor click on “Create new FAQ” button in 2. System redirect to “Create FAQ”

“FAQ management” page. page. System display these following

control for user to input:

 Question text field

 Answer text field

 DisplayOrder text field

 Active checkbox

 Publish checkbox

 Create button

 Back button

3. User input information and click „Create‟ 4. System checks the information

button [Exception 1]

[Alternative 1] 5. System inserts FAQ into database,

show message: „Your FAQ has been

created!‟ and then redirects to „FAQ

management‟ page.

Alternative Actor Actions: System Responses:

[Alternative 1]

1. Actor clicks „Back‟ button. 2. System returns to „FAQ

management‟ page.

Exception Actor Actions: System Responses:

[Exception 1] System displays message to Actor :

1. Actor left Question blank 1. „Question cannot be blank‟

2. Actor input Question less than 5 or 2. „Question‟s length must between 5

more than 255 characters and 255 characters‟

3. Actor left Answer blank 3. „Answer cannot be blank‟

4. Actor input Answer less than 5 or more 4. „Answer length must between 5

than 2000 characters and 2000 characters‟

5. Actor left DisplayOrder blank 5. „DisplayOrder cannot be blank‟

6. Actor input non-numeric in DisplayOrder 6. „DisplayOrder must be numeric‟









Project Team: 01 Prepared by: All members Page 50 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty









8.4.6.4. Update FAQ

Author Huynh Khanh Thien Vu

Use Case Name Update FAQ

Actors Administrator

Description Administrator want to edit FAQ‟s information

Requirements

Pre-conditions Logged in as administrator

Post-conditions Success: FAQ updated

Fail: Refill information

Basic flow Actor Actions: System Responses:

1. In “FAQ details” page, system

display details , user can input

information in following control:

 Question label

 Answer text field

 DisplayOrder text field

 Active checkbox

 Publish checkbox

 Update button

 Back button

2. Actor inputs information and clicks on to 3. System checks the information

Update button. [Exception 1]

[Alternative 1] 5. System update selected FAQ into

database, show message: „Your FAQ

has been updated!‟ and then redirects

to „FAQ details‟ page.

Alternative Actor Actions: System Responses:

[Alternative 1]

1. Actor clicks „Back‟ button. 2. System returns to „FAQ details‟

page.

Exception Actor Actions: System Responses:

[Exception 1] System displays message to Actor :

1. Actor left Question blank 1. „Question cannot be blank‟

2. Actor input Question less than 5 or more 2. „Question‟s length must between 5

than 255 characters and 255 characters‟

3. Actor left Answer blank 3. „Answer cannot be blank‟





Project Team: 01 Prepared by: All members Page 51 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



4. Actor input Answer less than 5 or more 4. „Answer length must between 5

than 2000 characters and 2000 characters‟

5. Actor left DisplayOrder blank 5. „DisplayOrder cannot be blank‟

6. Actor input non-numeric in DisplayOrder 6. „DisplayOrder must be numeric‟









8.4.6.5. Activate/Inactivate FAQ

Author Huynh Khanh Thien Vu

Use Case Name Activate/Inactivate FAQ

Actors Administrator

Description Administrator want to activate/inactivate FAQ

Requirements n/a

Pre-conditions Logged in as administrator

Post-conditions Success: FAQ inactivated

Fail: Refill information

Basic flow Actor Actions: System Responses:

1. Actor clicks on „Active‟ checkbox 2. System show message: “Are you

[Alternative 1] sure you want to active/inactive this

FAQ?”

3. Actor click on “Yes" button 4. System update selected account‟s

[Alternative 2] status into database, show message:

„FAQ status has been updated!‟ and

then redirects to „FAQ details‟ page.

Alternative Actor Actions: System Responses:

[Alternative 1]

1. Actor clicks „Back‟ button 2. System returns to „FAQ details‟

page.

[Alternative 2] [Alternative 2]

1. Actor clicks „No‟ button 2. System returns to „FAQ details‟

page.



Exception n/a n/a









Project Team: 01 Prepared by: All members Page 52 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty









8.4.6.6. Publish FAQs

Author Huynh Khanh Thien Vu

Use Case Name Publish FAQ

Actors Administrator

Description Administrator want to Publish FAQ

Requirements n/a

Pre-conditions Logged in as administrator

Post-conditions Success: FAQ published to homepage

Fail: Refill information

Basic flow Actor Actions: System Responses:

1. Actor clicks on „Publish‟ checkbox 2. System show message: “Are you

[Alternative 1] sure you want to Publish this FAQ?”

3. Actor click on “Yes" button 4. System update selected account‟s

[Alternative 2] status into database, show message:

„FAQ status has been updated!‟ and

then redirects to „FAQ details‟ page.

Alternative Actor Actions: System Responses:

[Alternative 1]

1. Actor clicks „Back‟ button. 2. System returns to „FAQ details‟

page.

[Alternative 2] [Alternative 2]

1. Actor clicks „No‟ button 2. System returns to „FAQ details‟

page.



Exception n/a n/a









Project Team: 01 Prepared by: All members Page 53 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty









8.4.7. Manage comments









8.4.7.1. View list of comments

Author Huynh Khanh Thien Vu

Use case name View comments

Actors Administrator

Description View comments

Requirements n/a

Pre-conditions Logged into the System as Administrator

Post-conditions Success: View comments

Fail : connection error, redirect to Administrator homepage

Basic flow Actor actions: System response:

1. Actor clicks on to a „View comments‟ 2. System redirects to „Comment

button. management‟ page and display comment

information:



Project Team: 01 Prepared by: All members Page 54 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



 Event‟s title label

 Username label

 Content label

 Delete button

Alternative n/a n/a

Exception n/a n/a









8.4.7.2. Delete comments

Author Huynh Khanh Thien Vu

Use Case Name Delete comment

Actors Administrator

Description Administrator want to delete comment

Requirements n/a

Pre-conditions Logged in as administrator

Post-conditions Success: comment deleted

Fail: Refill information

Basic flow Actor Actions: System Responses:

1. In „Comments details‟ page, actor clicks on 2. System show message: „Do you

„Delete‟ button want to delete this comment?‟

[Alternative 1] [Add later]

3. Actor click „Yes‟ button 4. System deletes comment in

database, shows message: „Delete

comment successfully‟ and returns to

„Comments management‟ page

[Exception 1]



Alternative Actor Actions: System Responses:

[Alternative 1]

1. Actor clicks „Back‟ button. 2. System returns to „Comments

management‟ page.

[Alternative 1]

1. Actor clicks „No‟ button 2. System returns to „Comments

management‟ page.



Exception Actor Actions: System Responses:

[Exception 1] System displays message to Actor :

n/a n/a







Project Team: 01 Prepared by: All members Page 55 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty









8.4.8. Manage event type









8.4.8.1. View list of event type

Author Huynh Khanh Thien Vu

Use case name View list of event type

Actors Administrator

Description View list of event type

Requirements n/a

Pre-conditions Logged into the System as Administrator

Post-conditions Success: View list of event type

Fail : connection error, redirect to Admin home page

Basic flow Actor actions: System response:

1. From „Admin‟ page, actor clicks on to 2. System redirects to „event type



Project Team: 01 Prepared by: All members Page 56 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



„Manage event type‟ button. management‟ page and display list of

event type in table form:

 Name label

 Description label

 Update button

 Delete button

 Create button

Alternative n/a n/a

Exception n/a n/a









8.4.8.2. View event type details

Author Huynh Khanh Thien Vu

Use case name View event type details

Actors Administrator

Description View event type details

Requirements n/a

Pre-conditions Logged into the System as Administrator

Post-conditions Success: View event type details

Fail : connection error, redirect to Admin home page

Basic flow Actor actions: System response:

1. From „Event type management‟ page, 2. System redirects to „Event type details‟

actor clicks on to a „View details‟ button. page and display event type information:

 Name text field

 Description textarea

 Update button

 Delete button

 Back button

Alternative n/a n/a

Exception n/a n/a









Project Team: 01 Prepared by: All members Page 57 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty









8.4.8.3. Create event type

Author Huynh Khanh Thien Vu

Use Case Name Create event type

Actors Administrator

Description Administrator want to create event type

Requirements Administrator must provide event type information

Pre-conditions Logged in as administrator

Post-conditions Success: event type created

Fail: Refill information

Basic flow Actor Actions: System Responses:

1. Actor click on “Create new event type” 2. System redirect to “Create event

button. type” page. System display these

following control for user to input:

 Name text field

 Description textarea

 Create button

 Back button

3. User input information and click „Create‟ 4. System checks the information

button [Exception 1]

[Alternative 1] 5. System inserts event type into

database, show message: „Your event

type has been created!‟ and then

redirects to „event type management‟

page.

Alternative Actor Actions: System Responses:

[Alternative 1]

1. Actor clicks „Back‟ button. 2. System returns to „event type

management‟ page.

Exception Actor Actions: System Responses:

[Exception 1] System displays message to Actor :

1. Actor left Name blank 1. „Name cannot be blank‟

2. Actor input Name less than 5 or more 2. „Name‟s length must between 5

than 50 characters and 255 characters‟

3. Actor left Description blank 3. „Description cannot be blank‟

4. Actor input Description less than 5 or 4. „Description length must between 5

more than 2000 characters and 2000 characters‟









Project Team: 01 Prepared by: All members Page 58 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty









8.4.8.4. Update event type

Author Huynh Khanh Thien Vu

Use Case Name Update event type

Actors Administrator

Description Administrator want to edit event type‟s information

Requirements n/a

Pre-conditions Logged in as administrator

Post-conditions Success: event type updated

Fail: Refill information

Basic flow Actor Actions: System Responses:

2. Actor inputs information and clicks on to 1. In “event type details” page, system

Update button. display details , user can input

[Alternative 1] information in following control:

 Name text field

 Description textarea

 Update button

 Delete button

 Back button

3. System checks the information

[Exception 1]

5. System update selected event type

into database, show message: „Your

event type has been updated!‟ and

then redirects to „event type details‟

page.

Alternative Actor Actions: System Responses:

[Alternative 1]

1. Actor clicks „Back‟ button. 2. System returns to „event type

details‟ page.

Exception Actor Actions: System Responses:

[Exception 1] System displays message to Actor :

1. Actor left Name blank 1. „Name cannot be blank‟

2. Actor input Name less than 5 or more 2. „Name‟s length must between 5

than 50 characters and 255 characters‟

3. Actor left Description blank 3. „Description cannot be blank‟



Project Team: 01 Prepared by: All members Page 59 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



4. Actor input Description less than 5 or 4. „Description length must between 5

more than 2000 characters and 2000 characters‟









8.4.8.5. Delete event type

Author Huynh Khanh Thien Vu

Use Case Name Delete event type

Actors Administrator

Description Administrator want to delete event type

Requirements n/a

Pre-conditions Logged in as administrator

Post-conditions Success: event type deleted

Fail: Refill information

Basic flow Actor Actions: System Responses:

1. In „event type details‟ page, actor clicks on 2. System show message: „Do you

„Delete‟ button want to delete this event type?‟

[Alternative 1] 4. System deletes comment in

3. Actor click „Yes‟ button database, shows message: „Delete

event type successfully‟ and returns to

„event type management‟ page



Alternative Actor Actions: System Responses:

[Alternative 1]

1. Actor clicks „Back‟ button. 2. System returns to „event type

management‟ page.

[Alternative 1]

1. Actor clicks „No‟ button 2. System returns to „event type

management‟ page.

Exception n/a n/a









Project Team: 01 Prepared by: All members Page 60 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty









8.5. System

uc Primary Use Cases





System









Remind Birthday









Accept Register Ev ent

System Request









Publish Upcoming

Ev ent









Publish The Winners

of Ev ent









8.5.1. Remind Birthday

Author Ha Thi Minh Phuong

Use Case Name Remind Birthday

Actors System

Description System automatically reminds the birthday of users (employee) in that week when they

logged in.



Project Team: 01 Prepared by: All members Page 61 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



Requirements n/a

Pre-conditions n/a

Post-conditions Success: show User panel page with the greeting.

Fail: show User panel page.

Basic flow Actor Actions: System Responses:

1. System receives the request which checks 2. System compares the birthday‟s all

the logging of any employee. of employees to the days in that week.

3. System redirects to the User panel

page with list of employee‟s name

and the greeting.

Alternative flow n/a n/a

Exception n/a n/a









8.5.2. Accept Register Event Request

Author Ha Thi Minh Phuong

Use Case Name Accept Register Event Request

Actors System

Description System automatically accepts the request of employee which registers event.

Requirements n/a.

Pre-conditions n/a.

Post-conditions Success: the event‟s history of employee is returned.

Fail: system notifies the message to actor.

Basic flow Actor Actions: System Responses:

1. System receives the employee„s event 2. System selects from database and

register. checks the following information:

 The number of participants of

event is not full.

 The registration date of event is

not expired.

[Alternative 1]

4. System shows the event‟s history of

employee.

Alternative flow Actor Actions: System Responses:

[Alternative 1] System shows popup form with the

message to employee:

- The registration date of event is expired. - ”The registration date of event is

expired”

- The number of participant is full. ” The number of participant is full”.

Exception n/a n/a





Project Team: 01 Prepared by: All members Page 62 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty









8.5.3. Publish Upcoming Event

Author Ha Thi Minh Phuong

Use Case Name Publish Upcoming Event.

Actors System

Description System automatically publishes the upcoming events on the homepage.

Requirements Registration is three days later

Pre-conditions n/a

Post-conditions Success: the upcoming events are show on top of content homepage.

Fail: n/a.

Basic flow Actor Actions: System Responses:

1. System receives the request which requests 2. System selects from database and

the homepage of employee. checks the registration start date and

the end date of all events.

3. System shows the list events, each

of event has the following information

and controls:

 Event‟s title.

 Event‟s short description.

 „View detail‟ link.

And one of following controls is

displayed:

 „Register‟ button if actor has

not registered the event

before, the number of

participant is not full.

 „Cancel‟ button if actor has

registered the event before,

the registration date is not

expired.

Alternative flow n/a n/a

Exception n/a n/a









Project Team: 01 Prepared by: All members Page 63 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty









8.5.4. Publish The Winners of Event

Author Ha Thi Minh Phuong

Use Case Name Publish The Winner of Event

Actors System

Description System automatically publishes the winners of event on the homepage of employees.

System requests the User panel page or detail of events.

Requirements After event ended 3 days

Pre-conditions n/a.

Post-conditions Success: return list of winners.

Fail: n/a.

Basic flow Actor Actions: System Responses:

1. System receives the request which requests 2. System checks the end date of all

the homepage of employee. events.

3. System checks the events do have

the winners.

4. System return list of winners, each

of winner has following information:

 Title of event.

 Title of prize.

 Full name of winner.

 Department of winner.

Alternative flow n/a n/a

Exception n/a n/a









Project Team: 01 Prepared by: All members Page 64 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty









9. Entity Relationship Diagram (ERD)

9.1. Conceptual



has Prize

n









1

n n

Event





n

n Company

Information

has comment Register Propose









1

1

n 1

Type Event User has







n

n



FAQs









Project Team: 01 Prepared by: All members Page 65 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



9.2. Logical

Company

has Prize

n Information







1

n n

Event Propose







1

1





has has









n n 1

1

n 1 1

Type Event Comment Event User has

Register



n 1 n



has

FAQs





10. Entity-Attribute

10.1. FAQ



FAQ









FAQID DisplayOrder





Info Value





IsActive





10.2. Company Information



Company

Information









CompanyInfoID IsActive





Info DisplayOrder





Value









Project Team: 01 Prepared by: All members Page 66 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



10.3. User



Department Email



IsActive Address







Username Phone





User



Password Birthday









IsAdmin Gender



Fullname





10.4. Comment



Content









CommentID Comment CreatedOn









IsActive





10.5. Prize



ShortDescription Title









PrizeID Prize IsActive









FullDescription









Project Team: 01 Prepared by: All members Page 67 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



10.6. Event



StartDate IsActive





EndDate

IsProposedEvent







EventID Event EndRegDate







Title StartRegDate





ShortDescription NoOfparticipants



FullDescription





10.7. Event Type



Name









EventTypeID EventType Description









IsActive





10.8. Event Register



DoOn









EventRegisterID EventRegister StatusPrize









StatusRegister









Project Team: 01 Prepared by: All members Page 68 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty





11. TASKSHEET

Project Ref. No 1 Project Title Activity Plan Date of Preparation of Activity Plan

Sr. No Task Prepared By Start Date End Date Actual Days Member’s name Status

CRS document

Huynh Khanh

1 Introduction Blue Pumpkin 12/04/2010 12/06/2010 3 Tran The Nhan DONE

Thien Vu

Huynh Khanh

2 Existing Scenario Blue Pumpkin 12/04/2010 12/06/2010 3 Tran The Nhan DONE

Thien Vu

Customer Requirement Huynh Khanh

3 Blue Pumpkin 12/04/2010 12/06/2010 3 Ao Hoang Hung DONE

Specification Thien Vu

Huynh Khanh Thien

Functional Requirement Huynh Khanh

5 Blue Pumpkin 12/04/2010 12/06/2010 3 Vu & Ha Thi Minh DONE

Specification Thien Vu

Phuong

Huynh Khanh

5 System Requirements Blue Pumpkin 12/04/2010 12/06/2010 3 Ao Hoang Hung DONE

Thien Vu

Huynh Khanh

6 Development Software Blue Pumpkin 12/04/2010 12/06/2010 3 Ao Hoang Hung DONE

Thien Vu

Use Case and Sequence Diagrams

Huynh Khanh

7 View homepage Blue Pumpkin 12/07/2010 12/11/2010 5 Ao Hoang Hung DONE

Thien vu

Huynh Khanh

8 Login Blue Pumpkin 12/07/2010 12/11/2010 5 Ao Hoang Hung DONE

Thien vu

Huynh Khanh

9 Forgot password Blue Pumpkin 12/07/2010 12/11/2010 5 Ao Hoang Hung DONE

Thien vu

Huynh Khanh

10 Search Event Blue Pumpkin 12/07/2010 12/11/2010 5 Ao Hoang Hung DONE

Thien vu

Huynh Khanh

11 View details of event Blue Pumpkin 12/07/2010 12/11/2010 5 Ao Hoang Hung DONE

Thien vu

Huynh Khanh

12 Register event Blue Pumpkin 12/07/2010 12/11/2010 5 Ao Hoang Hung DONE

Thien vu

Huynh Khanh

13 Cancel event register Blue Pumpkin 12/07/2010 12/11/2010 5 Ha Thi Minh Phuong DONE

Thien vu

View Another Employee‟s

Huynh Khanh

14 Information Blue Pumpkin 12/07/2010 12/11/2010 5 Ha Thi Minh Phuong DONE

Thien vu

Huynh Khanh Huynh Khanh Thien

15 Propose new event Blue Pumpkin 12/07/2010 12/11/2010 5 DONE

Thien vu Vu

Huynh Khanh

16 View FAQs Blue Pumpkin 12/07/2010 12/11/2010 5 Ha Thi Minh Phuong DONE

Thien vu

Huynh Khanh

17 Support Blue Pumpkin 12/07/2010 12/11/2010 5 Ha Thi Minh Phuong DONE

Thien vu

Huynh Khanh

18 Manage profile Blue Pumpkin 12/07/2010 12/11/2010 5 Ha Thi Minh Phuong DONE

Thien vu

Huynh Khanh

19 View list of event Blue Pumpkin 12/07/2010 12/11/2010 5 Tran The Nhan DONE

Thien vu

Huynh Khanh

20 View event details Blue Pumpkin 12/07/2010 12/11/2010 5 Tran The Nhan DONE

Thien vu

Huynh Khanh

21 Create event Blue Pumpkin 12/07/2010 12/11/2010 5 Tran The Nhan DONE

Thien vu

Huynh Khanh

22 Update event Blue Pumpkin 12/07/2010 12/11/2010 5 Tran The Nhan DONE

Thien vu

Huynh Khanh

23 Cancel event Blue Pumpkin 12/07/2010 12/11/2010 5 Tran The Nhan DONE

Thien vu

Huynh Khanh

24 Create prize Blue Pumpkin 12/07/2010 12/11/2010 5 Tran The Nhan DONE

Thien vu

Huynh Khanh

25 Update winner Blue Pumpkin 12/07/2010 12/11/2010 5 Tran The Nhan DONE

Thien vu

Huynh Khanh Huynh Khanh Thien

26 View list of proposed event Blue Pumpkin 12/07/2010 12/11/2010 5 DONE

Thien vu Vu

Huynh Khanh Huynh Khanh Thien

27 View proposed event details Blue Pumpkin 12/07/2010 12/11/2010 5 DONE

Thien vu Vu

Huynh Khanh

28 View list of accounts Blue Pumpkin 12/07/2010 12/11/2010 5 Ha Thi Minh Phuong DONE

Thien vu

Huynh Khanh

29 View account details Blue Pumpkin 12/07/2010 12/11/2010 5 Ha Thi Minh Phuong DONE

Thien vu

Huynh Khanh

30 Set administrator Blue Pumpkin 12/07/2010 12/11/2010 5 Ha Thi Minh Phuong DONE

Thien vu

Huynh Khanh

31 Create account Blue Pumpkin 12/07/2010 12/11/2010 5 Ha Thi Minh Phuong DONE

Thien vu





Project Team: 01 Prepared by: All members Page 69 of 70

Project: My Sweet Home Document: Development Guide Approved by: Faculty



Huynh Khanh

32 Block/Unblock account Blue Pumpkin 12/07/2010 12/11/2010 5 Ha Thi Minh Phuong DONE

Thien vu

Huynh Khanh Huynh Khanh Thien

33 View company information Blue Pumpkin 12/07/2010 12/11/2010 5 DONE

Thien vu Vu

Huynh Khanh Huynh Khanh Thien

34 Create company information Blue Pumpkin 12/07/2010 12/11/2010 5 DONE

Thien vu Vu

Update company Huynh Khanh Huynh Khanh Thien

35 Blue Pumpkin 12/07/2010 12/11/2010 5 DONE

information Thien vu Vu

Huynh Khanh Huynh Khanh Thien

36 Delete company information Blue Pumpkin 12/07/2010 12/11/2010 5 DONE

Thien vu Vu

Huynh Khanh Huynh Khanh Thien

37 View list of FAQs Blue Pumpkin 12/07/2010 12/11/2010 5 DONE

Thien vu Vu

Huynh Khanh Huynh Khanh Thien

38 View FAQ details Blue Pumpkin 12/07/2010 12/11/2010 5 DONE

Thien vu Vu

Huynh Khanh Huynh Khanh Thien

39 Create FAQ Blue Pumpkin 12/07/2010 12/11/2010 5 DONE

Thien vu Vu

Huynh Khanh Huynh Khanh Thien

40 Update FAQ Blue Pumpkin 12/07/2010 12/11/2010 5 DONE

Thien vu Vu

Huynh Khanh Huynh Khanh Thien

41 Activate/inactivate FAQ Blue Pumpkin 12/07/2010 12/11/2010 5 DONE

Thien vu Vu

Huynh Khanh Huynh Khanh Thien

42 Publish FAQs Blue Pumpkin 12/07/2010 12/11/2010 5 DONE

Thien vu Vu

Huynh Khanh Huynh Khanh Thien

43 View list of comments Blue Pumpkin 12/07/2010 12/11/2010 5 DONE

Thien vu Vu

Huynh Khanh Huynh Khanh Thien

44 Delete comment Blue Pumpkin 12/07/2010 12/11/2010 5 DONE

Thien vu Vu

Huynh Khanh Huynh Khanh Thien

45 View list of event types Blue Pumpkin 12/07/2010 12/11/2010 5 DONE

Thien vu Vu

Huynh Khanh Huynh Khanh Thien

46 View event type details Blue Pumpkin 12/07/2010 12/11/2010 5 DONE

Thien vu Vu

Huynh Khanh Huynh Khanh Thien

47 Create event type Blue Pumpkin 12/07/2010 12/11/2010 5 DONE

Thien vu Vu

Huynh Khanh Huynh Khanh Thien

48 Update event type Blue Pumpkin 12/07/2010 12/11/2010 5 DONE

Thien vu Vu

Huynh Khanh Huynh Khanh Thien

49 Delete event type Blue Pumpkin 12/07/2010 12/11/2010 5 DONE

Thien vu Vu

Huynh Khanh

50 Remind birthday Blue Pumpkin 12/07/2010 12/11/2010 5 Ha Thi Minh Phuong DONE

Thien vu

Accept register event Huynh Khanh

51 Blue Pumpkin 12/07/2010 12/11/2010 5 Ha Thi Minh Phuong DONE

request Thien vu

Huynh Khanh

52 Publish upcoming event Blue Pumpkin 12/07/2010 12/11/2010 5 Ha Thi Minh Phuong DONE

Thien vu

Huynh Khanh

53 Publish winner of event Blue Pumpkin 12/07/2010 12/11/2010 5 Ha Thi Minh Phuong DONE

Thien vu

ERD

Huynh Khanh

54 Conceptual Blue Pumpkin 12/12/2010 12/13/2010 2 Ao Hoang Hung DONE

Thien Vu

Huynh Khanh

55 Logical Blue Pumpkin 12/12/2010 12/13/2010 2 Ao Hoang Hung DONE

Thien Vu

Huynh Khanh

56 Entity - Attribute Blue Pumpkin 12/12/2010 12/13/2010 2 Tran The Nhan DONE

Thien Vu

GUI

57 Designing GUI 12/14/2010 12/24/2010 10 All of team PENDING

Task sheet

Huynh Khanh Huynh Khanh Thien

58 Task sheet Blue Pumpkin 12/14/2010 12/14/2010 1 DONE

Thien Vu Vu









Project Team: 01 Prepared by: All members Page 70 of 70