What are the differences between inter-network routing and intra-network routing?

- The individual networks when combined together form the inter-network. 

- Intermediate inter networking devices are used for making connections between them. 

- All these networking elements combine to work as single large unit. 

- The creation of the internetworking has been made possible because of the packet switching technology. 

- The router is the most common and important device used for performing inter-network routing and intranetwork routing.

- Routing across various networks in the inter network is termed as internetwork routing and routing within the same network is termed intranetwork routing. 

In this article we discuss about the differences between internetwork routing and intranetwork routing. 

- Just like inter-network, intranetwork also uses IP (internet protocol) technology for computing services and sharing information. 

- But what makes it different from internetworking is that it is limited to some organization whereas internetwork extends beyond all i.e., it is not limited.

- Or we can put it in other words: Internetwork is spread across organizations and Intranetwork lies within an organization. 

- In some cases, the term intranetwork might mean only the internal website of the organization, but in other cases it might be a larger part of the IT infrastructure of the organization. 

- Sometimes, it may span over a number of LANs (local area networks). 

- The intranetwork is driven by the goal of minimizing the time, effort and cost of the individual’s desktop in order to make it more competitive, cost efficient, timely as well as productive.

- An intranetwork is capable of hosting multiple websites that are private to organizations and may even constitute an important part of the collaboration and communication between the members of the organization. 

- Intranetwork also makes use of various well known protocols such as the FTP, SMTP and HTTP. 

- The intranets are often incorporated with the technologies for lending a modern interface to the systems that host the corporate data. 

- These systems are known as the legacy systems. 

- We can see intranetwork to be a private analog of the internetwork. 

- It means the internetwork has been simply extended to an organization for its private use. 

- Extranetworks are a modified version of the intranetworks.

- Here, the website might be accessed by the non-members i.e., the suppliers, customers or some other approved third parties and so on. 

- Intranetworks are well equipped with a special protocol called the AAA protocol. 

- The 3 As stand for authentication, authorization and accounting. 

- There are a number of organizations who are concerned about the security of their intranetworks. 

- They have deployed a firewall and a network gateway for controlling the access to their services. 

- The intermediate systems when connect together form the internetwork whereas they may bound together a part of the internetwork which might be an intranetwork. 

- The intranetwork routing involves routing between two routers which lie in the same network whereas in internetwork routing, routing is done between routers which reside across different networks. 

- Intranetwork routing is quite easy when compared to the internetwork routing. 

- Protocols used in both the types of routing are different.

- Interior gateway protocol is responsible for routing in the intranetworks whereas the exterior gateway protocol takes the responsibility of routing across the internetwork. 

- Most common example of interior gateway protocol is the OSPF or the open shortest path first protocol. 

- And most common example of exterior gateway protocol is the border gateway protocol or BGP. 

- Also, the routing graphs for both the types are different. 

- In the intranetwork’s graph, all the routers are simply linked to one another in the same network. 

- There is less mess.

- On the other hand, the inter network’s graph is quite tedious. 

- This is so because routers of different networks have to be inter-linked with one another. 

What is meant by Time sharing system?

In the field of computer science, sharing resources of a computer through techniques of multi-tasking and multi-programming by many other system users is termed as a time sharing system. 

- It was first introduced in the year of 1960 and eventually emerged as the most popular computing model of the 1970s. 

- With it, occurred a major shift in the technology of designing the efficient computers. 

- These types of systems allowed quite a large number of users for interacting with the same computer system at the same time. 

- Providing computing capabilities was a costly affair at that time. 

- Time sharing greatly brought down this cost by providing these capabilities at a very less cost. 

- Since time sharing allows multiple users to interact simultaneously with the same system, it has actually made it possible for the organizations and the individuals to use a system that they do not even own. 

- This has further led to the promotion of the computers to be used interactively and development of other applications with an interactive interface. 

- The earlier systems apart from being expensive were quite slow. 

- This was the reason why the systems could be dedicated only to one task at a time. 

- The task was carried out through the control panels from where the operator would enter small programs manually through switches so as to load and execute a new program series. 

- These programs would take even up to weeks for completing execution. 

- The realization of the interaction pattern was what that led to the development of time sharing systems. 

- Usually, the data entered by a single user was in small bursts of info and then a long pause. 

- But if there would have been multiple number of users working concurrently on the same system, there activities could fill up the pauses of the single user. 

- The overall process could be made very efficient for a given size of the use group. 

- In the same way, the slice or share of time that was engaged in waiting for network input or tape or disk could be utilized by activities of other users. 

- A system that would be able to harness this potential advantage was difficult to be implemented.

- Even though batch processing was a high at that time, it could only make use of the time delay between two programs. 

- In the early times, the multiplexing of computer terminals in to main frame computer systems was seen.

- Such implementations were capable of sequentially polling those terminals to check for additional action and data requests made by the user of the system.

- Later, came the interconnection technology that was interrupt driven and made use of the IEEE 488 i.e., parallel data transfer technologies.

- Time sharing faded for some time with the advent of the micro computing but again it came back in to the scene with the rise of internet. 

- The corporate server farms cost in millions and are capable of hosting a large number of customers sharing the same resources.

- The operation of the websites using the early serial terminals was in bursts of activity that were followed by idle periods. 

- However, it is because of this bursting that the services of the web sites could be used by a large number of users simultaneously and with the advantage that the delays in communications won’t be noticed by them.

- However, if the server gets too damn busy they will surely start coming in to the notice.

- Earlier some time sharing services such as the service bureaus were offered by many companies. 

- Some examples of common systems that are used for time sharing are:

1. SDS 940
2. PDP – 10
3. IBM 360

What are types of artificial neural networks?

In this article we discuss the types of artificial neural networks. These models simulate the real life biological system of nervous system.

1. Feed forward neural network: 

- This is the simplest type of neural network that has been ever devised. 

- In these networks the information flow is unidirectional; therefore the data moves only in forward direction. 

- From input nodes data flows to the output nodes via hidden nodes (if there are any). 

- In this model there are no loops or cycles. 

- Different types of units can be used for constructing feed forward networks for example, McCulloch – pitts neurons.

- Continuous neurons are used in error back propagation along with the sigmoidal activation.

2. Radial basis function network: 

- For interpolating in a multi – dimensional space radial basis functions are the most powerful tools. 

- These functions can be built in to criterion of distance with respect to some center.

- These functions can be applied in the neural networks. 

- In these networks, sigmoidal hidden layer transfer characteristic can be replaced by these functions.

3. Kohonen self–organization network: 

- Un–supervised learning is performed with the help of self – organizing map or SOM. 

- This map was an invention of Teuvo Kohonen.

- Few neurons learn mapping points in the input space that could not coordinate in the output space. 

- The dimensions and topology of the input space can be different from those of the output space. SOM makes an attempt for preserving these.

4. Learning vector quantization or LVQ: 

- This can also be considered as neural network architecture. 

- This one also was a suggestion of Teuvo Kohonen.  

- In these prototypical representatives are parameterized along with two important things namely, a classification scheme based - up on distance and a distance measure.

5. Recurrent neural network: 

- These networks are somewhat contrary to the feed forward networks. 

- They offer a bi–directional flow of data.

- On a feed forward network data is propagated linearly from input to output. 

- Data from later stages of processing is also transferred to its earlier stages by this network. 

- Sometimes these also double up as the general sequence processors. 

- Recurrent neural networks have a number of types as mentioned below:

Ø  Fully recurrent network

Ø  Hopfield network

Ø  Boltzmann machine

Ø  Simple recurrent networks

Ø  Echo state network

Ø  Long short term memory network

Ø  Bi – directional RNN

Ø  Hierarchical RNN

Ø  Stochastic neural networks

6. Modular neural networks: 

- As per the studies have shown that human brain works actually as a collection of several small networks rather than as just one huge network, this ultimately helped in realizing the modular neural networks where smaller networks cooperate in solving a problem. 

- Modular networks are also of many types such as:

Ø  Committee of machines: Different networks that work together on a given problem are collectively termed as the committee of machines. The result achieved through this kind of networking is quite better than what is achieved with the others. The result is highly stabilized.

Ø  Associative neural network or ASNN: This is an extension of the previous one. And extends a little beyond the weighted average of various models. This one is a combined form of the k- nearest neighbor technique (kNN) and the feed forward neural networks. Its memory is coincident with that of the training set.

7. Physical neural network: 

- It consists of some resistance material that is electrically adjustable and capable of simulating the artificial synapses.

There are other types of ANNs that do not fall in any of the above categories:

Ø  Holographic associative memory

Ø  Instantaneously trained networks

Ø  Spiking neural networks

Ø  Dynamic neural networks

Ø  Cascading neural networks

Ø  Neuro – fuzzy networks

Ø  Compositional pattern producing networks

Ø  One – shot associative memory

What are benefits of agile process improvement?

Agile methodologies that we have today are a resultant of the experiences gained from the real life projects that were undertaken by the leading software professionals. These professionals were thorough with the challenges and limitations imposed by the traditional development methodologies on various projects. 

- The agile process improvement directly addresses the issues of the traditional development methods both in terms of processes and philosophy behind it. 

- Agile process improvement provides a simple framework to the development teams suiting varying scenarios while focusing up on the fast delivery of the business values. 

- With all these benefits of the agile process improvements, the organizations have been able to reduce the associated overall risk with the development of the project. 

- The delivery of the initial business values is accelerated well by the agile process improvement. 

- This is achieved through a process of constant planning and feedback. 

- Agile process improvement ensures that the business values are maximized throughout the development process. 

- With the API’s iterative planning plus feedback loop, it becomes possible for teams to align the software process with the business needs as required. 

- Another major benefit of the agile process is that the software development process can adapt to the ever–changing requirements of the process and business. 

- By taking a measure and evaluation of the status based up on the amount of work and testing done, visibility can be obtained to a more accurate value. 

- The final result of the agile process improvement is a software system that is capable of addressing the customer requirements and the business in a much better way. 

- By following an agile process improvement program, not only just deployable, tested and working software can be delivered on an incremental basis but also increased visibility, adaptability and values are delivered earlier in the software development life cycle. 

- This proves to be a great thing in reducing the risk associated with the project. 

- There are a number of problems with the traditional development methods. 

- In a research it was found that the waterfall style development methodology was the major factor in the contribution of failure of the software. 

- Some other software could not meet the real needs. 

- They had the inability in dealing with the changing requirements and late integration. 

- All this has proven that the traditional development methods prove to be risky as well as a costly way for building software. 

- Thus the majority of the industry has turned towards agile development.

- There is a continuous feedback input from the customers and a face to face communication among all the stake holders. 

- The business needs associated with the agile process improvement are ever changing. 

- Organizations want quick results from what they invest. 

- They want their improvement programs to keep pace with these changing business needs. 

- The agile process improvement is composed of several mechanisms using which all this can be achieved. 

- Working iteratively lets you deliver the product before the deadline to the customer. 

- It lets you deliver only the things are actually required i.e., it does not let you waste your time on the un-required things. 

- Also, early and regular feedback from the customer lets you deliver the product with quality as desired by the customer.

- Agile projects are distributive in nature i.e., the work is divided among people. 

- Agile software development is still an immature process and there is a need for improving it for the betterment of the software industry. 

- Agile process improvement is one way to do this.

What are Software Process Improvement resources?

A supportive and effective infrastructure is required for facilitating the coordination of various activities that place during the course of the whole program. In addition to these qualities the infrastructure should be quite flexible so as to be able to support the changing demands of the software process improvement with time. 

Resources for this program include:

1. Infrastructure and building support
2. Sponsorship
3. Commitment
4. Baseline activities
5. Technologies
6. Coordinate training resources
7. Planning expertise
8. Baseline action plan and so on.

- When this program is initiated, a primitive infrastructure is put in to place for the management of the activities that would be carried out by the organization under SPI. 

- The resources mentioned above are also the initial accomplishments that tell how well the infrastructure has been performing. 

- It is the purpose of the infrastructure to establish a link between the program’s vision and mission, to monitor it and guide it and obtaining resources and allocating them.

- Once the SPI program, a number of improvement activities will be taking place across the different units of the organization. 

- These improvement activities cannot be performed serially rather they take place in parallel. 

- The configuration management, project planning, requirements management and reviews etc. are addressed by the TWGs (technical working groups). 

- But all these activities are tracked by the infrastructure.

- Support for the following issues must be provided by the infrastructure:

1. For a technology that is to be introduced.
2. Providing sponsorship
3. Assessment of the organization impact

- As the program progresses, the functions to be performed by the infrastructure increase. 

- There are 3 major components of the SPI program:

1. SEPG or software engineering process group
2. MSG or management steering group
3. TWG or technical work group

- It is third component from which most of the resources are obtained including:

1. Human resources
2. Finance
3. Manufacturing
4. Development

- However, the most important is the first one and is often called the process group. 

- It provides sustaining support for the SPI and reinforcing the sponsorship. 

- The second component i.e., the MSG charters the SEPG.

- This is actually a contract between the SEPG and the management of the organization. 

- Its purpose is to outline the roles and the responsibilities and not to forget the authority of the SEPG. 

- The third component is also known as the process improvement team or process action team. 

- Different work groups created focus on different issues of the SPI program. 

- A software engineering domain is addressed by the technical work group. 

- It is not necessary for the TWGs to address the technical domains; they can address issues such as software standardization, purchasing, travel reimbursement and so on. 

- The team usually consists of the people who have both knowledge and experiencing regarding the area under improvement. 

- The life of TWGs is however finite and is defined in the charter. 

- Once they complete their duties, they return back to their normal work. 

- In the early stages of SPI program, the TWGs might tend to underestimate the time that would be required for the completion of the objectives assigned to them. 

- So the TWGs have to request to the MSG for allotting them more time. 

- Another important component could be the SPIAC or software process improvement advisory committee. 

- This is created in organizations where there are multiple functioning SEPGs. 

What is the need of Agile Process Improvement?

It is commonly seen that a number of change projects are designed and published but none of actually goes into implementation. Most of the time is wasted in writing and publishing them. This approach usually fails. We should stop working with this methodology and develop a new one. Below mentioned are some common scenarios in the modern business:

1. Developing a stronger project
2. Changing the people working on it.
3. Threatening that project with termination
4. Appointment of a committee that would analyze the project
5. Taking examples from other organizations to see how they manage to do it.
6. Getting down to a dead project
7. Tagging a dead project as still worth of achieving something.
8. Putting many different projects together so as increase the benefit.
9. Additional training

-Drops in the delivery of the normal work always follow a change. 

-Big change projects are either dropped or rejected.

-It all happens because the changes introduced by such projects are mandatory to be followed.

-This threatens the normal functioning of the organization. 

-So, the organization is eventually compelled to kill the whole process and start with the old way of work again. 

-Instead of following this approach, a step by step process improvement can be followed that is nothing but the agile process improvement. 

Now you must be convinced why agile process improvement is actually needed. 

- The changes needs to be adaptive then only the process will be balanced. 

- An example is the CMMI maturity level. It takes 2 years approx. for completion and brings in the following:

1. Restructuring
2. New competitors
3. New products

-Only agile methods make these changes adaptive in nature.

-The change cycles when followed systematically produce results in every 2 – 6 weeks.

-Thus, your organization’s workload and improvement stay perfectly balanced. -The early identification of the issues becomes possible for the organizations thus giving you it a chance to be resolved early. 

-By and by the organization learns to tackle the problems and how to improve work.

-At the end it is able to adapt to the every changing needs of the business.

-The responsibility of the deployment and evaluation of the improvement is taken by the PPQA. 

-Whole process is implemented in 4 sprints:

1. Prototyping
2. Piloting
3. Deploying
4. Evaluating

-A large participation and leadership is required for these changes to take place.

-Some other agile techniques along with scrum can also be used in SPI.

-We can have the improvements continuously integrated in to the way the organization works. 

-The way of working can also be re-factored including assets and definitions by having an step by step integration of the improvements.

-Pair work can be carried out on improvements. 

-A collective ownership can be created for the organization. 

-Evaluations and pilots can be used for testing purpose. 

-In order to succeed with the sprints is important that only simple solutions should be developed. 

-An organization can write the coaching material with the help of the work description standards.

-This sprint technique helps the organization to strike a balance between the improvement and the normal workload. 

-In agile process improvement simple solutions are preferred over the complex ones.

-Here, the status quo and the vision are developed using the CMMI and SCAMPI. 

-Status quo and vision are necessary for the beginning of the software process improvement.

-SPI when conducted properly produces useful work otherwise unnecessary documentation has to be produced.

-An improvement in the process is an improvement in the work. 

-Improving work is what that is preferred by people. 

What is an Agile Process Improvement?

A process improvement program is successful only when the meaning of the word ‘process’ is clearly understood. Process means work. So when one improves, the other one also improves. The quality of the software depends a lot on the process. Whenever a change is introduced, a temporary drop in performance is always recorded. In most cases what happens is that the organization stops the implementation of changes fearing the disruption in the normal work since so much effort is required. To avoid such situations, the changes need to be adaptive. It is the agile process improvement that makes this possible. You might say that such a way of iterative improvement is not new. Well, the agile techniques introduce discipline in the whole program.

Stages of Agile Process Improvement

The following are the stages of the agile process improvement:

1. Initiating:

Ø  Stimulus of change

Ø  Set context

Ø  Build sponsorship

Ø  Charter infrastructure

2. Diagnosing:

Ø  Characterize current and desired states

Ø  Develop recommendation

3. Establishing:

Ø  Set priorities

Ø  Develop approach

Ø  Plan actions

4. Action:

Ø  Create solution

Ø  Test solution

Ø  Refine the solution

Ø  Implement solution

5. Learning:

Ø  Analyze

Ø  Validate

Ø  Propose future actions

- The improvement cycles are meant to be followed systematically so that the results might be obtained in time ranging from 2- 6 weeks.

- The whole process lets you maintain a balance the workload as well as the improvement. 

- The flow of the process is as follows:

1. Prioritized list of improvements
2. Detailed plan for the current cycle
3. Implemented improvement
4. Feedback

- After this process, the following becomes possible for the organization:

1. Identification and resolving of the issues earlier in the cycle.
2. Learning process regarding how to tackle difficulties and working of this process.
3. Adaption to the business needs that keep changing.
4. Giving response to the feedback.

- The sponsor holds the responsibility for prioritizing the improvement backlog at the start of each sprint. 

- Also, he is the one responsible for ROI. 

- Prioritization is a good tool for the sponsor to direct the change. 

- Using prioritization, the goals and feedback can be revised from quality assurance. 

- A focus can be kept on the benefit received from each improvement cycle. 

- PPQA deploys and evaluates the improvement in organization in every sprint. - The improvement package consists of 4 sprints namely:

1. Prototyping
2. Piloting
3. Deploying
4. Evaluating

- Active participation and leadership is required for a change to take place. 

- An endorsed vision and status quo is required for the beginning of the process. 

- Both of these are established via SCAMPI and CMMI. 

- The change is led by the management on an everyday basis.

- An excellent description is provided by the generic practices of CMMI for the leadership purpose.

- Similarly participation is a key element that is facilitated by the change team. - A vision is required for initiating the improvement project. 

- The initial improvement backlog is defined by 3 things namely scrumMaster, change team and the work owner i.e., the sponsor all based up on an assessment. 

- The organization is facilitated by the change team.

- With each sprint a tangible improvement is delivered. 

- The change is led by the management in a sprint.

- The effect introduced by the change is evaluated at the end of each sprint by PPQA. 

-The new improvements are defined by the work-owner who is also responsible for adding those in to the backlog of improvements and prioritizes it.

-Commitment is supported at the end of the sprint by appraisal.

-The improvements can also be continuously integrated in to the organization’s way of working. 

What is meant by Software Process Improvement?

About Software Process Improvement

- SPI or Software Process Improvement is a program that has been developed to provide guidance for the integrated long – range plan for the initiation and management of the SPI program. 

- SPI is based up on a model called the IDEAL model which has the following 5 major stages:

1. Initiating
2. Diagnosing
3. Establishing
4. Acting
5. Leveraging

- These 5 major steps form a continuous loop. 

- However, the time taken for the completion of one cycle varies from one organization to other. 

- Depending on the available resources an organization must be able to decide whether or not it would be able to commit to software process improvement. 

- SPI requires many activities to be carried out in parallel to each other. 

- Some part of the organization may take care of the activities in one phase while others take care of the other phase activities.

- Practically, the boundaries of the various stages in a software process improvement are not clearly defined. 

- The infrastructure also plays a great role in the success of the SPI. 

- The value added to SPI by infrastructure just cannot be underestimated. 

- It provides a great help in understanding its roles.

About Initiating Phase

- As the name indicates this is the starting point of the process. 

- This stage involves setting up of the improvement infrastructure. 

- Then the infrastructure’s roles and responsibilities are defined. 

- The resources are checked for availability and assigned.

- Finally, an SPI plan that will guide this initiating phase as well as the other higher stages. 

- It is during this stage that the goals of the software process improvement are defined and established based up on the organization’s business needs. 

- During the establishing phase these goals are further refined and specified.

- Two components are typically established namely:

Ø  A software engineering process group or SEPG

Ø  A management steering group or MSG 

About Diagnosing Phase

- In this stage, the organization as per the SPI plan starts. 

- This stage serves as foundation for the stages that will follow. 

- The plan is initiated keeping in view the vision of the organization along with its business strategy, past lessons, current business issues and long term goals. 

- Appraisal activities are carried out so that a baseline of the current state of the organization. 

- The results of these activities are reconciled with the existing efforts so as to be included in the main plan.

About Establishing Phase

 

- In this stage the issues to be addressed by the improvement activities are assigned priorities.

- Also, the strategies for obtaining a solution are also pursued. 

- The draft of the plan is completed as per the organization’s vision, plan, goals and issues. 

- From general goals, measurable goals are developed and put in to the final SPI plan. 

- Metrics essential to the process are also defined.

About Acting Phase

 

- Solutions addressing the improvement issues discovered in the previous stages are created and deployed in and out of the organization. 

- Other plans are developed for the evaluation of the improved processes.

About Leveraging Phase

 

- This stage is led by the objective of making the next pass through the process more effective. 

- By this time the organization has developed solutions and metrics concerning performance and achievement of the goals. 

- All this data obtained is stored in a process database that will later serve as source information for the next pass. 

- Also, this information would be used for the revaluation of the strategies and methods involved in the SPI program.

- Software process improvement activities work with two components namely, the tactical component and the strategic component. 

- The former is driven by the latter that is based up on the needs of the organization.