All Stories

Wednesday, 26 February 2014


Sin Cos Values In Easy Way


Posted at 12:31 |  by viralnom

Saturday, 8 February 2014

  1. #include<iostream.h>
  2. #include<conio.h>
  3. void main()
  4. {
  5. int a,b;
  6. clrscr();
  7. cout<<"\n\nEnter the two no=:";
  8. cin>>a>>b;
  9. cout<<"\na"<<a<<"\nb"<<b;
  10. a=a+b;
  11. b=a-b;
  12. a=a-b;
  13. cout<<"\n\na="<<a<<"\nb="<<b;
  14. getch();
  15. }
Learn Easy way of calculating sin-cos-tan values.

Swapping using two variables in C++

  1. #include<iostream.h>
  2. #include<conio.h>
  3. void main()
  4. {
  5. int a,b;
  6. clrscr();
  7. cout<<"\n\nEnter the two no=:";
  8. cin>>a>>b;
  9. cout<<"\na"<<a<<"\nb"<<b;
  10. a=a+b;
  11. b=a-b;
  12. a=a-b;
  13. cout<<"\n\na="<<a<<"\nb="<<b;
  14. getch();
  15. }
Learn Easy way of calculating sin-cos-tan values.

Posted at 02:42 |  by viralnom

Thursday, 6 February 2014


Ethernet Standardization

Notwithstanding its technical merits, timely standardization was instrumental to the success of Ethernet. It 

required well-coordinated and partly competitive activities in several standardization bodies such as the 

IEEE, ECMA, IEC, and finally ISO.

The "DIX-group" with Gary Robinson (DEC), Phil Arst (Intel), and Bob Printis (Xerox) submitted the so-

called "Blue Book" CSMA/CD specification as a candidate for the LAN specification. Since IEEE 

membership is open to all professionals, including students, the group received countless comments on this 

technology.

Networks

Simple switched Ethernet networks, while a great improvement over repeater-based Ethernet, suffer from 

single points of failure, attacks that trick switches or hosts into sending data to a machine even if it is not 

intended for it, scalability and security issues with regard to broadcast radiation and multicast traffic, and 

bandwidth choke points where a lot of traffic is forced down a single link.

Advanced networking features in switches and routers combat these issues through a number of means 

including spanning-tree protocol to maintain the active links of the network as a tree while allowing physical 

loops for redundancy, port security and protection features such as MAC lock down and broadcast 

radiation filtering, virtual LANs to keep different classes of users separate while using the same physical 

infrastructure, multi-layer switching to route between different classes and link aggregation to add bandwidth 

to overloaded links and to provide some measure of redundancy.

Standards

The vast majority of customer has LAN's that employ Ethernet as the network protocol - a few uses Token 

Ring.  At least 90% of these networks are 10 BASE-T.  The LAN sits behind the router and hub or high-

speed Ethernet switch, and the workstations are connected in a star topology.  Actually, most networks 

have replaced the Cat 3 cables with Cat 5.  Both Cat 3 and 5 cables have 4 un-shielded, twisted pairs of 

copper wires and use the RJ-45 connector, as shown below:

Comparison

Often referred to as Thick net, 10Base5 was the first incarnation of Ethernet technology. The industry used 

thick net in the 1980s until 10Base2 Thin net appeared. Compared to thick net, thin net offered the 

advantage of thinner (5 millimeters vs. 10 millimeters) and more flexible cabling, making it easier to wire 

office buildings for Ethernet.


The most common form of traditional Ethernet, however, is 10Base-T. 10Base-T offers better electrical 
properties than thick net or Thin net, because 10Base-T cables utilize unshielded twisted pair (UTP) wiring 
rather than coaxial. 10Base-T also proved more cost effective than alternatives like fiber optic cabling.
The table below details these traditional Ethernet technologies. Besides the type of cable involved, another 
important aspect of Ethernet networking is the segment length. A segment is a network connection made by 
a single unbroken network cable. Ethernet cables and segments can only span a limited physical distance, 
after which transmissions will likely fail due to line noise, reduced signal strength and other degradation. Per 
the Ethernet specifications, manufacturers of Ethernet equipment must meet the below minimum 
specifications for segment length.
Numerous other lesser-known Ethernet standards exist, including 10Base-FL, 10Base-FB, and 10Base-
FP for fiber optic networks and 10Broad36 for broadband (cable television) cabling.


Gigabit Ethernet

Whereas Fast Ethernet improved traditional Ethernet from 10 Megabit to 100 Megabit speed, Gigabit 

Ethernet boasts the same order-of-magnitude improvement over Fast Ethernet by offering speeds of 1000 

Megabits (1 Gigabit). Gigabit Ethernet was first made to travel over optical and copper cabling, but the 

1000Base-T standard successfully supports it as well. 1000Base-T uses Category 5 cabling similar to 100 

Mbps Ethernet, although achieving gigabit speed requires the use of additional wire pairs.

100BASE-FX:

100BASE-FX is a version of Fast Ethernet over optical fiber. It uses a 1300 nm near-infrared (NIR) light 

wavelength transmitted via two strands of optical fiber, one for receive (RX) and the other for transmit (TX). 

Maximum length is 400 meters (1,310 ft.) for half-duplex connections (to ensure collisions are detected), 

and 2 kilometres (6,600 ft) for full-duplex over multi-mode optical fiber. 100BASE-FX uses the same 

4B5B encoding and NRZI line code that 100BASE-TX does. 100BASE-FX should use SC, ST, LC, 

MTRJ or MIC connectors with SC being the preferred option.

100BASE-FX is not compatible with 10BASE-FL, the 10 MBit/s versions over optical fiber.

100BASE-SX:

100BASE-SX is a version of Fast Ethernet over optical fiber. It uses two strands of multi-mode optical 

fiber for receive and transmit. It is a lower cost alternative to using 100BASE-FX, because it uses short 

wavelength optics which are significantly less expensive than the long wavelength optics used in 100BASE-

FX. 100BASE-SX can operate at distances up to 550 meters (1,800 ft.).

100BASE-SX uses the same wavelength as 10BASE-FL, the 10 Mbit/s versions over optical fiber. Unlike 

100BASE-FX, this allows 100BASE-SX to be backwards-compatible with 10BASE-FL.

Because of the shorter wavelength used (850 nm) and the shorter distance it can support, 100BASE-SX 

uses less expensive optical components (LEDs instead of lasers) which makes it an attractive option for 

those upgrading from 10BASE-FL and those who do not require long distances.





Ethernet Standardization


Ethernet Standardization

Notwithstanding its technical merits, timely standardization was instrumental to the success of Ethernet. It 

required well-coordinated and partly competitive activities in several standardization bodies such as the 

IEEE, ECMA, IEC, and finally ISO.

The "DIX-group" with Gary Robinson (DEC), Phil Arst (Intel), and Bob Printis (Xerox) submitted the so-

called "Blue Book" CSMA/CD specification as a candidate for the LAN specification. Since IEEE 

membership is open to all professionals, including students, the group received countless comments on this 

technology.

Networks

Simple switched Ethernet networks, while a great improvement over repeater-based Ethernet, suffer from 

single points of failure, attacks that trick switches or hosts into sending data to a machine even if it is not 

intended for it, scalability and security issues with regard to broadcast radiation and multicast traffic, and 

bandwidth choke points where a lot of traffic is forced down a single link.

Advanced networking features in switches and routers combat these issues through a number of means 

including spanning-tree protocol to maintain the active links of the network as a tree while allowing physical 

loops for redundancy, port security and protection features such as MAC lock down and broadcast 

radiation filtering, virtual LANs to keep different classes of users separate while using the same physical 

infrastructure, multi-layer switching to route between different classes and link aggregation to add bandwidth 

to overloaded links and to provide some measure of redundancy.

Standards

The vast majority of customer has LAN's that employ Ethernet as the network protocol - a few uses Token 

Ring.  At least 90% of these networks are 10 BASE-T.  The LAN sits behind the router and hub or high-

speed Ethernet switch, and the workstations are connected in a star topology.  Actually, most networks 

have replaced the Cat 3 cables with Cat 5.  Both Cat 3 and 5 cables have 4 un-shielded, twisted pairs of 

copper wires and use the RJ-45 connector, as shown below:

Comparison

Often referred to as Thick net, 10Base5 was the first incarnation of Ethernet technology. The industry used 

thick net in the 1980s until 10Base2 Thin net appeared. Compared to thick net, thin net offered the 

advantage of thinner (5 millimeters vs. 10 millimeters) and more flexible cabling, making it easier to wire 

office buildings for Ethernet.


The most common form of traditional Ethernet, however, is 10Base-T. 10Base-T offers better electrical 
properties than thick net or Thin net, because 10Base-T cables utilize unshielded twisted pair (UTP) wiring 
rather than coaxial. 10Base-T also proved more cost effective than alternatives like fiber optic cabling.
The table below details these traditional Ethernet technologies. Besides the type of cable involved, another 
important aspect of Ethernet networking is the segment length. A segment is a network connection made by 
a single unbroken network cable. Ethernet cables and segments can only span a limited physical distance, 
after which transmissions will likely fail due to line noise, reduced signal strength and other degradation. Per 
the Ethernet specifications, manufacturers of Ethernet equipment must meet the below minimum 
specifications for segment length.
Numerous other lesser-known Ethernet standards exist, including 10Base-FL, 10Base-FB, and 10Base-
FP for fiber optic networks and 10Broad36 for broadband (cable television) cabling.


Gigabit Ethernet

Whereas Fast Ethernet improved traditional Ethernet from 10 Megabit to 100 Megabit speed, Gigabit 

Ethernet boasts the same order-of-magnitude improvement over Fast Ethernet by offering speeds of 1000 

Megabits (1 Gigabit). Gigabit Ethernet was first made to travel over optical and copper cabling, but the 

1000Base-T standard successfully supports it as well. 1000Base-T uses Category 5 cabling similar to 100 

Mbps Ethernet, although achieving gigabit speed requires the use of additional wire pairs.

100BASE-FX:

100BASE-FX is a version of Fast Ethernet over optical fiber. It uses a 1300 nm near-infrared (NIR) light 

wavelength transmitted via two strands of optical fiber, one for receive (RX) and the other for transmit (TX). 

Maximum length is 400 meters (1,310 ft.) for half-duplex connections (to ensure collisions are detected), 

and 2 kilometres (6,600 ft) for full-duplex over multi-mode optical fiber. 100BASE-FX uses the same 

4B5B encoding and NRZI line code that 100BASE-TX does. 100BASE-FX should use SC, ST, LC, 

MTRJ or MIC connectors with SC being the preferred option.

100BASE-FX is not compatible with 10BASE-FL, the 10 MBit/s versions over optical fiber.

100BASE-SX:

100BASE-SX is a version of Fast Ethernet over optical fiber. It uses two strands of multi-mode optical 

fiber for receive and transmit. It is a lower cost alternative to using 100BASE-FX, because it uses short 

wavelength optics which are significantly less expensive than the long wavelength optics used in 100BASE-

FX. 100BASE-SX can operate at distances up to 550 meters (1,800 ft.).

100BASE-SX uses the same wavelength as 10BASE-FL, the 10 Mbit/s versions over optical fiber. Unlike 

100BASE-FX, this allows 100BASE-SX to be backwards-compatible with 10BASE-FL.

Because of the shorter wavelength used (850 nm) and the shorter distance it can support, 100BASE-SX 

uses less expensive optical components (LEDs instead of lasers) which makes it an attractive option for 

those upgrading from 10BASE-FL and those who do not require long distances.





Posted at 12:49 |  by viralnom

Sunday, 2 February 2014




TYPES OF REQUIREMENTS:

  1. User requirements
      The software must provide a means of representing and accessing external files created by other tools.Statements in natural language plus diagrams of the services the system provides and its operational 
constraints.

  1. System requirements
             To be used efficiently, all computer software needs certain hardware components or other software resources to be present on a computer. It is a structured document setting out detailed descriptions of the system services and written as a contract between client and contractor.  These pre-requisites are known as (computer) system requirements and are often used as a guideline as opposed to an absolute rule.

  1. Functional requirements
           What a system should be able to do, the functions it should perform.Statements of services the system should provide how the system should react to particular inputs and how the system should behave in particular situations.
  1. Non-functional requirements
          Constraints on the services or functions offered by the system such as timing constraints, constraints on the development process, standards, etc.
An example of a non-functional requirement is an initialization sequence incorporated into the software that is specific to a given customer.

  1. Domain requirements
              Requirements that come from the application domain of the system and that reflect characteristics of that domain. For example: Library system etc.

  1. Customer Requirements 
             The customers are those that perform the eight primary functions of systems engineering, with special emphasis on the operator as the key customer.

  1. Operational requirements
             Operational requirements will define the basic need and, at a minimum, answer the questions posed.

  1. Architectural Requirements
         An architectural requirement is any requirement that is architecturally significant, whether this significance be implicit or explicit. Implicit architectural requirements are those requirements that have particular attributes. For example, any high-risk, high-priority, or low-stability requirement could be considered to be architecturally significant. The product will be localized.

  1. Behavioral Requirements
         Behavior which is abides by the Law, Responsibility for the Image of Infineon, Work-Related Standards and Principles.

  1. Performance Requirements
          Performance requirements (PR) are necessary for system design and development. If there is no written performance requirements, it just means that they exists in heads of stakeholders, but nobody bothered to write them down and made sure that everybody agrees with them.

  1. Design Requirements
         These Design Requirements apply to all plans, processes, and procedures required for compliance with the Design Process.

  1. Derived Requirements
          A derived requirement is one that was not explicitly stated by a stakeholder but has been derived as part of the requirements analysis process. A derived requirement is therefore not directly stated by a primary source but is derived by systems engineers from an explicit statement of requirement

  1. Product requirements
          Requirements which specify that the delivered product must behave in a particular way, e.g. execution speed, reliability etc.

  1. Organizational requirements
       Requirements which are a consequence of organizational policies and procedures, e.g. process standards used, implementation requirements
etc.
  1. External requirements

          Requirements which arise from factors which are external to the system and its development process, e.g. interoperability requirements, legislative requirements etc.



TYPES OF REQUIREMENTS




TYPES OF REQUIREMENTS:

  1. User requirements
      The software must provide a means of representing and accessing external files created by other tools.Statements in natural language plus diagrams of the services the system provides and its operational 
constraints.

  1. System requirements
             To be used efficiently, all computer software needs certain hardware components or other software resources to be present on a computer. It is a structured document setting out detailed descriptions of the system services and written as a contract between client and contractor.  These pre-requisites are known as (computer) system requirements and are often used as a guideline as opposed to an absolute rule.

  1. Functional requirements
           What a system should be able to do, the functions it should perform.Statements of services the system should provide how the system should react to particular inputs and how the system should behave in particular situations.
  1. Non-functional requirements
          Constraints on the services or functions offered by the system such as timing constraints, constraints on the development process, standards, etc.
An example of a non-functional requirement is an initialization sequence incorporated into the software that is specific to a given customer.

  1. Domain requirements
              Requirements that come from the application domain of the system and that reflect characteristics of that domain. For example: Library system etc.

  1. Customer Requirements 
             The customers are those that perform the eight primary functions of systems engineering, with special emphasis on the operator as the key customer.

  1. Operational requirements
             Operational requirements will define the basic need and, at a minimum, answer the questions posed.

  1. Architectural Requirements
         An architectural requirement is any requirement that is architecturally significant, whether this significance be implicit or explicit. Implicit architectural requirements are those requirements that have particular attributes. For example, any high-risk, high-priority, or low-stability requirement could be considered to be architecturally significant. The product will be localized.

  1. Behavioral Requirements
         Behavior which is abides by the Law, Responsibility for the Image of Infineon, Work-Related Standards and Principles.

  1. Performance Requirements
          Performance requirements (PR) are necessary for system design and development. If there is no written performance requirements, it just means that they exists in heads of stakeholders, but nobody bothered to write them down and made sure that everybody agrees with them.

  1. Design Requirements
         These Design Requirements apply to all plans, processes, and procedures required for compliance with the Design Process.

  1. Derived Requirements
          A derived requirement is one that was not explicitly stated by a stakeholder but has been derived as part of the requirements analysis process. A derived requirement is therefore not directly stated by a primary source but is derived by systems engineers from an explicit statement of requirement

  1. Product requirements
          Requirements which specify that the delivered product must behave in a particular way, e.g. execution speed, reliability etc.

  1. Organizational requirements
       Requirements which are a consequence of organizational policies and procedures, e.g. process standards used, implementation requirements
etc.
  1. External requirements

          Requirements which arise from factors which are external to the system and its development process, e.g. interoperability requirements, legislative requirements etc.



Posted at 11:22 |  by viralnom

Friday, 31 January 2014



  1. #include<iostream>
  2.  
  3. #include<cstdlib>
  4.  
  5. using namespace std;
  6.  
  7. int main()
  8.  
  9. {
  10.  
  11. int i=0, j=0, NUM=3;
  12.  
  13. for(i=-NUM; i<=NUM; i++)
  14.  
  15. {
  16.  
  17. for(j=-NUM; j<=NUM; j++)
  18.  
  19. {
  20.  
  21. if( abs(i)+abs(j)<=NUM)
  22.  
  23.  { cout<<"*"; }
  24.  
  25. else { cout<<" ";}
  26.  
  27. }
  28.  
  29. cout<<endl;
  30.  
  31. }
  32. return 0;
  33. }
Output:
*
***
*****
*******
*****
***
*

Printing a Diamond in C++ using Aesterics.



  1. #include<iostream>
  2.  
  3. #include<cstdlib>
  4.  
  5. using namespace std;
  6.  
  7. int main()
  8.  
  9. {
  10.  
  11. int i=0, j=0, NUM=3;
  12.  
  13. for(i=-NUM; i<=NUM; i++)
  14.  
  15. {
  16.  
  17. for(j=-NUM; j<=NUM; j++)
  18.  
  19. {
  20.  
  21. if( abs(i)+abs(j)<=NUM)
  22.  
  23.  { cout<<"*"; }
  24.  
  25. else { cout<<" ";}
  26.  
  27. }
  28.  
  29. cout<<endl;
  30.  
  31. }
  32. return 0;
  33. }
Output:
*
***
*****
*******
*****
***
*

Posted at 22:11 |  by viralnom

  1. #include<iostream>
  2. using namespace std;
  3. int main()
  4. {
  5.     int palindrome, reverse=0;
  6.     cout<<"Enter number:  ";
  7.     cin>>palindrome;
  8.     int num=0,key=palindrome;
  9.   for(int i=1;palindrome!=0;i++){

  10.     num=palindrome%10;
  11.     palindrome=palindrome/10;
  12.     reverse=num+(reverse*10);
  13.               }

  14.    if(reverse==key){
  15.       cout<<key<<" is a Palindrome Number";
  16.             }
  17.    else{
  18.       cout<<key<<"is NOT a Palindrome Number";
  19.             }
  20. return 0;
  21. }

Finding Palindrome C++ Code


  1. #include<iostream>
  2. using namespace std;
  3. int main()
  4. {
  5.     int palindrome, reverse=0;
  6.     cout<<"Enter number:  ";
  7.     cin>>palindrome;
  8.     int num=0,key=palindrome;
  9.   for(int i=1;palindrome!=0;i++){

  10.     num=palindrome%10;
  11.     palindrome=palindrome/10;
  12.     reverse=num+(reverse*10);
  13.               }

  14.    if(reverse==key){
  15.       cout<<key<<" is a Palindrome Number";
  16.             }
  17.    else{
  18.       cout<<key<<"is NOT a Palindrome Number";
  19.             }
  20. return 0;
  21. }

Posted at 21:46 |  by viralnom

Sunday, 19 January 2014

Requirement Elicitation is one of the most important phases in SDLC during which all the requirements of 

users are elicited.
SDLC Process



Following are the techniques of requirement elicitation:-

  • Conversational methods

        This is the verbal communication which takes place between stakeholders. Analysts and the experienced persons conduct different interviews, workshops to gather the requirements. Brain storming is also a conversational method by which requirements are elicited through the collection of ideas.

  •  Observational method

           In this method the requirements are elicited by observing the peoples. Persons may be attached to the environment in order to elicit the requirements. Observations are made in such a way that it doesn't disturb the peoples and the staff members of the organization.

  •  Analytical method

        In this method the analyst does the analysis of the gathered information. In this method we reuse the specification of the legacy systems to elicit the requirements. In this method requirements are also elicited through the questionnaires.

  •  Synthetic method

        In this method we start the requirement elicitation from the documentation study. In this method we combine the conversational, observational and analytic methods to elicit the requirements. In this method the scenarios and storyboards are used to elicit the requirements. This method also include the JAD/RAD sessions, the purpose of including it in this method is to include all the stakeholders in the design phase. The analyst and stakeholders conduct contextual inquiry to elicit the requirements.

  • GSD methodology

        In this methodology the advance problems are gathered and the strategy is made to lessen that problems.

  •  Analysis of data

        Requirement elicitation I responsible for the success or failure of the project.JAD/RAD and ethnography has very much usage rate as compared to the R-group. Elicitation methods also depend on the development process.

  •  Elicitation guidelines


  1.          Interviews/Surveys are important for web based systems
  2. 2       Checklists are important for the small scale systems   
  3.          JAD/RAD is recommended when we have to deal a lot of peoples in less time and in less budget
  4.          Scenarios/Storyboards are used for the legacy system updates
  5.          Ethnography is used during the updating and we have a lot of time and budget.


View Points

Many software houses have their own ways of developing. Due to this reason sometimes they fails because their own ways of developing are not sufficient sometimes to develop the modern software project. Engineers must use proper and adequate model and method for requirement elicitation and development for the user satisfactory.

Modern Trend Towards Requirement Elicitation

Requirement Elicitation is one of the most important phases in SDLC during which all the requirements of 

users are elicited.
SDLC Process



Following are the techniques of requirement elicitation:-

  • Conversational methods

        This is the verbal communication which takes place between stakeholders. Analysts and the experienced persons conduct different interviews, workshops to gather the requirements. Brain storming is also a conversational method by which requirements are elicited through the collection of ideas.

  •  Observational method

           In this method the requirements are elicited by observing the peoples. Persons may be attached to the environment in order to elicit the requirements. Observations are made in such a way that it doesn't disturb the peoples and the staff members of the organization.

  •  Analytical method

        In this method the analyst does the analysis of the gathered information. In this method we reuse the specification of the legacy systems to elicit the requirements. In this method requirements are also elicited through the questionnaires.

  •  Synthetic method

        In this method we start the requirement elicitation from the documentation study. In this method we combine the conversational, observational and analytic methods to elicit the requirements. In this method the scenarios and storyboards are used to elicit the requirements. This method also include the JAD/RAD sessions, the purpose of including it in this method is to include all the stakeholders in the design phase. The analyst and stakeholders conduct contextual inquiry to elicit the requirements.

  • GSD methodology

        In this methodology the advance problems are gathered and the strategy is made to lessen that problems.

  •  Analysis of data

        Requirement elicitation I responsible for the success or failure of the project.JAD/RAD and ethnography has very much usage rate as compared to the R-group. Elicitation methods also depend on the development process.

  •  Elicitation guidelines


  1.          Interviews/Surveys are important for web based systems
  2. 2       Checklists are important for the small scale systems   
  3.          JAD/RAD is recommended when we have to deal a lot of peoples in less time and in less budget
  4.          Scenarios/Storyboards are used for the legacy system updates
  5.          Ethnography is used during the updating and we have a lot of time and budget.


View Points

Many software houses have their own ways of developing. Due to this reason sometimes they fails because their own ways of developing are not sufficient sometimes to develop the modern software project. Engineers must use proper and adequate model and method for requirement elicitation and development for the user satisfactory.

Posted at 02:39 |  by viralnom

ExactSeek Approved !!

Blogger templates. Proudly Powered by Blogger.
back to top