Sommerville, I., Software engineering. 4th ed. International computer science series. 1992, Reading, Mass.: Addison-Wesley Pub. Co. xvi, 649. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Software Evolution and Software Evolvability - Cook, Ji, Harrison (2000) (1 citation) (Correct)
....our preliminary results of defining a quality model of evolvability. 4.1. Defining evolvability The essence of evolving a software product is to modify the corresponding parts and elements of the product. Modifications can be classified into three categories: corrective, adaptive and perfective [36]. In our model of evolvability, we are mainly concerned with the modifiers point of view, since the ease with which a product can be modified is experienced primarily by the modifiers. The modifiers could either be end users who want to make some changes on their own, or professional software ....
I. Sommerville, Software engineering, 5th ed. International Computer Science Series. Wokingham, UK: Addison-Wesley, 1995.
Using Decision Tools in Deciding System Product Requirements.. - Hurri (2000) (Correct)
....into use, possibly ported to other platforms etc. So we have a model of the life of a requirement, and we examine the goodness of a requirement by determining whether it will survive all states. The simple lifecycle used here is based on system and software development models (see, for example, [81, 73]) and logical reasoning of the steps that a product must go through in its lifetime. In each step of the lifecycle we can assess the goodness of the requirement. The states and corresponding success criteria that I have identified by this state based procedure are as follows. design: The ....
Sommerville, I. Software engineering, 4th ed. International computer science series. Addison-Wesley, 1992.
FT-SR: A Programming Language For Constructing Fault-Tolerant.. - Thomas (1993) (1 citation) (Correct)
....faults before they cause errors. Examples of hardware fault tolerance techniques are the use of error detection and correction codes, and instruction retry [Pra86] Fault prevention techniques commonly used in the design and development of software layers are the use of top down software design [Som92] structured programming [DDH72] program verification [Gri81] software walk throughs [Zie83] and software development tools [Fis91] All these techniques aim at systematizing the process of software development by encouraging the use of an engineering approach in the design and implementation ....
Ian Sommerville. Software Engineering. International computer science series. Addison-Wesley, Reading, Massachussetts, fourth edition, 1992.
Code review and personality: is performance linked to MBTI type? - Cunha, Greathead (2004) (Correct)
No context found.
Sommerville, I., Software engineering. 4th ed. International computer science series. 1992, Reading, Mass.: Addison-Wesley Pub. Co. xvi, 649.
Object-Oriented Requirements Engineering for GIS-Applications - Kösters, Pagel, Six (1995) (4 citations) (Correct)
No context found.
I. Sommerville. Software Engineering. International Computer Science Series. Addison-Wesley, Wokingham, England, 4th edition, 1992.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC