Steve McConnell - researchr alias

researchr

You are not signed in
Sign in
Sign up

Viewing Publication 1 - 53 from 53

2022

Harnessing Artificial Intelligence to Design Healthy, Sustainable, and Equitable PlacesPhillip Bernstein, Mark Greaves, Steve McConnell, Clifford Pearson, Joseph Williams. Computer, 55(2):67-71, 2022. [doi]

2011

What Does 10x Mean? Measuring Variations in Programmer ProductivitySteve McConnell. In Andy Oram, Greg Wilson, editors, Making Software - What Really Works, and Why We Believe It. Theory in practice, pages 567-574, O'Reilly, 2011.

2009

10 most powerful ideas in software engineeringSteve McConnell. ICSE 2009: 12 [doi]

2006

Software Construction, Part 1Steve McConnell. IEEE Software, 23(1):99, 2006. [doi]

Software Construction, Part 2Steve McConnell. IEEE Software, 23(2), 2006. [doi]

2005

Echoes?: structured design and modern software practicesSteven Fraser, Kent Beck, Grady Booch, Larry L. Constantine, Brian Henderson-Sellers, Steve McConnell, Rebecca Wirfs-Brock, Edward Yourdon. OOPSLA 2005: 383-386 [doi]

2004

Software development: arts & crafts or math & science?Jim Haungs, Martin Fowler, Ralph E. Johnson, Steve McConnell, Richard P. Gabriel. OOPSLA 2004: 141-142 [doi]

Code complete - a practical handbook of software construction, 2nd EditionSteve McConnell. Microsoft Press, 2004. [doi]

2002

Closing the GapSteve McConnell. IEEE Software, 19(1):3-5, 2002. [doi]

How to Write a Good Technical ArticleSteve McConnell. IEEE Software, 19(5):5-7, 2002. [doi]

Real Quality for Real EngineersSteve McConnell. IEEE Software, 19(2):5-7, 2002. [doi]

I Know What I KnowSteve McConnell. IEEE Software, 19(3):5-7, 2002. [doi]

Changing of the GuardSteve McConnell. IEEE Software, 19(6):5-7, 2002. [doi]

2001

Programming Skills of Software Engineering Students: What Is Required? (Panel)Donald J. Bagert, Thomas B. Hilburn, Gregory W. Hislop, Michael J. Lutz, Michael McCracken, Steve McConnell. csee 2001: 39 [doi]

From the Editor - Roundtable: Who Needs Software Engineering?Steve McConnell. IEEE Software, 18(1):5-8, 2001. [doi]

From the Editor - Art, Science, and EngineeringSteve McConnell. IEEE Software, 18(2):9-11, 2001. [doi]

From the Editor - An Ounce of PreventionSteve McConnell. IEEE Software, 18(3), 2001. [doi]

Raising Your Software ConsciousnessSteve McConnell. IEEE Software, 18(6):7-9, 2001. [doi]

The Nine Deadly sins of Project PlanningSteve McConnell. IEEE Software, 18(5):5-7, 2001. [doi]

Common SenseSteve McConnell. IEEE Software, 18(4):5-7, 2001. [doi]

After the Gold Rush: Establishing a True Profession of Software EngineeringSteve McConnell. csee 2001: 3 [doi]

2000

From the Editor - What s in a Name?Steve McConnell. IEEE Software, 17(5):7-9, 2000. [doi]

From the Editor - Quantifying Soft FactorsSteve McConnell. IEEE Software, 17(6):9-11, 2000. [doi]

From the Editor - The Software Manager s ToolkitSteve McConnell. IEEE Software, 17(4):5-7, 2000. [doi]

From the Editor - Cargo Cult Software EngineeringSteve McConnell. IEEE Software, 17(2):11-13, 2000. [doi]

From the Editor - Sitting on the SuitcaseSteve McConnell. IEEE Software, 17(3):5-7, 2000. [doi]

From the Editor - The Best Influences on Software EngineeringSteve McConnell. IEEE Software, 17(1):10-17, 2000. [doi]

1999

Update on Professional DevelopmentSteve McConnell. IEEE Software, 16(5):6-8, 1999. [doi]

Guest Editors Introduction: Professional Software Engineering-Fact or Fiction?Steve McConnell, Leonard L. Tripp. IEEE Software, 16(6):13-18, 1999. [doi]

From The Editor - Software Engineering PrinciplesSteve McConnell. IEEE Software, 16(2):6-8, 1999. [doi]

From the EditorSteve McConnell. IEEE Software, 16(4):6-11, 1999. [doi]

From the Editor - Y2K Countdown to CertificationSteve McConnell. IEEE Software, 16(3):4-7, 1999. [doi]

From the Editor - After the Gold RushSteve McConnell. IEEE Software, 16(1):6-8, 1999. [doi]

1998

The Power of ProcessSteve McConnell. Computer, 31(5):100-102, 1998.

Problem ProgrammersSteve McConnell. IEEE Software, 15(2):126-128, 1998. [doi]

Best Practices: The Art, Science, and Engineering of Software DevelopmentSteve McConnell. IEEE Software, 15(1):118-120, 1998.

Why You Should Use Routines...RoutinelySteve McConnell. IEEE Software, 15(4):94-96, 1998. [doi]

Weighing In on StandardsSteve McConnell. IEEE Software, 15(6):92-102, 1998. [doi]

Building the CommunitySteve McConnell. IEEE Software, 15(5):126-128, 1998. [doi]

Feasibility StudiesSteve McConnell. IEEE Software, 15(3):119-120, 1998. [doi]

How To Read a Technical ArticleSteve McConnell. IEEE Software, 15(6):126-128, 1998. [doi]

1997

Best Practices: The Programmer WritingSteve McConnell. IEEE Software, 14(4):119-120, 1997.

Best Practices: Software s Ten EssentialsSteve McConnell. IEEE Software, 14(2):143-144, 1997.

Best Practices: Tool Support for Project TrackingSteve McConnell. IEEE Software, 14(5):119-120, 1997.

Best Practices: Annualized Software DeliverySteve McConnell. IEEE Software, 14(1):103-104, 1997.

Best Practices: Achieving Leaner SoftwareSteve McConnell. IEEE Software, 14(6):127-128, 1997.

Best Practices: Gauging Software Readiness with Defect TrackingSteve McConnell. IEEE Software, 14(3):135-136, 1997.

1996

Daily Build and Smoke TestSteve McConnell. IEEE Software, 13(4):143-144, 1996. [doi]

How to Defend an Unpopular ScheduleSteve McConnell. IEEE Software, 13(3):118, 1996. [doi]

Missing in Action: Information HidingSteve McConnell. IEEE Software, 13(2):127-128, 1996. [doi]

Who Cares About Software Construction?Steve McConnell. IEEE Software, 13(1):128-129, 1996. [doi]

Avoiding Classic MistakesSteve McConnell. IEEE Software, 13(5):111-112, 1996. [doi]

Keep It SimpleSteve McConnell. IEEE Software, 13(6):127-128, 1996. [doi]

Sign in or sign up to see more results.

runs on WebDSL