Software Development & Management

197 Items

Sort by Date | Title

Telling Stories and User Role Modeling: By Mike Cohn; May 21, 2004; Agile software development is based on "telling stories." In this sample chapter, you'll learn about user roles, role modeling, user role maps, and personas. You'll also find out how taking these initial steps leads to better stories and better software.

Deadline Management: Are You Just Wasting Money?: By Dimitri Bertsekas; Apr 9, 2004

Enterprise Integration Styles: By Gregor Hohpe, Bobby Woolf; Feb 13, 2004; There are many issues that make application integration complicated. This chapter from "Enterprise Integration Patterns" explores multiple integration approaches that can help overcome these challenges.

Keys to Successful Venture Capital Investing: Due Diligence: By David Gladstone, Laura Gladstone; Dec 23, 2003; This chapter starts the beginning of what venture capitalists (VCs) call the due diligence process. That is, it describes the steps that an investor should take in researching an investment opportunity. This is a detailed process that takes weeks—sometimes months—of work. It begins when an investor is confronted with a business proposal and must decide whether the idea warrants further investigation.

Different Work: Why the Manufacturing Mindset Does Not Apply to Software Development: By Roy Miller; Oct 31, 2003; As it turns out, software development isn't like manufacturing at all. It's a different kind of work to solve a different kind of problem, despite what their learning and training tells most managers. The manufacturing mindset simply doesn't apply to software development. Roy Miller explains why.

Keeping the Code Clean: By Robert C. Martin; Sep 19, 2003; Is your kitchen a wreck? Your code probably is, too. "Uncle Bob" Martin explains why it's a bad idea to leave last week's "code spaghetti" drying on the dishes for cleanup later.

Software Architecture: The Difference between Marketecture and Tarchitecture: By Luke Hohmann; Jun 6, 2003; Luke Hohmann clarifies how the marketing and technical aspects of the software architecture system must work together to achieve business objectives.

How Chips Are Designed: By Jim Turley; May 2, 2003; Can't keep up with the ever-changing semiconductor sector? Learn how chips were designed 10 years ago and the drastic changes that process has undergone, along with current problems and future trends.

Introduction to Process Control and Instrumentation: By B. Wayne Bequette; Apr 18, 2003; Welcome to the world of process control and instrumentation! Discover how to identify and classify possible control objects and variables, assess the importance of process control, sketch a process instrumentation, and much more.

The Business of Making Semiconductors: By Jim Turley; Mar 28, 2003; Processed silicon is more valuable than gold, ounce for ounce. Look beyond the technical aspect and dive into the business side of semiconductors.

Test Driven Development: Equality for All: By Kent Beck; Jan 24, 2003; Kent Beck discusses how to achieve equality using Value Objects, Dollars, and Triangulation.

Facts of Software Engineering Management: By Robert L. Glass; Nov 22, 2002; Robert L. Glass explains why a software manager can't forget about the most important facts — like people are important, technical hype does more harm that good, and complexity is, well, complex.

Fallacies of Software Engineering Management: By Robert L. Glass; Nov 15, 2002; The usefulness of metrics, managing quality, and ego-less programming are all fallacies. Learn how software engineering management works in the real world.

Quality By Design, Part 1: Avoiding Rotten Code: By Pete McBreen; May 31, 2002; We all have to face the fact that some software stinks; it doesn't work right or it just plain feels wrong. Fixing these problems is simple, but may not be easy. We have to understand the nature of software development and make sure that we allow ourselves enough time to do a good job.

Becoming a Software Developer, Part 6: Design and Programming: By Pete McBreen; May 17, 2002; The step between having a design idea and the "simple matter" of programming that idea is a massive one. Understanding why programming is not easy is a first step toward mastering the craft of programming.

Becoming a Software Developer Part 5: Creating Acceptance Tests from Use Cases: By Pete McBreen; May 10, 2002; As well as being a great input into our design activities, use cases are a fantastic aid to our quality assurance activities in that they provide the information we need to design acceptance test cases.

Becoming a Software Developer Part 4: Understanding Use Cases and Requirements: By Pete McBreen; May 1, 2002; Where do requirements come from? How can use cases help to record requirements? What does a good use case look like? What do I do with a use case once I have it?

Becoming a Software Developer Part 3: Version Control for Fun and Profit: By Pete McBreen; Apr 19, 2002; Although version control is an old technology, few developers take the time to think about how it can help them become more effective. This article looks at how frequent versioning can take some of the stress out of software development.

Becoming a Software Developer Part 2: Test Driven Development with Ruby: By Pete McBreen; Apr 12, 2002; Developers can become more productive and spend a lot less time debugging code by creating Extreme Programming style unit tests before the rest of the code is written. Every "Ruby nuby" should learn about test-driven development and create unit tests.