000			03616nam a22003137a 4500
003			OSt
005			20250423191419.0
008			250423b |||||||| |||| 00| 0 eng d
020			_a9781774697795 [paperback]
040			_aUniversity of Cebu-Banilad _cUniversity of Cebu-Banilad
100			_aLal, Bechoo, _eauthor.
245			_aSoftware design / _cDr. Bechoo Lal.
260			_aBurlington, ON : _bToronto Academic Press, _cc2024.
300			_avii, 221 pages : _bcolor illustrations ; _c25 cm.
336			_2rdacontent _atext
337			_2rdamedia _aunmediated
338			_2rdacarrier _avolume
504			_aIncludes bibliographical references and index.
505			_a1 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.
520			_a"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.
521			_aAdult
541			_aPurchased _xBrigoli, Darlyne _yCollege of Computer Engineering _zComputer Engineering
546			_aText in English
650			_aSoftware design
650			_aComputer software _xDevelopment
942			_2ddc _cBK
998			_cJanna [new] _d04/23/2025
999			_c13540 _d13540