|
- Application User
- A person who uses an
application for an authorized purpose.
- Application
- A set of programs and their
associated data that, together, act together to achieve a
common purpose.
- Business Analyst
- A person who translates
business needs into business requirements.
- Business Line Expert
- A person who knows and can
articulate the business needs, and can judge the relative
merit of the business needs and requirements.
- Business Need
- An unstructured realization
of something the business needs in order to perform its
mission or achieve its objectives (at all or in a more
capable manner).
- Business Objective
- A situation that the
business wants to consistently achieve.
- Business Requirement
- A structured, complete and
precise written explanation of a business need.
- Code Unit
- A specific, named section of
code. Example: a class, a program, a class method.
- Company Office
- The physical location of the
buildings the company uses to perform work in.
- Problem Statement
- A description of the pain
that the organization feels that would motivate it to
undertake the expense and effort involved to build a
software solution.
- Programmer
- A person who translates
system designs into software code.
- Action Item
- An action that furthers the
software development process, particularly in reference to a
project or a request.
- Project Sponsor
- A person who approves the
project scope and is responsible for funding the project.
- Personal Software Process (PSP)
- Both the PSP and TSP are
techniques provided under the auspices of the Software
Engineering Institute (SEI) out of Carnegie-Mellon
University. They focus on simple techniques for managing and
improving your own work (PSP) and for working with others in
a simple, yet effective manner (TSP). They stress
incremental improvement by measurement.
- Project
- A way of grouping related
work together in order to accomplish all of it more
efficiently.
- Request (Software
Development)
- A written, well-structured
statement which describes a problem for which a software
solution is desired.
- Request Status History
- A record of the work started
and completed in order to evaluate or implement a request.
- Request Submitter
- A person who is to be
contacted in order to clarify any information about the
intent or purpose of the request.
- System Analyst
- A person responsible for
translating business requirements into a workable system
design.
- System Design
- An explanation of what will
be implemented in an application and how it will be
implemented, written in terms suitable for developing
software.
- Team Software Process (TSP)
- See Personal Software
Process.
|
|
|