! Aware > default selections > Activity specific > Software Development > Methods >

Software Development Methods

- - Software process paradigms, management, improvement, analysis.
Subsets on this page: - #Q&A - #Articles - #Books -
- #Personalize -
Search ! Aware:

  By ANN

Search all pages


By activity
Professions, Sciences, Humanities, Business, ...

User Interface
Text-based, GUI, Audio, Video, Keyboards, Mouse, Images,...

Text Strings
Conversions, tests, processing, manipulation,...

Integer, Floating point, Matrix, Statistics, Boolean, ...

Algorithms, Memory, Process control, Debugging, ...

Stored Data
Data storage, Integrity, Encryption, Compression, ...

Networks, protocols, Interprocess, Remote, Client Server, ...

Hard World
Timing, Calendar and Clock, Audio, Video, Printer, Controls...

File System
Management, Filtering, File & Directory access, Viewers, ...

Subject Divisions (default selections)
(These links to detailed subjects under this one retain your personalized selections.)

Components and OO Development - Component and Object-oriented reuse and development

#Overviews and other related subjects# - related, but not under or including this subject directly.

Books: Showing

Social Thinking--Software Practice
[Yvonne Dittrich (Editor), et al; 2002-04-21] ISBN 0262042045
- At Barnes & Noble - At Amazon - At Half

Radical Project Management
[Rob Thomsett; 2002-04-15] ISBN 0130094862
- At Barnes & Noble - At Amazon - At Half

Framework Process Patterns: Lessons Learned Developing Application Frameworks
[James Carey, Brent Carlson; 2002-04-11] ISBN 0201731320
- At Barnes & Noble - At Amazon - At Half

Agile Software Development Ecosystems
[Jim Highsmith; 2002-03-26] ISBN 0201760436
- At Barnes & Noble - At Amazon - At Half

Making Process Improvement Work: A Concise Action Guide for Software Managers and Practitioners
[Neil S. Potter, Mary E. Sakry; 2002-03-25] ISBN 0201775778
- At Barnes & Noble - At Amazon - At Half

Agile Modeling: Effective Practices for Extreme Programming and the Unified Process
[Scott W. Ambler, Ron Jeffries; 2002-03-22] ISBN 0471202827
- At Barnes & Noble - At Amazon - At Half

The Project Manager's Guide to Software Engineering's Best Practices
[Mark J. Christensen, Richard H. Thayer; 2002-03] ISBN 0769511996
- At Barnes & Noble - At Amazon - At Half

A Practical Guide to Feature-Driven Development
[Stephen R Palmer, John M. Felsing; 2002-02-11] ISBN 0130676152
- At Barnes & Noble - At Amazon - At Half

A Practical Guide to eXtreme Programming
[David Astels, et al; 2002-02-08] ISBN 0130674826
- At Barnes & Noble - At Amazon - At Half

Software Project Management in Practice
[Pankaj Jalote; 2002-01-31] ISBN 0201737213
- At Barnes & Noble - At Amazon - At Half

How to Run Successful Projects III: The Silver Bullet (3rd Edition)
[Fergus O'Connell; 2002-01-15] ISBN 0201748061
- At Barnes & Noble - At Amazon - At Half

Architecture Centric Software Project Managemenet: A Practical Guide
[Len Bass, Daniel J. Paulish; 2001-12-27] ISBN 0201734095
- At Barnes & Noble - At Amazon - At Half

Peer Reviews in Software: A Practical Guide
[Karl E. Wiegers; 2001-12-15] ISBN 0201734850
- At Barnes & Noble - At Amazon - At Half

Sams Teach Yourself Beginning Programming in 24 Hours (2nd Edition)
[Greg M. Perry; 2001-12-15] ISBN 0672323079
- At Barnes & Noble - At Amazon - At Half

People Capability Maturity Model
[Bill Curtis (Editor), et al; 2001-12-15] ISBN 0201604450
- At Barnes & Noble - At Amazon - At Half

Agile Software Development
[Alistair Cockburn; 2001-12-15] ISBN 0201699699
- At Barnes & Noble - At Amazon - At Half

Agile Software Development with SCRUM
[Schwaber Ken, et al; 2001-10-15] ISBN 0130676349
- At Barnes & Noble - At Amazon - At Half

Mechanizing Proof
[Donald A. MacKenzie; 2001-10] ISBN 0262133938
- At Barnes & Noble - At Amazon - At Half

Extreme Programming Applied: Playing to Win
[Ken Auer, Roy Miller; 2001-10] ISBN 0201616408
- At Barnes & Noble - At Amazon - At Half

(Partial list shown.)
[Complete List of Books]

Articles: Showing

Software System Engineering: A Tutorial ( Richard H. Thayer ; IEEE Computer Magazine 2002-04)

- Software, the dominant technology in many technical systems, often provides the cohesiveness and data control that enable a complex system to solve problems. Yet the vast majority of large software systems do not meet their projected schedule or estimated cost, nor do they completely fulfill the system acquirer's expectations.The application of system engineering principles to software development produces activities, tasks, and procedures called software system engineering, o rSwSE-a distinct and powerful tool for managing the technical development of large software projects. This tutorial integrates the definitions and processes from the IEEE software engineering standards into the SwSE process.

Planning and Executing Time-Bound Projects ( Eduardo Miranda ; IEEE Computer Magazine 2002-03)

- A time-bound project is constrained by hard deadlines, in which the delivery's timing is as important as the delivery itself. Because most time-bound projects start with more requirements than developers can handle within the imposed time constraints, requirements often must be slashed halfway through the project, resulting in missed deadlines, customer frustration, and wasted effort. A better approach defines requirement priorities before the project's start. But failing to prioritize requirements is not the only reason that projects miss deadlines.Traditional planning methods' inability to deal with uncertain estimates and their failure to recognize that development work does not progress linearly are also to blame. Statistically Planned Incremental Deliveries offer an approach that addresses these problems by combining ideas from critical chain planning, incremental development, and rate monitoring into a practical method for planning and executing time-bound projects.

Lessons in Agility From Internet-Based Development ( Scott W. Ambler ; IEEE Software Magazine 2002-03)

- This article describes the experiences of two Internet startup companies adopting effective and efficient modeling and documentation practices. Both organizations successfully developed agile approaches for enterprise architectural modeling, one taking a communal team-based approach and the other a chief architect approach. They adopted similar strategies for project-level modeling, adopting highly iterative and incremental approaches that focused on the act of modeling and not on the resulting models themselves. There is a "sweet spot" where modeling efforts can provide significant benefit without incurring the costs of onerous documentation.

Making Architecture Reviews Work in the Real World ( Rick Kazman, Len Bass ; IEEE Software Magazine 2002-01)

- This article explores the non-technical aspects of formal architecture reviews-social, psychological, and managerial. Architecture reviews differ from other technical reviews because of their close relationship to a system's business goals, so they need to be approached differently. The authors draw lessons from their experiences in reviewing and evaluating software and system architectures in a wide variety of application domains. They discuss the issues architects face when running such reviews, common pitfalls to avoid, and ways of increasing an organization's chances of a successful review.

Get Ready for Agile Methods, with Care ( Barry Boehm ; IEEE Computer Magazine 2002-01)

- A new generation of developers cites the crushing weight of corporate bureaucracy, the rapid pace of information technology change, and the dehumanizing effects of detailed plan-driven development as cause for revolution. In their rallying cry, the Manifesto for Agile Software Development, these developers call for a revitalized approach to development that dispenses with all but the essentials. Real-world examples argue for and against agile methods. Responding to change has been cited as the critical technical success factor in the Internet browser battle between Microsoft and Netscape. But overresponding to change has been cited as the source of many software disasters, such as the $3 billion overrun of the US Federal Aviation Administration's Advanced Automation System for national air traffic control. The author believes that both agile and plan-driven approaches have a responsible center and overinterpreting radical fringes. Agile and plan-driven methods both form part of the planning spectrum. Thus, while each approach has a home ground within which it performs very well, and much better than the other, a combined approach is feasible and preferable in some circumstances.

Continuous Process Improvement and the Risk to Information Assurance ( Goerge E. Kalb, Gerald M. Masson ; IEEE Software Magazine 2002-01)

Function-Class Decomposition: A Hybrid Software Engineering Method ( Carl K.Chang, JaneCleland-Haung, ShiyanHua, AnnieKuntzmann-Combelles ; IEEE Computer Magazine 2001-12)

Using Extreme Programming in a Maintenance Environment ( Charles Poole, Jan Willem Huisman ; IEEE Software Magazine 2001-11)

- In response to problems experienced by the Orbix Generation 3 maintenance and enhancement team, Iona Technologies tried to introduce industry-level best practices by adopting Extreme Programming. The issues discussed are common for companies moving from start-up mode to those supporting numerous customers in need of bug fixes and application enhancements for existing deployment scenarios.

Launching Extreme Programming at a Process-Intensive Company ( James Grenning ; IEEE Software Magazine 2001-11)

- The author describes a project that was started using many Extreme Programming practices in a company that has a traditional formal development process. He discusses how XP was proposed to management, how the project seed was started and grown, what the team faced during its first six months, and what worked.

Survival Patterns in Fast-Moving Software Organizations ( Lena Holmberg, Lars Mathiassen ; IEEE Software Magazine 2001-11)

- To survive, fast-moving software organizations must respond quickly to changing market needs and technological options as well as deliver high-quality products and services at competitive prices. They must therefore constantly improve their capabilities. The authors learned important lessons on how to deal effectively with the dilemmas and opportunities involved in such a goal.

Accelerating Learning from Experience: Avoiding Defects Faster ( Lutz Prechelt ; IEEE Software Magazine 2001-11)

- Defect logging and defect data analysis aim to decrease programmers' repetitive errors. DLDA was inspired by Watts Humphrey's Personal Software Process but has a much lower learning cost. A controlled experiment validated the technique.

Recovery, Redemption, and Extreme Programming ( Peter Schuh ; IEEE Software Magazine 2001-11)

- The author retells a downtrodden project's attempt to rejuvenate itself by doing Extreme Programming, discussing successes, shortcomings, and, ultimately, lessons learned. In particular, the author credits the team's composition for its ultimate success. Although XP wasn't the team's immediate salvation, it made the application sustainable past the project's deadline.

Agile Software Development: The People Factor ( Alistair Cockburn, Jim Highsmith ; IEEE Computer Magazine 2001-11)

Extreme Programming from a CMM Perspective ( Mark C. Paulk ; IEEE Software Magazine 2001-11)

- Extreme Programming has been advocated recently as an appropriate programming method for the high-speed, volatile world of Internet and Web software development. The author reviews XP from the perspective of the Capability Maturity Model for Software, gives overviews of both approaches, and critiques XP from a SW-CMM perspective. He concludes that lightweight methodologies such as XP advocate many good engineering practices and that both perspectives have something to offer the other.

What I Did Last Summer: A Software Development Benchmarking Case Study ( James T. Heires ; IEEE Software Magazine 2001-09)

- This article describes a vendor-supported benchmarking study of an applications development (IT) department. The study established a quantitative performance baseline of the organization and compared it to industry trends.

Software Cultures and Evolution ( Václav Rajlich, Norman Wilde, Michelle Buckellew, Henry Page ; IEEE Computer Magazine 2001-09)

- Working effectively with legacy code requires understanding a legacy computer program's culture: the combination of programmer background, hardware environment, and programming techniques that guided its creation. Software systems typically pass through a series of stages. During the development stage, software developers create a functioning version of the code. An evolution stage follows, during which developmental efforts focus on extending system capabilities to meet user needs. The servicing stage restricts development to minor repairs and simple functional changes. The phase-out stage essentially freezes the system, but it still produces value. Finally, in the close down stage, developers withdraw the system and possibly replace it. Effective comprehension requires viewing a legacy program as an artifact of the circumstances in which it was developed. This information can be important in determining appropriate strategies for the program's transition from the evolution stage to the servicing or phase-out stage.

Agile Software Development: The Business of Innovation ( Jim Highsmith, Alistair Cockburn ; IEEE Computer Magazine 2001-09)

- Agile development combines creative teamwork with an intense focus on effectiveness and maneuverability.

The Benchmarking Process: One Team's Experience ( Sam Fogle, Carol Loulis, Bill Neuendorf ; IEEE Software Magazine 2001-09)

- Recently, the Software Productivity Consortium conducted a benchmarking study of process asset libraries. The report provided a significant set of ideas for organizations seeking to create new PALs or improve existing ones. Even the participants with the most "best practices" found gems among other participants' best practices for use in their continuous improvement efforts. This article discusses why we chose a benchmarking approach, the process we used in conducting this study, and key lessons we learned for future studies.

Using Structured Benchmarking to Fast-Track CMM Process Improvement ( Gareth C. Thomas, Howard R. Smith ; IEEE Software Magazine 2001-09)

- Sikorsky Aircraft, in pursuit of a formal rating based on the Capability Maturity Model from the Software Engineering Institute, determined that software benchmarking would help plan the process improvement and assessment effort. With the assistance of a benchmarking expert, Sikorsky developed a benchmarking questionnaire, which it used at five selected companies. The results then successfully guided its process improvement project. This article describes the activities in preparing for the benchmarking trips, structuring the questionnaire, aggregating the results, and evaluating the lessons learned.

(Partial list shown.)
[Complete List of Articles]

Questions and Answers: Showing

How Many Developers to Maintain Large Project? [2001/11/20]

At Ask Slashdot

Web-Based Project Management Tools? [ 2000/03/29]

At Ask Slashdot

Open Source Project Management Guides? [ 1999/09/22]

At Ask Slashdot

Related Subjects (default selections)
Subject classifications directly under this one are #here#.

(The following links to subjects at this site retain your personalized selections.)

Automated Build Utilities - make and similar programs for compiling and creating executable software from source

Specific Programming Languages - C, PERL, Fortran, et al.

Protocol Development - Theory and techniques for developing communications protocols.

Software Licensing - Intellectual Property Considerations, comparing licenses, legal issues

Software Quality - Software correctness and reliability

Software Measurement and Metrics - Measurement of software for various uses

Software Design - Planning, specification, requirements.

Software Documentation - Creating user and developer documentation. Visualizing existing systems.

(There may be additional related subject pages listed here)

Personalized Selections
MS Windows.
  GPL or LGPL.
Tip: To exclude choices, select all others in same column

Use our system: Bring Rapid Knowledge Transfer and Awareness to your company website!

Rapid-Links: Search | About | Comments | Submit Path: RocketAware > Activity specific > Software Development > Methods >
RocketAware.com is a service of Mib Software
Copyright 2002, Forrest J. Cavalier III. All Rights Reserved.
We welcome submissions and comments