21
Half day Workshop

Code workshop

Embed Size (px)

Citation preview

Page 1: Code workshop

Half day Workshop

Page 2: Code workshop

Syed Mansoor Ahmed

(Project Manager)

Proud Wiproite from last 10 Yrs

Leads AppC Automation team

[email protected]

Ankit Kashyap

(Analyst Programmer)

Proud Wiproite from last 5.9 Yrs

Developer for AppC tools

[email protected]

Page 3: Code workshop
Page 4: Code workshop
Page 5: Code workshop

http://en.wikipedia.org/wiki/User_story

• A user story is one or more sentences in the

everyday or business language of the end user or

user of a system that captures what a user does or

needs to do as part of his or her job function.

• Basis for defining the functions a business system

must provide, and to facilitate requirements

management.

• It captures the 'who', 'what' and 'why' of a requirement

in a simple, concise way, often limited in detail by

what can be hand-written on a small paper notecard.

• User stories are written by or for the business user as

that user's primary way to influence the functionality

of the system being developed. User stories may also

be written by developers to express non-functional

requirements (security, performance, quality, etc.)

Page 6: Code workshop

• "As a <role>, I want <goal/desire> so that <benefit>"

• "As a <role>, I want <goal/desire>"

• "In order to <receive benefit> as a <role>, I want

<goal/desire>"

• "As <who> <when> <where>, I <what> because

<why>."

Page 7: Code workshop

• As a user, I want to search for my customers by their first and last

names.

• As a non-administrative user, I want to modify my own schedules but not

the schedules of other users.

• As a mobile application tester, I want to test my test cases and report

results to my management.

Page 8: Code workshop
Page 9: Code workshop

Transition

Role

Question

Employee

Page 10: Code workshop

And Put some dummy data

Page 11: Code workshop
Page 12: Code workshop

• What are the required fields for creating a Transition Tkt?

• Make a Sproc – Test it!

• Make a Corresponding method in DB Layer

• Now, make form

• On submit button, fetch data from UI and pass to the DB Layer!

Page 13: Code workshop
Page 14: Code workshop

• What we need to show on UI?

• Write a Sproc – Test it!

• Make a Corresponding method in DB Layer

• In Page Load method, fill the GridView with the data

Page 15: Code workshop

• What we need to show on UI?

• Write a Sproc – Test it!

• Make a Corresponding method in DB Layer

• In Page Load method, fill the GridView with the data

Page 16: Code workshop

• What we need to show on UI?

• Write a Sproc – Test it!

• Make a Corresponding method in DB Layer

• Make UI with controls

• In Page Load method, wire up data with controls

Page 17: Code workshop

• What we need to show on UI?

• Write a Sproc – Test it! (Can we use View page’s Sproc)

• Make a Corresponding method in DB Layer for initial Data

• Make UI with controls

• In Page Load method, wire up data with controls

• On Submit, update database with each question status

Look and feel of Update page should be

same as View Page

Page 18: Code workshop

• My/All Page with Completion %

• Place Edit/View Links in “My” and “All” Pages.

• Place Edit button on View Page.

• Time for Validation!!!!

Page 19: Code workshop

Unit Tests

Source version control

Documentation – SRS? User manual?

Client Side validation

CSS

Logos/Access control

Provision for adding new Questions

Page 20: Code workshop
Page 21: Code workshop