Home | | Embedded and Real Time Systems | | Embedded Systems | Important Short Questions and Answers: Embedded System Development

Chapter: Embedded Systems

| Study Material, Lecturing Notes, Assignment, Reference, Wiki description explanation, brief detail |

Important Short Questions and Answers: Embedded System Development

Embedded Systems - Important Short Questions and Answers: Embedded System Development

EMBEDDED SYSTEM DEVELOPMENT

 

1. What is design technology?

 

Design technology involves the manner in which we convert our concept of desired system functionality into an implementation. Design methodologies are used in taking the decisions at the time of designing the large systems with multiple design team members.

 

2. What are the goals of design process?

 

A design process has several important goals beyond function, performance, and power. They are time to market, design cost and quality

 

3. What is a design flow?

A design flow is a sequence of steps to be followed during a design.

 

4. What are the phases in water fall development model?

 

The waterfall development model consists of five major phases; they are requirements analysis, architecture, coding, testing and maintenance.

 

5. What are the elements of concurrent engineering?

Cross-functional teams

 

Concurrent product realization

 

Incremental information sharing and use Integrated project management

 

Early and continual supplier involvement Early and continual customer focus

 

6. What are requirements and specification?

 

Requirements are informal descriptions of what the customer wants, while specifications are more detailed, precise, and consistent descriptions of the system that can be used to create the architecture.

 

7. What are the several tests met by a good set of requirements?

 

The several tests that should be met by a good set of requirements are Correctness, Unambiguousness, Completeness, Verifiability, Consistency, Modifiability and Traceability.

 

8. What does the acronym CRC stands for?

CRC stands for Classes, Responsibilities and Collaborators.

 

Classes - define the logical groupings of data and functionality. Responsibilities - describe what the classes do.

 

Collaborators -are the other classes with which a given class works.

 

9. What are the steps to be followed in a CRC card methodology?

Develop an initial list of classes:

 

Write an initial list of responsibilities and collaborators Create some usage scenarios

 

Walk through the scenarios

 

Refine the classes, responsibilities, and collaborators Add class relationships

 

10.            What is the need for quality assurance (QA)?

The quality assurance (QA) process is vital for the delivery of a satisfactory system.

 

11.            What are the observations about quality management based on ISO 9000?

Process is crucial

 

Documentation is important Communication is important

 

12.            What are the five levels of maturity in capability maturity model?

Initial, Repeatable, Defined, Managed and Optimizing are the five levels of maturity in

 

CMM.

 

13. What is a design review?

 

Design review is a simple, low-cost way to catch bugs early in the design process. A design review is simply a meeting in which team members discuss a design, reviewing how a component of the system works.

 

14. Give the members of the design review team.

 

Designers, Review leader, Review scribe and Review audience are the members of the design review team.

 

15. What is the role of a review scribe in a design review?

 

The review scribe records the minutes of the meeting so that designers and others know which problems need to be fixed.

 

16. Give the role of the review leader in a design review team.

 

The review leader coordinates the pre-meeting activities, the design review itself, and the post-meeting follow-up. During the meeting, the leader is responsible for ensuring that the meeting runs smoothly.

 

17.            What are the potential problems to be looked for by the audience of a design review meeting?

 

Is the design team’s view of the component’s specification consistent with the overall system specification, or has the team misinterpreted something?

 

Is the interface specification correct?

 

Does the component’s internal architecture work well? Are there coding errors in the component?

 

Is the testing strategy adequate?

 

18.            Why is the verification of specification very important?

 

Verifying the requirements and specification is very important for the simple reason that bugs in the requirements or specification can be extremely expensive to fix later on. A bug introduced in the requirements or specification and left until maintenance could force an entire redesign of the product

 

 

19. What is prototype?

 

Prototype is the model of the system being designed. Prototypes are a very useful tool when dealing with end users—rather than simply describe the system to them in broad, technical terms, a prototype can let them see, hear, and touch at least some of the important aspects of the system.

 

20. Define successive refinement design methodology.

 

In successive refinement design methodology, the system is built several times. A first system is used as a rough prototype, and successive models of the system are further refined. This methodology makes sense when you are relatively unfamiliar with the application domain for which you are building the system.

 

Study Material, Lecturing Notes, Assignment, Reference, Wiki description explanation, brief detail


Copyright © 2018-2020 BrainKart.com; All Rights Reserved. Developed by Therithal info, Chennai.