Software Engineering: A Methodical Approach

Software Engineering: A Methodical Approach

Elvis C. Foster

Language: English

Pages: 582

ISBN: B00OLET516

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.

 

 

 

 

 

 

 

 

 

 

243 14.​2 Standards and Quality Assurance 244 14.​2.​1 The Relationship between Quality and Standards 245 14.​2.​2 Software Quality Factors 246 14.​2.​3 Quality Assurance Evaluation 246 14.​3 Management of Targets and Financial Resources 247 14.​3.​1 Managing Budget and Expenditure 248 14.​3.​2 Managing Software Cost and Value 249 14.​4 Leadership and Motivation 249 14.​5 Planning of Implementation Strategy 251 14.​6 Summary and Concluding Remarks 251 14.​7 Review Questions 252 14.​8

to know what a relationship is and what types of relationships there are. Your course in database systems will elucidate these issues to some level of detail. For now, you may consider a relationship as a mapping involving two or more information entities (or object types) so that a data item (an object) in one relates in some way to at least one data item (object) in the other(s) and vice versa. There are seven types of relationships: One-to-one (1:1) relationship One-to-many (1:M)

development phase of a software engineering project? 2.Explain how software standards relate to quality assurance. Outline a procedure for maintaining software quality. 3.Discuss the QA evaluation exercise and propose an instrument for use during this experience. 4.Describe a technique for managing resources, targets, budget and expenditure during software development. 5.How important is leadership during a software engineering project? Explain. 14.8 References and/or Recommended Readings

Elvis C. Foster1  (1)MA, USA Software economics was first introduced in chapter 3 (section 3.7) though not by that term. At that time, we were discussing the feasibility of the software engineering project. After reading chapter 3, one may get the impression that software cost is equal to development cost. In this chapter, you will see that the two are often different; that development cost is just one component of software cost; and that there are other factors. You will also see that

is determined based on the following seven factors (called cost drivers). In the interest of clarity, the originally proposed acronyms have been changed: Product Reliability and Complexity (PRC) Required Reuse (RR) Platform Difficulty (PD) Personnel Capability (PC) Personnel Experience (PE) Facilities (F) Schedule (S) Post-Architecture Model The post-architecture model is the most detailed of the COCOMO II sub-models. It is recommend for use during actual development, and subsequent

Download sample

Download