model design

Sheffield Hallam University WEB APPLICATION DESIGN AND MODELLING (A-2011/2) WADAM

Software

CLASS DIAGRAMS

Version 1 DL 02/12/2011

Web Application

Travel Itinerary Planning System

WEB APPLICATION DESIGN AND MODELLING WADAM

2012


Hallam Internet Systems Ltd

Document Version Control System - Google web docs

Document Management Control - Google web docs

Version Document Authors Student ID Datev6 Mr Adrian Ashley 12030388 2/12/2011

Mr. Mohamed Hagras 21046615 2/12/2011

Mr. Akilu Rilwan Muhammad 20049705 2/12/2011

Mr. Zhao Jian 21040874 2/12/2011

2 | P a g e


2012


Travel Itinerary Planning System Project Plan

CONTENTS 1.0 INTRODUCTION

1.1 OBJECTIVES Version 2 - 03/12/2011

2.0 CLASS DIAGRAM

3.0 USE CASE DESCRIPTION & SEQUENCE DIAGRAM

4.0 RISK MONITORING

4.1 Risk Verification and quality control

Bibliography

Glossary

APPENDIX A - Project Management

APPENDIX B - QUALITY CONTROL

APPENDIX C - Extended Use case diagram

APPENDIX D - Risk Management Class diagram

APPENDIX E Google Map Investigation Map API

APPENDIX F Google Map Investigation Map API

3 | P a g e


2012


1.0 INTRODUCTION

Customers contact details Mr Dharam Shadija, Mr Steve Lofthouse

We at Innovative travel solutions are known for pioneering travel solutions for example the ability for people to be able to search for flights for any airline on a single website was first developed by us over 10 years ago.

We have had another brilliant innovation which will help people organise their travel itineraries online. This will allow users to share information about their travel with their loved ones and friends.

Users should be able to create their itinerary online using our website. They could add Flight details, train details and hotels information into their itinerary. This is private information and should be only accessible to that particular user. The system should allow users to create any number of itineraries. Our system should allow people visiting our site to become users on our site.

Hallam Internet Systems - Team members established 19/10/2011

Mr Adrian Ashley B.Sc (Hons) Student ID 12030388

Mr. Mohamed Hagras Student ID 21046615

Mr. Akilu Rilwan Muhammad Student ID 20049705

Mr. Zhao Jian Student ID 21040874

1.1 OBJECTIVES Version 2 - 2/12/2011To develop the class diagram of the new system.

Deliverables: CLASSS DIAGRAM

Deliver date : 2/12/2011

4 | P a g e


2012


2.0 CLASS DIAGRAM

For clarity we have submitted the rational rose original file so that it can be reviewed Please see Appendix C, for a larger diagram

5 | P a g e


2012


Figure 1 Class Diagram by Rational Rose (please see the attached file)

3.0 USE CASE DESCRIPTIONS & SEQUENCE DIAGRAM1. Use Case Description: Register

Use Case ID Register RG-01Primary Actor Non-registered userBrief Description User selects Register

System prompts for user detailsUser enters details, checks approve on terms and conditions and submitsSystem store user’s details into the databaseSystem displays account created successfully.

Preconditions User is not registeredpost conditions User a new registered

Flow of events Actor Input System Response1 Select Register -2 - Prompt for user details3 User enters details -4 - store user’s details into the database5 - Account created successfully.

Alternates Actor Input System Response4.1 If unable to create account4.2 Display warning message

"User already exists "4.3 Display message

"Please enter new details"

6 | P a g e


2012


2. Use Case Description: Login

3.

Use Case Description: Logout

7 | P a g e

Use Case ID Login LIN-01Primary Actor Registered user: itinerary ownerBrief Description User select login

System prompt for user accountUser supply login accountSystem validate user accountSystem starts user’s sessionSystem display login success messageUser is login successfully

Preconditions User is not logged inpost conditions User is logged in

Flow of events Actor Input System Response1 Select login -2 - Prompt for user account3 Enter login details

- Validate user account- Starts user’s session- Display login success message

Alternates Actor Input System Response3.1 Display message:

"invalid user account"3.2 Display message

"Please enter account login"


2012


i)ii)

8 | P a g e

Use Case ID Logout LT-01Primary Actor Registered user: itinerary ownerBrief Description User select logout

System prompt for logout confirmationUser verify logout selectionSystem confirms user logoutSystem display logout successUser is logout successfully

Preconditions User is logged into the systempost conditions User is logged out successfully

Flow of events Actor Input System Response1 Select logout -2 - Prompt for logout confirmation3 User Confirm4 - Logout user5 - Display logout success


2012


4. Use Case Description: Create travel itinerary.

Use Case ID Create travel Itinerary CTI-01Primary Actor Registered user: itinerary ownerBrief Description User selects create new travel itinerary

User search for itinerary contents (flight, hotel etc...).User selects the contents he likes from the search results.User selects publish to share it with his friends or make it private.User submit contentSystem updates user's travel itinerary.

Preconditions User logged inpost conditions new travel itinerary

Flow of events Actor Input System Response1 Select create itinerary2 - Display the itinerary entry form3 Select privacy level

share with friendsor private

-

4 insert itinerary contentFlight, Hotels, Events

-

5 in each content details6 Select publish itinerary -7 - Confirm publish literary and privacy level8 User Confirm details -9 Update the database10 Publish the itinerary

Alternates Actor Input System Response

9 | P a g e


2012


Create travel itinerary sequence diagram

10 | P a g e


2012


5. Use Case Description: Add travel itinerary content.Use Case ID ATIC-01Primary Actor Registered user: itinerary ownerBrief Description User selects the travel itinerary he wants to add contents to.

User puts the new contents into the fields of the itinerary contents.User selects publish to share it with his friends or make it private.User submits.

Preconditions User is logged inpost conditions Updated user travel itinerary

Flow of events Actor Input System Response1 Selects the itinerary -

Selects the itinerary entry2 Fill the itinerary contents' fields -3 Select update itinerary -4 - Confirm update itinerary entries5 User Confirm changes -6 - Update the database7 - Publish the itinerary


11 | P a g e


2012


6. Use Case Description: Edit travel itinerary contents.Use Case ID ETIC-01Primary Actor Registered user: itinerary ownerBrief Description User selects the travel itinerary he wants to manage.

User selects edit or delete his travel itinerary contents.User selects publish to share it with his friends or make it private.User submits.


Flow of events Actor Input System Response1 Selects the itinerary -

Selects the itinerary entry2 Select function edit or delete -3 Select update itinerary -4 - Confirm update itinerary entries5 User Confirm changes -6 - Update the database7 - Publish the itinerary


12 | P a g e


2012


7. Use Case Description: Delete travel itinerary.

Use Case ID DTI-01Primary Actor Registered user: itinerary ownerBrief Description User selects delete itinerary

User selects the travel itinerary the user wants to deleteSystem updates user's travel itineraries database.


Flow of events Actor Input System Response1 Selects itinerary -2 Selects delete -3 - Confirm delete itinerary4 User Confirm changes -5 - Delete itinerary6 - Publish update


13 | P a g e


2012


8. Use Case Description: View friend's itinerary

Use Case ID VFI-01Primary Actor Registered user: itinerary owner's friendBrief Description User selects his friend from his friend's list.

User selects the itinerary he wants to view from his friend's itineraries list.

System views the selected itinerary.

Preconditions User is logged inpost conditions

Flow of events Actor Input System Response1 Selects friend from friends list -2 Load friends available itineraries to

share3 Selects itinerary from itineraries

list4 Load itinerary content for the user to

viewAlternates Actor Input System Response

14 | P a g e


2012


9. Use Case Description: Add Friends

Use Case ID ADD-01Primary Actor Registered user: itinerary ownerBrief Description User selects find friends.

User enters his friend email.User select add friend.System sends a friend request to your friend.If your friend accepts system adds your friend to your friend list.

Preconditions User is logged inpost conditions Updated friends

Flow of events Actor Input System Response1 Selects add friends -2 Enter friends email -3 - Search the database4 add friend -5 - Sends friend request6 <friends Accepted > Add friend to users friend list

Alternates Actor Input System Response3.1 Display message

"Unable to find your friend"3.2 Redirect to the find friend page again.

15 | P a g e


2012


10. Use Case Name: Accept Friend Request.

Use Case ID ACCEPT ACC-01Primary Actor Registered user: itinerary ownerBrief Description User selects friend requests.

User selects his friend from the friend requests list.User selects accept.System adds his friend into his friends list and him into his friend’s friends list.

Preconditions User is logged inpost conditions Updated friends list

Flow of events Actor Input System Response1 Selects friend requests -2 Selects specific accept -3 Select accept -4 adds his friend into his friends list and

him into his friend’s friends listAlternates Actor Input System Response

3.1 User doesn't accept the friend request.

16 | P a g e


2012


11. Use Case Name: Remove Friend.

Use Case ID Remove Friend RF-01Primary Actor Registered user: itinerary ownerBrief Description Select friend from list

Select removeRemove friend from list and user from friend’s list

Preconditions User is logged inpost conditions Updated friends list

Flow of events Actor Input System Response1 Select friend from list -2 Select remove -3 Remove friend from list and user from

friend’s listAlternates Actor Input System Response

17 | P a g e


2012


12. Use Case Name: Send Recommendations and notes about traveling to friends.

Use Case ID Send Recommendations and notes about traveling to friends.

SRF-01

Primary Actor Registered user: itinerary owner's friendBrief Description Selects send notes

Selects friend from listTypes the note he wants to sendSelects send

Preconditions User is logged inpost conditions

Flow of events Actor Input System Response1 Selects send notes -2 Select friend from list -3 Types the note he wants to send -4 Selects send

Sends the note to user's friendAlternates Actor Input System Response

18 | P a g e


2012


13. Use Case Name: Add Recommendations and notes about traveling to friends.

Use Case ID Add Recommendations and notes about traveling from friends to an itinerary make them public or private. ARN-01

Primary Actor Registered user: itinerary ownerBrief Description Selects view friends notes

Selects add notes to an itinerary.Selects the itinerary he wants to add the note to.Selects make the note public or privateSubmits.

Preconditions User is logged inpost conditions Updated itinerary contents.

Flow of events Actor Input System Response1 Selects view friends notes -2 Selects add notes to an itinerary. -3 Selects the itinerary he wants to

add the note to.send

-

4 Selects make the note public or private

-

5 Submits -Updates user's itinerary


19 | P a g e


2012


14. Use Case Name: Invite a friend or more to an itinerary so it will be owned by them too.

Use Case ID Invite a friend or more to an itinerary so it will be owned by them too.IAFOM-01

Primary Actor Registered user: itinerary ownerBrief Description Selects invite friends to itinerary.

Selects the itinerary he wants to invite his friends into.Selects his friends from his friends list.Submits.

Preconditions User is logged inpost conditions Updated itinerary contents.

Flow of events Actor Input System Response1 Selects invite friends to itinerary. -2 Selects the itinerary he wants to

invite his friends into.-

3 Selects his friends from his friends list.

-

4 Submits. -Sends an invitation to a friend


20 | P a g e


2012


15. Use Case Name: Accept friend’s invitation to share the ownership of an itinerary with him.

Use Case ID Accept friend’s invitation to share the ownership of an itinerary with him.AFITS-01

Primary Actor Registered user: itinerary owner's friendBrief Description Selects friends' invitations.

Selects the invitation he wants.Selects accept.

Preconditions User is logged inpost conditions Updated user's itineraries list.

Flow of events Actor Input System Response1 Selects friends' invitations. -2 Selects the invitation he wants. -3 Selects accept. -

Add the itinerary into his itineraries.

Alternates Actor Input System ResponseReject the invitation.

21 | P a g e


2012


16. Use Case Name: Create a group with role based so everyone included inside the group will have different privileges and make it private or public.

Use Case ID Create a group with role based so everyone included inside the group will have different privileges and make it private or public.CAGWRB-01

Primary Actor Registered user: Group AdminBrief Description Selects Create Group.

Adds group details.Submits.


Flow of events Actor Input System Response1 Selects Create Group. -2 Adds group details. -3 Submits. -

Creates the group.


22 | P a g e


2012


17. Use Case Name: Invite members to the group

Use Case ID Invite members to the group.IMTTG-01Primary Actor Registered user: Group AdminBrief Description Selects the group from his groups list.

Selects add members to the group.Selects members from his friends list.Submits.


Flow of events Actor Input System Response1 Selects the group from his

groups list.-

2 Selects add members to the group.

-

3 Selects members from his friends list.

-

4 Submits.Sends an invitation to these members.


23 | P a g e


2012


18. Use Case Name: Accept group invitation.

Use Case ID Accept group invitation.AGI-01Primary Actor Registered user: Group MemberBrief Description Selects friends' invitations.

Selects the invitation he wants.Selects accept.


Flow of events Actor Input System Response1 Selects friends' invitations. -2 Selects the invitation he wants. -3 Selects accept. -

Add the user into the group.Alternates Actor Input System Response

Reject.

24 | P a g e


2012


19. Use Case Name: Set roles to the group members.

Use Case ID Set roles to the group members.SRTTGM-01Primary Actor Registered user: Group AdminBrief Description Selects the group from the groups list.

Selects Set roles.Selects a member from group members.Selects the role he wants to assign to this member


Flow of events Actor Input System Response1 Selects the group from the

groups list.-

2 Selects Set roles. -3 Selects a member from group

members.-

4 Selects the role he wants to assign to this member

Updates this member's role.Alternates Actor Input System Response

25 | P a g e


2012


20. Use Case Name: Edit a group.

Use Case ID Edit a group.EAG-01Primary Actor Registered user: Group AdminBrief Description Selects the group from the groups list.

Selects edit group.Edits the details he wants to change.Submits.



groups list.-

2 Selects edit group. -3 Edits the details he wants to

change.-

4 Submits. -Updates the group details.


26 | P a g e


2012


21. Use Case Name: Post comments on group's discussion board.

Use Case ID Post comments on group's discussion board.PCOGD01Primary Actor Registered user: Group MemberBrief Description Selects the group from the groups list.

Selects post a comment.Write the comment he wants.Submits.



groups list.-

2 Selects post a comment. -3 Write the comment he wants. -4 Submits. -

Updates the group details.Alternates Actor Input System Response

27 | P a g e


2012


4.0 RISK MANAGEMENT Version 2 - 2/12/2011

According to the project plan v17, the Risk management is in full operation for the project and adhered to. the present object is to submit a class diagram,

TABLE 3, Risk of Organisational Roles

Responsibility Risk Monitoring Journal Update

Mohamed HagrasMr Akilu Rilwan MuhammadMr. Zhao JianAdrian Ashley

Project Manager Class DiagramClient Interview new requirementsSPECIFICATION REQUIREMENTSResponsibilities overall project tasks sequence and activityProviding staff needsTeam Meeting attendance recording

2/12/11

Mohamed HagrasMr Akilu Rilwan Muhammad

Communications Administrator

Client Interview new requirementsUpdate Project requirementsChange management

2/12/11

Adrian AshleyMr. Zhao Jian

Documentations & Backup Administrator

Document standardsUML Maintenance

2/12/11

Mohamed HagrasAdrian Ashley

Staff Training Administrator

Maintaining staff training for the projectRisk monitoring,Document control

2/12/11

4.1 Risk Verification and quality control

28 | P a g e


2012


The clarification has reduced the risk to the project, the request and response is listed below [Tracking ID QC CLASS DIAGRAM - ]

Bibliographyclient, i. w., n.d. interview with client. [Online] Available at: https://rcpt.yousendit.com/1287167602/b0eedff4b4c44d4c7543982905cfe740[Accessed 17 11 2011].

dictionary.reference.com, n.d. http://dictionary.reference.com/browse/noun. [Online] Available at: http://dictionary.reference.com/browse/noun[Accessed 17 11 2011].

IEEE, 2011. mtibugs.com. [Online] Available at: http://mtibugs.com/Howsrs.php[Accessed 09 11 2011].

Manual, A. D. F. C., 2005. Application Development Framework Case Manual. [Online] Available at: http://download.oracle.com/docs/cd/B25016_08/doc/dl/web/B19163_01/adfcase_intro.htm[Accessed 20 10 2011].

Mr Dharam Shadija, M. S. L., 2011. Lectures Sheffield Hallam Univerity. [Online] Available at: https://shuspace.shu.ac.uk[Accessed 3 11 2011].

oxforddictionaries.com, n.d. http://oxforddictionaries.com/definition/verb. [Online] Available at: http://oxforddictionaries.com/definition/verb[Accessed 17 11 2011].

simon bennet , John skelton, ken lunn, 2001. UML. s.l.:schaum's outline series.

www.freedomscientific.com, 2011. FreedomScientific. [Online] Available at: http://www.freedomscientific.com/products/fs/jaws-product-page.asp[Accessed 20 10 2011].

29 | P a g e


2012


Glossary

QC Quality Control

RM Risk Management

UML Unified Modelling Language

GPS Global Positing System

Further Reading

Software Specifications

Quality Assurance Plan

Configuration Management Plan

Risk Management Plan

Project Schedule

Project Resources

Rational Rose - For used case diagram

30 | P a g e


2012


APPENDIX A Project Management

31 | P a g e


2012


Ref 3.The Spiral Model diagram from (Boehm 1987)

http://www.ics.uci.edu/~wscacchi/Papers/SE-Encyc/Process-Models-SE-Encyc.pdf

32 | P a g e


2012


APPENDIX B QUALITY CONTROL

33 | P a g e

Investigate Assignment

Develop a plan of action

Draft the main

discussion Meeting

RefineAssignment

Hand in assignment


2012


Figure 1 Class diagram by Rational Rose ( Please see the attached See rational )

34 | P a g e

APPENDIX C Extended Class diagram


2012


APPENDIX E Risk Management Class diagram

Risk Management RM 02 - Class Diagrams

As the project is monitored for project risks, it has been determined that there is a risk of misunderstandings or misinterpretation of any class implementation therefore sequence diagrams were developed .

APPENDIX F Google Map Investigation Map API

Test Google map for location to help develop the class diagram

35 | P a g e


2012


APPENDIX G Google Map Investigation Map API

Test Google map for location to help develop the class diagram

36 | P a g e


2012


37 | P a g e

model design

Documents