독일 일반 면세 구매대행
임시 중단 안내
안녕하세요. 오마이집입니다.
더 나은 서비스를 위해
독일 일반 면세 구매대행 서비스를 임시 중단합니다.
새로운 모습으로 빠른 시일 내 다시 인사드리겠습니다.
감사합니다.
US
DE
498 Centerpoint Blvd
[사서함번호]
New Castle, DE, 19720
302-322-8792
* 항공운송만 가능
US
CA
2601 Walnut Ave
[사서함번호]
Tustin, CA, 92780
714-676-7274
* 해상운송만 가능
China
山东省威海市 环翠区 苘山镇
福州路9号 顺丰速递北20米
[사서함번호]
264414
156-8451-3564
* 항공&해상운송 가능
Germany
WarpEx [사서함번호]
Carl-Benz Str. 35
Frankfurt am Main, Hessen, Deutschland
60386
0614-2482-9236
* 항공운송만 가능
Korea
서울시 강서구 마곡중앙6로 11 보타닉파크타워3 405호
[사서함번호]
07801
070-5228-2983
Japan
福岡県 福岡市東区
和白東1丁目16-15 HANIRO
[사서함번호]
811-0214
092-608-7642
* 해상운송만 가능
고객센터 알림
NO | 안내시간 | 수취인명 | 신청서번호 | 알림내용 |
---|
* 알림 내용을 클릭하면 해당 페이지로 이동합니다.
Delaware
$14.95
책 정보
출판사 | Createspace Independent Publis |
---|---|
저자 | Steve McClure |
판형 | Paperback |
ISBN-10 | 149759233X |
ISBN-13 | 9781497592339 |
발행일 | 2014/04/10 |
언어 | eng |
무게 (LB) | 1.23 |
주제 분류
책 소개
This Handbook reviews the Software Development and Engineering Principles involved in the Design of Embedded Computer Systems.
The reason behind developing this book can be answered by the following question. What does an embedded software engineer produce? Now most people would say 'prototypes' and this might seem like the correct answer but it is not. The correct answer is that the engineer produces documentation, documentation that shows other people how to understand and build the product. Now imagine that you are a software engineer who has newly joined the company and you have been given the unenviable task of maintaining an existing product. Why was this work given to the new guy? The answer is that no one else in the company wanted to tackle this project. Why? Because there is no documentation. So to figure out what the product does and to fix the bugs the new guy (or gal) has to reverse-engineer the source code. So the money that management thought they saved when some code was quickly thrown together by a software engineer (who has since left the company) they now find that several times more is being spent to fix up all the bugs and possibly add on some minor enhancement. This type of problem occurs when there is no development procedure. Which brings us to the Handbook. The Handbook provides a standard procedure which may be used by the Systems, Software, Embedded, Firmware and Hardware departments. Various design and development documents are produced at specific points in the project and are passed out for review prior to being used by other team members. By having this consistency the entire team now know which design elements will be produced and the need for implementing any reverse-engineering will be eliminated. Product costs for maintenance will be greatly reduced. Manufacturing and Test departments will now have the necessary details with with to complete their work. For shouldn't the designers who intuitively understand the product be the ones to write down their knowledge such that it can be passed on to others? By presenting these steps in the form of a Handbook which is distributed to the engineering team, it then identifies the documents that are to be generated, when they should be produced, who should create them and who should be involved in the review process. This keeps the entire team synchronized, fully aware of their responsibilities. Now some companies do have such procedures but they are long-winded and stored away in some unknown location on a harddrive. But a bright green Handbook that clearly spells out the implementation process along with detail gleaned from the author's 30+ years of experience in this field of engineering. Now wouldn't that be worth having?
트래킹 도착 조회
조회
조회 결과가 없는 경우, 센터로 상품이 도착하지 않은 것이니 판매처로 문의해주시기 바랍니다.
배송신청서에 이미 입고처리가 된 건이나 미작성 입고로 안내된 건은 조회가 되지 않습니다.