project : IP Recovery Using Multiple Routing Configurations Requirements: Softwa
ID: 3766341 • Letter: P
Question
project :
IP Recovery Using Multiple Routing Configurations
Requirements:
Software Requirements:
FRONT END : User Based
TOOLS USED : User Based
OPERATING SYSTEM: WINDOWS
Hardware Requirements:
PROCESSOR : 2.6 GHz
RAM : 2 GB
MONITOR : 13”
HARD DISK : 20 GB
CDDRIVE : 52X
KEYBOARD : STANDARD 102 KEYS
MOUSE : 3 BUTTONS
Functional Requirements:
Server
Client
Routers
Server:
It will receive the data send by the client which came from the active router.
It can have any number of clients.
Client:
This module is used to send the data to server through routers
It will provide user friendly interface to send the data to the required destination
Routers:
These are placed in between server and client to transfer the data.
Whenever client send the data to the server it will pass through any one router.
If the router is failed the data will be transferred through another router to reduce the system failure.
Functional Requirements should include:
Descriptions of data to be entered into the system
Descriptions of operations performed by each screen
Descriptions of work-flows performed by the system
Descriptions of system reports or other outputs
Who can enter the data into the system?
How the system meets applicable regulatory requirements
The functional specification is designed to be read by a general audience. Readers should understand the system, but no particular technical knowledge should be required to understand the document.
Introduction to IP Recovery Using Multiple Routing Configurations Networking Project:
With the invention of internet the communication system is being developed to a great extent. Presently slow junction of routing protocols for a network infrastructure is a great problem faced by numerous people, so to recuperate the failures of IP networks the MRC system is being developed.
Multiple routing configurations can be applied with little change. In this article the performance of the MRC system will be measured in terms of few technical prospects after the network failure. While using MRC how the increased traffic is performing the network distribution it also can be exhibited. The aim of this system is to facilitate the functional and non-functional needs.
SYSTEM DESIGN CONCEPTS
Presently internet has become an important part of communication infrastructure and the ease of use and consistency make it really useful. The facility of get back to normal from the failure is the chief objective of network developers. Though IP networks are truly strong with the use of IGP routing protocols and others, these protocols are designed in such a way so that it can be able to inform immediately after failure and the protocols are based on tailored topology. The functionality is evaluated in different parameters like load distribution and backup lengths.
There are some technical requirements that should be included in multiple routing configurations. There should be details of data to be accessed into the system, the functions operated by every screen, the detailed work flow on the system.
There should be system reports and one individual who would enter the details of data into the system and check out how the system matches with the necessary requirements. For ordinary public the technical specifications are being publicized. Those who are interested to know all about MRC but lacking technical knowledge can easily understand the entire system.
Explanation / Answer
Functional Requirements:
Functional requirements should include functions performed by specific screens, outlines of work-flows performed by the system and other business or compliance requirements the system must meet.
Interface requirements
Field accepts numeric data entry
Field only accepts dates before the current date
Screen can print on-screen data to the printer
A.Business Requirements
Data must be entered before a request can approved
Clicking the Approve Button moves the request to the Approval Workflow
All personnel using the system will be trained according to internal training strategies
Regulatory/Compliance Requirements
The database will have a functional audit trail
The system will limit access to authorized users
The spreadsheet can secure data with electronic signatures
C.Security Requirements
Member of the Data Entry group can enter requests but not approve or delete requests
Members of the Managers group can enter or approve a request, but not delete requests
Members of the Administrators group cannot enter or approve requests, but can delete requests
A backup or the process of backing up refers to making copies of data so that these additional copies may be used to restore the original after a data loss event. These additional copies are typically called "backups."
Certification refers to the confirmation of certain characteristics of an object, system, or organization. This confirmation is often, but not always, provided by some form of external review, education, or assessment
Compliance is the act of adhering to, and demonstrating adherence to, a standard or regulation.
Configuration management (CM) is a field that focuses on establishing and maintaining consistency of a system's or product's performance and its functional and physical attributes with its requirements, design, and operational information throughout its life.
Documentation may refer to the process of providing evidence ("to document something") or to the communicable material used to provide such documentation (i.e. a document). Documentation may also (seldom) refer to tools aiming at identifying documents or to the field of study devoted to the study of documents and bibliographies
Disaster recovery is the process, policies and procedures related to preparing for recovery or continuation of technology infrastructure critical to an organization after a natural or human-induced disaster.
Disaster recovery planning is a subset of a larger process known as business continuity planning and should include planning for resumption of applications, data, hardware, communications (such as networking) and other IT infrastructure
Maintenance is the ease with which a software product can be modified in order to:
correct defects
meet new requirements
make future maintenance easier, or
cope with a changed environment;
Open source describes practices in production and development that promote access to the end product's source materials—typically, their source code
Operability is the ability to keep equipment, a system or a whole industrial installation in a safe and reliable functioning condition, according to pre-defined operational requirements.
In a computing systems environment with multiple systems this includes the ability of products, systems and business processes to work together to accomplish a common task.
Computer performance is characterized by the amount of useful work accomplished by a computer system compared to the time and resources used.
Depending on the context, good computer performance may involve one or more of the following:
Short response time for a given piece of work
High throughput (rate of processing work)
Low utilization of computing resource(s)
High availability of the computing system or application
Fast (or highly compact) data compression and decompression
High bandwidth / short data transmission time
Price in economics and business is the result of an exchange and from that trade we assign a numerical monetary value to a good, service or asset
Portability is one of the key concepts of high-level programming. Portability is the software-code base feature to be able to reuse the existing code instead of creating new code when moving software from an environment to another. When one is targeting several platforms with the same application, portability is the key issue for development cost reduction.
Quality is the common element of the business definitions is that the quality of a product or service refers to the perception of the degree to which the product or service meets the customer's expectations. Quality has no specific meaning unless related to a specific function and/or object. Quality is a perceptual, conditional and somewhat subjective attribute.
Reliability may be defined in several ways:
The idea that something is fit for purpose with respect to time;
The capacity of a device or system to perform as designed;
The resistance to failure of a device or system;
The ability of a device or system to perform a required function under stated conditions for a specified period of time;
The probability that a functional unit will perform its required function for a specified interval under stated conditions.
The ability of something to "fail well" (fail without catastrophic consequences
Resilience is the ability to provide and maintain an acceptable level of service in the face of faults and challenges to normal operation.
These services include:
supporting distributed processing
supporting networked storage
maintaining service of communication services such as
video conferencing
instant messaging
online collaboration
access to applications and data as needed
Response time perceived by the end user is the interval between
(a) The instant at which an operator at a terminal enters a request for a response from a computer and
(b) The instant at which the first character of the response is received at a terminal.
In a data system, the system response time is the interval between the receipt of the end of transmission of an inquiry message and the beginning of the transmission of a response message to the station originating the inquiry.
Robustness is the quality of being able to withstand stresses, pressures, or changes in procedure or circumstance. A system or design may be said to be "robust" if it is capable of coping well with variations (sometimes unpredictable variations) in its operating environment with minimal damage, alteration or loss of functionality.
The concept of scalability applies to technology and business settings. Regardless of the setting, the base concept is consistent - The ability for a business or technology to accept increased volume without impacting the system.
In telecommunications and software engineering, scalability is a desirable property of a system, a network, or a process, which indicates its ability to either handle growing amounts of work in a graceful manner or to be readily enlarged.
Security is the degree of protection against danger, loss, and criminals.
Security has to be compared and contrasted with other related concepts: Safety, continuity, reliability. The key difference between security and reliability is that security must take into account the actions of people attempting to cause destruction.
Security as a state or condition is resistance to harm. From an objective perspective, it is a structure's actual (conceptual and never fully knowable) degree of resistance to harm.
Stability - it means much of the objects will be stable over time and will not need changes.
Safety is the state of being "safe", the condition of being protected against physical, social, spiritual, financial, political, emotional, occupational, psychological, educational or other types or consequences of failure, damage, error, accidents, harm or any other event which could be considered non-desirable. This can take the form of being protected from the event or from
exposure to something that causes health or economical losses. It can include protection of people or of possessions
Supportability is one of the aspects of RASU (Reliability, Availability, Serviceability, and Usability)). It refers to the ability of technical support personnel to install, configure, and monitor products, identify exceptions or faults, debug or isolate faults to root cause analysis, and provide hardware or software maintenance in pursuit of solving a problem and restoring the product into service. Incorporating serviceability facilitating features typically results in more efficient product maintenance and reduces operational costs and maintains business continuity.
(1) the logical property that is variously described as contingency, defeasibility, or falsifiability, which means that counter examples to the hypothesis are logically possible, and
(2) the practical feasibility of observing a reproducible series of such counter examples if they do exist. In short it refers to the capability of an equipment or system to be tested
Usability is a term used to denote the ease with which people can employ a particular tool or other human-made object in order to achieve a particular goal. In human-computer interaction and computer science, usability often refers to the elegance and clarity with which the interaction with a computer program or a web site is designed.
ANALYSIS
Analysis is the phase where the system observes the feasibility of system. Development is the cost efficient based on the mamagement approval,and then design,codingphases will be executed.
Analysis phase delivers requirement specification.The system specification serves as an interface between designer and developer as well as between developer and user.This describes external behavior of software without bothering the internal implementation.
Problem analysis is performed to getting a clear understanding of needs of the clients and the user and what exactly desired from the software.Analysis leads to actual specification.During the process of analysis a massive amount of information is collected in the form of interviews,questionnaires and information from documentation and so korth.One of the information can be effectively evaluated for completeness and consistency.
Existing System:
Existing work on load distribution in connectionless IGP networks has either focused on the failure free case or on finding link weights that work well both in the normal case and when the routing protocol has converged after a single link failure Many of the approaches listed provide elegant and efficient solutions to fast network recovery, however MRC and Not-via tunneling seems to be the only two covering all evaluated requirements. However, we argue that MRC offers the same functionality with a simpler and more intuitive approach, and leaves More room for optimization with respect to load balancing.
Syetem DEsign Algorithm
Let denote the backup configuration where node is isolated,Similarly, let denote the backup configuration where the link is isolated, i.e., Assuming that node is the egress (or the destination) in the local network domain, we can distinguish between two cases. If forwarding can be done in configuration where both and will be avoided. In the other case, the challenge is to provide recovery for the failure of link when node is operative. Our strategy is to forward the packet using a path to that does not contain Furthermore, packets that have changed configuration before, and still meet a failed component on their forwarding path, must be discarded. This way packets loops are avoided, also in the case that node indeed has failed. The steps that are taken in the forwarding process by the detecting node are summarized
Assume there is only a single component failure in the network, detected by node on path to the network-local destination via node
If node selects in step , and neither node nor link will be in the shortest path.
Assume that is the egress node for destination Remember that according to, We distinguish between three possible cases.
If as in then according to the definition of an isolated node. Forwarding step will select does not contain If and as in forwarding step will select and does not contain
Finally, if as in , forwarding will select Link is not isolated in and will be returned as the next hop. Step 3 will detect this, and stepwill select and does not contain
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.