| 000 -LEADER |
|---|
| fixed length control field |
03616nam a22003137a 4500 |
| 003 - CONTROL NUMBER IDENTIFIER |
|---|
| control field |
OSt |
| 005 - DATE AND TIME OF LATEST TRANSACTION |
|---|
| control field |
20250423191419.0 |
| 008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION |
|---|
| fixed length control field |
250423b |||||||| |||| 00| 0 eng d |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER |
|---|
| International Standard Book Number |
9781774697795 [paperback] |
| 040 ## - CATALOGING SOURCE |
|---|
| Original cataloging agency |
University of Cebu-Banilad |
| Transcribing agency |
University of Cebu-Banilad |
| 100 ## - MAIN ENTRY--PERSONAL NAME |
|---|
| Personal name |
Lal, Bechoo, |
| Relator term |
author. |
| 245 ## - TITLE STATEMENT |
|---|
| Title |
Software design / |
| Statement of responsibility, etc |
Dr. Bechoo Lal. |
| 260 ## - PUBLICATION, DISTRIBUTION, ETC. (IMPRINT) |
|---|
| Place of publication, distribution, etc |
Burlington, ON : |
| Name of publisher, distributor, etc |
Toronto Academic Press, |
| Date of publication, distribution, etc |
c2024. |
| 300 ## - PHYSICAL DESCRIPTION |
|---|
| Extent |
vii, 221 pages : |
| Other physical details |
color illustrations ; |
| Dimensions |
25 cm. |
| 336 ## - CONTENT TYPE |
|---|
| Source |
rdacontent |
| Content type term |
text |
| 337 ## - MEDIA TYPE |
|---|
| Source |
rdamedia |
| Media type term |
unmediated |
| 338 ## - CARRIER TYPE |
|---|
| Source |
rdacarrier |
| Carrier type |
volume |
| 504 ## - BIBLIOGRAPHY, ETC. NOTE |
|---|
| Bibliography, etc |
Includes bibliographical references and index. |
| 505 ## - FORMATTED CONTENTS NOTE |
|---|
| Formatted contents note |
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. |
| 520 ## - SUMMARY, ETC. |
|---|
| Summary, etc |
"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 ## - TARGET AUDIENCE NOTE |
|---|
| Target audience note |
Adult |
| 541 ## - IMMEDIATE SOURCE OF ACQUISITION NOTE |
|---|
| Source of acquisition |
Purchased |
| Deans/Chairperson |
Brigoli, Darlyne |
| Department |
College of Computer Engineering |
| Subject Category |
Computer Engineering |
| 546 ## - LANGUAGE NOTE |
|---|
| Language note |
Text in English |
| 650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| Topical term or geographic name as entry element |
Software design |
| 650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| Topical term or geographic name as entry element |
Computer software |
| General subdivision |
Development |
| 942 ## - ADDED ENTRY ELEMENTS (KOHA) |
|---|
| Source of classification or shelving scheme |
|
| Type of record |
Book |
| 998 ## - LOCAL CONTROL INFORMATION (RLIN) |
|---|
| Encoded by |
Janna [new] |
| Date encoded |
04/23/2025 |
