]project-open[ Development Methodology. ]project-open[ Development cycle Functional analysis...

]project-open[

Development Methodology

]project-open[Development cycle

Functional analysis

Decision point

Structured Analysis

Prototype User Test ProductMaintenan

ceDefinition

Decision point

]project-open[Project Definition

Functional analysis

Structured Analysis


ceDefinition

Business Idea ROI Analysis Priorization

Cost

Impact (ROI)

Dependency

50k€ 400k€200k€100k€24m

12m

6m

3m

Project 7

Project 2

Project 1 Project 5

Project 6

Project 9

Project 4

Project 3

Project 8

Decision pointDecision point

]project-open[Functional analysis

Functional analysis

Structured Analysis


ceDefinition

Logic Wemo Use Cases


]project-open[Structured analysis

Functional analysis

Structured Analysis


ceDefinition

Data Model

Test Cases


]project-open[Structured analysis

Functional analysis

Decision point

Structured Analysis


ceDefinition

Decision point

Prototype Market Test

phase I

phase II

phase ...

Structured analysis can break the project into pieces to be delivered in phases

]project-open[Prototyping

Functional analysis

Decision point

Structured Analysis


ceDefinition

Decision point

Development Unit Testing Integration testing in

staging server

]project-open[ Development cycle: User test

Functional analysis

Structured Analysis


ceDefinition

Decision point

Acceptance test with advanced users

Business test

Decision point

]project-open[ Development cycle: product

Functional analysis

Structured Analysis


ceDefinition

Decision point

ConsolidationThe new idea is developed and productiveSmall improvements and corrections

Decision point

]project-open[Considerations

Functional analysis

Decision point

Structured Analysis


ceDefinition

Decision point

found problems in a phase can force re-study of previous phases

the sooner the better

]project-open[ Development cycle: considerations

Functional analysis

Decision point

Structured Analysis


ceDefinition

Decision point

is standard allows a controlled way

of develop must be followed for any

new business idea

]project-open[Considerations

Functional analysis

Structured Analysis


ceDefinition

is standard allows a controlled way

of develop must be followed for any

new business idea


]project-open[ Static HTML Mockup (Wemo)

If you wish to add a new shipping address in your register profile, contact your clustermanager at [email protected]

Please choose the deliverydate inwhich you would like to receive your bids, aswell as the appropiate shipping address*.

Desea Continuar ?

* If you wish to ship this order to a different shipping address, contact your clustermanager at [email protected]

ShippingBilling

Details -DetailsTejidon S.L. Almacen1 (Cabrera)

Almacen 2 (Mataró)

Desired Delivery Date

ShippingBilling


Almacen 2 (Mataró)


OK

OK

Please choose the deliverydate inwhich you would like to receive your bids, aswell as the appropiate shipping address*.

Desea Continuar ?

* If you wish to ship this order to a different shipping address, contact your clustermanager at [email protected]

ShippingBilling


Almacen 2 (Mataró)


ShippingBilling


Almacen 2 (Mataró)


OK

OK

]project-open[

9 1 P l a u s i b i l i t y c h e c k s R u l e s ( b u s i n e s s r u l e s , d e p e n d e n c i e s i n t h e b u s i n e s s , f o r m u l a e , v a l i d i t y a n d v a l i d a t i o n r u l e s )

O n l y – b u t a l l - - L i v i n g C o n t r a c t D A s w h e r e U s e r i s w i n n e r a r e d i s p l a y e d / s e l e c t a b l e O n l y – b u t a l l – o r d e r s w i t h s t a t u s ' r e g i s t e r e d ' o r ' n o t i f i e d ' o f t h e u s e r a r e s h o w n

1 0 2 M a s k l a y o u t / p r o t o t y p e G r a p h i c a l u s e r i n t e r f a c e

M a i n S c r e e n O r d e r s S c r e e n P o s t O r d e r S c r e e n s O r d e r D e t a i l s S c r e e n

1 1 3 P r i n t l a y o u t L a y o u t ( P r i n t o u t , f o r m , t e m p l a t e s )

N o n a p p l i c a b l e

1 2 4 D i a g r a m s

1 2 . 1 4 . 1 [ S e q u e n c e d i a g r a m s ] R e p r e s e n t a t i o n o f t h e c h r o n o l o g i c a l s e q u e n c e o f p r o c e s s i n g

1 2 . 2 4 . 2 [ A c t i v i t y d i a g r a m s , d e s c r i p t i o n o f a c t i v i t i e s ] B u s i n e s s p r o c e s s e s , f l o w c h a r t s F o u n d u n n e c e s s a r y

1 2 . 3 4 . 3 [ S t a t e d i a g r a m s ] D e s c r i p t i o n o f t h e s t a t e / s t a t e d i a g r a m o f p a r t s ( o b j e c t s ) o f t h i s u s e c a s e F o u n d u n n e c e s s a r y

G e n e r a l w o r k f l o wT r a d i n g u s e r S y s t e m

l o g i n v a l i d a t e

P M

d i s p l a y m a i n s c r e e n

S e l e c t ‘ O r d e r s ’ o p t i o n d i s p l a y ‘ o r d e r ’ s c r e e n

S e l e c t ‘ P o s t O r d e r ’ o p t i o n

d i s p l a y ‘ p o s t o r d e r ’ s c r e e n

D e f i n e q u a n t i t i e s f o r r e q u i r e d v a r i e t i e s

r e g i s t e r q u a n t i t i e s

D e f i n e d e l i v e r y d a t e a n d a d d r e s s e s

r e g i s t e r d a t a a n d a d d r

C o n f i r m o r d e r R e g . o r d e r

N o t i f y P M n o t i f y s e l l e r

S e t n o t i f i e d o r d e rC h a n g e o r d e r s t a t u s

S e l e c t ‘ D e t a i l s ’ o p t i o n d i s p l a y ‘ D e t a i l s ’ s c r e e n

D i s p l a y ‘ o r d e r ’ s c r e e n

S e l e c t ‘ B a c k ’ o p t i o n d i s p l a y ‘ O r d e r ’ s c r e e n

L o g o u t L o g o u t u s e r

Pos

t B

idch

eck

deta

ils

1 Short description Short description of the business requirements.

A trading User logs in the system and the option 'Orders' is offered. This option allows the user to consult the posted orders and to post new ones on the ongoing contract DAs. PM is notified on new orders to process them off-line.

2 Actors Users, other systems, interfaces Trading user System PM

3 Triggering event Trading user wants to consult her posted orders and/or post new ones on ongoing contract DAs

4 Preconditions Necessary conditions for this use case; State of the system before entering the basic course of actions

Trading user has to be registered in the system. User has to appear as a winner of a Contract DA (to be able to post orders) There are "alive" Contract DAs i.e. current date should be in some DA's living period (to be able to consult orders) There are posted orders that have not been removed

5 Basic course of action Description of the proceeding of the normal case without exceptions and special cases

Step Actor Description 1 User Logs in the system 2 System Validates user and (on success) displays main screen 3 User Selects 'Orders' option 4 System Displays 'Order' screen containing the living DAs and posted orders 5 User Selects 'Post order' on a living DA or 'Details' on posted orders 6 System Displays corresponding screen 7 User Posts order or consults details and comes back 8 System Displays main screen 9 User Logs out

6 Special cases/variants/messages Description of the proceeding in special cases, ... Special Case: Case Name Description 1 User has no living DA No living DA will be displayed in the main screen, therefore it will not

be possible to post an order. 2 User has no orders No orders will be displayed in the main screen, therefore it will not be

possible to see details

7 Result Result of the successfully performed basic course of action

Trading User has post orders on living DAs and/or consult existing order's status

8 Post conditions (pos. result) Further results which were not the objective of the basic course; State of the system after the basic course of actions None

Use Cases

]project-open[

ContractOrder

Tracking

cl_bid_line cl_bid_multi_product

cl_bid_order

cl_bid_order_spec

cl_user

cl_product_attribute

cl_da_linecl_da_multi_product

cl_da_period

DAMPS

cl_da_line

cl_line_spec_pm

cl_da_multi_product cl_bid_line cl_bid_multi_product

cl_user

cl_attribute_value

cl_product_attribute

cl_product_class

cl_bid_line_spec

cl_line_spec_user

cl_status_da

cl_da_invitation_mp

cl_transaction_result

User Registration

cl_user

cl_tenant

users

cl_portal

cl_cluster

cl_legacy

user_groups cl_portal_logos

cl_language

cl_activity cl_user_activity

Data Model

]project-open[

1 Test contents Test contents are the expected ones

Step Description Result 1 Logs in the system as the selected user 2 Press 'Orders' button 3 Check 'Orders' screen contents about living DAs

DA ids correspond to contract DAs user has won Product classes correspond to DAs Sellers correspond to DAs Periods correspond to DAs DA ids correspond to living DAs = current day is within all the periods All the living DAs where this user has won are present in this screen

4 Check 'Orders' screen contents about orders DA ids correspond to contract DAs user has won Order ids correspond to orders related to the DAs and user Product classes correspond to DAs Variant attributes and values correspond to order variant's Sellers correspond to DAs Delivery dates correspond to orders Quantities correspond to order variant's Status correspond to order variant's

5 Log out

2 Test language Test language is the expected one

Step Description en es it 1 Log in the system as the selected user 2 Check 'Orders' button appears in the correct language 3 Press 'Orders' button 4 Check 'Orders' screen title is in the correct language 5 Check 'Orders' screen living DAs title is in the correct language 6 Check 'Orders' screen living DAs table headers are in the correct language 7 Check 'Orders' screen living DAs buttons are in the correct language 8 Check 'Orders' screen Orders title is in the correct language 9 Check 'Orders' screen Orders table headers are in the correct language 10 Check 'Orders' screen Orders buttons are in the correct language 11 Perform Test Case Order Tracking 1 Post Order v.1.0.rtf section 2 Test

language

12 Perform Test Case Order Tracking 1 Check Order Details v.1.0.rtf section 2 Test language

13 Log out 14 Change User language and return to step 1 until all the languages have been tested

63 Test special cases/variants/messages Description of the testing proceeding in special cases, variants, messages Special Case: Case Name Description Result 1 No living DAs Check an user without living DAs: 'Orders' screen should display

no lines in living DAs table

2 No orders Check an user without orders: 'Orders' screen should display no lines in the orders table

1 Test case goals Short description of the test case goals

Test Order Tracking functionalities for the Trading User: post order and check order details

2 Test case performing data Information about the test case performing

Tester name Testing date Comments

23 Actors Users, other systems, interfaces Trading user System PM

4 Preconditions Necessary actions to be taken to prepare the system for performing this test case.

Description Done Select a trading user registered in the system or check in a new one Select a product (or create a new one) with at least the following kind of attributes:

An attribute that has specified the values (drop down) Two attributes without specific values

Open a Contract DA of the selected product with the following variants Has at least a fixed attribute Has at least a free attribute that must be defined during the bid posting Has at least a free attribute that can be left undefined during the bid posting

Specify a period that starts today and Invite the selected user

(to be able to post orders) There are "alive" Contract DAs i.e. current date should be in some DA's living period

(to be able to consult orders) There are posted orders that have not been removed User post a bid for each DA PM marks bids of this user as winners and specify a different price for each one

5 Test basic course of action Testing steps for the proceeding of the normal case without exceptions and special cases (results: pass; error)

Step Description Result 1 Log in the system as the selected user 2 Check main screen appears with 'Orders' button 3 Press 'Orders' button 4 Check 'Orders' screen appears containing living DAs 5 Perform Test Case Order Tracking 1 Post Order v.1.0.rtf section 5 Test basic

course of action

6 Perform Test Case Order Tracking 1 Check Order Details v.1.0.rtf section 5 Test basic course of action

7 Log out

Test Cases

]project-open[ Development cycle: program

]project-open[ Development Methodology. ]project-open[ Development cycle Functional analysis...

Documents

Transcript of ]project-open[ Development Methodology. ]project-open[ Development cycle Functional analysis...