1gathering Data To Identify Business Requirements Filtered
1gathering Data To Identify Business Requirements Filtered
Evaluating means determining significance or worth usually by careful appraisal and study.
- It is the process of determining the worth or value of something
- Kinds of evaluation can be – qualitative or quantitative
Example: - Answers the question "How well did we do?" (Qualitative evaluation)
- Answers the question "How much did we do? (Quantitative evaluation)
3.2 Resolving conflicts in information or point of views
- Conflicts in information or points of view are resolved with stakeholders.
Conflict, arguments, and change are natural parts of our lives, as well as the lives of every agency, organization, and nation.
Conflict resolution is a way for two or more parties to find a peaceful solution to a disagreement among them. The
disagreement may be personal, financial, political, or emotional.
LO4. Submit analysis and gain agreements
4.1 Preparing detailed document
4.1.1 Using documentation standards
Documentation is collection of information that describes the product to its users how it can be operated or used.
Detailed document must be prepared according to documentation standards and organizational templates.
Standard documentation is a set of documents provided on paper, or online, or on digital media within standard format.
4.1.2 Using organizational templates
A template is a form, mold, or framework as a guide to making something.
Example: - A ruler is a template when used to draw a straight line.
- A document in which the standard opening and closing part is a template.
An Organizational template means an organizational format.
4.2 .Writing succinct/concise and appropriate document
Succinct means 'short and to the point' or 'brief and to the point.'
- Document in a style are written that is succinct and appropriate to the audience.
For example the structure for requirements of concise document:
Chapter Description
Preface This should define the expected readership of the document and describe its version
history, including a rationale for the creation of a new version and a summary of the
changes made in each version.
Introduction This should describe the need for the system. It should briefly describe its functions
and explain how it will work with other systems. It should describe how the system fits
into the overall business or strategic objectives of the organisation commissioning the
software.
Glossary This should define the technical terms used in the document. You should not make
assumptions about the experience or expertise of the reader.
User requirements The services provided for the user and the non-functional system requirements should
definition be described in this section. This description may use natural language, diagrams or
other notations that are understandable by customers. Product and process standards
which must be followed should be specified.
System architecture This chapter should present a high-level overview of the anticipated system architecture
showing the distribution of functions across system modules. Architectural components
that are reused should be highlighted.
System requirements This should describe the functional and non-functional requirements in more detail. If
specification necessary, further detail may also be added to the non-functional requirements, eg
interfaces to other systems may be defined.
System models This should set out one or more system models showing the relationships between the
system components and the system and its environment. These might be object models,
data-flow models and semantic data models.
System evolution This should describe the fundamental assumptions on which the system is based and
anticipated changes due to hardware evolution, changing user needs, etc.
Appendices These should provide detailed, specific information which is related to the application
being developed. Examples of appendices that may be included are hardware and
database descriptions. hardware requirements define the minimal and optimal
configurations for the system. Database requirements define the logical organisation of
the data used by the system and the relationships between data.
Index Several indexes to the document may be included. As well as a normal alphabetic
index, there may be an index of diagrams, an index of functions, etc.
Introduction
System description
Functional requirements
Non-functional requirements
Information domain
Project costs
Benefits
Other project specific topic
* The table below summarizes what each heading contains.
These headings are described in detail below.
Introduction
Defines the purpose of the document with a summary of the entire document.
The introduction should describe the scope of the system - i.e. what functions will the system implement.
System Description
Describes top-level functions of the system and the system environment. Diagrams (eg Use Cases and Context
Diagrams) can be used to model the system and interactions with its environment.
For example if the system is a website - you could include a top level storyboard to demonstrate to the client the
main functions.
Functional Requirements
Defines the services that the system provides.
Examples of mandatory and desirable functional requirements might be:
The system Must associate non-stock purchases of raw materials to a specified customer order
The system Must associate design work as well as production work to customer special orders
The system Must provide a users' guide for products
The system Must capture customer details online
The system May have password protection for a members only section
The system May track the completion status of customer special orders
Use Case diagrams, Data Flow diagrams and State chart diagrams are common techniques used to describe the
systems functions.
Non Functional Requirements
Defines any constraints within which the current system operates. For example: database size, response times, and
web page download times.
Information domain
Defines the data requirements of the system. ER diagrams, Class diagrams and Data Dictionaries are common
techniques used to describe a system's data.
For websites, the storyboard information should be expanded to show what information (web pages) will be
included.
Project Costs
Defines estimated costs of the project in terms of development and running costs.
Benefits
Defines the areas that the new system will improve. This includes benefits measurable in dollars (tangible) and
those that cannot be measured in dollars (intangible) but are important nonetheless.
Other Project Specific topics
Defines any other topics that may impact on the project.
These may include such things as methodology, legal implications or employee acceptance etc.