New User Special Price Expires in

Let's log you in.

Sign in with Facebook


Don't have a StudySoup account? Create one here!


Create a StudySoup account

Be part of our community, it's free to join!

Sign up with Facebook


Create your account
By creating an account you agree to StudySoup's terms and conditions and privacy policy

Already have a StudySoup account? Login here


by: Mrs. Maximo Lueilwitz


Mrs. Maximo Lueilwitz
GPA 3.95


Almost Ready


These notes were just uploaded, and will be ready to view shortly.

Purchase these notes here, or revisit this page.

Either way, we'll remind you when they're ready :)

Preview These Notes for FREE

Get a free preview of these Notes, just enter your email below.

Unlock Preview
Unlock Preview

Preview these materials now for free

Why put in your email? Get access to more of this material and other relevant free materials for your school

View Preview

About this Document

Class Notes
25 ?




Popular in Course

Popular in ComputerScienence

This 3 page Class Notes was uploaded by Mrs. Maximo Lueilwitz on Monday October 19, 2015. The Class Notes belongs to CS 361 at Oregon State University taught by Staff in Fall. Since its upload, it has received 21 views. For similar materials see /class/224499/cs-361-oregon-state-university in ComputerScienence at Oregon State University.

Similar to CS 361 at OSU

Popular in ComputerScienence




Report this Material


What is Karma?


Karma is the currency of StudySoup.

You can buy or earn more Karma at anytime and redeem it for class notes, study guides, flashcards, and more!

Date Created: 10/19/15
Req u ire me nts Review Requirements Elicitation I Customers do not always understand what their needs and problems are I It is important to discuss the requirements with everyone who has a stake in the system I Come up with agreement on what the requirements are I If we cannot agree on what the requirements are then the project is doomed to fail Means of Eliciting Requirements I Interviewing stake holders I Reviewing available documentations I Observing the current system if one exists I Apprenticing with users to learn about user39s task in more details I Interviewing users or stakeholders in groups I Using domain specific strategies such as Joint Application Design or PIECES I Brainstorming with current and potential users Types of Requirements I Functional requirement describes required behaviour in terms of required activities I Quality requirement or nonfunctional requirement describes some quality characteristic that the software must possess I Design constraint a design decision such as choice of platform or interface components I Process constraint a restriction on the techniques or resources that can be used to build the system Characteristics of Requirements I Correct I Consistent I Unambiguous I Complete I Feasible I Relevant I Testable I Traceable Making Requirements Testable I Fit criteria form objective standards for judging whether a proposed solution satisfies the requirements I It is easy to set fit criteria for quantifiable requirements I It is hard for subjective quality requirements I Three ways to help make requirements testable I Specify a quantitative description for each adverb and adjective I Replace pronouns with specific names of entities I Make sure that every noun is defined in exactly one place in the requirements documents Resolving Conflicts I Different stakeholder has different set of requirements I potential conflicting ideas I Need to prioritize requirements I Prioritization might separate requirements into three categories I essential absolutely must be met I desirable highly desirable but not necessary I optional possible but could be eliminated Two Kinds of Requirements Documents I Requirement definition a complete listing of everything the customer wants to achieve I Describing the entities in the environment where the system will be installed I Requirements specification restates the requirements as a specification of how the proposed system shall behave Risk Management Review I Five common sources of risk I Processes of Identifying Risks I Addressing Risk I Avoidance I Mitigation I I I Risk Exposure I Risk Probability I Total Potential Cost of Risk UML Review I Domain Specific Modeling I Allows more detail for any one domain but can be harder to understand if you are not familiar with the domain I Standard Language eg UML I Broader use may allow easier communication but the standard may not meet the needs of each and every domain requiring extensions to be added Four Models Using UML Notation I EntityRelationship Diagram I Event Traces I State Machines I DataFlow Diagrams


Buy Material

Are you sure you want to buy this material for

25 Karma

Buy Material

BOOM! Enjoy Your Free Notes!

We've added these Notes to your profile, click here to view them now.


You're already Subscribed!

Looks like you've already subscribed to StudySoup, you won't need to purchase another subscription to get this material. To access this material simply click 'View Full Document'

Why people love StudySoup

Steve Martinelli UC Los Angeles

"There's no way I would have passed my Organic Chemistry class this semester without the notes and study guides I got from StudySoup."

Janice Dongeun University of Washington

"I used the money I made selling my notes & study guides to pay for spring break in Olympia, Washington...which was Sweet!"

Jim McGreen Ohio University

"Knowing I can count on the Elite Notetaker in my class allows me to focus on what the professor is saying instead of just scribbling notes the whole time and falling behind."


"Their 'Elite Notetakers' are making over $1,200/month in sales by creating high quality content that helps their classmates in a time of need."

Become an Elite Notetaker and start selling your notes online!

Refund Policy


All subscriptions to StudySoup are paid in full at the time of subscribing. To change your credit card information or to cancel your subscription, go to "Edit Settings". All credit card information will be available there. If you should decide to cancel your subscription, it will continue to be valid until the next payment period, as all payments for the current period were made in advance. For special circumstances, please email


StudySoup has more than 1 million course-specific study resources to help students study smarter. If you’re having trouble finding what you’re looking for, our customer support team can help you find what you need! Feel free to contact them here:

Recurring Subscriptions: If you have canceled your recurring subscription on the day of renewal and have not downloaded any documents, you may request a refund by submitting an email to

Satisfaction Guarantee: If you’re not satisfied with your subscription, you can contact us for further help. Contact must be made within 3 business days of your subscription purchase and your refund request will be subject for review.

Please Note: Refunds can never be provided more than 30 days after the initial purchase date regardless of your activity on the site.