Nc3 adl 2013 successful project bus req

Hope Opportunity Jobs

Want a successful project? Good business requirements are an

essential component.

Vicki Strayer – NC Community College System Office Chris Cline – NC Community College System Office


Audience Participation

• Need a volunteer

• How do you brush your teeth?


Contents of the Business Requirements

• Purpose of the Business Requirements

• Overview of Life Cycle Process

• Introduction

• Overview of Business Requirements Document

• Document Revision History

• Introduction

• Scope

• Assumptions and Constraints


Contents continued

• Glossary

– Technical Terms

• Business Requirements Table Key

• Business Objectives

• Business Objectives and Related Business Requirements

• Stakeholder Sign-off

• Appendix


Why are the business terms important?

• Simple. The same work can carry two different meanings. For example Full-Time Student – Registered for more than three and one-half full

course equivalents

– An undergraduate student registered for 12 or more semester credits – NCSU definition

– Student registered for 16 or more hours – NCCCS definition

– Student registered for 12 to 18.5 semester hours

– Five to six hours if a student is working


What happens after the Business Requirements are

complete? • Detail Design

• Development

• Unit Test

• System Test

• User Acceptance Testing

• Beta Test

• Beta Live

• General Availability


Why are business requirements important?

• 1/3 of budget to correct errors originate from business requirements

• Defining business requirements is critical to the success of the project and is important for all stakeholders

• Several ways to collect good business requirements, including Use Cases and User Stories

9/27/2013 8


What is a Use Case?

• Describes how the system should respond under various conditions to a request from a stakeholder (primary actor) to deliver a specific goal

• Usually done in the form of a scenario that defines a sequence of steps

• May have a primary actor and supporting actors

9/27/2013 9


Use Case should be iterative

• Identify all actors and their goals

• Use MoSCoW list to define the scope of the project

• Set up and actor/goal list

9/27/2013 10


MoSCoW

• Must Have – essential component for project

• Should Have – should be included but if it is not included upon initial delivery, a workaround can be successfully implemented

• Could Have – if we can complete within time and budget we will include

• Won’t Have – not necessary for the success of the project

9/27/2013 11


Best Practices

• Action Verb + Qualified Object

• Avoid Vague Verbs (Do, Process, etc.)

• Avoid database-oriented Verbs (Create, Read, Update, Delete)

• Include definitions

• Associate Actors and Use Cases

• Use Cases should be created first and can be used during testing

9/27/2013 12


Use Case Diagram

9/27/2013 13


Use Case Example • Use Case Name: Place Order • Actors:

– Shopper – Fulfillment System – Billing System

• Use Case Description: After the user has selected items to purchase, they can then order the items. The user will provide payment and shipping information. The system will respond with confirmation of the order and a tracking number that the user can use to check on order status in the future. The system will also provide the user with an estimated delivery date for the order, which will include all selected items. The user may already have an account with the company with billing and shipping information.

9/27/2013 14


Use Case Example

• Actors: – Registered Shopper (Has an existing account, possibly with billing and shipping

information) – Non-registered Shopper (Does not have an existing account) – Fulfillment System (processes orders for delivery to customers) – Billing System (bills customers for orders that have been placed)

• Triggers: – The user indicates that she wants to purchase items that she has selected.

• Preconditions: – User has selected the items to be purchased.

• Post-conditions: – The order will be placed in the system. – The user will have a tracking ID for the order. – The user will know the estimated delivery date for the order.

9/27/2013 15


Use Case Example

• Normal Flow: – The user will indicate that she wants to order the items that have already been selected. – The system will present the billing and shipping information that the user previously

stored. – The user will confirm that the existing billing and shipping information should be used

for this order. – The system will present the amount that the order will cost, including applicable taxes

and shipping charges. – The user will confirm that the order information is accurate. – The system will provide the user with a tracking ID for the order. – The system will submit the order to the fulfillment system for evaluation. – The fulfillment system will provide the system with an estimated delivery date. – The system will present the estimated delivery date to the user. – The user will indicate that the order should be placed. – The system will request that the billing system should charge the user for the order. – The billing system will confirm that the charge has been placed for the order. – The system will submit the order to the fulfillment system for processing. – The fulfillment system will confirm that the order is being processed. – The system will indicate to the user that the user has been charged for the order. – The system will indicate to the user that the order has been placed. – The user will exit the system.

9/27/2013 16


…but I just have a simple project/ initiative: User Stories

•Who are the users?

•What do the users want?

•How do I to get the details from the users?


Who are the users?

• Pet lovers with cameras

• People who need to spice up presentations

• Web designer who loves to do web design

• Site administrator for www.cutepets.com

So I'm creating an application for posting, rating, and commenting on THE CUTEST pet pictures ever.


What do the users want?

• Pet lovers – recognition of a cute pet

• Presentation people – quickly find cute pet pictures

• Web designer – recognition of cool and creative site

• Site administrator for www.cutepets.com – make sure pictures are appropriate and ensure hackers can’t add inappropriate pictures or text

For each user in your list, what do they want from your site? Why would they visit it in the first place? How will it make their life better?

http://www.cutepets.com/


How do I get the details from the users?...User Stories

"As a __(type of user)__, I can __(description of task)__ so that __(motivation)__."

Each user story should be one to three sentences long, and should briefly describe (in non-technical language that the user themselves would understand) how the user accomplishes a task on your site.


User Story Examples

"As a pet owner, I can post pictures of my pet and have them credited to my username so people know that's my pet.“

"As a pet owner, I see how many people “like” my pet pictures, so I can be recognized

for my awesomely cute pet.“

"As a presentation creator, I can sort the pictures on the site by how many “likes” they've gotten, so that I can quickly find the cutest ones.“

"As the web designer, I can copy photos from the site, photoshop them in funny ways, and then re-upload them with a link to the original, so that people see how witty and

talented I am.“

"As a site administrator, I want users to be able to flag offensive photos so I can quickly check them out, so users aren't driven away from the site."


How do I get started?

Hope Opportunity Jobs 9/27/2013 23

Questions?


References

• Sehlhorst, Scott (2009). Sample Use Case Example. http://tynerblain.com/blog/2007/04/09/sample-use-case-example/

9/27/2013 24

http://tynerblain.com/blog/2007/04/09/sample-use-case-example/









Nc3 adl 2013 successful project bus req

Business

Transcript of Nc3 adl 2013 successful project bus req