Software Engineering: A Methodical Approach
Elvis C. Foster
Format: PDF / Kindle (mobi) / ePub
This text provides a comprehensive, but concise introduction to software engineering. It adopts a methodical approach to solving software engineering problems proven over several years of teaching, with outstanding results.
The book covers concepts, principles, design, construction, implementation, and management issues of software systems. Each chapter is organized systematically into brief, reader-friendly sections, with itemization of the important points to be remembered. Diagrams and illustrations also sum up the salient points to enhance learning. Additionally, the book includes a number of the author's original methodologies that add clarity and creativity to the software engineering experience, while making a novel contribution to the discipline.
Upholding his aim for brevity, comprehensive coverage, and relevance, Foster's practical and methodical discussion style gets straight to the salient issues, and avoids unnecessary fluff as well as an overkill of theoretical calculations.
What you'll learn
- The main activities of the software development life cycle (SDLC)
- How to conceptualize, research, design, construct, implement, and manage top quality software systems
- How to evaluate the impact of software systems on organizations
- The nature, importance, and scope of software engineering as opposed to programming
Who this book is for
This book is best suited for students who are pursuing a course in software engineering. Practicing software engineers who need a quick reference on various aspects of the field will also find this text useful.
Distributed Systems: Concepts and Design (5th Edition)
Data Structures and Algorithm Analysis in C++ (4th Edition)
HCI Beyond the GUI: Design for Haptic, Speech, Olfactory, and Other Nontraditional Interfaces (Interactive Technologies)
Persons), then it is advisable to develop an easy to read document. The requirements specification may be developed with inexpensive applications such as MS Office, Corel Suite, etc. If a CASE tool is available, it should be used since this will enhance the system development process. In fact, in many cases, the diagrams used in the CASE tool are executable — code is generated from them — so that the distinction of requirements specification from design and design from development are absent.
Software design and development standards. Describe six important issues that these standards must address. 6.Which deliverable comes after software design? What is this deliverable comprised of? How would you proceed to construct such a deliverable? 9.9 References and/or Recommended Readings [Lee, 2002] Lee, Richard C. and William M. Tepfenhart. Practical Object-Oriented Development With UML and Java. Upper Saddle River, NJ: Prentice Hall, 2002. See chapter 4. [Martin, 1993] Martin, James,.
And James Odell. Principles of Object-Oriented Analysis and Design. Eaglewood Cliffs, NJ: Prentice Hall, 1993. See chapters 6 and 7. [Rumbaugh, 1991] Rumbaugh, James, Michael Blaha, William Premerlani, Frederick Eddy and William Lorensen. Object Oriented Modeling And Design. Eaglewood Cliffs, NJ: Pretence Hall, 1991. See chapter 4. [Ullman, 1997] Ullman, Jeffrey and Jennifer Widom. A First Course in Database Systems. Upper Saddle River, NJ: Prentice Hall, 1997. See chapters 1-3. � Elvis C.
Technical document that is ideally suited for system managers and software engineers, whose responsibility it will be to maintain the system. It is a technical summary of the system, outlining: The main components The operating constraints and configuration issues Security issues Syntax and explanations of system commands (for command interface) Explanations of system commands (for menu or graphical interface) For other categories of software such as development tools for software.
Infrastructure. Recurrent expenditures relate to operational issues (such as salaries, stationary, fuel, heating, electricity, transportation, etc.) Figure 14-3 illustrates how a budget might be composed. Please note: 1.Each summary item (e.g. Network Upgrade) would have associated detail line items that may be part of the main document, or included as an appendage. The details will show how each summary amount was arrived at. 2.In some instances, supporting documentation (such as quotations.