Other Requirements, Requirement specification and map

1. CSK –oxford Engineering College -trichy

3.  It applies across all the components of the
system which includes.
 Supplemental requirements
 Financial requirements
 Enterprise requirements

4.  Three characteristics of performance that
reflect customer’s impact are
 Operational suitability
 Supportability and
 Confidence.
 Operational suitability:
 Measure of how well our network design can be
configured, monitored and adjusted by the
customer’s operators.

5.  Supportability:
 Measure of how well the customer can keep the
system performing as designed, over the entire
life of the system.
 Confidence:
 Measure of the ability of the network to deliver
data without error or loss at the required
throughput(rate of production).
 During the requirements analysis phase:
 The network engineer ensures that the customer
understands the trade-offs(quality/aspect) between
cost and performance.

6.  Engineer prepares customers network has
exceeded the design capacity thus
 An upgrade (or)
 Service life extension (or)
 Replacement.
 Network design to support 1000 connections
should be aware that, when their becomes
20,000 connections, they need an entirely
different network.

7.  These three factors must be taken into
account when contracting for external
services,
 Such as
 WAN, MAN (or)
 ISP connections (or)
 Maintenance services.

8.  Funding to network devices and services,
instead of including of the parts of the
system(ex: desktop computer and servers).
 Funding is bounded by an overall cost limit,
 consisting of both (
 One time cost.
 Recurring cost (repeatedly/ periodically).

9.  One time cost :
 Based on the actual planning and construction of the
network.
 Consist of network architecture, design,
procurement(external source), deployment, integration,
testing network hardware / software components, the
initial installation or establishment of any services from
service providers.
 Recurring cost :
 Tasks and items that are expected / replaced / upgraded
on a periodic basis.
 This includes network OAM&P (Operations,
Administration, Maintenance & Provisions(supply)),
modifications(edit) to the network.

10.  Time frames for recurring costs vary ,
 Driven by customer/ user/ administrative,
management financial cycles(accrual accounting,
audit, budget cycle, budget execution),
technology cycles(development phase).
 Financial requirements gathered during the
analysis process.

11.  Enterprise requirements are
 Phone, FAX, voice based and video based.
 The integration of these types of requirements
over the same transmission infrastructure as data
is becoming common.

12.  It shows the location dependencies between
application and devices.
 MAP: Requirement analysis, gathering,
deriving and determining requirements from
variety of sources including users,
management, application and staff.
 Requirements specification: (figure refer
book)
 ID/Name , date, type Description, gathered /
delivered, Locations, status, priority.

13.  ID/ Name : name of the requirement
 Date : indicates the date that the
requirement was developed.
 Type: component from which requirements
(user, application, device, network or other)
 Description: details for the requirements. It
indicate functional / non – functional.
 Gathered / Derived: a requirement was
gathered, this where it is gathered.
Requirements was derived, this how it was
derived.

14.  Locations: where this requirement applies in
the environment.
 Status : represents the current state of this
requirement(core or fundamental, features,
future requirements, rejected
requirements).
 Priority:
 representing priority level of this requirement.
 s/w requirements may be managed and tracked
through common word – processing and spread
sheet software applications.


15.  Gathering requirements for building a LAN
network, the result as follows
 150 users:
 (60 – Engineers)
 (15 – HR Executives) & finance
 (30 - Manufacturer)
 (10 - management)
 (30 – sales / marketing)
 (05 - others)

16.  Each area in the building must support fast
Ethernet connection to the backbone.
 Inventory application for manufacturing
requirements not determined at this time.
 Database application require a minimum of
150 kb/s per session.
 Visualization application finance requires up
to 40 mb/s cap and 100 ms round trip delay.
 Payroll applications(financial records of
salaries for an employee, wages, bonuses and
deductions) require 100% uptime between
finance and outside payroll company.

17.  Company must be kept secure from internet
attacks.
 Other general applications:
 Mail.
 Word processing
 Internal / external web access.

18. THANK YOU