McDermid J. and Rook, P.,(1991) "Software Development Process Models" in "The Software Engineers Reference Book", ed. McDermid, J., Butterworth-Heineman  Home/Search   Document Not in Database   Summary   Related Articles   Check

....of the procedural logic of the modules function members the code itself house keeping and project management information. the Tcl Tk prototyping langauages. 7] 2.3.1.3 Experimental Programming Experimental programming has been referred to as programming without a specification. [8]. It is particularly useful for designing new algorithms, but likely to cause maintenance problems if the code developed is not subsequently documented. MOOSE allows this approach with the caveat that it is best done in conjunction with the JACI CASE tool, which gives significant help with ....

McDermid J. and Rook, P.,(1991) "Software Development Process Models" in "The Software Engineers Reference Book", ed. McDermid, J., Butterworth-Heineman

....interface items (menus, buttons, etc. onto classes that can implement that means of interaction. Tool support for this is available via the Tcl Tk prototyping langauages. 9] 3.3.1.3 Experimental Programming Experimental programming has been referred to as programming without a specification. [10]. It is particularly useful for designing new algorithms, but likely to cause maintenance problems if the code developed is not subsequently documented. MOOSE allows this approach with the caveat that it is best done in conjunction with the JACI CASE tool, which gives significant help with ....

McDermid J. and Rook, P.,(1991) "Software Development Process Models" in "The Software Engineers Reference Book", ed. McDermid, J., Butterworth-Heineman

....skills. The principal aim of the project is to give students an opportunity to apply practically what they have been taught in the Software Engineering lectures. The project itself is well structured into phases [3] and follows the classical software lifecycle model with a few alterations [4] (Figure 1) B.Meyer, On Formalism in Specification IEEE Software 1985 pp6 26 Preparatory Phase: 1week Phase 5: 1 week Phase 4: 4 weeks Phase 3: 4 weeks Phase 2: 1 week Phase 1: 5 weeks Domain Analysis Accept. Test Implementation Testing Design Req.Appraisal Requirements ....

J. A. McDermid and P. Rook, "Software development process models," in Software Engineer's Reference Book, J. A. McDermid, Ed.: Butterworth-Heinemann, 1991, pp. 1-35.

....system should be adhered to that conforms to BS 5750 [64] These requirements are the minimum for safety critical software, and additional recommendations are outlined. 15 7.2. 1 To follow a suitable software life cycle model: There are many such models of the development cycle of software [65] and it is not too important which particular one is used as long as a life cycle model is formally adopted. This imposes a structure on the development of software to prevent the uncontrolled chaos that it can too easily slide into. The combination of a software life cycle, an agreed ....

P Rook. Software Development Process Models. In P Rook, editor, Software Reliability Handbook, pages 413--440. Elsevier Applied Science, 1990. 23

....approach we would have to establish existence of an object by reasoning about the sequence of inputs to the system and determining whether the object had been created (successfully) since it was last deleted. This would make the specification obscure and cumbersome. John McDermid and Paul Rook [MR91] Work reported here has been partially supported by the CEC under Grant No. 6112 (COMPASS) We do not follow the above arguments, but propose an algebraic approach to the specification of information systems dealing with the notion of state in an implicit manner. Thus the above criticism ....

J. McDermid and P. Rook. Software Development Process Models. In J. McDermid, editor, Software Engineer's Reference Book, chapter 15, pages 15/1--15/36. Butterworth-Heinemann, Oxford, 1991.

....can be performed using traditional implementation techniques like programming languages, data definition manipulation languages, existing resources like communication platforms etc. Although this straightforward process in the software engineering community called waterfall model [MR91] is appealing due to clearly defined interfaces between different specification documents, it is generally accepted that such an approach is seldom practical because [Hum90] it does not adequately address changes, usually the development steps are not in such an orderly sequence, and it ....

J.A. McDermid and P. Rook. Software Development Process Models. In J.A. McDermid, editor, Software Engineer's Handbook, Chapter 15. Butterworth-Heinemann Ltd., 1991.

....when we discuss and illustrate particular formal techniques in appendix A. 3.1 The Software Life Cycle We give here a brief overview of the nature and scope of the software life cycle. A fuller description of life cycle concepts and the important concepts of process design can be found in [ MR91] The software life cycle is concerned with the development of software from initial concepts through delivery, use, and so called maintenance. It is helpful to produce a generic model of the life cycle in order to have a basis for discussing different software development paradigms. Therefore ....

J A McDermid and P Rook. Software development process models. Software Engineers' Reference Book, 1991.

No context found.

McDermid, J. and Rook, P., Software development process models, in Software Engineer's Reference Book, CRC Press, 1993. pp15/26~28.

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