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 [22] "An engineering discipline that is concerned with all aspects of software production."—Ian Sommerville [23] "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 [24]
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 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.
[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.
Over the last 10–15 years Michael A. Jackson has written extensively about the nature of software engineering, has identified the main source of its difficulties as lack of specialization, and has suggested that his problem frames provide the basis for a "normal practice" of software engineering, a prerequisite if software engineering is to ...
Functionality, usability, reliability, performance and supportability are together referred to as FURPS in relation to software requirements. Agility in working software is an aggregation of seven architecturally sensitive attributes: debuggability, extensibility, portability, scalability, securability, testability and understandability.
He and software developer Dennis Austin led the development of a program called Presenter, which they later renamed PowerPoint. [1] Also in 1984, Forethought acquired the rights to publish a Macintosh version of a DOS-based application called Nutshell. They named the Mac version FileMaker and it soon became enormously successful. [2]