Functional User Requirements - answer-A subset of the user requirements
Requirements that describe what the SW should do in terms of tasks and services
Functional User Requirements Include: - answer-Data Transfer
Data Transformation
Data Storage
Data Retrieval
Technical Requirements Chara...
FUNCTION POINT ANALYSIS EXAM
Functional User Requirements - answer-A subset of the user requirements
Requirements that describe what the SW should do in terms of tasks and services
Functional User Requirements Include: - answer-Data Transfer
Data Transformation
Data Storage
Data Retrieval
Technical Requirements Characteristics - answer-Dependent on technology
Terminology unfamiliar to the user may be used
Functionality may be determined by placing too much emphasis on technical constraints
Boundaries may be determined according to the technical architecture rather than business
processes
Purpose of Function Point Count - answer-Determine the type of FP count and the scope of the
required count to obtain the answer to the business problem
Influence the positioning of the boundary between the SW under review and the surrounding SW
Data Function - answer-Represents functionality provided to the user to meet internal and
external data storage requirements
Either an External Interface File (EIF) or Internal Logical File (ILF)
ILF Primary Intent - answer-Hold data maintained through one or more elementary processes of
the application being measured
ELF Primary Intent - answer-Hold data referenced through one or more elementary processes
within the boundary of the application being measured
Rules for Counting RETs - answer-Count one RET for each data function
Count one additional RET for each of the following additional logical subgroups of DETs
(within the data function) that contains more than one DET:
-Associative entity with non-key attributes
-Subtype (other than the first subtype)
-Attributive entity, in a relationship other than mandatory 1-1
Do not count RETs for any data that exists because technology or methodology (headers, trailers,
separate text files)
Elementary Process - answer-Smallest unit of activity that is meaningful to the user
-Is meaningful to the user
-Constitutes a complete transaction
-Is self-contained
-Leaves the business of the application being counted in a constant state
Data Entities - answer-Business Data
, Reference Data
Code Data
Business Data - answer-Aka Core User Data or Business Objects
Reflects the information needed to be stored and retrieved by the functional area addressed by
the application
Business Data Logical Characteristics - answer-Data is mandatory for operation of the users'
functional area
Data is user identifiable (usually by a business user)
Data is user maintainable (usually by a business user)
Data stores the users' Core User Data to support business transactions
Data is very dynamic in that normal business operations cause it to be regularly referenced and
routinely added to, changed, or deleted
Data is reported on
Business Data Physical Characteristics - answer-Data has key fields and usually many attributes
Data may have 0 - infinity records
Reference Data - answer-Stored to support the business rules for the maintenance of the Business
Data
Reference Data Logical Characteristics - answer-Data is mandatory for operation of the users'
functional area
Data is user identifiable (usually by a business user)
Data is usually user maintainable (usually by an administrative user)
Data is usually established when the application is first installed and maintained intermittently
Data supports core user activities
Data is less dynamic (occasionally changes in response to changes in the environment, external
functional processes, and/or business rules of the functional area)
Reference Data Physical Characteristics - answer-Data has key fields and few attributes
Data contains usually at least one record or a limited number of records
Code Data - answer-Aka List Data or Translation Data
Provides a list of valid values that a descriptive attribute may have
Code Data Logical Characteristics - answer-Data is mandatory to the functional area but
optionally stored as a data file
Data is not usually identified as part of the functional requirements but are usually identified as
part of the design to meet nonfunctional requirements
Data is sometimes user maintainable (usually by a user support person)
Data is used to standardize and facilitate business activities and business transactions
Data is essentially static and only changes in response to changes in the way that the business
operates
The benefits of buying summaries with Stuvia:
Guaranteed quality through customer reviews
Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.
Quick and easy check-out
You can quickly pay through credit card or Stuvia-credit for the summaries. There is no membership needed.
Focus on what matters
Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!
Frequently asked questions
What do I get when I buy this document?
You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.
Satisfaction guarantee: how does it work?
Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.
Who am I buying these notes from?
Stuvia is a marketplace, so you are not buying this document from us, but from seller TOPDOCTOR. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy these notes for $8.99. You're not tied to anything after your purchase.
