When would you choose top down methodology?
- 3 Answers
- 16030 Views
- CTS, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / katti
Top down methodology is one where overall picture of the
system is defined first. Then we go into the details of the
sub-systems in the next level and so on. So to brief this,
first the complex system is seen as a whole and then this
is broken down to smaller simpler pieces.
Top down approach is preferred when understanding of the
complete system is done. Sufficient knowledge of the system
is required.
| Is This Answer Correct ? | 23 Yes | 2 No |
Answer / mansi
In a top down approach an overview of the system is first
formulated, specifying but not dealing any first level
subsystem, Each subsystem is then refined in yet greater
detail, sometimes in many additional subsystem levels, until
the entire specification is reduced to base elements.
| Is This Answer Correct ? | 10 Yes | 1 No |
Answer / mansi
Separating the low level work from the higher level objects
leads to a modular design.
Modular design means development can be self contained.
Having skeleton code illustrates clearly how low level
module integrate.
No functionality will exist until development of low level
objects is complete
| Is This Answer Correct ? | 5 Yes | 4 No |
What is the important aspect of a real-time system ?
what are the rules u follow when u r writing critical section of code?
What is the difference b/n any GPOS and RTOS?Give suitable examples or characteristic of RTOS to support your answer. What changes can be done in a GPOS to make it work like a RTOS? What basic features will you support, if you have to design a RTOS?
8 Answers Bosch, Emulogic, L&T, Qualcomm,
what is difference between IRQ and FRQ ?
What is the difference between Hard and Soft real-time systems ?
11 Answers Google, Hella, Satyam,
I have been working on one thread which manage and control a couple of circular buffers. It has api for other thread to access. As the thread grows bigger and bigger, I split it as 3 to 4 threads which need to share common buffers, and also their api could be used by other threads, (not these three threads). Inside api, I also allow other threads to access these three threads' common buffers(more than one buffer). SO I have to use mutex to avoid race condition . But I found mutex will be everwhere in all the threads when they update the common buffer. I am wondering whether I could reduce mutex usage(more mutex will hure my system performance). any ideas for how to reduce mutex usage meanwhile to avoid race condition. Thanks
Describe different job scheduling in operating systems.
What is a Real-Time System ?
What do you mean by deadlock?
what is major concerns about any RTOS selection ?
What is priority inversion ? and What is the solution ?
6 Answers Qualcomm, Tandberg, Wipro,
What is the state of the processor, when a process is waiting for some event to occur?
Vxworks 
