Software Engineering

A: A DAC and ADC will have by design a certain assignment of bits or steps each step or bit value is dependent o the total number of bits available 12 bit dac assuming 10v reference its LSB value will be 4.08 mv minimum 10V/2048=4.08 mv

2048 is 2 raised 12 times

yes it is related 2 engineering because it has got to do with making and producing so that's related to engineering

software concept is a concept of your software. BOOM!

twisted pair cable, coaxial cable, and fiber optic cable

1.the compression ratio is higher compared to huffman coding.

2.efficiency is greater comparatively.

3.Redundancy is much reduced.

The critieria is based on what other techniques you might employ. The waterfall method in SDLC (software development life cycle) has been largely discounted in favor of more effective methods, such as the iterative approach.

One of the main problems with the waterfall design is that it does not easily allow for negative feedback at several stages of the project (for example, water flows downhill, not uphill, so feedback into the cycle can be very costly).

true

Because not maintaining them would lead to unfixed bugs and security flaws. If you release buggy software and make no effort to fix them, you will not have any return customers.

Software Process framework is a set of guidelines, concepts and best practices that describes high level processes in software engineering. It does not talk about how these processes are carried out and in what order. Although some do.

eg Eclipse Process Framework, Microsoft Solutions Framework.

High level processes like Build, Testing, Elaboration, Open Process Framework etc.

Software Methodologies a.k.a Software Development models build on such frameworks and specify in detail the How and When(order of executing) of the high level processes.

eg. Waterfall, Agile, Iterative models.

Processes like Requirements Analysis, Validation, Verification, Development etc.

Software Processes are contained in the Software development Models and specify in detail how a particular activity is to be performed. This is usually specific to an organization.

eg. Steps to perform Requirements Analysis, Design etc.

In monostable multivibrators Circuits (quasi stable state) is one of two states, stable state and quasi stable state which is invoked by an external trigger and it will stay there for value determined by time constant.

CMM verifies the quality of the overall software development process beginning from problem definition. Software validation and verification are the subitems of CMM.

Validation should always be considered in a software program. The amount of validation depends on what the program is doing, and how it is doing it. If the validation is a small percentage of the overall program then it doesn't matter much how efficient it is in terms of performance.

There are good and bad ways (actually inefficient ways) to do validation. If you instrument a program and find that a significant portion of the time is spent in validation you may want to visit the algorithms used in the validation to see if there is a more effective way to do this.

In some cases the performance of validation of data is very important; in other cases it is a side-effect.

ITP en términos de ingeniería significa '' Plan de Inspección y Prueba "

Analog to digital conversion done by the ADC's. It's digitization.

... Also referred to as video capture.

The collision resistance of a hash is proportional to the number of hash values that are stored, relative to the number of items that can be hashed, and it is proportional to the adequacy of the hash. The latter means that the hash should usually be of cryptographic quality.

The difference is exactly what you have just stated: deadlock prevention is used to stop deadlocks before they happen (to prevent them), while deadlock detection is used to figure out when a process has deadlocked (to detect it).

Hi,

Its just an naming convention followed by SAP after its acquisition over BO.

contextual meaning of XI in BOXI is "extreme insight".

Regards,

Vikas

Abstraction and refinement are complementary concepts. Abstraction enables

you to specify procedure and data internally but suppress the need for "outsiders" to have knowledge of low-level details.

Refinement helps you to reveal low-level details as design progresses. Both concepts allow you to create a complete design model as the design evolves.

google it for the result Study material for infosys campus connect

I will try to answer this quickly as I don't have much time.

As the name suggests, the waterfall model follows the path of an waterfall. It starts in the first stage of orientation, and ends at the release. It can only go one way (to the end goal) and the stages are very strict (you cant go back to a earlier stage).

The Spiral model understands that reality doesn't always follow theory, and that an project should be designed to follow that reality. There are multiple prototypes released, and phases can be repeated until the desired result is reached (hence the spiral).

The iterative model combines those two, making (IMHO) the waterfall model more ready for the real world.

You should try googling yourself, I found lots of info about the differences in this article about the advantages of the waterfall model: http://www.waterfall-model.com/the-waterfall-model-avantages-and-disadvantages

Two Phase locking protocol prevent deadlock. This protocol maintain the schedule which lock should be granted or not. For more information I think this link help you.

http://www.databaseidea.com/2012/03/two-phase-locking-protocol.html

The development of the National Railway System in the United States took place in 1916. This aimed to reduce the cost of moving goods to distant markets.

There are quite a few different advantages and disadvantages of using flow charts instead of text-based programming. One pro is that this is a visual aid that helps explain your ideas.

spiral model is just like incremental model but in spiral emphasize is on risk analysis.