Beginning Software Engineering
Описание книги
Become the applicant Google can't turn down Cracking the Tech Career is the job seeker's guide to landing a coveted position at one of the top tech firms. A follow-up to The Google Resume, this book provides new information on what these companies want, and how to show them you have what it takes to succeed in the role. Early planners will learn what to study, and established professionals will discover how to make their skillset and experience set them apart from the crowd. Author Gayle Laakmann McDowell worked in engineering at Google, and interviewed over 120 candidates as a member of the hiring committee – in this book, she shares her perspectives on what works and what doesn't, what makes you desirable, and what gets your resume saved or deleted. Apple, Microsoft, and Google are the coveted companies in the current job market. They field hundreds of resumes every day, and have their pick of the cream of the crop when it comes to selecting new hires. If you think the right alma mater is all it takes, you need to update your thinking. Top companies, especially in the tech sector, are looking for more. This book is the complete guide to becoming the candidate they just cannot turn away. Discover the career paths that run through the top tech firms Learn how to craft the prefect resume and prepare for the interview Find ways to make yourself stand out from the hordes of other applicants Understand what the top companies are looking for, and how to demonstrate that you're it These companies need certain skillsets, but they also want a great culture fit. Grades aren't everything, experience matters, and a certain type of applicant tends to succeed. Cracking the Tech Career reveals what the hiring committee wants, and shows you how to get it.
Оглавление
Stephens Rod. Beginning Software Engineering
INTRODUCTION
WHAT IS SOFTWARE ENGINEERING?
WHY IS SOFTWARE ENGINEERING IMPORTANT?
WHO SHOULD READ THIS BOOK?
APPROACH
WHAT THIS BOOK COVERS (AND WHAT IT DOESN'T)
WHAT TOOLS DO YOU NEED?
CONVENTIONS
ERRATA
IMPORTANT URLS
CONTACTING THE AUTHOR
DISCLAIMER
PART I. Software Engineering Step-by-Step
CHAPTER 1. Software Engineering from 20,000 Feet
REQUIREMENTS GATHERING
HIGH-LEVEL DESIGN
LOW-LEVEL DESIGN
DEVELOPMENT
TESTING
DEPLOYMENT
MAINTENANCE
WRAP-UP
EVERYTHING ALL AT ONCE
SUMMARY
CHAPTER 2. Before the Beginning
DOCUMENT MANAGEMENT
HISTORICAL DOCUMENTS
E-MAIL
CODE
CODE DOCUMENTATION
APPLICATION DOCUMENTATION
SUMMARY
CHAPTER 3. Project Management
EXECUTIVE SUPPORT
PROJECT MANAGEMENT
SUMMARY
CHAPTER 4. Requirement Gathering
REQUIREMENTS DEFINED
REQUIREMENT CATEGORIES
GATHERING REQUIREMENTS
REFINING REQUIREMENTS
RECORDING REQUIREMENTS
VALIDATION AND VERIFICATION
CHANGING REQUIREMENTS
SUMMARY
CHAPTER 5. High-Level Design
THE BIG PICTURE
WHAT TO SPECIFY
UML
SUMMARY
CHAPTER 6. Low-Level Design
OO DESIGN
DATABASE DESIGN
SUMMARY
CHAPTER 7. Development
USE THE RIGHT TOOLS
SELECTING ALGORITHMS
TOP-DOWN DESIGN
PROGRAMMING TIPS AND TRICKS
SUMMARY
CHAPTER 8. Testing
TESTING GOALS
REASONS BUGS NEVER DIE
LEVELS OF TESTING
TESTING TECHNIQUES
TESTING HABITS
HOW TO FIX A BUG
ESTIMATING NUMBER OF BUGS
SUMMARY
CHAPTER 9. Deployment
SCOPE
THE PLAN
CUTOVER
DEPLOYMENT TASKS
DEPLOYMENT MISTAKES
SUMMARY
CHAPTER 10. Metrics
WRAP PARTY
DEFECT ANALYSIS
SOFTWARE METRICS
SUMMARY
CHAPTER 11. Maintenance
MAINTENANCE COSTS
TASK CATEGORIES
TASK EXECUTION
SUMMARY
PART II. Process Models
CHAPTER 12. Predictive Models
MODEL APPROACHES
PREREQUISITES
PREDICTIVE AND ADAPTIVE
WATERFALL
WATERFALL WITH FEEDBACK
SASHIMI
INCREMENTAL WATERFALL
V-MODEL
SYSTEMS DEVELOPMENT LIFE CYCLE
SUMMARY
CHAPTER 13. Iterative Models
ITERATIVE VERSUS PREDICTIVE
ITERATIVE VERSUS INCREMENTAL
PROTOTYPES
SPIRAL
UNIFIED PROCESS
CLEANROOM
SUMMARY
CHAPTER 14. RAD
RAD PRINCIPLES
JAMES MARTIN RAD
AGILE
XP
SCRUM
LEAN
CRYSTAL
FEATURE-DRIVEN DEVELOPMENT
AGILE UNIFIED PROCESS
DISCIPLINED AGILE DELIVERY
DYNAMIC SYSTEMS DEVELOPMENT METHOD
KANBAN
SUMMARY
APPENDIX. Solutions to Exercises
GLOSSARY
ABOUT THE AUTHOR
ABOUT THE TECHNICAL EDITOR
CREDITS
ACKNOWLEDGMENTS
WILEY END USER LICENSE AGREEMENT
Отрывок из книги
With modern development tools, it's easy to sit down at the keyboard and bang out a working program with no previous design or planning, and that's fine under some circumstances. My VB Helper (www.vb-helper.com) and C# Helper (www.csharphelper.com) websites contain thousands of example programs written in Visual Basic and C#, respectively, and built using exactly that approach. I had an idea (or someone asked me a question) and I pounded out a quick example.
Those types of programs are fine if you're the only one using them and then for only a short while. They're also okay if, as on my websites, they're intended only to demonstrate a programming technique and they never leave the confines of the programming laboratory.
.....
Often, however, things don’t go so smoothly. Deployment can be difficult, time-consuming, and expensive. For example, suppose you’ve written a new billing system to track payments from your company’s millions of customers. Deployment might involve any or all of the following:
As soon as the users start pounding away on your software, they’ll find bugs. (This is another software axiom. Bugs that were completely hidden from testers appear the instant users touch the application.)
.....