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

Econo 1

by: kamesh

Econo 1 TBD



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

This is what the description is
Class Notes
25 ?




Popular in Economics1

Popular in Economcs

This 11 page Class Notes was uploaded by kamesh on Tuesday September 22, 2015. The Class Notes belongs to TBD at DCH Regional Medical Center taught by Kristein in Summer 2015. Since its upload, it has received 23 views. For similar materials see Economics1 in Economcs at DCH Regional Medical Center.


Reviews for Econo 1


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/22/15
Functional Requirements Document Template Version Description of Change Author Date CONTENTS 1 INTRODUCTION 4 11 Purpose 4 12 Scope 4 13 Background 4 14 References 4 15 Assumptions and Constraints 4 16 Document Overview 5 2 METHODOLOGY 5 3 FUNCTIONAL REQUIREMENTS 5 41 Context 5 42 User Requirements 5 43 Data Flow Diagrams 6 44 Logical Data ModelData Dictionary 6 45 Functional Requirements 6 5 OTHER REQUIREMENTS 6 51 Interface Requirements 7 52 Data Conversion Requirements 7 53 HardwareSoftware Requirements 7 54 Operational Requirements 7 APPENDIX A GLOSSARY 11 1 INTRODUCTION Provide an overview of the system and some additional information to place the system in context 11 Purpose Provide an overall description of the FRD its purpose Reference the system name and identifying information about the system to be implemented 12 Scope Discuss the scope of the document and how it accomplishes its purpose 13 Background Describe the organization and its overall responsibilities Describe Who is producing the document and Why 14 References List references and controlling documents including meeting summaries White papers other deliverables etc 15 Assumptions and Constraints Provide a list of contractual or task level assumptions andor constraints that are preconditions to preparation of the FRD Assumptions are future situations beyond the control of the project Whose outcomes in uence the success of a project 151 Assumptions Examples of assumptions include availability of a technical platform legal changes and policy decisions 152 Constraints Constraints are boundary conditions on how the system must be designed and constructed Examples include legal requirements technical standards strategic decisions 0 Constraints exist because of real business conditions For example a delivery date is a constraint only if there are real business consequences that Will happen as a result of not meeting the date If failing to have the subject application operational by the specified date places the organization in legal default the date is a constraint 0 Preferences are arbitrary For example a date chosen arbitrarily is a preference Preferences if included in the FRD should be noted as such 16 Document Overview Provide a description of the document organization 2 METHODOLOGY Describe the overall approach used in the determination of the FRD contents Describe the modeling methods so nontechnical readers can understand what they are conveying 3 FUNCTIONAL REQUIREMENTS 41 Context Provide a context diagram of the system with explanations as applicable The context of a system refers to the connections and relationships between the system and its environment Exhibit 2 Generic Context Diagram DMa3 K quot DMa1 mmHaH Name1 mmHaH D Name2 WSeU 4rDMa2 Dam4 SyHem ApMmmmn Name Dam7 MtMMce DaM5 InMHaH Name3 Name4 V K DMa6 D ata8dv 42 User Requirements Provide requirements of the system user or business taking into account all major classescategories of users Provide the type of security or other distinguishing characteristics of each set of users List the functional requirements that compose each user requirement As the functional requirements are decomposed the highest level functional requirements are traced to the user requirements Inclusion of lower level functional requirements is not mandatory in the traceability to user requirements if the parent requirements are already traced to them User requirement information can be in text or process ow format for each major user class that shows What inputs Will initiate the system functions system interactions and What outputs are expected to be generated by the system The scenarios should be comprehensive to the extent that all user types and all major functions are covered Give each user requirement a unique number Typically user requirements have a numbering system that is separate from the functional requirements Requirements may be labeled With a leading U or other label indicating user requirements 43 Data Flow Diagrams Decompose the context level diagrams to determine the functional requirements Data ow diagrams should be decomposed down to the functional primitive level These diagrams are further decomposed during design 44 Logical Data ModelData Dictionary Create the initial Logical Data Model Describe data requirements by providing data entities decomposition and definitions in a data dictionary The data requirements describe the business data needed by the application system Data requirements do not describe the physical database and are not at the level of identifying field names 45 Functional Requirements List the functional requirements of the system 451 Functional Requirements Group 1 List the functional requirements for each functional requirements group Exhibit 4 Sample Requirements Group 1 Sectior Requirement ID Requirement Definition FR10 The system shall parent requirement group 1 FR11 The system shall childparent requirement FR111 The system shall child requirement FR112 The system shall child requirement 452 Functional Requirements Group 2 Etc 5 OTHER REQUIREMENTS Describe the nonbehavioral requirements 51 Interface Requirements Describe the user interfaces that are to be implemented by the system 511 Hardware Interfaces Define hardware interfaces supported by the system including logical structure physical addresses and expected behavior 512 Software Interfaces Name the applications with which the subject application must interface State the following for each such application name of application external owner of application interface details only if determined by the other application It is acceptable to reference an interface control document for details of the interface interactions 513 Communications Interfaces Describe communications interfaces to other systems or devices such as local area networks 52 Data Conversion Requirements Describe the requirements needed for conversion of legacy data into the system 53 HardwareSoftware Requirements Provide a description of the hardware and software platforms needed to support the system 54 Operational Requirements Provide the operational requirements in this section Do not state how these requirements will be satisfied For example in the Reliability section answer the question How reliable must the system be Do not state what steps will be taken to provide reliability Distinguish preferences from requirements Requirements are based on business needs preferences are not If for example the user requires a special response but does not have a businessrelated reason for it that requirement is a preference Other applicable requirements on system attributes may be added to the list of subsections below Operational requirements describe how the system will run and communicate with operations personnel 541 Security and Privacy Provide a list of the security requirements using the following criteria A State the consequences of the following breaches of security in the subject application 1 Loss or corruption of data 2 Disclosure of secrets or sensitive information 3 Disclosure of privilegedprivacy information about individuals 4 Corruption of software or introduction of malware such as viruses B State the types of security required Include the need for the following as appropriate 1 Physical security 2 Access by user role or types 3 State access control requirements by data attribute For example one group of users has permission to view an attribute but not update it while another group of users has permissions to update or view it 4 State access requirements based on system function For example if there is a need to grant access to certain system functions to one group of users but not to another For example quotThe system shall make Function X available to the System Administrator onlyquot 5 State if there is a need for certification and accreditation of the security measures The Security Section describes the need to control access to the data adopted for this application This includes controlling who may view and alter application data 542 Audit Trail List the activities recorded in the application s audit trail For each activity list the data recorded 543 Reliability A State the following in this section 1 State the damage can result from failure of this system indicate the criticality of the software such as a Loss of human life b Complete or partial loss of the ability to perform a missioncritical function 0 Loss of revenue d Loss of employee productivity 2 What is the minimum acceptable level of reliability B State required reliability 1 MeanTimeBetweenFailure is the number of time units the system is operable before the first failure occurs 2 MeanTimeToFailure is the number of time units before the system is operable divided by the number of failures during the time period 3 MeanTimeToRepair is the number of time units required to perform system repair divided by the number of repairs during the time period Reliability is the probability that the system processes work correctly and completely without being aborted 544 Recoverability Answer the following questions in this section A In the event the application is unavailable to users down because of a system failure how soon after the failure is detected must function be restored B In the event the database is corrupted to what level of currency must it be restored For example The database must be capable of being restored to its condition of no more than 1 hour before the corruption occurred C If the processing site hardware data and onsite backup is destroyed how soon must the application be able to be restored Recoverability is the ability to restore function and data in the event of a failure 545 System Availability State the period during which the application must be available to users For example The application must be available to users Monday through Friday between the hours of 630 am and 530 pm EST If the application must be available to users in more than one time zone state the earliest start time and the latest stop time Consider daylight savings time too Include use peak times These are times when system unavailability is least acceptable System availability is the time when the application must be available for use Required system availability is used in determining when maintenance may be performed 546 General Performance Describe the requirements for the following A Response time for queries and updates B Throughput C Expected rate of user activity for example number of transactions per hour day or month or cyclical periods Specific performance requirements related to a specific functional requirement should be listed with that functional requirement 547 Capacity List the required capacities and expected volumes of data in business terms Do not state capacities in terms of system memory requirements or disk space if growth trends or projections are available provide them 548 Data Retention Describe the length of time various forms of data must be retained and the requirements for its destruction For example The system shall retain application information for 3 years Different forms of data include system documentation audit records database records access records 549 Error Handling Describe system error handling 5410 Validation Rules Describe System Validation Rules 5411 ConventionsStandards Describe system conventions and standards followed For example Microsoft standards are followed for windows Institute of Electrical and Electronics Engineers IEEE for data formats etc APPENDIX A GLOSSARY Define terms acronyms and abbreviations used in the FRD


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

Anthony Lee UC Santa Barbara

"I bought an awesome study guide, which helped me get an A in my Math 34B class this quarter!"

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.