Plan Till Are Quisi to s Traduci Da

8/13/2019 Plan Till Are Quisi to s Traduci Da

1/35

IS-1/00/2012 Project:

Online Social Shopping System Development

System Requirements

Specification

The purpose of this ocument is specifying the re!uirements that the

system shall meet" In orer to ma#e the unerstaning of the system easier$

apart from proviing the re!uirements themselves$ se!uence iagrams an

use case iagrams %accompanie &y a template 'hen consiere relevant(are also provie"

This ocument intens to esta&lish the functionality an &ehavior of the

application$ an also sets up the metrics that shall &e use 'hen evaluating

the !uality of the system" )ence$ using this ocument as a guieline uring

the esign phase of the system evelopment is a *must+ in orer to

guarantee the success of the project"

Document ID, S.S10Department, nalysis

Type, e!uirements

Privacy, O34ID.3TI5

Status, 4inal Document

ersion, 1"0

Date, 01/11/2012

uthors, Tsvetelina aryanova$ afael Perea$ 6orja P7re8$

lfonso e la ega

evisers, Tsvetelina aryanova$ afael Perea$ 6orja P7re8$

lfonso e la ega

Starting Project, 19/10/2012

Duration, : months


2/35

2

)3;. 5O;

ersion Date hange uthor

0"1 1/11/2012 TranslateTemplate

lfonso

0"2 :/11/2012 e

&i&liography

Tsvetelina

0": /11/2012 e thea&stract 6orja

0"> >/11/2012 evise the

ocument

6orja

0"? >/11/2012 e iagrams

an templates

Tsvetelina

0"9 >/11/2012 e use case

iagrams

e@planation

6orja

0"A >/11/2012 e the

appeni@

6orja


3/35

:

1. IntroductionThe aim of this ocument is to collect the re!uirements 'hich our final

soft'are system shall meet" It contains functional an non-functional

re!uirements$ a representation of the ata our 'e& service shall managean the operations that users shall &e a&le to o" It also escri&es some

restrictions an minimum !uality re!uirements that the system must fulfill"

2. RequirementsTo escri&e the re!uirements$ 'e have use the ne@t efinitions of roles,

Word Description

;uest Bnientifie user"

ustomer egistere system user %lso

Bser epresents a customer or a guest"

Provier sella&le provier

.mployee ny system employee

Traer n .mployee 'ith traer

Offer .mployee 'ith offer manager

ustomer .mployee 'ith customer service

System .mployee 'ith aministrator

Ce have also classifie the functional re!uirements accoring to the

follo'ing structure$ so it is easier to #eep trac# of the part of the system

affecte &y each re!uirement,

Id Description

1"@ System sales offers

2"@ .@ternal user functionalities, guests$ customers or proviers

:"@ Internal use, traers$ offer managers$ customer service employees$

system aministrators

The functional re!uirements that have &een etecte are containe in the

follo'ing ta&le,

Id Description

1"@ System sales offers

1"0

1

Sella&les shall &e inclue in offers"

1"0 Offers shall have a time limitation"


4/35

ustomers shall &e a&le to moify their personal information through

their personal area"

2"0

?

ustomers shall &e a&le to moify their su&scription through their

personal area"

2"0

9

ustomers shall &e a&le to sign on the premium service through their

personal area"

2"0

A

ustomers shall &e a&le to consult their accumulate e@pense in the

last month"

2"1

0

ustomers shall &e a&le to see their points through their personal

area"

2"1

1ustomers shall &e a&le to purchase coupons using points"

2"1

2ustomers shall &e a&le to use coupons on their purchases"

2"1

:ustomers shall &e a&le to participate in open offers"

2"1

Bsers shall &e a&le to ma#e sella&le searches"

2"1

?Bsers shall &e a&le to see the information a&out the offers"

2"1

9

Proviers shall &e a&le to &ro'se purchases orere to them"

2"1 Proviers shall &e a&le to complete orers 'hich have &een sent"


6/35

>

A

:"@ ompany employees use, traers$ offer managers$ customer

attenance employees$ system aministrators:"0

1

.mployees shall ientify in the system"

:"0

2Traers shall &e a&le to register proviers"

:"0

:Traers shall &e a&le to moify provier ata"

:"0

ustomers Service employees shall &e a&le to elete an ans'er to a

customer !uestion"


7/35

?

:"1

?System managers shall &e a&le to a ne' employees to the system"

:"1

9System managers shall &e a&le elete employees from the system"

:"1

ASystem managers shall &e a&le to grant permissions to employees"

:"2

0

System managers shall &e a&le to remove permissions from

employees"

:"2

1System managers shall &e a&le to loc# system users"

:"2

2System managers shall &e a&le to unloc# system users"

3. System Domain Model


8/35

9

Figure 1: System domain model

4. Use ases Model

In orer to ma#e the unerstaning of the use case iagrams easier$

the system has &een ivie into three separate parts$ one for user

management relate use cases$ another one for offer management

relate ones an a thir one for purchase management use cases"

These su&systems still have a consiera&le si8e$ so their use cases

have &een further su&ivie into several iagrams" .ach iagram is

follo'e &y the templates of the cases$ containe in the use case

iagram$ that 'ere consiere to have a comple@ity re!uiring this

#in of specification" The se!uence iagram for some use cases is

containe in an appeni@ at the en of this ocument" The general

use case iagram for the system is the follo'ing,

!eneral Use ases:


9/35

A

Figure 2: !eneral use cases

The actors that appear in the iagram match the roles previously efine

&ut for the *Bser+$ 'hich is just an a&straction use in the re!uirements that

covers any iniviual that accesses the system" n e@tra actor is ae in

the iagrams$ the Timer$ 'hich performs some tas#s perioically"

1. User Management Use ases "#art 1$:

This iagram contains the use cases of the tas# e@ternal users can perform

on the system,


10/35

10

Figure 3: User Management1

User log in

Template 1

ID 013ame Bser log in

Description The system shall &ehave as follo's in case a

user tries to log in"Primary Seconary ctors guest$ the system

Preconitions

ain 4lo' 1" The system re!uests the user to input

his username an pass'or

2" The user provies his user name an

pass'or

:" The information provie &y the user isverifie


11/35

11

Template 2

ID 02

3ame hange personal ata


user esires to moify his personal

information"Primary Seconary ctors customer$ the system

Preconitions

ain 4lo' 1" Inclue%ccess personal Eone(

2" The user chooses the ata that he

'ants change %pass'or$ shipping

information$ a/remove/change

payment methosF("

:" The user inputs the re!uire ata


12/35

12

ain 4lo' 1" The customer chooses to moify his

su&scription"

2" Inclue %ccess to Personal Eone("

:" The system sho's the current su&scription

of the user" This means that the system sho's

a list containing the categories that the user issu&scri&e to"

" The moification of the su&scription is

store"

Post-onitions The system upates the su&scription an the

customer 'ill receives accoringly from thismoment on"

lternative 4lo's - If there is an error uring the

moification process$ it is reporte$ the

ata remains an change an the

system returns to step 2"

2. User Management Use ases "#art 2$:

The purpose of this iagram is specifying the actions that can &e ta#en &y

internal users %employees(,

Figure 4: User Management2


13/35

1:

3. (&&er Management Use ases "#art 1$:

This iagram contains the use cases relate to offer access &y users an

offer pu&lication an visi&ility,

Figure ): (&&er Management1

Searc% o&&ers

Template

=" #urc%ase Management Use ases"#art 1$:

This use case specifies the actions irectly relate to the purchase of an

item$ 'hich are triggere &y the user" It also contains the roll&ac# of e@pire

&atch sales,

Figure ,: #urc%ase Management

#urc%ase Item

Template ?

ID 0?

3ame Purchase Item


customer tries to purchase an itemPrimary Seconary ctors ustomer

Preconitions The user is a registere customer

ain 4lo' 1" The customer chooses an offer

2" .@tensionPoint,Shipping Ta@es %

Shipping Ta@es(

:" .@tensionPoint, oupon%Bse e'ar(


17/35

1?

lternative 4lo's If the purchase is not complete %the

purchase is relate to a &atch offer

'hich has not reache its minimum of

sol units yet($ the purchase is flagge

*pening+" This means that the

purchase is recore in the system &utis not final until the conitions of the

&atch offer are met"

The customer may cancel the purchase

in any moment$ in 'hich case the

system must remain unaffecte"

Please refer to the se!uence iagram num&er 1 on the anne@ at the en of

this ocument for more information on this use case"

Use Re-ard

Template 9

ID 09

3ame Bse e'ar


customer 'ants to use one of his re'ar

coupons in a purchasePrimary Seconary ctors ustomer

Preconitions

ain 4lo' 1" The customer ecies to use a re'ar

coupon

2" The system sho's the re'ar coupons

that the customer o'ns

:" The user chooses a re'ar coupon


18/35

19

lternative 4lo's If a iscount re'ar has alreay &een

use$ the system 'ill only sho' free

shipping coupons if the user tries to use

a secon re'ar

If a free shipping coupon has alreay

&een use in this purchase$ the system

'ill only sho' iscount coupons

The user may cancel the selection of a

re'ar" If so happens$ the use case

ens

Please refer to the se!uence iagram num&er 2 on the anne@ at the en of


omplete #urc%ase

Template A

ID 0A

3ame omplete Purchase


purchase is getting confirmePrimary Seconary ctors ustomer$ the system

Preconitions The offer is relate to the purchase

ain 4lo' 1" The customer is charge the price of

the item

2" The clientGs points are upate

:" The clientGs cumulate monthly

e@pense is increase

" Sen an email to the customer

containing the &ill of the purchase

?" The purchase is flagge as

*omplete+Post-onitions The purchase is omplete an charge an

&oth the customer an the provier are

reportelternative 4lo's If the payment cannot &e performe$

the purchase is cancelle

Please refer to the se!uence iagram num&er : on the anne@ at the en of


omplete atc% #urc%ase


19/35

1A

Template 10

ID 10

3ame omplete 6atch Purchase

Description The system shall &ehave as follo's in case

every pening purchase relate to an offer

has to get confirme" This happens 'hen the

minimum num&er of sol units for the offer is

reache"Primary Seconary ctors ustomer$ the system

Preconitions The offer relate to the purchase is a &atch

offer an its minimum num&er of units sol

has &een reacheain 4lo' 4or each purchase relate to the offer

containe in the purchase that triggers this

use case,

1" The customer is charge the price ofthe item

2" The clientGs points are upate

:" The clientGs cumulate monthly

e@pense is increase

" Sen an email to the customer

containing the &ill of the purchase?" The purchase is flagge as

*omplete+Post-onitions The pening purchases relate to the offer

are complete an charge an &oth the

customer an the provier are reportelternative 4lo's If the payment o a purchase cannot &e

performe$ the purchase is cancelle

Please refer to se!uence iagram num&er < on the anne@ at the en of this

ocument for more information on this use case"

!rant #remium Mem'ers%ip

Template 11

ID 113ame ;rant Premium em&ership


20/35

20


customer reaches the cumulate monthly

e@pense neee to &e re'are 'ith

premium mem&ership"Primary Seconary ctors ustomer$ the system

Preconitions The customer meets the re!uirements to &ere'are 'ith premium mem&ership

ain 4lo' 1" The mem&ership status is change to

premium

2" The en of the premium perio is

recore

:" The user is reporte via email a&out the

re'ar he has &een a'arePost-onitions The customer su&scription is set to premium

lternative 4lo's

Roll'ac/ atc% Sales

Template 12

ID 12

3ame oll&ac# 6atch Sales


the purchases relate to a &atch offer have to

&e cancelle" This happens 'hen the time

limit for a &atch offer is reache &ut the

minimum num&er of sol units is not"Primary Seconary ctors the system

Preconitions The time limit for a &atch offer is reache &ut

the minimum num&er of sol units is not"ain 4lo' 1" The purchases relate to the offer are

flagge as *cancelle+

2" The customer is given &ac# the

coupons he ha use in the purchase %if

any(

:" The customer is reporte on the

cancellation via emailPost-onitions .very purchase relate to the &atch offer

'hose time limit has e@pire is cancelle" The

customers recover their coupons %provie

they use any(lternative 4lo's

%oose #ayment Met%od


21/35

21

Template 1:

ID 1:

3ame hoose Payment etho


customer tries to choose his payment metho"

Primary Seconary ctors ustomer$ Premium ustomer$ the system

Preconitions The customer is logge in"

The customer has chosen an offer that he

'ants to purchase %or Premium mem&ership("ain 4lo' 1" The user chooses to introuce the

payment metho"

2" The system sho's the information of

the payment methos that 'ere recently use

&y the customer"

:" .@tension point, ne'PaymentType%

payment metho(


22/35

22

lternative 4lo's If the provie ata is not correct$ the

system re!uires the incorrect ata to

&e retype"


23/35

2:

>" #urc%ase Management Use ases"#art 2$:

This iagram contains the actions relate to customer/provier service after

the purchase has &een complete,

Figure 0: #urc%ase Management2

on&irm S%ipment

Template 1=

ID 1=

3ame onfirm Shipment


shipment nees to &e confirme"Primary Seconary ctors Provier$ the system

Preconitions 1" The provier is logge in"2" The shipment has ta#en place"


24/35

2

ID 1>

3ame 6ro'se Sales


'hen a customer 'ants to &ro'se his sales"Primary Seconary ctors Provier$ the system

Preconitions 1" The provier is logge in"

ain 4lo' 1" The provier 'ants to &ro'se his sales"

2" The system re!uests search criteria"

:" The provier su&mits the criteria"

" The system sho's the ata of the sale"

Post-onitions The ata of a sale is sho'n"

lternative 4lo's If no search criteria are provie$ the system

'ill sho' every sale relate to the provier"


25/35

2=

). onFunctional RequirementsCe have use ISO 2=010 stanar to classify the non-functional

re!uirements of our system" This stanar groups t'o previous

stanars, ISO A12>-1 y ISO A12>-


26/35

2>

FR1.2

.4

t least 9= of the users shall &e a&le to purchase items

in less than 10 minutes" %Opera&ility(

5o'

ID Description Importan

ce

FR1.2

.)

The system shall &e esigne so the esire information

is reache using five clic#s or less ?0 of the times"

%Opera&ility(

5o'

FR1.2

.*

The simplest language possi&le shall &e use$ so user is

familiar 'ith the system" %Bser interface aesthetics(

eium

FR1.2

.,

The interface shall &e esigne so the user is a&le to spot

important elements easily" %Bser interface aesthetics(

eium

FR1.2

.0

The contrast generate &y the colors composing the

interface shall &e pleasant to the human eye$ using colors

&elonging to the same range of colors" %Bser interface

aesthetics(

eium

FR1.2

.5

The interface shall &e organi8e so user errors are

minimi8e" %Bser interface aesthetics(

eium

FR1.2

.16

The interface shall use &ig &uttons that clearly efine

their functionality %Bser interface aesthetics(

eium

Relia'ility

FR1.3.1

The system availa&ility shall &e at least A0" )igh

FR1.3

.2

System &ac#ups shall &e perioically performe"% 4ault

tolerance(

)igh

FR1.3

.3

Bser ata shall &e valiate an errors shall &e reporte %

4ault tolerance(

eium

FR1.3

.4

The error messages presente &y the system shall &e

useful to ientify the origin of error" % 4ault tolerance(

eium

FR1.3.)

The system shall store a critical errors recor" % 4aulttolerance(

eium

FR1.3

.*

In case of soft'are failure$ the system shall &e restore

an &ac# online in less than 12 hours" %ecovera&ility(

eium

Security

FR1.4

.1

The system shall manage personal ata in o&servance to

the Organic 5a' 1=/1AAA on the Protection of Personal

Data" %onfientiality(

ery )igh


27/35

2?

FR1.4

.2

Chen a customer signs out$ all of his ata shall &e

elete from the ata&ase" %onfientiality(

eium

FR1.4

.3

Sensi&le ata shall &e encrypte" %Integrity( ery )igh

FR1.4

.4

egistere users shall only &e a&le to use moules

associate to their user #in" %Integrity(

ery )igh

FR1.4

.)

Data shall not &e transferre as plain te@t" %Integrity( eium


ce

FR1.4

.*

Bnauthori8e users shall not &e a&le to access the store

ata %ccounta&ility(

ery )igh

FR1.4

.,

Bser name an/or pass'or shall not &e e@change 'ith

the &ro'ser once the valiation has ta#en place"

%uthenticity(

)igh

Modi&ia'ility

FR1.)

.1

The 'e&site shall &e esigne in a 'ay that allo's easy

maintenance an gro'th" %oifia&ility(

)igh

FR1.).2

The ata&ase shall &e esigne in a 'ay that allo's easy

maintenance an gro'th" %oifia&ility(

)igh

#orta'ility

FR1.*

.1

System access shall &e possi&le using any evice 'ith an

internet connection"

)igh

FR1.*

.2

The system shall 'or# properly on any &ro'ser" )igh

FR1.*

.3

The system shall 'or# properly regarless of the

operating system"

)igh

uality in use

#orta'ility

FR2.1

.1

The actions that cannot &e unone shall re!uire a

confirmation %Trust("

)igh

FR2.1

.2

The user shall &e a&le to e@it unesire states cleanly

%Pleasure("

eium

Fle7i'ility


28/35

29


ce

FR2.2

.1

Tool&ars an menu options that ma#e the use of the

system easier shall &e provie"

5o'

FR2.2

.2

ccess to all of the system functionalities shall &e

possi&le from ifferent positions 'ithin the 'e&site"

5o'


29/35

2A

*. SummaryThis paper ma#es an accurate escription of our system &y using functional

re!uirements" It outlines the ata that shall &e manage &y the system

through a omain moel$ an specifies the actions that the users of theservice shall &e a&le to perform 'ith use case moels" This ocument also

points out the restrictions an !uality re!uirements 'hich the final soft'are

shall meet$ &y using the ISO 2=010 hierarchy of non-functional

re!uirements" 4or the reasons state a&ove$ the unerstaning of this

ocument an a evelopment in accorance to the re!uirements an

iagrams it contains$ are #ey factors in orer to o&tain a piece of soft'are

that offers the functionalities e@pecte &y the user an matches his !uality

e@pectancies"

,. 8or/ #lanning

Tas# In charge /

uthor

Done evie'ers 4i@e 3otes

Sales

functional

re!uirements

6orja Jes lfonso

.mployees

functional

re!uirements

Tsvetelina Jes 6orja$

lfonso

Jes 3e' tas#, Inclue

proviers on system"

System

managers

functional

re!uirements

afael Jes 6orja$

lfonso

Jes Incorporate to employees

re!uirements

ustomers

functional

re!uirements

lfonso Jes 6orja Jes

System

omain moel

lfonso Jes 6orja$

Tsvetelina

Jes

Bse case

moel,

Purchase

anagement

6orja Jes lfonso$

afael

Jes


30/35

:0

Bse case

moel, Offers

Bse

anagement

afael Jes lfonso$

Tsvetelina$

6orja

Jes

3on-functional

re!uirements

Tsvetelina Jes afael$6orja$

lfonso

Jes

4unctional

re!uirements

complete

revie'

lfonso Jes Tsvetelina Jes Inclue proviers on 1"@$

ne' changes neee on

omain moel%payment

types$ minimum time-

percentage on offers(

hanges on

omain moel

lfonso Jes Jes hanges on contract,

contract has several offersof sella&les$ not only

sella&les"

4unctional

re!uirements

translation

lfonso Jes 6orja Jes

3on functional

re!uirements

translation

6orja Jes lfonso$

Tsvetelina

Jes

Bse case

templates

6orja$

Tsvetelina

Jes lfonso$

afael$

6orja$

Tsvetelina

Jes

Se!uence

Diagrams

lfonso Jes 6orja$

Tsvetelina$

afael

Jes

Bse case

templates

translation

6orja Jes lfonso Jes

0. i'liograp%y

K1

L

ISO/I. 4DIS 2=010 %2010(" Systems and software engineering -

Systems and software Quality Requirements and Evaluation (SQuaRE) -

System and software quality models.

K2

L

Sommerville$ I" %200=(" Software engineering%?M ."(" ari, Pearson

eucation"


31/35

:1

K:

L

oral$ "$ oraga$ " " Piattini$ " %2010(" Calidad del producto y

proceso software" ari, -"


32/35

:2

5. +ppendi7: Sequence Diagrams

1. Sequence Diagram 1: #urc%ase Item

This iagram is referre &y use case template num&er ?"

Sequence Diagram 1


33/35

::

2. Sequence Diagram 2: Use Re-ard

This iagram is referre &y use case template num&er 9"

Sequence Diagram 2


34/35

:

Documents

Plan Till Are Quisi to s Traduci Da