Search results
Results from the WOW.Com Content Network
Ian Sommerville's research work, partly funded by the EPSRC [5] has included systems requirements engineering and system evolution. He defined the process of Construction by configuration (CbC). A major focus has been system dependability , including the use of social analysis techniques such as ethnography to better understand how people and ...
IEEE Standard Glossary of Software Engineering Terminology [21] "An engineering discipline that is concerned with all aspects of software production."—Ian Sommerville [22] "The establishment and use of sound engineering principles in order to economically obtain software that is reliable and works efficiently on real machines."—Fritz Bauer [23]
The ACM SIGSOFT Software Engineering Notes (SEN) is published by the Association for Computing Machinery (ACM) for the Special Interest Group on Software Engineering (SIGSOFT). [1] It was established in 1976, and the first issue appeared in May 1976. [2] It provides a forum for informal articles and other information on software engineering.
The Quest for Software Requirements: Probing Questions to Bring Nonfunctional Requirements Into Focus; Proven Techniques to Get the Right Stakeholder Involvement. MavenMark Books. ISBN 978-1-59598-067-0. Sommerville, Ian; Sawyer, Pete (May 1997). Requirements Engineering: A Good Practice Guide. John Wiley. ISBN 0-471-97444-7.
Ian Sommerville may refer to: Ian Sommerville (software engineer) (born 1951), British computer scientist and author; Ian Sommerville (technician) (1940–1976), British electronics technician and computer programmer
The following outline is provided as an overview of and topical guide to software engineering: Software engineering – application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software; that is the application of engineering to software. [1]
[1] [2] Some like software engineer and author Ian Sommerville don't use the term "quality control" (as quality control is often viewed as more a manufacturing term than a software development term), rather, linking its associated concepts with the concept of quality assurance. [3] However, the three core components otherwise remain the same.
A similar effort to define a body of knowledge for software engineering is the "Computing Curriculum Software Engineering (CCSE)," officially named Software Engineering 2004 (SE2004). The curriculum largely overlaps with SWEBOK 2004 since the latter has been used as one of its sources, although it is more directed towards academia.