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

Intro to Software Engineering

by: Abe Jones

Intro to Software Engineering CS 230

Marketplace > West Virginia University > ComputerScienence > CS 230 > Intro to Software Engineering
Abe Jones
GPA 3.77


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 4 page Class Notes was uploaded by Abe Jones on Saturday September 12, 2015. The Class Notes belongs to CS 230 at West Virginia University taught by Staff in Fall. Since its upload, it has received 11 views. For similar materials see /class/202773/cs-230-west-virginia-university in ComputerScienence at West Virginia University.

Similar to CS 230 at WVU

Popular in ComputerScienence


Reviews for Intro to Software Engineering


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: 09/12/15
1 Equot 3 4 Sample Format of Requirements De nition Document Based on IEEE Standard 830 Software Requirements Speci cations Introduction Provide an overview of the complete document 11 Purpose De ne the purpose of the document and for whom it is written 12 Scope gt Name of the product gt What the product will do gt What the product will not do gt Description of the bene ts goals and objectives 13 Def39mitionsAbbreviations gt De nition of all the terms gt Acronyms and abbreviations used in the document Note Special attention should be paid to the clari cation of terms and concepts from the domain of application 14 References References to all documents that are referred to in the remainder of the requirement speci cation 15 Overview Outline of the remainder of the document and its organization General Description 21 Product perspective gt Is this an independent product or is it part of a larger product gt If it is part of larger product identify the other components and describe the interfaces with those components gt De ne the interfaces to other applications gt Identify the hardware to be used 22 System Evolution gt Description of the life cycle model to be used gt Training setup intended gt Installation method intended 23 Product Functions An overview of the functions of the system to be delivered Note Detailed discussion of the functions will be given in the Requirements Speci cation Document 24 Users of the product Identify the potential users of the product For each category of user describe general user characteristics relevant for the requirements speci cation These include experience training educational level technical expertise and assigned priorities 25 General Constraints Indicate any constraints that apply These may concern government regulations hardware constraints security regulations and so on 26 Assumptions and dependencies This does not concern constraints on the system to be developed but things which may in uence the requirements speci cation once they change Context diagram Use case diagram Sample Format of Requirements Speci cations Document Based on IEEE Standard 830 Software Requirements Speci cations This document contains all details which are relevant for the design phase to follow 1 Analysis modeling 11 Specify data entities and relationship between them using an Entity Relationship Diagram or a Class Diagram 12 Specify the information ow and the transforms that are applied as data move from input to output using a Data Flow Diagram or specify the dynamic behavior using Sequence Diagrams 2 Functional requirements This subsection describes how the transformation of inputs to outputs is achieved The following description is given for each individual function 21 Name of the function 22 Description of the function A description of the purpose of this function 23 Inputs A precise description of the function s inputs gt Source howwherewho provides the input gt Range of acceptable values 24 Processing A definition of the operations that must be performed such as checking for acceptable values reaction to abnormal situations or a description of the algorithms to be used 25 Outputs A precise description of the function s outputs gt Destination howwherewho receives the output gt Error messages 26 Pre condition What must be true before the function is called 27 Post condition What is true after the function is called 28 Requirements Indication of what other entities are used that are not directly input 29 Side effects not directly related to output items 210 Annotation 2101 Stability Will the needs change during the expected life of the product 2102 Degree of necessity gt Mandatory 7 software will not be acceptable unless this function is provided in an agreed manner gt Desirable 7 this function would enhance the software product but would not make it unacceptable if it is absent gt Optional 7 this function may or may not be worthwhile 3 Non functional requirements 31 External interface requirements 311 User interfaces A description of the characteristics of the user interfaces such as screen layout function keys help functions 312 Hardware interfaces A description of the logical characteristics of hardware interfaces 313 Software interfaces A description of software needed such as a certain operating system or software package Interfaces to other application software are also discussed here 314 Communication interfaces An example is a communication protocol 32 Performance requirements Performance requirements encompass both static and dynamic requirements Static requirements concern amongst others the number of terminals to be connected and the number of users to be handled concurrently Dynamic requirements concern operational performance of the system how frequently will certain functions be called for and how fast should the system s reaction be These requirements should be stated in measurable terms 33 Design constraints 331 Standard compliance Existing standards or regulations that must be followed and the requirements that result from these 332 Hardware limitations A description of the characteristics of the hardware as far as they lead to software requirements 34 Quality attributes In this section particular attention is paid to quality aspects These requirements must be measurable and veri able 341 Availability Factors that guarantee a certain level of availability such as restart procedures redundancy etc 342 Security Requirements regarding unauthorized access and others form of misuse These include cryptographic techniques constraints on the access and communication 343 Portability Requirements regarding the portability of the software to different hardware platforms andor different operating systems 344 Maintainability Requirements to guarantee a certain level of maintainability of the system 35 Other requirements A description of requirements that are specific to certain software and which have not been discussed yet Sample Format of the Acceptance Test Plan The purpose of the acceptance test plan is to describe the tests that must be performed to demonstrate all features of the product For each function in your speci cation individual test plans should be developed for testing correctness and robustness They should include data which exhibit both normal functionality and error conditions


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

Bentley McCaw University of Florida

"I was shooting for a perfect 4.0 GPA this semester. Having StudySoup as a study aid was critical to helping me achieve my goal...and I nailed it!"

Allison Fischer University of Alabama

"I signed up to be an Elite Notetaker with 2 of my sorority sisters this semester. We just posted our notes weekly and were each making over $600 per month. I LOVE StudySoup!"

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."

Parker Thompson 500 Startups

"It's a great way for students to improve their educational experience and it seemed like a product that everybody wants, so all the people participating are winning."

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.