• Corpus ID: 14910595

CHAPTER 3 SOFTWARE DESIGN

@inproceedings{Tremblay2002CHAPTER3S,
  title={CHAPTER 3 SOFTWARE DESIGN},
  author={Guy Tremblay},
  year={2002}
}
This chapter presents a description of the Software Design knowledge area for the Guide to the SWEBOK (Stone Man version). First, a general definition of the knowledge area is given. A breakdown of topics is then presented for the knowledge area along with brief descriptions of the various topics. These topic descriptions are also accompanied by references to material that provide more detailed presentation and coverage of these topics. The recommended references are then briefly described… 
1 Citations

Figures from this paper

References

SHOWING 1-10 OF 61 REFERENCES

Software design

  • D. Budgen
  • Art, Computer Science
    International computer science series
  • 1994
TLDR
This text provides students with an introduction to the role of design in software engineering, reviewing the leading design methods, both formal and informal, from a neutral viewpoint.

Recommended Practice for Software Design Descriptions

  • Computer Science
  • 1998
TLDR
The necessary information content and recommendations for an organization for Software Design Descriptions are described and this recommended practice is applicable to paper documents, automated databases, design description languages, or other means of description.

Design patterns: elements of reuseable object-oriented software

The book is an introduction to the idea of design patterns in software engineering, and a catalog of twenty-three common patterns. The nice thing is, most experienced OOP designers will find out

An Integrated Approach to Software Engineering

  • P. Jalote
  • Computer Science
    Springer Compass International
  • 1991
TLDR
This is the requirements document for the case study that will be used throughout the book, for scheduling the courses in a computer science department, based on the input about classrooms, lecture times, and time preferences of the different instructors.

Designing Software for Ease of Extension and Contraction

  • D. Parnas
  • Computer Science
    IEEE Transactions on Software Engineering
  • 1979
TLDR
It is shown that the identification of minimal subsets and minimal extensions can lead to software that can be tailored to the needs of a broad variety of users.

Designing object-oriented software

Offers basic design principles, and a specific design process, that can be applied to any software programming effort, even those not using object-oriented programming languages or environments.

Object-Oriented Design Heuristics

TLDR
Object-Oriented Design Heuristics offers insight into object-oriented design improvement and gives programmers of all levels a fast track to understanding the concepts of object- oriented programming.

The 4+1 View Model of Architecture

The 4+1 View Model organizes a description of a software architecture using five concurrent views, each of which addresses a specific set of concerns. Architects capture their design decisions in

Software architecture in practice

TLDR
This second edition of this book reflects the new developments in the field and new understanding of the important underpinnings of software architecture with new case studies and the new understanding both through new chapters and through additions to and elaboration of the existing chapters.

Program Development in Java - Abstraction, Specification, and Object-Oriented Design

TLDR
This book shows how to build production-quality programs—programs that are reliable, easy to maintain, and quick to modify with an emphasis on modular program construction.
...