Further Requirement Specification

8/3/2019 Further Requirement Specification

1/40

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

Software

FURTHER

REQUIREMENTS SPECIFICATION

Version 2 - 18/11/2011

Web Application

Travel Itinerary Planning System


2/40

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 Date

v6 Mr Adrian Ashley 12030388 18/11/2011Mr. Mohamed Hagras 21046615 18/11/2011

Mr. Akilu Rilwan Muhammad 20049705 18/11/2011

Mr. Zhao Jian 21040874 18/11/2011

Travel Itinerary Planning SystemProject Plan

CONTENTS

1.0 INTRODUCTION

2 | P a g e


3/40


WADAM

2012


1.1 OBJECTIVES Version 2 - 18/11/2011

1.2 Customer Interview Transcript

1.3 Transcript Notes Taken

1.4 Extracting the Nouns and verbs Summary

1.5 Extracting the Nouns and verbs Table

2.0 FUNCTIONAL REQUIREMENTS Version 2 - 18/11/2011

3.0 USE CASE DIAGRAM Version 2 - 18/11/2011

4.0 USE CASE DESCRIPTION Version 2 - 18/11/2011

5.0 RISK MONITORING

5.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 RM 01 - Nouns Verbs Definitions

1.0 INTRODUCTION

Customers contact details

Mr Dharam Shadija, Mr Steve Lofthouse

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

We have had another brilliant innovation which will help people organise their

3 | P a g e


4/40


WADAM

2012

Travel Itinerary Planning Systemtravel itineraries online. This will allow users to share information about theirtravel 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 member s 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 - 18/11/2011

To develop the software specification requirements of the new system.

Deliverables:

Following an interview the client the following

Use case diagrams version 2

Use case descriptions version 2

Deliver date : Monday 21/11/2011 - estimate 18/11/2011

1.2 Customer Interview Transcript

Client Interview to update the requirements

specification

Objective - the interview of the client interview was observes in order to

extract the verbs and noun from eth interview and therefore establish the

new software requirements of the new system:-_

Interview with client (client)

Interview with clie n t

4 | P a g e
https://shuspace.shu.ac.uk/webapps/portal/frameset.jsp?tab_tab_group_id=null&url=/webapps/blackboard/execute/courseMain?course_id=_234849_1https://shuspace.shu.ac.uk/webapps/portal/frameset.jsp?tab_tab_group_id=null&url=/webapps/blackboard/execute/courseMain?course_id=_234849_1


5/40


WADAM

2012


1.3 Transcript Notes Taken

Like any web site these days require the user to registration, because we want to

capture data that validates users, we can log what data they look at, how

they use our site and we want to them to login to the account and have a

personalised experience.

We would like the user to be able to add their trip information, flight,

accommodation and other means of transport, train journeys so they can

have the integrated information in one place to access.

Advanced functionality extending what we are currently doing you can add a

flight item, train item hotel or accommodation.

It could be good to if our users could add car rental, cruises, meetings,

restaurants, or any type of activity that they wish, that will an accompaniment

to that functionality .

Extending the item functionality for example, these notes could be public or

private - like a review if public people viewing the site can view your tips

Google map showing the locations, in relation to your accommodation location

Take notes capture unstructured information about your trip

For example add a booking for a restaurant that your friend, has recommended

also add a notes to at booking - eg, they recommended a particular dish

Extending the login and registration functionality, upload data, drag and drop

If the user can invite a friend or a guest to be able to access that account for the

purpose ofsharing the trip information or if you are planning that trip together,

your friend or guest can login with their own credentials and they can see the

shared information

Once you have planned this you can click a button and an email will be sent toyou friends or guest who then opens the email and clicks on a link, the friend will

be able to register and create a login account

Create a role based account, for example a travel agent can manage the

travel itinerary , the travel agent can login to an account and plan all the travel

activities, original account holder can still view and edit their itinerary

1.4 Transcript Extracted Nouns and Verbs Summary

Some verbs assumptions have been made for example assuming the invested

friend/gust can delete itinerary items

5 | P a g e

type of accommodation ITEM

locations GPS of

accommodation

used on Google maps

-------------------------- NOUNS

Hostel, Hotel, Villa

----------------------< common >date time from

date time until

----------------------< common

VERBS>

make accommodation

bookin

type of transport ITEM

locations GPS of transports

used on Google maps

---------------------------- NOUNS

taxi, train, flight

---------------------------< common

>

departure from locations GPS

departure time datearrival to location GPS

arrival time date

----------------------< common

VERBS>

make a transport booking

edit a transport booking


6/40


WADAM

2012


6 | P a g e

add type of activity ITEM

locations GPS of activity

used on Google maps

------------------------ NOUN

bicycle rental ,car rental,cruises, meetings,

restaurants,

any

-------------------< common >

date time from

date time until

----------------------< VERB >

ADD NOTES TO BOOKING

make notes public or private

edit notesdelete notes

----------------------< common

VERBS>

make an activity event

booking

edit an activity event booking

LOGIN < extended

functionality >

-----------------< VERBS>

invites a friend / guest

remove friend / guest

send email invite

------------------< NOUN>

Friend / Guest

--------------

register implies creating a

login

view shared information

make itinerary

edit itinerary

delete itinerary=================

========

travel agent

--------------

make itinerary

edit itinerar


7/40


WADAM

2012


1.5 Extracting the Nouns and verbs Table

To comply with risk management monitoring requirements according to the project

plan it has been determined that there is a risk of misunderstandings or

misinterpretation of any objective.

In this case the objective is update to the new software requirements fromthe recent client interview, to reduce this risk of misunderstanding the

exact definition of nouns and verbs has been defined in reference to this

present project and to satisfy the risk analysis and risk management

requirements. Please see, APPENDIX E Risk Management RM 01 -

Nouns Verbs Definitions.

Validate

Nouns Verbs ReviewDate

reviewed

taxi, make a transport booking 18/11/2011

train edit a transport booking

7 | P a g e


8/40


WADAM

2012

Travel Itinerary Planning Systemflight delete a transport booking

departure from locations

GPS

make accommodation

bookingHostel, Hotel, Villa edit accommodation booking

arrival to location GPS delete accommodation

bookingdate time from ADD NOTES TO BOOKING

date time until make notes public or private

bicycle rental ,car rental,

cruises, meetings,

restaurants, any

edit / delete notes

Friend / Guest make an activity eventbooking

Role travel agent edit an activity event booking

delete an activity event

bookinginvites a friend / guest

remove friend / guest

send email inviteregister implies creating a

login

view shared informationmake itinerary

edit itinerary

delete itinerary

Project review meeting 17/11/2011 and 18/11/2011

2.0 FUNCTIONAL REQUIREMENTS v2 9/11/2011

The following requirements were updated to v1 Date 9/11/2011.The new

functional requirements are as follows:

Travel Itinerary Planning System-Functional

Requirements

1. Register users into the system.

2. Login registered users into the system.

3. Log out registered users from the system.4. Create travel itinerary and make it private or share it with friends.

8 | P a g e


9/40


WADAM

2012

Travel Itinerary Planning System5. Add contents to the travel itinerary.

6. Edit travel itinerary contents.

7. Delete travel itinerary.

8. View friends itineraries.

9. Add friends.

10.Accept friend request.

11.Remove friends.

12.Send Recommendations and notes about traveling to friends.

13.Add Recommendations and notes about traveling from friends to an

itinerary make them public or private.

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

15.Accept friends invitation to share the ownership of an itinerary withhim.

16.Create a group with role based so everyone included inside the group

will have different privileges and make it private or public.

17.Invite members to a group.

18.Accept group invitation.

19.Set roles to the group members.

20.Edit a group.

21.Post a comment to a group's discussion board.

Travel Itinerary Planning System-Users of the system1. Registered user: itinerary owner.

2. Registered user: itinerary owners friend.

3. Registered user: Group: Admin.

4. Registered user: Group: Travel agent.

5. Registered user: Group: Member.

6. Un-Registered user.

Travel Itinerary Planning System-Assumptions Registered user: itinerary owner is the only one that can edit, delete

or create his itinerary.

Registered user: itinerary owner can make his itinerary private or he

can publish it for his friends to see it.

In order to share your own itinerary with your friends they should beregistered and added to your friend list.

Travel itinerary contents are plane tickets details, train tickets,coach ticket and hotel/hostel reservation.

Manage travel itinerary contents means edit or delete these

contents.

9 | P a g e


10/40


WADAM

2012

Travel Itinerary Planning System When you add a friend or more to an itinerary so it will be owned by

them too, the itinerary is saved in this friends itineraries and your

itineraries too so any change he or you make affects the sameitinerary.

Creating a group with role based so everyone included inside the

group will have different privileges that means this group will have

an admin and members.

An admin in the group can change the itineraries and delete (full

privileges), other members within the group have only the right to

see the itineraries and add comments.

Any user out of the group cant see what is inside of it if it is private. If a group is public every user can see it. An admin can edit the group by removing members or edit the

details inside or change the privacy (private or public). The group is same as any users account, in other words you can

create itineraries inside the group and it is viewed by all groupmembers.

The admin of the group can set roles to the member which will givethem more or less privileges.

The role travel agent gives the user in the group the privilege tocreate an itinerary, add itinerary contents, edit content and deleteitinerary.

Making a note private or public might be strange but after thinkingit's very good ,for example if my friend is giving me arecommendation about something personal and I dont want otherfriends to see that but I still want to keep this info inside of myitinerary to view it later .

Travel Itinerary Planning System- Use Case

1. Use Case Name: Register

Actor: Non-registered user

Use Case Description:

i) User selects Registerii) System prompts for user details

10 | P a g e


11/40


WADAM

2012

Travel Itinerary Planning Systemiii) User enters his details, checks approve on terms

and conditions and submits

iv) System store users details into the database

v) System displays account created successfully.

2. Use Case Name: Login

Actor: Registered user: itinerary owner


i) User select login

ii) System prompt for user account

iii) User supply login account

iv) System validate user accountv) System starts users session

vi) System display login success message

vii) User is login successfully

3. Use Case Name: Logout



i) User is login

ii) User select logout

iii) System prompt for logout confirmation

iv) User verify logout selection

v) System confirms user logout

vi) System display logout success

vii) User is logout successfully.

4. Use Case Name: Create travel itinerary.



i) User is login

ii) User selects create new Create travel itinerary

11 | P a g e


12/40


WADAM

2012

Travel Itinerary Planning Systemiii) User search for itinerary contents (flight, hotel

etc...).

iv) User selects the contents he likes from the search

results.

v) User selects publish to share it with his friends or

make it private.

vi) User submit content

vii) System updates user's travel itinerary.

5. Use Case Name: Add contents to the travel itinerary

Actor: Registered user: itinerary ownerUse Case Description:

i) User is login

ii) User selects the travel itinerary he wants to add

contents in.

iii) User puts the new contents into the fields of the

itinerary contents.

iv) User selects publish to share it with his friends or

make it private.

v) User submits.vi) System updates user's travel itinerary.

6. Use Case Name: Edit travel itinerary contents.



vii) User is login

viii) User selects the travel itinerary he wants to editits contents.

12 | P a g e


13/40


WADAM

2012

Travel Itinerary Planning Systemix) User selects the new contents he wants to edit.

x) User puts the new contents into the fields of the

itinerary contents.

xi) User selects publish to share it with his friends or

make it private.

xii) User submits.

xiii) System updates user's travel itinerary.

7. Use Case Name: Delete travel itinerary.



i) User is login

ii) User selects delete itinerary

iii) User selects the travel itinerary he wants to delete

iv) User submits.

v) System updates user's travel itineraries database.

8. Use Case Name: View Friends itineraries.

Actor: Registered user: itinerary owner's friend


i) User is login.

ii) User selects his friend from his friend's list.

iii) User selects the itinerary he wants to view from

his friend's itineraries list.iv) System views the selected itinerary.

9. Use Case Name: Add Friends.



i) User is login.ii) User selects find friends.

13 | P a g e


14/40


WADAM

2012

Travel Itinerary Planning Systemiii) User put his friend email.

iv) User select add friend.

v) System sends a friend request to your friend.

vi) If your friend accepts system adds your friend to

your friend list.

10. Use Case Name: Accept Friend.

Actor: Registered user: itinerary owners friend


i) User is login.ii) User selects friend requests.

iii) User selects his friend from the friend requests list.

iv) User selects accept.

v) System adds his friend into his friends list and him

into his friends friends list.

11. Use Case Name: Remove Friend.



i) User is login.

ii) Select friend from listiii) Select remove

iv) Remove friend from list and user from friends list

12. Use Case Name: Send Recommendations and notes about

traveling to friends.



i) User is login.

ii) Selects send notesiii) Selects friend from list

14 | P a g e


15/40


WADAM

2012

Travel Itinerary Planning Systemiv) Types the note he wants to sendv) Selects send

13. Use Case Name: Add Recommendations and notes about

traveling from friends to an itinerary make them public or private.



i) User is login.ii) Selects view friends notesiii) Selects add notes to an itinerary.iv) Selects the itinerary he wants to add the note to.v) Selects make the note public or privatevi) Submits.vii) System updates user's itinerary.

14. Use Case Name: Invite a friend or more to an itinerary

so it will be owned by them too.



i) User is login.

ii) Selects invite friends to itinerary.iii) Selects the itinerary he wants to invite his friends into.iv) Selects his friends from his friends list.v) Submits.vi) System sends an invitation to his friends.

15. Use Case Name: Accept friends invitation to share the

ownership of an itinerary with him.

Actor: Registered user: itinerary owner's friend


i) User is login.ii) Selects friends' invitations.iii) Selects the invitation he wants.iv) Selects accept.

v) System will add the itinerary into his itineraries.

15 | P a g e


16/40


WADAM

2012


16. Use Case Name: Create a group with role based soeveryone included inside the group will have different privileges and

make it private or public.

Actor: Registered user: Group Admin


i) User is login.ii) Selects Create Group.iii) Adds group details.iv) Submits.

v) System will create the group.

17. Use Case Name: Invite members to the group



i) User is login.ii) Selects the group from his groups list.iii) Selects add members to the group.iv) Selects members from his friends list.

v) Submits.vi) System sends an invitation to these members.

18. Use Case Name: Accept group invitation.Actor: Registered user: itinerary owner


i) User is login.ii) Selects friends' invitations.iii) Selects the invitation he wants.iv) Selects accept.v) System will add the user into the group.

16 | P a g e


17/40


WADAM

2012

Travel Itinerary Planning System19. Use Case Name: Set roles to the group members.



i) User is login.ii) Selects the group from the groups list.iii) Selects Set roles.iv) Selects a member from group members.v) Selects the role he wants to assign to this membervi) System updates this member's role.

20. Use Case Name: Edit a group.



i) User is login.ii) Selects the group from the groups list.iii) Selects edit group.iv) Edits the details he wants to change.v) Submits.

vi) System updates the group details.

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

board.

Actor: Registered user: Group member


i) User is login.ii) Selects the group from the groups list.iii) Selects post a comment.iv) Write the comment he wants.v) Submits.

vi) System updates the group discussion board.

17 | P a g e


18/40


WADAM

2012


3.0 USE CASE DIAGRAMS Version 2 - 18/11/2011

For clarity we have submitted the rational rose original file so that it be reviewed

please see Appendix C, for a larger diagram

18 | P a g e


19/40


WADAM

2012


Figure 1 Use Case by Rational Rose

4.0 USE CASE DESCRIPTIONS Version 2 - 18/11/2011

1. Use Case Description: Register

19 | P a g e


20/40


WADAM

2012


20 | P a g e

Use Case ID Register RG-01

Primary Actor Non-registered user

Brief Description User selects RegisterSystem prompts for user details

User enters details, checks approve on terms and

conditions and submits

System store users details into the database

System displays account created successfully.Preconditions User is not registered

post conditions User a new registered

Flow of events Actor Input System Response1 Select Register -2 - Prompt for user details

3 User enters details -4 - store users 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"


21/40


WADAM

2012


2. Use Case Description: Login

21 | P a g e

Use Case ID Login LIN-01

Primary Actor Registered user: itinerary owner

Brief Description User select loginSystem prompt for user account

User supply login account

System validate user account

System starts users session

System display login success message

User is login successfullyPreconditions User is not logged in

post 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 users session- Display login success message

Alternates Actor Input System Response3.1 Display message:

"invalid user account"3.2 Display message

"Please enter account login"


22/40


WADAM

2012


3. Use Case Description: Logout

i)ii)

4. Use Case Description: Create travel itinerary.

22 | P a g e

Use Case ID Logout LT-01


Brief Description User select logout

System prompt for logout confirmation

User verify logout selection

System confirms user logout

System display logout success

User is logout successfullyPreconditions User is logged into the system

post conditions User is logged out successfully

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


23/40


WADAM

2012


5. Use Case Description: Add travel itinerary content.

23 | P a g e

Use Case ID Create travel Itinerary CTI-01


Brief Description User selects create new travel itineraryUser 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 content

System updates user's travel itinerary.Preconditions User logged in

post conditions new travel itinerary

Flow of events Actor Input System Response1 Select create itinerary2 - Display the itinerary entry form

3 Select privacy levelshare with friends

or private

-

4 insert itinerary information

Flight, Hotels, Events

-

5 Select publish itinerary -6 - Confirm publish literary and

privacy level7 User Confirm details -8 Update the database9 Publish the itinerary

Alternates Actor Input System Response


24/40


WADAM

2012


6. Use Case Description: Edit travel itinerary contents.

7. Use Case Description: Delete travel itinerary.

24 | P a g e

Use Case ID ATIC-01


Brief 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 in

post conditions Updated user travel itinerary

Flow of events Actor Input System Response1 Selects the itinerary -

Selects the itinerary entry

2 Fill the itinerary contents'fields

-

3 Select update itinerary -4 - Confirm update itinerary entries5 User Confirm changes -6 - Update the database7 - Publish the itinerary


Use Case ID ETIC-01Primary Actor Registered user: itinerary owner

Brief 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.Preconditions User is logged in


Flow of events Actor Input System Response1 Selects the itinerary -

Selects the itinerary entry

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



25/40


WADAM

2012


8. Use Case Description: View friend's itinerary

9. Use Case Description: Add Friends

25 | P a g e

Use Case ID DTI-01


Brief Description User selects delete itineraryUser selects the travel itinerary the user wants to delete

System updates user's travel itineraries database.

Preconditions User is logged in


Flow of events Actor Input System Response1 Selects itinerary -2 Selects delete -3 - Confirm delete itinerary4 User Confirm changes -

5 - Update the database6 - Publish the itineraryAlternates Actor Input System Response

Use Case ID VFI-01

Primary Actor Registered user: itinerary owner's friend

Brief Description User selects his friend from his friend's list.

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

System views the selected itinerary.


post conditions

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

share

3 Selects itinerary from

itineraries list4 Load itinerary content for the user

to viewAlternates Actor Input System Response


26/40


WADAM

2012


10. Use Case Name: Accept Friend Request.

26 | P a g e

Use Case ID ADD-01


Brief 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 in

post conditions Updated friends

Flow of events Actor Input System Response1 Selects add friends -2 Enter friends email -3 - Search the database

4 add friend -5 - Sends friend request6 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.


27/40


WADAM

2012


11. Use Case Name: Remove Friend.



27 | P a g e

Use Case ID ACCEPT ACC-01


Brief 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 friends

friends list.Preconditions User is logged in

post conditions Updated friends list

Flow of events Actor Input System Response1 Selects friend requests -2 Selects friend from list -3 Select accept -

4 adds his friend into his friends listand him into his friends friends list

Alternates Actor Input System Response3.1 User doesn't accept the

friend request.

Use Case ID Remove Friend RF-01


Brief Description Select friend from list

Select removeRemove friend from list and user from friends list


post 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 friends listAlternates Actor Input System Response


28/40


WADAM

2012




28 | P a g e

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

SRF-01

Primary Actor Registered user: itinerary owner's friend

Brief Description Selects send notesSelects friend from listTypes the note he wants to sendSelects send


post conditions

Flow of events Actor Input System Response1 Selects send notes -2 Select friend from list -

3 Types the note he wants tosend

-

4 Selects sendSends the note to user's friend



29/40


WADAM

2012


14. Use Case Name: Invite a friend or more to an itinerary

so it will be owned by them too.

29 | P a g e

Use Case ID Add Recommendations and notes about traveling from

friends to an itinerary make them public or private.

ARN-01


Brief 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 private

Submits.Preconditions User is logged in

post conditions Updated itinerary contents.

Flow of events Actor Input System Response

1 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



30/40


WADAM

2012


15. Use Case Name: Accept friends invitation to share the

ownership of an itinerary with him.

30 | P a g e

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.


post 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



31/40


WADAM

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.

17. Use Case Name: Invite members to the group

31 | P a g e

Use Case ID Accept friends invitation to share the ownership

of an itinerary with him.

AFITS-01Primary Actor Registered user: itinerary owner's friend

Brief Description Selects friends' invitations.

Selects the invitation he wants.

Selects accept.


post 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.

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-01Primary Actor Registered user: Group Admin

Brief 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.



32/40


WADAM

2012


18. Use Case Name: Accept group invitation.

32 | P a g e

Use Case ID Invite members to the group.IMTTG-01Primary Actor Registered user: Group Admin

Brief Description Selects the group from his groups list.Selects add members to the group.

Selects members from his friends list.



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 hisfriends list.

-

4 Submits.Sends an invitation to these

members.Alternates Actor Input System Response


33/40


WADAM

2012


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

20. Use Case Name: Edit a group.

33 | P a g e

Use Case ID Accept group invitation.AGI-01Primary Actor Registered user: Group Member

Brief 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 ResponseReject.

Use Case ID Set roles to the group members.SRTTGM-01Primary Actor Registered user: Group Admin

Brief 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 memberPreconditions User is logged in


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 memberUpdates this member's role.



34/40


WADAM

2012


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

board.

5.0 RISK MANAGEMENT Version 2 - 18/11/2011

According to the project plan v17, the Risk management is in full operation for the project andadhered to. the present object is to submit a software specification,

34 | P a g e

Use Case ID Edit a group.EAG-01Primary Actor Registered user: Group Admin

Brief Description Selects the group from the groups list.Selects edit group.

Edits the details he wants to change.




groups list.

-

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

change.

-

4 Submits. -Updates the group details.


Use Case ID Post comments on group's discussion

board.PCOGD01Primary Actor Registered user: Group Member

Brief Description Selects the group from the groups list.

Selects post a comment.

Write the comment he wants.




groups list.

-

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

Updates the group details.Alternates Actor Input System Response


35/40


WADAM

2012


TABLE 3, Risk of Organisational Roles

Responsibility Risk Monitoring JournalUpdate

Mohamed Hagras

Mr Akilu Rilwan

Muhammad

Mr. Zhao Jian

Adrian Ashley

Project Manager Client Interview new

requirements

SPECIFICATION REQUIREMENTS

Responsibilities overall project

tasks sequence and activity

Providing staff needs

Team Meeting attendance

recording

18/11/11

Mohamed

Hagras

Mr Akilu Rilwan

Muhammad

Communications

Administrator

Client Interview new

requirements

Update Project requirements

Change management

18/11/11

Adrian Ashley

Mr. Zhao Jian

Documentations

& Backup

Administrator

Document standardsUML Maintenance

18/11/11

Mohamed

Hagras

Adrian Ashley

Staff Training

Administrator

Maintaining staff training for the

project

Risk monitoring,

Document control

18/11/11

5.1 Risk Verification and quality control

The clarification has reduced the risk to the project, the request and response is

listed below

[Tracking ID QC RM 02 - further Specifications Client Interview new

requirements]

Follow the feedback from the second submission functional requirements

Bibliography

35 | P a g e


36/40


WADAM

2012

Travel Itinerary Planning Systemclient, 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].

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].

Glossary

QC Quality Control

RM Risk Management

UML Unified Modelling Language

GPS Global Positing System

Further ReadingSoftware Specifications

Quality Assurance Plan

Configuration Management Plan

Risk Management Plan

Project Schedule

Project ResourcesRational Rose - For used case diagram

36 | P a g e


37/40


WADAM

2012


APPENDIX A Project Management

Ref3.The Spiral Model diagram from (Boehm 1987)

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

APPENDIX B QUALITY CONTROL

37 | P a g e

Hand in

assignmen


38/40


39/40


WADAM

2012


Figure 1 Use Case by Rational Rose ( Please see the attached See rational )

39 | P a g e


40/40


WADAM

2012


APPENDIX ERisk Management RM 01 - Nouns Verbs

DefinitionsRisk Management RM 01 - Nouns Verbs Definitions

As the project is monitored for project risks, it has been determined that

there is a risk of misunderstandings or misinterpretation of any objective.

In this case the objective is update to the new software requirements from

the recent client interview, to reduce this risk of misunderstanding the

exact definition of nouns and verbs has been defined in reference to this

present project and to satisfy the risk analysis and risk management

requirements.

Noun Definition (dictionary.reference.com)

Any member of a class of words that are formally distinguished in manylanguages, as in English, typically by the plural andpossessive endings and thatcan function as the main or only elements of subjects or objects, as cat, belief,writing, Ohio, darkness. nouns are often thought of as referring topersons,places, things, states, or qualities.

Verbs Definition (oxforddictionaries.com)

In grammar this word is used in two separate but linked ways:

1. It describes a particular word class in the same way that noun,preposition, and adjective do.

2. It describes a part of a clause in the same way that subject, object, andcomplement do. In this sense it is also sometimes called the verb phrase.

As a word class, verbs are used for three main purposes:

1. to express an action:She fledupstairs to the bathroom.

2. to express a state:She sleptnoiselessly.

3. to link the subject with its complement:She was alone.
http://dictionary.reference.com/browse/nounshttp://dictionary.reference.com/browse/nouns

Documents

Further Requirement Specification