University of Cebu-Banilad Library catalog › Details for: Software design /

Normal view MARC view ISBD view

Software design / Dr. Bechoo Lal.

By: Lal, Bechoo [author. ]Material type: Text

TextPublisher: Burlington, ON : Toronto Academic Press, c2024Description: vii, 221 pages : color illustrations ; 25 cmContent type: text Media type: unmediated Carrier type: volume ISBN: 9781774697795 [paperback] Subject(s): Software design | Computer software -- Development

Contents:

1 Introduction to software design -- 2 Software design process -- 3 Design qualities -- 4 Design principles -- 5 Software architecture -- 6 Typical architectural styles -- 7 Using styles in design -- 8 Architectural design space.

Summary: "The importance of design in software development cannot be overstated. Software design is complex for a variety of reasons. It is significantly more challenging to teach and learn software design. There have been numerous textbooks created on software design. Most focus on a single program design method, such as object-oriented software development. Few, however, have tackled software design at a higher level of abstraction, such as the methodological level, which is the focus of this subject. In my experience teaching software design in advanced undergraduate courses and overseeing student dissertation projects, I've discovered that students frequently have misconceptions about software design. One of the most widespread misconceptions about software design is that there is only one correct answer to each design problem. Many software design textbooks provide case studies and examples, but few offer many answers to a single design problem. A prevalent fallacy to software design approaches is that using a well-established design method correctly always results in the correct solution to a design problem. As a result, many student rush to the implementation stage of their dissertation projects after completing a design without extensively analyzing and assessing it; even fewer thought of creating alternative ideas and comparing them. Few software design textbooks tackle how to analyze a design and compare different software designs. Learning software design techniques might help correct misconceptions about software design methodologies. Theories of software architecture, particularly software architectural styles and architectural design analysis and evaluation, are at the appropriate level of abstraction and are especially useful for correcting students' mistakes. Another difficulty in teaching and learning software design is that most students have no prior experience with large-scale, complex software systems. The theories of software architecture also provide an appropriate communication medium for students to learn how to design large-scale software systems. It can combine numerous software engineering, development processes, and programming information taught in multiple courses into a well-organized framework. It also considerably broadens student's understanding of software systems." -- Preface.

Tags from this library: No tags from this library for this title. Log in to add tags.

Average rating: 0.0 (0 votes)

Holdings ( 1 )
Title notes ( 6 )
Comments ( 0 )

Item type	Current location	Call number	Status	Date due	Barcode
Subject Reference	College Annex Library Subject Reference	005.12 L15 2024 (Browse shelf)	Available		3UCBL000028807

Includes bibliographical references and index.

"The importance of design in software development cannot be overstated. Software design is complex for a variety of reasons. It is significantly more challenging to teach and learn software design. There have been numerous textbooks created on software design. Most focus on a single program design method, such as object-oriented software development. Few, however, have tackled software design at a higher level of abstraction, such as the methodological level, which is the focus of this subject. In my experience teaching software design in advanced undergraduate courses and overseeing student dissertation projects, I've discovered that students frequently have misconceptions about software design. One of the most widespread misconceptions about software design is that there is only one correct answer to each design problem. Many software design textbooks provide case studies and examples, but few offer many answers to a single design problem. A prevalent fallacy to software design approaches is that using a well-established design method correctly always results in the correct solution to a design problem. As a result, many student rush to the implementation stage of their dissertation projects after completing a design without extensively analyzing and assessing it; even fewer thought of creating alternative ideas and comparing them. Few software design textbooks tackle how to analyze a design and compare different software designs. Learning software design techniques might help correct misconceptions about software design methodologies. Theories of software architecture, particularly software architectural styles and architectural design analysis and evaluation, are at the appropriate level of abstraction and are especially useful for correcting students' mistakes. Another difficulty in teaching and learning software design is that most students have no prior experience with large-scale, complex software systems. The theories of software architecture also provide an appropriate communication medium for students to learn how to design large-scale software systems. It can combine numerous software engineering, development processes, and programming information taught in multiple courses into a well-organized framework. It also considerably broadens student's understanding of software systems." -- Preface.