SlideShare ist ein Scribd-Unternehmen logo
1 von 61
Downloaden Sie, um offline zu lesen
Custom Closet
                                    Fashion Designer and E-Commerce
                                    Web Application




                                     Date :            8thDecember 2011

                                     Authors:



                                     Version:          4

                                     Status:           Draft

usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 1 of 61
Document Control


Contributors

Name/Position                       Organization                 Contact Details

Fabrizio Valerio Covone             DIT                          Fabrizio.covone@mydit.ie

Cara Murphy                         DIT                          Cara.murphy@mydit.ie

Christopher Conlan                  DIT                          Christopher.conlan@mydit.ie

Stephen Carberry                    DIT                          Stephen.carberry@mydit.ie

Shane Ellis                         DIT                          Shane.ellis@mydit.ie



Version History

Date                      Version                  Status                 Comments

05/12/2011                1                        Draft                  Use Cases of the first 4
                                                                          Functional Modules
                                                                          added.

06/12/2011                2                        Draft                  Document Recycled for
                                                                          Admin Profile new FM

07/12/11                  3                        Draft                  4 New Use Cases
                                                                          added.

08/12/11                  4                        Release Candidate      Added last 3 Use
                                                                          Cases.



Changes since last version

NA




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 2 of 61
Known Omissions

NA



Approvals

Date        Name                 Title                 Signature   Version




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 3 of 61
Reviewers Comments
No comments




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 4 of 61
Table of Contents

DOCUMENT CONTROL............................................................................................................................. 2

REVIEWERS COMMENTS ......................................................................................................................... 4

TABLE OF CONTENTS ............................................................................................................................... 5

1     INTRODUCTION .............................................................................................................................. 10
1.1     PURPOSE OF THE DOCUMENT ............................................................................................................. 10

1.2     INTENDED AUDIENCE ........................................................................................................................ 10

1.3     DEFINITIONS, ACRONYMS AND ABBREVIATIONS ...................................................................................... 11

2     USE CASES ...................................................................................................................................... 12
2.1     LIST .............................................................................................................................................. 12

2.2     UC0001 – CUSTOMER REGISTRATION .................................................................................................. 14

2.2.1      ACTORS .................................................................................................................................................. 14

2.2.2      BRIEF DESCRIPTION .................................................................................................................................. 14

2.2.3      TRIGGER EVENT ....................................................................................................................................... 15

2.2.4      BASIC FLOW ............................................................................................................................................ 15

2.2.5      CONSTRAINTS .......................................................................................................................................... 16

2.2.6      DATA MODEL AND METADATA REQUIREMENTS .............................................................................................. 16

2.3     UC0002 – FASHION DESIGNER REGISTRATION ....................................................................................... 18

2.3.1      ACTORS .................................................................................................................................................. 18

2.3.2      BRIEF DESCRIPTION .................................................................................................................................. 18

2.3.3      TRIGGER EVENT ....................................................................................................................................... 19

2.3.4      BASIC FLOW ............................................................................................................................................ 19

usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 5 of 61
2.3.5     CONSTRAINTS .......................................................................................................................................... 20

2.3.6     DATA MODEL AND METADATA REQUIREMENTS .............................................................................................. 20

2.4     UC0003 – REGISTERED CUSTOMER PROFILE .......................................................................................... 22

2.4.1     ACTORS .................................................................................................................................................. 22

2.4.2     BRIEF DESCRIPTION .................................................................................................................................. 22

2.4.3     PRE-CONDITIONS ..................................................................................................................................... 22

2.4.4     TRIGGER EVENT ....................................................................................................................................... 23

2.4.5     BASIC FLOW ............................................................................................................................................ 23

2.4.6     CONSTRAINTS .......................................................................................................................................... 24

2.4.7     DATA MODEL AND METADATA REQUIREMENTS .............................................................................................. 24

2.5     UC0004 – FASHION DESIGNER PROFILE ................................................................................................ 26

2.5.1     ACTORS .................................................................................................................................................. 26

2.5.2     BRIEF DESCRIPTION .................................................................................................................................. 26

2.5.3     PRE-CONDITIONS ..................................................................................................................................... 26

2.5.4     TRIGGER EVENT ....................................................................................................................................... 27

2.5.5     BASIC FLOW ............................................................................................................................................ 27

2.5.6     CONSTRAINTS .......................................................................................................................................... 28

2.5.7     DATA MODEL AND METADATA REQUIREMENTS .............................................................................................. 28

2.6     UC0005 – WEB ADMINISTRATOR PROFILE ............................................................................................ 30

2.6.1     ACTORS .................................................................................................................................................. 30

2.6.2     BRIEF DESCRIPTION .................................................................................................................................. 30

2.6.3     PRE-CONDITIONS ..................................................................................................................................... 30

2.6.4     TRIGGER EVENT ....................................................................................................................................... 31

2.6.5     BASIC FLOW ............................................................................................................................................ 31

usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 6 of 61
2.6.6     CONSTRAINTS .......................................................................................................................................... 32

2.6.7     DATA MODEL AND METADATA REQUIREMENTS .............................................................................................. 32

2.7     UC0006 – USER LOGIN .................................................................................................................... 33

2.7.1     ACTORS .................................................................................................................................................. 33

2.7.2     BRIEF DESCRIPTION .................................................................................................................................. 33

2.7.3     PRE-CONDITIONS ..................................................................................................................................... 33

2.7.4     TRIGGER EVENT ....................................................................................................................................... 34

2.7.5     BASIC FLOW ............................................................................................................................................ 34

2.7.6     CONSTRAINTS .......................................................................................................................................... 35

2.7.7     DATA MODEL AND METADATA REQUIREMENTS .............................................................................................. 35

2.8     UC0007 – PRODUCTS GALLERY .......................................................................................................... 36

2.8.1     ACTORS .................................................................................................................................................. 36

2.8.2     BRIEF DESCRIPTION .................................................................................................................................. 36

2.8.3     PRE-CONDITIONS ..................................................................................................................................... 36

2.8.4     TRIGGER EVENT ....................................................................................................................................... 37

2.8.5     BASIC FLOW ............................................................................................................................................ 37

2.8.6     DATA MODEL AND METADATA REQUIREMENTS .............................................................................................. 38

2.9     UC0008 – FASHION DESIGNER ENGAGEMENT ........................................................................................ 39

2.9.1     ACTORS .................................................................................................................................................. 39

2.9.2     BRIEF DESCRIPTION .................................................................................................................................. 39

2.9.3     PRE-CONDITIONS ..................................................................................................................................... 39

2.9.4     TRIGGER EVENT ....................................................................................................................................... 40

2.9.5     BASIC FLOW ............................................................................................................................................ 40

2.9.6     CONSTRAINTS .......................................................................................................................................... 41

usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 7 of 61
2.9.7    DATA MODEL AND METADATA REQUIREMENTS .............................................................................................. 41

2.10     UC0009 – CUSTOM PRODUCT REQUEST ............................................................................................. 42

2.10.1     ACTORS ................................................................................................................................................ 42

2.10.2     BRIEF DESCRIPTION ................................................................................................................................ 42

2.10.3     PRE-CONDITIONS ................................................................................................................................... 42

2.10.4     TRIGGER EVENT ..................................................................................................................................... 43

2.10.5     BASIC FLOW .......................................................................................................................................... 43

2.10.6     CONSTRAINTS ........................................................................................................................................ 44

2.11     UC0010 – SHOPPING CART ............................................................................................................. 45

2.11.1     ACTORS ................................................................................................................................................ 45

2.11.2     BRIEF DESCRIPTION ................................................................................................................................ 45

2.11.3     PRE-CONDITIONS ................................................................................................................................... 45

2.11.4     TRIGGER EVENT ..................................................................................................................................... 46

2.11.5     BASIC FLOW .......................................................................................................................................... 46

2.11.6     CONSTRAINTS ........................................................................................................................................ 47

2.12     UC0011 – PURCHASE PROCESS ........................................................................................................ 48

2.12.1     ACTORS ................................................................................................................................................ 48

2.12.2     BRIEF DESCRIPTION ................................................................................................................................ 48

2.12.3     PRE-CONDITIONS ................................................................................................................................... 48

2.12.4     TRIGGER EVENT ..................................................................................................................................... 49

2.12.5     BASIC FLOW .......................................................................................................................................... 49

2.12.6     DATA MODEL AND METADATA REQUIREMENTS............................................................................................ 50

2.13     UC0012 – REFUND PROCESS ........................................................................................................... 51

2.13.1     ACTORS ................................................................................................................................................ 51

usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 8 of 61
2.13.2       BRIEF DESCRIPTION ................................................................................................................................ 51

2.13.3       PRE-CONDITIONS ................................................................................................................................... 51

2.13.4       TRIGGER EVENT ..................................................................................................................................... 52

2.13.5       BASIC FLOW .......................................................................................................................................... 52

2.13.6       CONSTRAINTS ........................................................................................................................................ 53

3     APPENDIX ....................................................................................................................................... 54
3.1     NOTE ............................................................................................................................................ 54

3.2     WHAT IS A USE-CASE? ....................................................................................................................... 54

3.3     PROCEDURE FOR CREATING A USE-CASE ................................................................................................. 54

3.4     USE CASE STRUCTURE ........................................................................................................................ 58




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 9 of 61
1 Introduction
1.1   Purpose of the Document
This document addresses the use cases associated with the following functional modules:

Ref        Name

FM-0001    Customer Registration

FM-0002    FD Registration

FM-0003    RC Profile

FM-0004    FD Profile

FM-0005    Admin Profile

FM-0006    User Log In

FM-0007    Products Gallery

FM-0008    FD Engagement

FM-0009    Custom Product Request

FM-0010    Shopping Cart

FM-0011    Purchase Process

FM-0012    Refund Process




1.2   Intended Audience
This document is a business level document intended for all project members, the project stakeholders and
potential users of the system.



usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 10 of 61
1.3   Definitions, Acronyms and Abbreviations
UCD: User Centred Design

Requirements Specification: A document that describes the high level functional requirements of the
system to be developed.

RC: Registered Customer.

FD: Fashion Designer.

Admin: Custom Closet’s Administrator.




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 11 of 61
2 Use cases
2.1   List




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 12 of 61
Ref       Description


 UC-0001   This is the registration process of any user who wants to buy FD’s shown products and/or
           engage a FD for a customized product.

 UC-0002   This is the registration process that a Fashion Designer has to fulfil in order to set up his/her
           Personal Profile. During this process FDs have to apply to the monthly subscription.

 UC-0003   This functional module is the RCs’ personal profile where FDs can manage their purchased
           products and rate FDs.


 UC-0004   This functional module is the FDs’ personal showroom where FDs can exhibit their work and
           be contacted by RC.


 UC-0005   This functional module is the Admin’s personal console where he/she can approve refunds
           and ban RCs and FDs.

 UC-0006   This is the module where RCs and FDs log in in order to access their relative features.

 UC-0007   In this module all FD’s products are shown and can be purchased by RCs.

 UC-0008   This functionality module provides RCs to contact and engage FDs to order tailored attire.


 UC-0009   RCs can customize their purchase by choosing different products by many FDs and see how
           they will look like on a stylized Avatar.

 UC-0010   RCs can add to the shopping cart the products that they want to purchase.


 UC-0011   During this process RCs will pay the products they want to purchase. After they have
           received their purchased products, RCs and FDs have to rate each other.


 UC-0012   During this process RCs can ask for a refund, but only a Admin will decide to proceed further
           or to reject it.




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 13 of 61
2.2     UC0001 – Customer Registration


 Use case reference      UC0001

 Use case title          Customer Registration

 Author                  Fabrizio Valerio Covone

 Creation Date           05/12/2011

 Version                 1

 Last Modified by        Fabrizio Valerio Covone

 Date Modified           05/12/2011



2.2.1    Actors

         Customer type user
         Web Application



2.2.2    Brief Description

This is the registration process of any user who wants to buy FD’s shown products and/or engage a FD for a
customized product.




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 14 of 61
2.2.3   Trigger Event

Clicking on the Sign Up Button.

2.2.4   Basic Flow




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 15 of 61
2.2.5   Constraints



 Ref        Description


 0001       Terms & Conditions: A refund is granted to the client only in case of wrong size and damaged product delivery.


 0002       Terms & Conditions: Registered users whether they are Fashion Designer or Customers have to behave properly.


 0003       Terms & Conditions: If a registered user (RC and/or FD) is caught behaving in an inappropriate way (e.g.: usage of
            bad words in rating system, spamming, etc.) by and Admin. He/she will be banned for a period of time related to
            the gravity of his/her actions.




2.2.6   Data model and metadata requirements




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 16 of 61
Name                  Type             Mandatory   Restrictions          Description

 Name                  Text Field       Y                                 Customer’s Name

 Surname               Text Field       Y                                 Customer’s Surname

 Gender                Radio Button     N                                 Customer’s Gender

 Date of Birth         Date Field       Y           DD/mm/YYYY format     Customer’s Date of Birth

 Address               Text Field       Y                                 Customer’s Address

 Country               Drop Down list   Y                                 Customer’s Country

 State                 Drop Down list   N                                 Customer’s State (for US Residents)

 Phone Number          Text Field       Y                                 Customer’s Main Phone Number

 Secondary Phone No.   Text Field       N                                 Customer’s Secondary Phone Number

 Email                 Text Field       Y                                 Customer’s Email

 Password              Password Field   Y                                 Customer’s Password

 Credit Card Type      Radio Button     Y                                 Customer’s Credit Card Type

 Card Number           Text Field       Y                                 Customer’s Credit Card Number

 Expiration Date       Date Field       Y                                 Customer’s Credit Card Expiration Date

 CCV                   Text Field       Y           Maximum of 4 digits   Customer’s Credit Card Verification Number




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 17 of 61
2.3     UC0002 – Fashion Designer Registration


 Use case reference        UC0002

 Use case title            FD Registration

 Author                    Fabrizio Valerio Covone

 Creation Date             06/12/2011

 Version                   1

 Last Modified by          Fabrizio Valerio Covone

 Date Modified             06/12/2011



2.3.1    Actors

         FD type user
         Web Application



2.3.2    Brief Description

This is the registration process that a Fashion Designer has to fulfill in order to set up his/her Personal
Profile. During this process FDs have to apply to the monthly subscription.




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 18 of 61
2.3.3   Trigger Event

Clicking on the Join Us Button.

2.3.4   Basic Flow




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 19 of 61
2.3.5   Constraints



 Ref        Description


 0001       Terms & Conditions: A refund is granted to the client only in case of wrong size and damaged product delivery.


 0002       Terms & Conditions: Registered users whether they are Fashion Designer or Customers have to behave properly.


 0003       Terms & Conditions: If a registered user (RC and/or FD) is caught behaving in an inappropriate way (e.g.: usage of
            bad words in rating system, spamming, etc.) by and Admin. He/she will be banned for a period of time related to
            the gravity of his/her actions.


 0004       Terms & Conditions: Custom Closet will keep a small percentage of the revenues of each purchase.




2.3.6   Data model and metadata requirements




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 20 of 61
Name                  Type             Mandatory   Restrictions          Description

 Name                  Text Field       Y                                 FD’s Name

 Surname               Text Field       Y                                 FD’s Surname

 Gender                Radio Button     N                                 FD’s Gender

 Date of Birth         Date Field       Y           DD/mm/YYYY format     FD’s Date of Birth

 Address               Text Field       Y                                 FD’s Address

 Country               Drop Down list   Y                                 FD’s Country

 State                 Drop Down list   N                                 FD’s State (for US Residents)

 Phone Number          Text Field       Y                                 FD’s Main Phone Number

 Secondary Phone No.   Text Field       N                                 FD’s Secondary Phone Number

 Email                 Text Field       Y                                 FD’s Email

 Password              Password Field   Y                                 FD’s Password

 Credit Card Type      Radio Button     Y                                 FD’s Credit Card Type

 Card Number           Text Field       Y                                 FD’s Credit Card Number

 Expiration Date       Date Field       Y                                 FD’s Credit Card Expiration Date

 CCV                   Text Field       Y           Maximum of 4 digits   FD’s Credit Card Verification Number

 Subscription Type     Radio Button     Y                                 FD’s Subscription Type




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 21 of 61
2.4     UC0003 – Registered Customer Profile


 Use case reference        UC0003

 Use case title            Registered Customer Profile

 Author                    Fabrizio Valerio Covone

 Creation Date             06/12/2011

 Version                   1

 Last Modified by          Fabrizio Valerio Covone

 Date Modified             06/12/2011



2.4.1    Actors

         RC user
         Web Application



2.4.2    Brief Description

This functional module is the RCs’ personal profile where FDs can manage their purchased products and
rate FDs.

2.4.3    Pre-conditions

A Registered Customer can access to this feature only after the registration process.




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 22 of 61
2.4.4   Trigger Event

Clicking on the Profile Button/Link or redirected from Login page.

2.4.5   Basic Flow




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 23 of 61
2.4.6   Constraints



 Ref        Description


 0001       Terms & Conditions: A refund is granted to the client only in case of wrong size and damaged product delivery.


 0002       Terms & Conditions: Registered users whether they are Fashion Designer or Customers have to behave properly.


 0003       Terms & Conditions: If a registered user (RC and/or FD) is caught behaving in an inappropriate way (e.g.: usage of
            bad words in rating system, spamming, etc.) by and Admin. He/she will be banned for a period of time related to
            the gravity of his/her actions.




2.4.7   Data model and metadata requirements




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 24 of 61
Name                  Type             Mandatory   Restrictions          Description

 Name                  Text Field       Y                                 Customer’s Name

 Surname               Text Field       Y                                 Customer’s Surname

 Gender                Radio Button     N                                 Customer’s Gender

 Date of Birth         Date Field       Y           DD/mm/YYYY format     Customer’s Date of Birth

 Address               Text Field       Y                                 Customer’s Address

 Country               Drop Down list   Y                                 Customer’s Country

 State                 Drop Down list   N                                 Customer’s State (for US Residents)

 Phone Number          Text Field       Y                                 Customer’s Main Phone Number

 Secondary Phone No.   Text Field       N                                 Customer’s Secondary Phone Number

 Email                 Text Field       Y                                 Customer’s Email

 Password              Password Field   Y                                 Customer’s Password

 Credit Card Type      Radio Button     Y                                 Customer’s Credit Card Type

 Card Number           Text Field       Y                                 Customer’s Credit Card Number

 Expiration Date       Date Field       Y                                 Customer’s Credit Card Expiration Date

 CCV                   Text Field       Y           Maximum of 4 digits   Customer’s Credit Card Verification Number




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 25 of 61
2.5     UC0004 – Fashion DesignerProfile


 Use case reference        UC0004

 Use case title            Fashion Designer Profile

 Author                    Fabrizio Valerio Covone

 Creation Date             06/12/2011

 Version                   1

 Last Modified by          Fabrizio Valerio Covone

 Date Modified             06/12/2011



2.5.1    Actors

         FD user
         Web Application



2.5.2    Brief Description

This functional module is the FDs’ personal showroom where FDs can exhibit their work and be contacted
by RC.

2.5.3    Pre-conditions

A Fashion Designer can access to this feature only after the registration process.




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 26 of 61
2.5.4   Trigger Event

Clicking on the Profile Button/Link or redirected from Login page.

2.5.5   Basic Flow




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 27 of 61
2.5.6   Constraints



 Ref        Description


 0001       Terms & Conditions: A refund is granted to the client only in case of wrong size and damaged product delivery.


 0002       Terms & Conditions: Registered users whether they are Fashion Designer or Customers have to behave properly.


 0003       Terms & Conditions: If a registered user (RC and/or FD) is caught behaving in an inappropriate way (e.g.: usage of
            bad words in rating system, spamming, etc.) by and Admin. He/she will be banned for a period of time related to
            the gravity of his/her actions.


 0004       Terms & Conditions: Custom Closet will keep a small percentage of the revenues of each purchase.




2.5.7   Data model and metadata requirements




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 28 of 61
Name                  Type             Mandatory   Restrictions          Description

 Name                  Text Field       Y                                 FD’s Name

 Surname               Text Field       Y                                 FD’s Surname

 Gender                Radio Button     N                                 FD’s Gender

 Date of Birth         Date Field       Y           DD/mm/YYYY format     FD’s Date of Birth

 Address               Text Field       Y                                 FD’s Address

 Country               Drop Down list   Y                                 FD’s Country

 State                 Drop Down list   N                                 FD’s State (for US Residents)

 Phone Number          Text Field       Y                                 FD’s Main Phone Number

 Secondary Phone No.   Text Field       N                                 FD’s Secondary Phone Number

 Email                 Text Field       Y                                 FD’s Email

 Password              Password Field   Y                                 FD’s Password

 Credit Card Type      Radio Button     Y                                 FD’s Credit Card Type

 Card Number           Text Field       Y                                 FD’s Credit Card Number

 Expiration Date       Date Field       Y                                 FD’s Credit Card Expiration Date

 CCV                   Text Field       Y           Maximum of 4 digits   FD’s Credit Card Verification Number

 Subscription Type     Radio Button     Y                                 FD’s Subscription Type




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 29 of 61
2.6     UC0005 – Web AdministratorProfile


 Use case reference        UC0005

 Use case title            Web Administrator Profile

 Author                    Fabrizio Valerio Covone

 Creation Date             06/12/2011

 Version                   1

 Last Modified by          Fabrizio Valerio Covone

 Date Modified             06/12/2011



2.6.1    Actors

         Admin user
         Web Application



2.6.2    Brief Description

This functional module is the Admin’s personal console where he/she can approve refunds and ban RCs and
FDs.

2.6.3    Pre-conditions

Only a registered employee of Custom Closet can access to this feature.




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 30 of 61
2.6.4   Trigger Event

Clicking on the Profile Button/Link or redirected from Login page.

2.6.5   Basic Flow




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 31 of 61
2.6.6     Constraints



 Ref             Description


 0001            Terms & Conditions: A refund is granted to the client only in case of wrong size and damaged product delivery.


 0002            Terms & Conditions: Registered users whether they are Fashion Designer or Customers have to behave properly.


 0003            Terms & Conditions: If a registered user (RC and/or FD) is caught behaving in an inappropriate way (e.g.: usage of
                 bad words in rating system, spamming, etc.) by and Admin. He/she will be banned for a period of time related to
                 the gravity of his/her actions.




2.6.7     Data model and metadata requirements




 Name                      Type               Mandatory     Restrictions             Description

 Name                      Text Field         Y                                      Admin’s Name

 Surname                   Text Field         Y                                      Admin’s Surname

 Gender                    Radio Button       N                                      Admin’s Gender

 Date of Birth             Date Field         Y             DD/mm/YYYY format        Admin’s Date of Birth

 Password                  Password Field     Y                                      Admin’s Password




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 32 of 61
2.7     UC0006 – User Login


 Use case reference       UC0006

 Use case title           User Login

 Author                   Fabrizio Valerio Covone

 Creation Date            07/12/2011

 Version                  1

 Last Modified by         Fabrizio Valerio Covone

 Date Modified            07/12/2011



2.7.1    Actors

         Customer type user
         Fashion Designer user type
         Web Administrator user type
         Web Application



2.7.2    Brief Description

This is the module where RCs, FDs and Admins log in in order to access their relative features and profiles.

2.7.3    Pre-conditions

In order to complete the Log In process properly, a user has to be registeredto Custom Closet.




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 33 of 61
2.7.4   Trigger Event

Clicking on the Log In Button.

2.7.5   Basic Flow




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 34 of 61
2.7.6    Constraints



 Ref         Description


 0001        Terms & Conditions: A refund is granted to the client only in case of wrong size and damaged product delivery.


 0002        Terms & Conditions: Registered users whether they are Fashion Designer or Customers have to behave properly.


 0003        Terms & Conditions: If a registered user (RC and/or FD) is caught behaving in an inappropriate way (e.g.: usage of
             bad words in rating system, spamming, etc.) by and Admin. He/she will be banned for a period of time related to
             the gravity of his/her actions.




2.7.7    Data model and metadata requirements




 Name                  Type               Mandatory     Restrictions             Description

 Email                 Text Field         Y                                      User’s Email

 Password              Password Field     Y                                      User’s Password




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 35 of 61
2.8     UC0007 – Products Gallery


 Use case reference       UC0007

 Use case title           Products Gallery

 Author                   Fabrizio Valerio Covone

 Creation Date            07/12/2011

 Version                  1

 Last Modified by         Fabrizio Valerio Covone

 Date Modified            07/12/2011



2.8.1    Actors

         Guest user type
         Registered Customer user type
         Fashion Designer user type
         Web Application



2.8.2    Brief Description

In this module all FD’s products are shown and can be purchased by RCs.

2.8.3    Pre-conditions

In order to access to the features “Add to The Shopping Cart” and “Fit it on your Avatar” features a
customer has to be registered.




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 36 of 61
2.8.4   Trigger Event

Clicking on the Gallery Button.

2.8.5   Basic Flow




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 37 of 61
2.8.6     Data model and metadata requirements




 Name               Type             Mandatory   Restrictions   Description

 Name               Text Field       N                          Product’s Name

 FD Name            Text Field       N                          Product’s Fashion Designer Name

 Colour             Drop Down List   N                          Product’s Colour

 Price Range        Radio Button     N                          Product’s Price Range

 Type               Drop Down List   N                          Product’s Type of Clothing

 Fashion Season     Drop Down List   N                          Product’s Fashion Season




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 38 of 61
2.9     UC0008 – Fashion Designer Engagement


 Use case reference       UC0008

 Use case title           Fashion Designer Engagement

 Author                   Fabrizio Valerio Covone

 Creation Date            07/12/2011

 Version                  1

 Last Modified by         Fabrizio Valerio Covone

 Date Modified            07/12/2011



2.9.1    Actors

         Registered Customer user type
         Fashion Designer user type
         Web Application



2.9.2    Brief Description

This functionality module provides RCs to contact and engage FDs to order tailored attire.

2.9.3    Pre-conditions

In order to access to this feature a Customer has to be Registered, while a FD has to be Registered and
Active.




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 39 of 61
2.9.4   Trigger Event

RC point of view:

Clicking on the Ask for an Engagement in RC’s Profile.

FD Point of view:

Clicking on Manage Engagement in FD’s Profile.

2.9.5   Basic Flow




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 40 of 61
2.9.6   Constraints



 Ref         Description


 0001        Terms & Conditions: A refund is granted to the client only in case of wrong size and damaged product delivery.


 0002        Terms & Conditions: Registered users whether they are Fashion Designer or Customers have to behave properly.


 0003        Terms & Conditions: If a registered user (RC and/or FD) is caught behaving in an inappropriate way (e.g.: usage of
             bad words in rating system, spamming, etc.) by and Admin. He/she will be banned for a period of time related to
             the gravity of his/her actions.


 0004        Terms & Conditions: Custom Closet will keep a small percentage of the revenues of each purchase.




2.9.7   Data model and metadata requirements



See Chapters 2.4.7 and 2.5.7.




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 41 of 61
2.10 UC0009 – Custom Product Request


 Use case reference      UC0009

 Use case title          Custom Product Request

 Author                  Fabrizio Valerio Covone

 Creation Date           07/12/2011

 Version                 1

 Last Modified by        Fabrizio Valerio Covone

 Date Modified           07/12/2011



2.10.1 Actors

        Registered Customer user type
        Web Application



2.10.2 Brief Description

RCs can customize their purchase by choosing different products by many FDs and see how they will look
like on a stylized Avatar.

2.10.3 Pre-conditions

In order to access to this feature a Customer has to be Registered.




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 42 of 61
2.10.4 Trigger Event

Clicking on the Fit on Avatar.

2.10.5 Basic Flow




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 43 of 61
2.10.6 Constraints



 Ref       Description


 0001      Terms & Conditions: A refund is granted to the client only in case of wrong size and damaged product delivery.


 0002      Terms & Conditions: Registered users whether they are Fashion Designer or Customers have to behave properly.


 0003      Terms & Conditions: If a registered user (RC and/or FD) is caught behaving in an inappropriate way (e.g.: usage of
           bad words in rating system, spamming, etc.) by and Admin. He/she will be banned for a period of time related to
           the gravity of his/her actions.


 0004      Terms & Conditions: Custom Closet will keep a small percentage of the revenues of each purchase.




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 44 of 61
2.11 UC0010 – Shopping Cart


 Use case reference      UC0010

 Use case title          Shopping Cart

 Author                  Fabrizio Valerio Covone

 Creation Date           08/12/2011

 Version                 1

 Last Modified by        Fabrizio Valerio Covone

 Date Modified           08/12/2011



2.11.1 Actors

        Registered Customer type user
        Web Application



2.11.2 Brief Description

RCs can add to the shopping cart the products that they want to purchase.

2.11.3 Pre-conditions

In order to access this feature a user has to be registered to Custom Closet.




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 45 of 61
2.11.4 Trigger Event

Clicking on the Shopping Cart button.

2.11.5 Basic Flow




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 46 of 61
2.11.6 Constraints



 Ref       Description


 0001      Terms & Conditions: A refund is granted to the client only in case of wrong size and damaged product delivery.


 0002      Terms & Conditions: Registered users whether they are Fashion Designer or Customers have to behave properly.


 0003      Terms & Conditions: If a registered user (RC and/or FD) is caught behaving in an inappropriate way (e.g.: usage of
           bad words in rating system, spamming, etc.) by and Admin. He/she will be banned for a period of time related to
           the gravity of his/her actions.




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 47 of 61
2.12 UC0011 – Purchase Process


 Use case reference      UC0011

 Use case title          Purchase Process

 Author                  Fabrizio Valerio Covone

 Creation Date           08/12/2011

 Version                 1

 Last Modified by        Fabrizio Valerio Covone

 Date Modified           08/12/2011



2.12.1 Actors

        Registered Customer user type
        Fashion Designer user type
        Web Application



2.12.2 Brief Description

During this process RCs will pay the products they want to purchase. After they have received their
purchased products, RCs and FDs have to rate each other.

2.12.3 Pre-conditions

In order to access to this feature a Customer has to be registered and there should be at least one product
in his/her Shopping cart.




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 48 of 61
2.12.4 Trigger Event

Clicking on the Buy Now Button.

2.12.5 Basic Flow




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 49 of 61
2.12.6 Data model and metadata requirements




 Name                  Type             Mandatory   Restrictions          Description

 Name                  Text Field       Y                                 Customer’s Name

 Surname               Text Field       Y                                 Customer’s Surname

 Gender                Radio Button     N                                 Customer’s Gender

 Date of Birth         Date Field       Y           DD/mm/YYYY format     Customer’s Date of Birth

 Address               Text Field       Y                                 Customer’s Address

 Country               Drop Down list   Y                                 Customer’s Country

 State                 Drop Down list   N                                 Customer’s State (for US Residents)

 Phone Number          Text Field       Y                                 Customer’s Main Phone Number

 Secondary Phone No.   Text Field       N                                 Customer’s Secondary Phone Number

 Email                 Text Field       Y                                 Customer’s Email

 Password              Password Field   Y                                 Customer’s Password

 Credit Card Type      Radio Button     Y                                 Customer’s Credit Card Type

 Card Number           Text Field       Y                                 Customer’s Credit Card Number

 Expiration Date       Date Field       Y                                 Customer’s Credit Card Expiration Date

 CCV                   Text Field       Y           Maximum of 4 digits   Customer’s Credit Card Verification Number




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 50 of 61
2.13 UC0012 – Refund Process


 Use case reference       UC0012

 Use case title           Refund Process

 Author                   Fabrizio Valerio Covone

 Creation Date            08/12/2011

 Version                  1

 Last Modified by         Fabrizio Valerio Covone

 Date Modified            08/12/2011



2.13.1 Actors

        Registered Customer user type
        Fashion Designer user type
        Web Application



2.13.2 Brief Description

During this process RCs can ask for a refund, but only a Admin will decide to proceed further or to reject it.

2.13.3 Pre-conditions

In order to access to this feature a Customer has to have purchased at least one product.




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 51 of 61
2.13.4 Trigger Event

Clicking on the Ask for a Refund.

2.13.5 Basic Flow




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 52 of 61
2.13.6 Constraints



 Ref       Description


 0001      Terms & Conditions: A refund is granted to the client only in case of wrong size and damaged product delivery.


 0002      Terms & Conditions: Registered users whether they are Fashion Designer or Customers have to behave properly.


 0003      Terms & Conditions: If a registered user (RC and/or FD) is caught behaving in an inappropriate way (e.g.: usage of
           bad words in rating system, spamming, etc.) by and Admin. He/she will be banned for a period of time related to
           the gravity of his/her actions.


 0004      Terms & Conditions: Custom Closet will keep a small percentage of the revenues of each purchase.




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 53 of 61
3 Appendix
3.1   Note
This appendix would not be in every use case. An appendix in a use case contains additional information
and artifact examples that might be use full in describing or understanding the usage scenario.


3.2   What is a use-case?
Use-cases are an unfolding story that describes the functions in a system and the usage paths through
them. They are essentially narrative descriptions with diagrams and example screens. Their purpose is to
describe in the simplest possible terms how the proposed system would be used.

Use-cases document the accomplishment of a single task by the user.

The use cases illustrate the functionality of the system in terms of the business processes the system is
being built to support. Use cases describe how it is envisioned users of the system (actors) would perform
tasks such as login, change settings, and enter a particular type of data.


3.3   Procedure for creating a use-case
The diagram below illustrates the process by which each use case is created. Basically it is an iterative
process where the business function required is considered from a number of different perspectives which
can be summarized as : CRUD-SPARP.

For example in a use case area like add a moodle site to the site list the analyst asks themselves how will I :

        Create a Site                                                                       (Create)

        Review site details e.g. URL, Username – are there different views                  (Review)

        Correct site details                                                                (Update)

        Delete or Retire a site from use                                                    (Delete)

        Search for a site on the site list                                                  (Search)

        Print a sites details, a list of sites – are there different print styles           (Print)

        Archive or backup the site list e.g. send to dropbox                                (Archive)

usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 54 of 61
Generate a report on all sites e.g. how frequently are they accessed             (Report)

      Publish  Export  Import e.g. send the list to twitter, facebook or a website   (Publish)

      All of the above are self contained functionality within a module. But what are the reporting
      requirements of this module in relation to other modules in the system – are there lookup to other
      modules, what cross system reports are executed within this module or involve this module
      (Report across system)




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 55 of 61
usecasenamecustomclosetv4-111211101506-phpapp01.docx   Page 56 of 61
usecasenamecustomclosetv4-111211101506-phpapp01.docx   Page 57 of 61
3.4   Use case structure
Each use case has the following narrative structure:




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 58 of 61
Ref    Heading                       Description


       Actors                        Who performs the process described in the use case


       Brief Description             A description of the use case being specified with an overview diagram of the
                                     process.

                                     What is the goal of this use case, what is the objective of the user.


       User Interface                A wire frame diagram of the main screens and dialogs presented to the user as
                                     they execute the use case. This is only used where appropriate. Its purpose is to
                                     provide a visual aid to the reader as to the functionality available.

                                     The user interface in this case is used to help explain the proposed functionality.
                                     As user experience designers get involved the UI may change and even use cases
                                     may disappear.

                                     Including a mock up user interface can however drive out issues as to what data
                                     needs to be displayed and if data is to be entered how it is validated. This
                                     information then helps the design of the data model.


       User Interface description    A description of the user interface components and their functions


       Trigger Event                 What event or action triggers this use case


       Flow of Events


       - Basic Flow                  A description of the main process where each step is referenced by a number. A
                                     flow, state or sequence diagram may also be added to explain the process.


       - Alternative Flow            The basic flow describes how the process would be executed in 90% of the cases
                                     i.e. where no error has occurred or where no business rule exceptions occur.

                                     The alternate flows concern the business logic applied to a basic flow. For
                                     instance the basic flow could be for to enter a URL, username and password.
                                     Access to the moodle site is checked and the site is added.

                                     Alternative flows may describe situations where there is an error in the input
                                     data, the site cannot be reached etc.


       Non-functional Requirements   This section only contains content if it is specific to that particular use case not
                                     the system as a whole.


       - Usability                   A particular usability requirement. For instance command line functionality
                                     required, quick key, must be able to select all and deselect a list, or deselect all
                                     and select a list etc.


       - Reliability                 A particular reliability requirement. For instance no site should be stored unless
                                     connection to the site has been established at least once.


       - Performance                 Minimum performance requirements. For instance the system should respond
                                     report an issue with uploading within 10 seconds and ask if the user wants to


usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 59 of 61
continue or wait until they have a WiFi connection.


       - Supportability          What support/debug features need to be provided for this process.


       Artefacts                 What is created, updated or deleted as a result of this business process


       Pre-conditions            This section outlines the Pre-conditions prior to the execution of the basic flow.
                                 For instance there must be at least one valid site in the site list before the main
                                 functionality of the moodle app can be accessed.

                                 Assumptions may also be expressed here




Ref    Heading                   Description


       Post-Conditions           How must the system or user interface be left after the execution of the basic
                                 flow.


       Authorization and Audit   What roles are allowed access this functionality. Are there any confidentiality,
       Requirements              auditor logging requirements.


       Business Rules            Business rules referenced within the basic or alternative flows. For instance theire
                                 may be rules as to what constitutes a valid password e.g. One capital letter, One
                                 number, one non-numberalpha character where the password has not been used
                                 before in the last 6 months..


       Issues                    Any potential issues identified which may cause problems in the deployment of
                                 this use case functionality.


       Assumptions               What assumptions have been made e.g. a wifi network connection is available as
                                 opposed to an Edge or 3G connection


       Constraints               Are there scheduling constraints, legal constraints, accessibility constraints,
                                 environment constraints


       Data model and metadata   Description of any data required or stored in relation to this usecase.
       requirements
                                 For a photo graph, audio recording or video there maybe metadata such as the
                                 time takenrecorded, location of the recordingphotovideo.

                                 The focus is a business description of the data rather than a technical description
                                 of the data. For instance a use case may require a drop known list of participant
                                 types – administrator, teacher, student, reviewer they would be mentioned here

                                 If there was a particular XML format for publishing the site list to twitter or
                                 facebook then the specification or definition would be mentioned here.




usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 60 of 61
usecasenamecustomclosetv4-111211101506-phpapp01.docx
                                  Page 61 of 61

Weitere ähnliche Inhalte

Ähnlich wie Custom Closet Use Cases v4

Custom Closet Requirements Specification v2
Custom Closet Requirements Specification v2Custom Closet Requirements Specification v2
Custom Closet Requirements Specification v2Fabrizio Valerio Covone
 
PATHS Functional specification first prototype
PATHS Functional specification first prototypePATHS Functional specification first prototype
PATHS Functional specification first prototypepathsproject
 
Group charter projectcode_v1
Group charter projectcode_v1Group charter projectcode_v1
Group charter projectcode_v1caramurf
 
Md050 application extensions_functional_design_080112
Md050 application extensions_functional_design_080112Md050 application extensions_functional_design_080112
Md050 application extensions_functional_design_080112magik570
 
Open Tms Software Architecure
Open Tms Software ArchitecureOpen Tms Software Architecure
Open Tms Software ArchitecureKlemens Waldhör
 
Software requirements specifications wp2
Software requirements specifications wp2Software requirements specifications wp2
Software requirements specifications wp2ambitlick
 
D4.3. Content and Concept Filter V1
D4.3. Content and Concept Filter V1D4.3. Content and Concept Filter V1
D4.3. Content and Concept Filter V1LinkedTV
 
Creative commons internship report
Creative commons internship reportCreative commons internship report
Creative commons internship reportSteren Giannini
 
Documentation - Element and ElementVector
Documentation - Element and ElementVectorDocumentation - Element and ElementVector
Documentation - Element and ElementVectorMichel Alves
 
Documentation of the Hands-on workshop: experience the life of your Content O...
Documentation of the Hands-on workshop: experience the life of your Content O...Documentation of the Hands-on workshop: experience the life of your Content O...
Documentation of the Hands-on workshop: experience the life of your Content O...Chamilo Association
 
Hands-on workshop: experience the life of your Content Object aka the power o...
Hands-on workshop: experience the life of your Content Object aka the power o...Hands-on workshop: experience the life of your Content Object aka the power o...
Hands-on workshop: experience the life of your Content Object aka the power o...Chamilo Association
 
Kessuud Process Model2.1
Kessuud Process Model2.1Kessuud Process Model2.1
Kessuud Process Model2.1chen meng
 
Volunteer Management Reporting System
Volunteer Management Reporting SystemVolunteer Management Reporting System
Volunteer Management Reporting SystemDainSanye
 

Ähnlich wie Custom Closet Use Cases v4 (20)

User Experience Custom Closet v1
User Experience Custom Closet v1User Experience Custom Closet v1
User Experience Custom Closet v1
 
Custom Closet Requirements Specification v2
Custom Closet Requirements Specification v2Custom Closet Requirements Specification v2
Custom Closet Requirements Specification v2
 
User Experience Custom Closet v3
User Experience Custom Closet v3User Experience Custom Closet v3
User Experience Custom Closet v3
 
Custom Closet Use Cases v1
Custom Closet Use Cases v1Custom Closet Use Cases v1
Custom Closet Use Cases v1
 
User Experience Custom Closet v2
User Experience Custom Closet v2User Experience Custom Closet v2
User Experience Custom Closet v2
 
PATHS Functional specification first prototype
PATHS Functional specification first prototypePATHS Functional specification first prototype
PATHS Functional specification first prototype
 
Group charter projectcode_v1
Group charter projectcode_v1Group charter projectcode_v1
Group charter projectcode_v1
 
Md050 application extensions_functional_design_080112
Md050 application extensions_functional_design_080112Md050 application extensions_functional_design_080112
Md050 application extensions_functional_design_080112
 
301132
301132301132
301132
 
Open Tms Software Architecure
Open Tms Software ArchitecureOpen Tms Software Architecure
Open Tms Software Architecure
 
Subversion howto
Subversion howtoSubversion howto
Subversion howto
 
Software requirements specifications wp2
Software requirements specifications wp2Software requirements specifications wp2
Software requirements specifications wp2
 
D4.3. Content and Concept Filter V1
D4.3. Content and Concept Filter V1D4.3. Content and Concept Filter V1
D4.3. Content and Concept Filter V1
 
Creative commons internship report
Creative commons internship reportCreative commons internship report
Creative commons internship report
 
Documentation - Element and ElementVector
Documentation - Element and ElementVectorDocumentation - Element and ElementVector
Documentation - Element and ElementVector
 
Nextcloud manual
Nextcloud manualNextcloud manual
Nextcloud manual
 
Documentation of the Hands-on workshop: experience the life of your Content O...
Documentation of the Hands-on workshop: experience the life of your Content O...Documentation of the Hands-on workshop: experience the life of your Content O...
Documentation of the Hands-on workshop: experience the life of your Content O...
 
Hands-on workshop: experience the life of your Content Object aka the power o...
Hands-on workshop: experience the life of your Content Object aka the power o...Hands-on workshop: experience the life of your Content Object aka the power o...
Hands-on workshop: experience the life of your Content Object aka the power o...
 
Kessuud Process Model2.1
Kessuud Process Model2.1Kessuud Process Model2.1
Kessuud Process Model2.1
 
Volunteer Management Reporting System
Volunteer Management Reporting SystemVolunteer Management Reporting System
Volunteer Management Reporting System
 

Mehr von Fabrizio Valerio Covone (18)

Shards Idea Proposal
Shards Idea ProposalShards Idea Proposal
Shards Idea Proposal
 
Shards 2nd presentation
Shards 2nd presentation Shards 2nd presentation
Shards 2nd presentation
 
Prince of Persia - Flow charts
Prince of Persia - Flow chartsPrince of Persia - Flow charts
Prince of Persia - Flow charts
 
Shards - Presentation
Shards - PresentationShards - Presentation
Shards - Presentation
 
Custom Closet Presentation Phase 3
Custom Closet Presentation Phase 3Custom Closet Presentation Phase 3
Custom Closet Presentation Phase 3
 
Custom Closet Prototype Storyboard
Custom Closet Prototype StoryboardCustom Closet Prototype Storyboard
Custom Closet Prototype Storyboard
 
Sound State Presentation
Sound State PresentationSound State Presentation
Sound State Presentation
 
Custom Closet Presentation
Custom Closet PresentationCustom Closet Presentation
Custom Closet Presentation
 
Custom Closet Presentation
Custom Closet PresentationCustom Closet Presentation
Custom Closet Presentation
 
Game Analysis - Mafia Wars
Game Analysis - Mafia WarsGame Analysis - Mafia Wars
Game Analysis - Mafia Wars
 
Na Celtigh v1.1
Na Celtigh v1.1Na Celtigh v1.1
Na Celtigh v1.1
 
Na Celtigh - v1.0
Na Celtigh - v1.0Na Celtigh - v1.0
Na Celtigh - v1.0
 
Na Celtigh - v0.9
Na Celtigh - v0.9Na Celtigh - v0.9
Na Celtigh - v0.9
 
Na Celtigh - v0.8
Na Celtigh - v0.8Na Celtigh - v0.8
Na Celtigh - v0.8
 
Na Celtigh - v0.7
Na Celtigh - v0.7Na Celtigh - v0.7
Na Celtigh - v0.7
 
Na Celtigh - v0.6
Na Celtigh - v0.6Na Celtigh - v0.6
Na Celtigh - v0.6
 
Na Celtigh - v0.5
Na Celtigh - v0.5Na Celtigh - v0.5
Na Celtigh - v0.5
 
Integrated Project Phase 1
Integrated Project Phase 1Integrated Project Phase 1
Integrated Project Phase 1
 

Kürzlich hochgeladen

Prescribed medication order and communication skills.pptx
Prescribed medication order and communication skills.pptxPrescribed medication order and communication skills.pptx
Prescribed medication order and communication skills.pptxraviapr7
 
How to Manage Cross-Selling in Odoo 17 Sales
How to Manage Cross-Selling in Odoo 17 SalesHow to Manage Cross-Selling in Odoo 17 Sales
How to Manage Cross-Selling in Odoo 17 SalesCeline George
 
The Stolen Bacillus by Herbert George Wells
The Stolen Bacillus by Herbert George WellsThe Stolen Bacillus by Herbert George Wells
The Stolen Bacillus by Herbert George WellsEugene Lysak
 
The Singapore Teaching Practice document
The Singapore Teaching Practice documentThe Singapore Teaching Practice document
The Singapore Teaching Practice documentXsasf Sfdfasd
 
5 charts on South Africa as a source country for international student recrui...
5 charts on South Africa as a source country for international student recrui...5 charts on South Africa as a source country for international student recrui...
5 charts on South Africa as a source country for international student recrui...CaraSkikne1
 
Easter in the USA presentation by Chloe.
Easter in the USA presentation by Chloe.Easter in the USA presentation by Chloe.
Easter in the USA presentation by Chloe.EnglishCEIPdeSigeiro
 
Patient Counselling. Definition of patient counseling; steps involved in pati...
Patient Counselling. Definition of patient counseling; steps involved in pati...Patient Counselling. Definition of patient counseling; steps involved in pati...
Patient Counselling. Definition of patient counseling; steps involved in pati...raviapr7
 
Quality Assurance_GOOD LABORATORY PRACTICE
Quality Assurance_GOOD LABORATORY PRACTICEQuality Assurance_GOOD LABORATORY PRACTICE
Quality Assurance_GOOD LABORATORY PRACTICESayali Powar
 
How to Solve Singleton Error in the Odoo 17
How to Solve Singleton Error in the  Odoo 17How to Solve Singleton Error in the  Odoo 17
How to Solve Singleton Error in the Odoo 17Celine George
 
How to Add a New Field in Existing Kanban View in Odoo 17
How to Add a New Field in Existing Kanban View in Odoo 17How to Add a New Field in Existing Kanban View in Odoo 17
How to Add a New Field in Existing Kanban View in Odoo 17Celine George
 
Ultra structure and life cycle of Plasmodium.pptx
Ultra structure and life cycle of Plasmodium.pptxUltra structure and life cycle of Plasmodium.pptx
Ultra structure and life cycle of Plasmodium.pptxDr. Asif Anas
 
CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...
CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...
CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...Nguyen Thanh Tu Collection
 
Human-AI Co-Creation of Worked Examples for Programming Classes
Human-AI Co-Creation of Worked Examples for Programming ClassesHuman-AI Co-Creation of Worked Examples for Programming Classes
Human-AI Co-Creation of Worked Examples for Programming ClassesMohammad Hassany
 
Benefits & Challenges of Inclusive Education
Benefits & Challenges of Inclusive EducationBenefits & Challenges of Inclusive Education
Benefits & Challenges of Inclusive EducationMJDuyan
 
PISA-VET launch_El Iza Mohamedou_19 March 2024.pptx
PISA-VET launch_El Iza Mohamedou_19 March 2024.pptxPISA-VET launch_El Iza Mohamedou_19 March 2024.pptx
PISA-VET launch_El Iza Mohamedou_19 March 2024.pptxEduSkills OECD
 
How to Use api.constrains ( ) in Odoo 17
How to Use api.constrains ( ) in Odoo 17How to Use api.constrains ( ) in Odoo 17
How to Use api.constrains ( ) in Odoo 17Celine George
 
The basics of sentences session 10pptx.pptx
The basics of sentences session 10pptx.pptxThe basics of sentences session 10pptx.pptx
The basics of sentences session 10pptx.pptxheathfieldcps1
 
Patterns of Written Texts Across Disciplines.pptx
Patterns of Written Texts Across Disciplines.pptxPatterns of Written Texts Across Disciplines.pptx
Patterns of Written Texts Across Disciplines.pptxMYDA ANGELICA SUAN
 

Kürzlich hochgeladen (20)

Prescribed medication order and communication skills.pptx
Prescribed medication order and communication skills.pptxPrescribed medication order and communication skills.pptx
Prescribed medication order and communication skills.pptx
 
How to Manage Cross-Selling in Odoo 17 Sales
How to Manage Cross-Selling in Odoo 17 SalesHow to Manage Cross-Selling in Odoo 17 Sales
How to Manage Cross-Selling in Odoo 17 Sales
 
The Stolen Bacillus by Herbert George Wells
The Stolen Bacillus by Herbert George WellsThe Stolen Bacillus by Herbert George Wells
The Stolen Bacillus by Herbert George Wells
 
The Singapore Teaching Practice document
The Singapore Teaching Practice documentThe Singapore Teaching Practice document
The Singapore Teaching Practice document
 
5 charts on South Africa as a source country for international student recrui...
5 charts on South Africa as a source country for international student recrui...5 charts on South Africa as a source country for international student recrui...
5 charts on South Africa as a source country for international student recrui...
 
Easter in the USA presentation by Chloe.
Easter in the USA presentation by Chloe.Easter in the USA presentation by Chloe.
Easter in the USA presentation by Chloe.
 
Patient Counselling. Definition of patient counseling; steps involved in pati...
Patient Counselling. Definition of patient counseling; steps involved in pati...Patient Counselling. Definition of patient counseling; steps involved in pati...
Patient Counselling. Definition of patient counseling; steps involved in pati...
 
Quality Assurance_GOOD LABORATORY PRACTICE
Quality Assurance_GOOD LABORATORY PRACTICEQuality Assurance_GOOD LABORATORY PRACTICE
Quality Assurance_GOOD LABORATORY PRACTICE
 
How to Solve Singleton Error in the Odoo 17
How to Solve Singleton Error in the  Odoo 17How to Solve Singleton Error in the  Odoo 17
How to Solve Singleton Error in the Odoo 17
 
How to Add a New Field in Existing Kanban View in Odoo 17
How to Add a New Field in Existing Kanban View in Odoo 17How to Add a New Field in Existing Kanban View in Odoo 17
How to Add a New Field in Existing Kanban View in Odoo 17
 
Ultra structure and life cycle of Plasmodium.pptx
Ultra structure and life cycle of Plasmodium.pptxUltra structure and life cycle of Plasmodium.pptx
Ultra structure and life cycle of Plasmodium.pptx
 
Prelims of Kant get Marx 2.0: a general politics quiz
Prelims of Kant get Marx 2.0: a general politics quizPrelims of Kant get Marx 2.0: a general politics quiz
Prelims of Kant get Marx 2.0: a general politics quiz
 
CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...
CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...
CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...
 
Human-AI Co-Creation of Worked Examples for Programming Classes
Human-AI Co-Creation of Worked Examples for Programming ClassesHuman-AI Co-Creation of Worked Examples for Programming Classes
Human-AI Co-Creation of Worked Examples for Programming Classes
 
Benefits & Challenges of Inclusive Education
Benefits & Challenges of Inclusive EducationBenefits & Challenges of Inclusive Education
Benefits & Challenges of Inclusive Education
 
Finals of Kant get Marx 2.0 : a general politics quiz
Finals of Kant get Marx 2.0 : a general politics quizFinals of Kant get Marx 2.0 : a general politics quiz
Finals of Kant get Marx 2.0 : a general politics quiz
 
PISA-VET launch_El Iza Mohamedou_19 March 2024.pptx
PISA-VET launch_El Iza Mohamedou_19 March 2024.pptxPISA-VET launch_El Iza Mohamedou_19 March 2024.pptx
PISA-VET launch_El Iza Mohamedou_19 March 2024.pptx
 
How to Use api.constrains ( ) in Odoo 17
How to Use api.constrains ( ) in Odoo 17How to Use api.constrains ( ) in Odoo 17
How to Use api.constrains ( ) in Odoo 17
 
The basics of sentences session 10pptx.pptx
The basics of sentences session 10pptx.pptxThe basics of sentences session 10pptx.pptx
The basics of sentences session 10pptx.pptx
 
Patterns of Written Texts Across Disciplines.pptx
Patterns of Written Texts Across Disciplines.pptxPatterns of Written Texts Across Disciplines.pptx
Patterns of Written Texts Across Disciplines.pptx
 

Custom Closet Use Cases v4

  • 1. Custom Closet Fashion Designer and E-Commerce Web Application Date : 8thDecember 2011 Authors: Version: 4 Status: Draft usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 1 of 61
  • 2. Document Control Contributors Name/Position Organization Contact Details Fabrizio Valerio Covone DIT Fabrizio.covone@mydit.ie Cara Murphy DIT Cara.murphy@mydit.ie Christopher Conlan DIT Christopher.conlan@mydit.ie Stephen Carberry DIT Stephen.carberry@mydit.ie Shane Ellis DIT Shane.ellis@mydit.ie Version History Date Version Status Comments 05/12/2011 1 Draft Use Cases of the first 4 Functional Modules added. 06/12/2011 2 Draft Document Recycled for Admin Profile new FM 07/12/11 3 Draft 4 New Use Cases added. 08/12/11 4 Release Candidate Added last 3 Use Cases. Changes since last version NA usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 2 of 61
  • 3. Known Omissions NA Approvals Date Name Title Signature Version usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 3 of 61
  • 5. Table of Contents DOCUMENT CONTROL............................................................................................................................. 2 REVIEWERS COMMENTS ......................................................................................................................... 4 TABLE OF CONTENTS ............................................................................................................................... 5 1 INTRODUCTION .............................................................................................................................. 10 1.1 PURPOSE OF THE DOCUMENT ............................................................................................................. 10 1.2 INTENDED AUDIENCE ........................................................................................................................ 10 1.3 DEFINITIONS, ACRONYMS AND ABBREVIATIONS ...................................................................................... 11 2 USE CASES ...................................................................................................................................... 12 2.1 LIST .............................................................................................................................................. 12 2.2 UC0001 – CUSTOMER REGISTRATION .................................................................................................. 14 2.2.1 ACTORS .................................................................................................................................................. 14 2.2.2 BRIEF DESCRIPTION .................................................................................................................................. 14 2.2.3 TRIGGER EVENT ....................................................................................................................................... 15 2.2.4 BASIC FLOW ............................................................................................................................................ 15 2.2.5 CONSTRAINTS .......................................................................................................................................... 16 2.2.6 DATA MODEL AND METADATA REQUIREMENTS .............................................................................................. 16 2.3 UC0002 – FASHION DESIGNER REGISTRATION ....................................................................................... 18 2.3.1 ACTORS .................................................................................................................................................. 18 2.3.2 BRIEF DESCRIPTION .................................................................................................................................. 18 2.3.3 TRIGGER EVENT ....................................................................................................................................... 19 2.3.4 BASIC FLOW ............................................................................................................................................ 19 usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 5 of 61
  • 6. 2.3.5 CONSTRAINTS .......................................................................................................................................... 20 2.3.6 DATA MODEL AND METADATA REQUIREMENTS .............................................................................................. 20 2.4 UC0003 – REGISTERED CUSTOMER PROFILE .......................................................................................... 22 2.4.1 ACTORS .................................................................................................................................................. 22 2.4.2 BRIEF DESCRIPTION .................................................................................................................................. 22 2.4.3 PRE-CONDITIONS ..................................................................................................................................... 22 2.4.4 TRIGGER EVENT ....................................................................................................................................... 23 2.4.5 BASIC FLOW ............................................................................................................................................ 23 2.4.6 CONSTRAINTS .......................................................................................................................................... 24 2.4.7 DATA MODEL AND METADATA REQUIREMENTS .............................................................................................. 24 2.5 UC0004 – FASHION DESIGNER PROFILE ................................................................................................ 26 2.5.1 ACTORS .................................................................................................................................................. 26 2.5.2 BRIEF DESCRIPTION .................................................................................................................................. 26 2.5.3 PRE-CONDITIONS ..................................................................................................................................... 26 2.5.4 TRIGGER EVENT ....................................................................................................................................... 27 2.5.5 BASIC FLOW ............................................................................................................................................ 27 2.5.6 CONSTRAINTS .......................................................................................................................................... 28 2.5.7 DATA MODEL AND METADATA REQUIREMENTS .............................................................................................. 28 2.6 UC0005 – WEB ADMINISTRATOR PROFILE ............................................................................................ 30 2.6.1 ACTORS .................................................................................................................................................. 30 2.6.2 BRIEF DESCRIPTION .................................................................................................................................. 30 2.6.3 PRE-CONDITIONS ..................................................................................................................................... 30 2.6.4 TRIGGER EVENT ....................................................................................................................................... 31 2.6.5 BASIC FLOW ............................................................................................................................................ 31 usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 6 of 61
  • 7. 2.6.6 CONSTRAINTS .......................................................................................................................................... 32 2.6.7 DATA MODEL AND METADATA REQUIREMENTS .............................................................................................. 32 2.7 UC0006 – USER LOGIN .................................................................................................................... 33 2.7.1 ACTORS .................................................................................................................................................. 33 2.7.2 BRIEF DESCRIPTION .................................................................................................................................. 33 2.7.3 PRE-CONDITIONS ..................................................................................................................................... 33 2.7.4 TRIGGER EVENT ....................................................................................................................................... 34 2.7.5 BASIC FLOW ............................................................................................................................................ 34 2.7.6 CONSTRAINTS .......................................................................................................................................... 35 2.7.7 DATA MODEL AND METADATA REQUIREMENTS .............................................................................................. 35 2.8 UC0007 – PRODUCTS GALLERY .......................................................................................................... 36 2.8.1 ACTORS .................................................................................................................................................. 36 2.8.2 BRIEF DESCRIPTION .................................................................................................................................. 36 2.8.3 PRE-CONDITIONS ..................................................................................................................................... 36 2.8.4 TRIGGER EVENT ....................................................................................................................................... 37 2.8.5 BASIC FLOW ............................................................................................................................................ 37 2.8.6 DATA MODEL AND METADATA REQUIREMENTS .............................................................................................. 38 2.9 UC0008 – FASHION DESIGNER ENGAGEMENT ........................................................................................ 39 2.9.1 ACTORS .................................................................................................................................................. 39 2.9.2 BRIEF DESCRIPTION .................................................................................................................................. 39 2.9.3 PRE-CONDITIONS ..................................................................................................................................... 39 2.9.4 TRIGGER EVENT ....................................................................................................................................... 40 2.9.5 BASIC FLOW ............................................................................................................................................ 40 2.9.6 CONSTRAINTS .......................................................................................................................................... 41 usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 7 of 61
  • 8. 2.9.7 DATA MODEL AND METADATA REQUIREMENTS .............................................................................................. 41 2.10 UC0009 – CUSTOM PRODUCT REQUEST ............................................................................................. 42 2.10.1 ACTORS ................................................................................................................................................ 42 2.10.2 BRIEF DESCRIPTION ................................................................................................................................ 42 2.10.3 PRE-CONDITIONS ................................................................................................................................... 42 2.10.4 TRIGGER EVENT ..................................................................................................................................... 43 2.10.5 BASIC FLOW .......................................................................................................................................... 43 2.10.6 CONSTRAINTS ........................................................................................................................................ 44 2.11 UC0010 – SHOPPING CART ............................................................................................................. 45 2.11.1 ACTORS ................................................................................................................................................ 45 2.11.2 BRIEF DESCRIPTION ................................................................................................................................ 45 2.11.3 PRE-CONDITIONS ................................................................................................................................... 45 2.11.4 TRIGGER EVENT ..................................................................................................................................... 46 2.11.5 BASIC FLOW .......................................................................................................................................... 46 2.11.6 CONSTRAINTS ........................................................................................................................................ 47 2.12 UC0011 – PURCHASE PROCESS ........................................................................................................ 48 2.12.1 ACTORS ................................................................................................................................................ 48 2.12.2 BRIEF DESCRIPTION ................................................................................................................................ 48 2.12.3 PRE-CONDITIONS ................................................................................................................................... 48 2.12.4 TRIGGER EVENT ..................................................................................................................................... 49 2.12.5 BASIC FLOW .......................................................................................................................................... 49 2.12.6 DATA MODEL AND METADATA REQUIREMENTS............................................................................................ 50 2.13 UC0012 – REFUND PROCESS ........................................................................................................... 51 2.13.1 ACTORS ................................................................................................................................................ 51 usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 8 of 61
  • 9. 2.13.2 BRIEF DESCRIPTION ................................................................................................................................ 51 2.13.3 PRE-CONDITIONS ................................................................................................................................... 51 2.13.4 TRIGGER EVENT ..................................................................................................................................... 52 2.13.5 BASIC FLOW .......................................................................................................................................... 52 2.13.6 CONSTRAINTS ........................................................................................................................................ 53 3 APPENDIX ....................................................................................................................................... 54 3.1 NOTE ............................................................................................................................................ 54 3.2 WHAT IS A USE-CASE? ....................................................................................................................... 54 3.3 PROCEDURE FOR CREATING A USE-CASE ................................................................................................. 54 3.4 USE CASE STRUCTURE ........................................................................................................................ 58 usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 9 of 61
  • 10. 1 Introduction 1.1 Purpose of the Document This document addresses the use cases associated with the following functional modules: Ref Name FM-0001 Customer Registration FM-0002 FD Registration FM-0003 RC Profile FM-0004 FD Profile FM-0005 Admin Profile FM-0006 User Log In FM-0007 Products Gallery FM-0008 FD Engagement FM-0009 Custom Product Request FM-0010 Shopping Cart FM-0011 Purchase Process FM-0012 Refund Process 1.2 Intended Audience This document is a business level document intended for all project members, the project stakeholders and potential users of the system. usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 10 of 61
  • 11. 1.3 Definitions, Acronyms and Abbreviations UCD: User Centred Design Requirements Specification: A document that describes the high level functional requirements of the system to be developed. RC: Registered Customer. FD: Fashion Designer. Admin: Custom Closet’s Administrator. usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 11 of 61
  • 12. 2 Use cases 2.1 List usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 12 of 61
  • 13. Ref Description UC-0001 This is the registration process of any user who wants to buy FD’s shown products and/or engage a FD for a customized product. UC-0002 This is the registration process that a Fashion Designer has to fulfil in order to set up his/her Personal Profile. During this process FDs have to apply to the monthly subscription. UC-0003 This functional module is the RCs’ personal profile where FDs can manage their purchased products and rate FDs. UC-0004 This functional module is the FDs’ personal showroom where FDs can exhibit their work and be contacted by RC. UC-0005 This functional module is the Admin’s personal console where he/she can approve refunds and ban RCs and FDs. UC-0006 This is the module where RCs and FDs log in in order to access their relative features. UC-0007 In this module all FD’s products are shown and can be purchased by RCs. UC-0008 This functionality module provides RCs to contact and engage FDs to order tailored attire. UC-0009 RCs can customize their purchase by choosing different products by many FDs and see how they will look like on a stylized Avatar. UC-0010 RCs can add to the shopping cart the products that they want to purchase. UC-0011 During this process RCs will pay the products they want to purchase. After they have received their purchased products, RCs and FDs have to rate each other. UC-0012 During this process RCs can ask for a refund, but only a Admin will decide to proceed further or to reject it. usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 13 of 61
  • 14. 2.2 UC0001 – Customer Registration Use case reference UC0001 Use case title Customer Registration Author Fabrizio Valerio Covone Creation Date 05/12/2011 Version 1 Last Modified by Fabrizio Valerio Covone Date Modified 05/12/2011 2.2.1 Actors Customer type user Web Application 2.2.2 Brief Description This is the registration process of any user who wants to buy FD’s shown products and/or engage a FD for a customized product. usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 14 of 61
  • 15. 2.2.3 Trigger Event Clicking on the Sign Up Button. 2.2.4 Basic Flow usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 15 of 61
  • 16. 2.2.5 Constraints Ref Description 0001 Terms & Conditions: A refund is granted to the client only in case of wrong size and damaged product delivery. 0002 Terms & Conditions: Registered users whether they are Fashion Designer or Customers have to behave properly. 0003 Terms & Conditions: If a registered user (RC and/or FD) is caught behaving in an inappropriate way (e.g.: usage of bad words in rating system, spamming, etc.) by and Admin. He/she will be banned for a period of time related to the gravity of his/her actions. 2.2.6 Data model and metadata requirements usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 16 of 61
  • 17. Name Type Mandatory Restrictions Description Name Text Field Y Customer’s Name Surname Text Field Y Customer’s Surname Gender Radio Button N Customer’s Gender Date of Birth Date Field Y DD/mm/YYYY format Customer’s Date of Birth Address Text Field Y Customer’s Address Country Drop Down list Y Customer’s Country State Drop Down list N Customer’s State (for US Residents) Phone Number Text Field Y Customer’s Main Phone Number Secondary Phone No. Text Field N Customer’s Secondary Phone Number Email Text Field Y Customer’s Email Password Password Field Y Customer’s Password Credit Card Type Radio Button Y Customer’s Credit Card Type Card Number Text Field Y Customer’s Credit Card Number Expiration Date Date Field Y Customer’s Credit Card Expiration Date CCV Text Field Y Maximum of 4 digits Customer’s Credit Card Verification Number usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 17 of 61
  • 18. 2.3 UC0002 – Fashion Designer Registration Use case reference UC0002 Use case title FD Registration Author Fabrizio Valerio Covone Creation Date 06/12/2011 Version 1 Last Modified by Fabrizio Valerio Covone Date Modified 06/12/2011 2.3.1 Actors FD type user Web Application 2.3.2 Brief Description This is the registration process that a Fashion Designer has to fulfill in order to set up his/her Personal Profile. During this process FDs have to apply to the monthly subscription. usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 18 of 61
  • 19. 2.3.3 Trigger Event Clicking on the Join Us Button. 2.3.4 Basic Flow usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 19 of 61
  • 20. 2.3.5 Constraints Ref Description 0001 Terms & Conditions: A refund is granted to the client only in case of wrong size and damaged product delivery. 0002 Terms & Conditions: Registered users whether they are Fashion Designer or Customers have to behave properly. 0003 Terms & Conditions: If a registered user (RC and/or FD) is caught behaving in an inappropriate way (e.g.: usage of bad words in rating system, spamming, etc.) by and Admin. He/she will be banned for a period of time related to the gravity of his/her actions. 0004 Terms & Conditions: Custom Closet will keep a small percentage of the revenues of each purchase. 2.3.6 Data model and metadata requirements usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 20 of 61
  • 21. Name Type Mandatory Restrictions Description Name Text Field Y FD’s Name Surname Text Field Y FD’s Surname Gender Radio Button N FD’s Gender Date of Birth Date Field Y DD/mm/YYYY format FD’s Date of Birth Address Text Field Y FD’s Address Country Drop Down list Y FD’s Country State Drop Down list N FD’s State (for US Residents) Phone Number Text Field Y FD’s Main Phone Number Secondary Phone No. Text Field N FD’s Secondary Phone Number Email Text Field Y FD’s Email Password Password Field Y FD’s Password Credit Card Type Radio Button Y FD’s Credit Card Type Card Number Text Field Y FD’s Credit Card Number Expiration Date Date Field Y FD’s Credit Card Expiration Date CCV Text Field Y Maximum of 4 digits FD’s Credit Card Verification Number Subscription Type Radio Button Y FD’s Subscription Type usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 21 of 61
  • 22. 2.4 UC0003 – Registered Customer Profile Use case reference UC0003 Use case title Registered Customer Profile Author Fabrizio Valerio Covone Creation Date 06/12/2011 Version 1 Last Modified by Fabrizio Valerio Covone Date Modified 06/12/2011 2.4.1 Actors RC user Web Application 2.4.2 Brief Description This functional module is the RCs’ personal profile where FDs can manage their purchased products and rate FDs. 2.4.3 Pre-conditions A Registered Customer can access to this feature only after the registration process. usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 22 of 61
  • 23. 2.4.4 Trigger Event Clicking on the Profile Button/Link or redirected from Login page. 2.4.5 Basic Flow usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 23 of 61
  • 24. 2.4.6 Constraints Ref Description 0001 Terms & Conditions: A refund is granted to the client only in case of wrong size and damaged product delivery. 0002 Terms & Conditions: Registered users whether they are Fashion Designer or Customers have to behave properly. 0003 Terms & Conditions: If a registered user (RC and/or FD) is caught behaving in an inappropriate way (e.g.: usage of bad words in rating system, spamming, etc.) by and Admin. He/she will be banned for a period of time related to the gravity of his/her actions. 2.4.7 Data model and metadata requirements usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 24 of 61
  • 25. Name Type Mandatory Restrictions Description Name Text Field Y Customer’s Name Surname Text Field Y Customer’s Surname Gender Radio Button N Customer’s Gender Date of Birth Date Field Y DD/mm/YYYY format Customer’s Date of Birth Address Text Field Y Customer’s Address Country Drop Down list Y Customer’s Country State Drop Down list N Customer’s State (for US Residents) Phone Number Text Field Y Customer’s Main Phone Number Secondary Phone No. Text Field N Customer’s Secondary Phone Number Email Text Field Y Customer’s Email Password Password Field Y Customer’s Password Credit Card Type Radio Button Y Customer’s Credit Card Type Card Number Text Field Y Customer’s Credit Card Number Expiration Date Date Field Y Customer’s Credit Card Expiration Date CCV Text Field Y Maximum of 4 digits Customer’s Credit Card Verification Number usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 25 of 61
  • 26. 2.5 UC0004 – Fashion DesignerProfile Use case reference UC0004 Use case title Fashion Designer Profile Author Fabrizio Valerio Covone Creation Date 06/12/2011 Version 1 Last Modified by Fabrizio Valerio Covone Date Modified 06/12/2011 2.5.1 Actors FD user Web Application 2.5.2 Brief Description This functional module is the FDs’ personal showroom where FDs can exhibit their work and be contacted by RC. 2.5.3 Pre-conditions A Fashion Designer can access to this feature only after the registration process. usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 26 of 61
  • 27. 2.5.4 Trigger Event Clicking on the Profile Button/Link or redirected from Login page. 2.5.5 Basic Flow usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 27 of 61
  • 28. 2.5.6 Constraints Ref Description 0001 Terms & Conditions: A refund is granted to the client only in case of wrong size and damaged product delivery. 0002 Terms & Conditions: Registered users whether they are Fashion Designer or Customers have to behave properly. 0003 Terms & Conditions: If a registered user (RC and/or FD) is caught behaving in an inappropriate way (e.g.: usage of bad words in rating system, spamming, etc.) by and Admin. He/she will be banned for a period of time related to the gravity of his/her actions. 0004 Terms & Conditions: Custom Closet will keep a small percentage of the revenues of each purchase. 2.5.7 Data model and metadata requirements usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 28 of 61
  • 29. Name Type Mandatory Restrictions Description Name Text Field Y FD’s Name Surname Text Field Y FD’s Surname Gender Radio Button N FD’s Gender Date of Birth Date Field Y DD/mm/YYYY format FD’s Date of Birth Address Text Field Y FD’s Address Country Drop Down list Y FD’s Country State Drop Down list N FD’s State (for US Residents) Phone Number Text Field Y FD’s Main Phone Number Secondary Phone No. Text Field N FD’s Secondary Phone Number Email Text Field Y FD’s Email Password Password Field Y FD’s Password Credit Card Type Radio Button Y FD’s Credit Card Type Card Number Text Field Y FD’s Credit Card Number Expiration Date Date Field Y FD’s Credit Card Expiration Date CCV Text Field Y Maximum of 4 digits FD’s Credit Card Verification Number Subscription Type Radio Button Y FD’s Subscription Type usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 29 of 61
  • 30. 2.6 UC0005 – Web AdministratorProfile Use case reference UC0005 Use case title Web Administrator Profile Author Fabrizio Valerio Covone Creation Date 06/12/2011 Version 1 Last Modified by Fabrizio Valerio Covone Date Modified 06/12/2011 2.6.1 Actors Admin user Web Application 2.6.2 Brief Description This functional module is the Admin’s personal console where he/she can approve refunds and ban RCs and FDs. 2.6.3 Pre-conditions Only a registered employee of Custom Closet can access to this feature. usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 30 of 61
  • 31. 2.6.4 Trigger Event Clicking on the Profile Button/Link or redirected from Login page. 2.6.5 Basic Flow usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 31 of 61
  • 32. 2.6.6 Constraints Ref Description 0001 Terms & Conditions: A refund is granted to the client only in case of wrong size and damaged product delivery. 0002 Terms & Conditions: Registered users whether they are Fashion Designer or Customers have to behave properly. 0003 Terms & Conditions: If a registered user (RC and/or FD) is caught behaving in an inappropriate way (e.g.: usage of bad words in rating system, spamming, etc.) by and Admin. He/she will be banned for a period of time related to the gravity of his/her actions. 2.6.7 Data model and metadata requirements Name Type Mandatory Restrictions Description Name Text Field Y Admin’s Name Surname Text Field Y Admin’s Surname Gender Radio Button N Admin’s Gender Date of Birth Date Field Y DD/mm/YYYY format Admin’s Date of Birth Password Password Field Y Admin’s Password usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 32 of 61
  • 33. 2.7 UC0006 – User Login Use case reference UC0006 Use case title User Login Author Fabrizio Valerio Covone Creation Date 07/12/2011 Version 1 Last Modified by Fabrizio Valerio Covone Date Modified 07/12/2011 2.7.1 Actors Customer type user Fashion Designer user type Web Administrator user type Web Application 2.7.2 Brief Description This is the module where RCs, FDs and Admins log in in order to access their relative features and profiles. 2.7.3 Pre-conditions In order to complete the Log In process properly, a user has to be registeredto Custom Closet. usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 33 of 61
  • 34. 2.7.4 Trigger Event Clicking on the Log In Button. 2.7.5 Basic Flow usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 34 of 61
  • 35. 2.7.6 Constraints Ref Description 0001 Terms & Conditions: A refund is granted to the client only in case of wrong size and damaged product delivery. 0002 Terms & Conditions: Registered users whether they are Fashion Designer or Customers have to behave properly. 0003 Terms & Conditions: If a registered user (RC and/or FD) is caught behaving in an inappropriate way (e.g.: usage of bad words in rating system, spamming, etc.) by and Admin. He/she will be banned for a period of time related to the gravity of his/her actions. 2.7.7 Data model and metadata requirements Name Type Mandatory Restrictions Description Email Text Field Y User’s Email Password Password Field Y User’s Password usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 35 of 61
  • 36. 2.8 UC0007 – Products Gallery Use case reference UC0007 Use case title Products Gallery Author Fabrizio Valerio Covone Creation Date 07/12/2011 Version 1 Last Modified by Fabrizio Valerio Covone Date Modified 07/12/2011 2.8.1 Actors Guest user type Registered Customer user type Fashion Designer user type Web Application 2.8.2 Brief Description In this module all FD’s products are shown and can be purchased by RCs. 2.8.3 Pre-conditions In order to access to the features “Add to The Shopping Cart” and “Fit it on your Avatar” features a customer has to be registered. usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 36 of 61
  • 37. 2.8.4 Trigger Event Clicking on the Gallery Button. 2.8.5 Basic Flow usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 37 of 61
  • 38. 2.8.6 Data model and metadata requirements Name Type Mandatory Restrictions Description Name Text Field N Product’s Name FD Name Text Field N Product’s Fashion Designer Name Colour Drop Down List N Product’s Colour Price Range Radio Button N Product’s Price Range Type Drop Down List N Product’s Type of Clothing Fashion Season Drop Down List N Product’s Fashion Season usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 38 of 61
  • 39. 2.9 UC0008 – Fashion Designer Engagement Use case reference UC0008 Use case title Fashion Designer Engagement Author Fabrizio Valerio Covone Creation Date 07/12/2011 Version 1 Last Modified by Fabrizio Valerio Covone Date Modified 07/12/2011 2.9.1 Actors Registered Customer user type Fashion Designer user type Web Application 2.9.2 Brief Description This functionality module provides RCs to contact and engage FDs to order tailored attire. 2.9.3 Pre-conditions In order to access to this feature a Customer has to be Registered, while a FD has to be Registered and Active. usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 39 of 61
  • 40. 2.9.4 Trigger Event RC point of view: Clicking on the Ask for an Engagement in RC’s Profile. FD Point of view: Clicking on Manage Engagement in FD’s Profile. 2.9.5 Basic Flow usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 40 of 61
  • 41. 2.9.6 Constraints Ref Description 0001 Terms & Conditions: A refund is granted to the client only in case of wrong size and damaged product delivery. 0002 Terms & Conditions: Registered users whether they are Fashion Designer or Customers have to behave properly. 0003 Terms & Conditions: If a registered user (RC and/or FD) is caught behaving in an inappropriate way (e.g.: usage of bad words in rating system, spamming, etc.) by and Admin. He/she will be banned for a period of time related to the gravity of his/her actions. 0004 Terms & Conditions: Custom Closet will keep a small percentage of the revenues of each purchase. 2.9.7 Data model and metadata requirements See Chapters 2.4.7 and 2.5.7. usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 41 of 61
  • 42. 2.10 UC0009 – Custom Product Request Use case reference UC0009 Use case title Custom Product Request Author Fabrizio Valerio Covone Creation Date 07/12/2011 Version 1 Last Modified by Fabrizio Valerio Covone Date Modified 07/12/2011 2.10.1 Actors Registered Customer user type Web Application 2.10.2 Brief Description RCs can customize their purchase by choosing different products by many FDs and see how they will look like on a stylized Avatar. 2.10.3 Pre-conditions In order to access to this feature a Customer has to be Registered. usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 42 of 61
  • 43. 2.10.4 Trigger Event Clicking on the Fit on Avatar. 2.10.5 Basic Flow usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 43 of 61
  • 44. 2.10.6 Constraints Ref Description 0001 Terms & Conditions: A refund is granted to the client only in case of wrong size and damaged product delivery. 0002 Terms & Conditions: Registered users whether they are Fashion Designer or Customers have to behave properly. 0003 Terms & Conditions: If a registered user (RC and/or FD) is caught behaving in an inappropriate way (e.g.: usage of bad words in rating system, spamming, etc.) by and Admin. He/she will be banned for a period of time related to the gravity of his/her actions. 0004 Terms & Conditions: Custom Closet will keep a small percentage of the revenues of each purchase. usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 44 of 61
  • 45. 2.11 UC0010 – Shopping Cart Use case reference UC0010 Use case title Shopping Cart Author Fabrizio Valerio Covone Creation Date 08/12/2011 Version 1 Last Modified by Fabrizio Valerio Covone Date Modified 08/12/2011 2.11.1 Actors Registered Customer type user Web Application 2.11.2 Brief Description RCs can add to the shopping cart the products that they want to purchase. 2.11.3 Pre-conditions In order to access this feature a user has to be registered to Custom Closet. usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 45 of 61
  • 46. 2.11.4 Trigger Event Clicking on the Shopping Cart button. 2.11.5 Basic Flow usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 46 of 61
  • 47. 2.11.6 Constraints Ref Description 0001 Terms & Conditions: A refund is granted to the client only in case of wrong size and damaged product delivery. 0002 Terms & Conditions: Registered users whether they are Fashion Designer or Customers have to behave properly. 0003 Terms & Conditions: If a registered user (RC and/or FD) is caught behaving in an inappropriate way (e.g.: usage of bad words in rating system, spamming, etc.) by and Admin. He/she will be banned for a period of time related to the gravity of his/her actions. usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 47 of 61
  • 48. 2.12 UC0011 – Purchase Process Use case reference UC0011 Use case title Purchase Process Author Fabrizio Valerio Covone Creation Date 08/12/2011 Version 1 Last Modified by Fabrizio Valerio Covone Date Modified 08/12/2011 2.12.1 Actors Registered Customer user type Fashion Designer user type Web Application 2.12.2 Brief Description During this process RCs will pay the products they want to purchase. After they have received their purchased products, RCs and FDs have to rate each other. 2.12.3 Pre-conditions In order to access to this feature a Customer has to be registered and there should be at least one product in his/her Shopping cart. usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 48 of 61
  • 49. 2.12.4 Trigger Event Clicking on the Buy Now Button. 2.12.5 Basic Flow usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 49 of 61
  • 50. 2.12.6 Data model and metadata requirements Name Type Mandatory Restrictions Description Name Text Field Y Customer’s Name Surname Text Field Y Customer’s Surname Gender Radio Button N Customer’s Gender Date of Birth Date Field Y DD/mm/YYYY format Customer’s Date of Birth Address Text Field Y Customer’s Address Country Drop Down list Y Customer’s Country State Drop Down list N Customer’s State (for US Residents) Phone Number Text Field Y Customer’s Main Phone Number Secondary Phone No. Text Field N Customer’s Secondary Phone Number Email Text Field Y Customer’s Email Password Password Field Y Customer’s Password Credit Card Type Radio Button Y Customer’s Credit Card Type Card Number Text Field Y Customer’s Credit Card Number Expiration Date Date Field Y Customer’s Credit Card Expiration Date CCV Text Field Y Maximum of 4 digits Customer’s Credit Card Verification Number usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 50 of 61
  • 51. 2.13 UC0012 – Refund Process Use case reference UC0012 Use case title Refund Process Author Fabrizio Valerio Covone Creation Date 08/12/2011 Version 1 Last Modified by Fabrizio Valerio Covone Date Modified 08/12/2011 2.13.1 Actors Registered Customer user type Fashion Designer user type Web Application 2.13.2 Brief Description During this process RCs can ask for a refund, but only a Admin will decide to proceed further or to reject it. 2.13.3 Pre-conditions In order to access to this feature a Customer has to have purchased at least one product. usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 51 of 61
  • 52. 2.13.4 Trigger Event Clicking on the Ask for a Refund. 2.13.5 Basic Flow usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 52 of 61
  • 53. 2.13.6 Constraints Ref Description 0001 Terms & Conditions: A refund is granted to the client only in case of wrong size and damaged product delivery. 0002 Terms & Conditions: Registered users whether they are Fashion Designer or Customers have to behave properly. 0003 Terms & Conditions: If a registered user (RC and/or FD) is caught behaving in an inappropriate way (e.g.: usage of bad words in rating system, spamming, etc.) by and Admin. He/she will be banned for a period of time related to the gravity of his/her actions. 0004 Terms & Conditions: Custom Closet will keep a small percentage of the revenues of each purchase. usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 53 of 61
  • 54. 3 Appendix 3.1 Note This appendix would not be in every use case. An appendix in a use case contains additional information and artifact examples that might be use full in describing or understanding the usage scenario. 3.2 What is a use-case? Use-cases are an unfolding story that describes the functions in a system and the usage paths through them. They are essentially narrative descriptions with diagrams and example screens. Their purpose is to describe in the simplest possible terms how the proposed system would be used. Use-cases document the accomplishment of a single task by the user. The use cases illustrate the functionality of the system in terms of the business processes the system is being built to support. Use cases describe how it is envisioned users of the system (actors) would perform tasks such as login, change settings, and enter a particular type of data. 3.3 Procedure for creating a use-case The diagram below illustrates the process by which each use case is created. Basically it is an iterative process where the business function required is considered from a number of different perspectives which can be summarized as : CRUD-SPARP. For example in a use case area like add a moodle site to the site list the analyst asks themselves how will I : Create a Site (Create) Review site details e.g. URL, Username – are there different views (Review) Correct site details (Update) Delete or Retire a site from use (Delete) Search for a site on the site list (Search) Print a sites details, a list of sites – are there different print styles (Print) Archive or backup the site list e.g. send to dropbox (Archive) usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 54 of 61
  • 55. Generate a report on all sites e.g. how frequently are they accessed (Report) Publish Export Import e.g. send the list to twitter, facebook or a website (Publish) All of the above are self contained functionality within a module. But what are the reporting requirements of this module in relation to other modules in the system – are there lookup to other modules, what cross system reports are executed within this module or involve this module (Report across system) usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 55 of 61
  • 58. 3.4 Use case structure Each use case has the following narrative structure: usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 58 of 61
  • 59. Ref Heading Description Actors Who performs the process described in the use case Brief Description A description of the use case being specified with an overview diagram of the process. What is the goal of this use case, what is the objective of the user. User Interface A wire frame diagram of the main screens and dialogs presented to the user as they execute the use case. This is only used where appropriate. Its purpose is to provide a visual aid to the reader as to the functionality available. The user interface in this case is used to help explain the proposed functionality. As user experience designers get involved the UI may change and even use cases may disappear. Including a mock up user interface can however drive out issues as to what data needs to be displayed and if data is to be entered how it is validated. This information then helps the design of the data model. User Interface description A description of the user interface components and their functions Trigger Event What event or action triggers this use case Flow of Events - Basic Flow A description of the main process where each step is referenced by a number. A flow, state or sequence diagram may also be added to explain the process. - Alternative Flow The basic flow describes how the process would be executed in 90% of the cases i.e. where no error has occurred or where no business rule exceptions occur. The alternate flows concern the business logic applied to a basic flow. For instance the basic flow could be for to enter a URL, username and password. Access to the moodle site is checked and the site is added. Alternative flows may describe situations where there is an error in the input data, the site cannot be reached etc. Non-functional Requirements This section only contains content if it is specific to that particular use case not the system as a whole. - Usability A particular usability requirement. For instance command line functionality required, quick key, must be able to select all and deselect a list, or deselect all and select a list etc. - Reliability A particular reliability requirement. For instance no site should be stored unless connection to the site has been established at least once. - Performance Minimum performance requirements. For instance the system should respond report an issue with uploading within 10 seconds and ask if the user wants to usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 59 of 61
  • 60. continue or wait until they have a WiFi connection. - Supportability What support/debug features need to be provided for this process. Artefacts What is created, updated or deleted as a result of this business process Pre-conditions This section outlines the Pre-conditions prior to the execution of the basic flow. For instance there must be at least one valid site in the site list before the main functionality of the moodle app can be accessed. Assumptions may also be expressed here Ref Heading Description Post-Conditions How must the system or user interface be left after the execution of the basic flow. Authorization and Audit What roles are allowed access this functionality. Are there any confidentiality, Requirements auditor logging requirements. Business Rules Business rules referenced within the basic or alternative flows. For instance theire may be rules as to what constitutes a valid password e.g. One capital letter, One number, one non-numberalpha character where the password has not been used before in the last 6 months.. Issues Any potential issues identified which may cause problems in the deployment of this use case functionality. Assumptions What assumptions have been made e.g. a wifi network connection is available as opposed to an Edge or 3G connection Constraints Are there scheduling constraints, legal constraints, accessibility constraints, environment constraints Data model and metadata Description of any data required or stored in relation to this usecase. requirements For a photo graph, audio recording or video there maybe metadata such as the time takenrecorded, location of the recordingphotovideo. The focus is a business description of the data rather than a technical description of the data. For instance a use case may require a drop known list of participant types – administrator, teacher, student, reviewer they would be mentioned here If there was a particular XML format for publishing the site list to twitter or facebook then the specification or definition would be mentioned here. usecasenamecustomclosetv4-111211101506-phpapp01.docx Page 60 of 61