| R. S. Pressman. Software Engineering, A Practitioner Approach. McGraw-Hill, third edition, 1992. |
....the Apriori algorithm [7] originally presented in the data mining domain to 1 For simplicity we refer to the term label attribute as attribute. 2 In the rest of paper we refer to aggregate type and global variable as type and var, respectively. 2 1 A = 3, 3, 3, 3, 3, 3, 3, 3, 3, 2] 1 N = [1, 7, 10, 2, 13, 11, 16, 15, 12, 6] (c) Region G1: after applying Apriori. a) Source model graph G (b) Region G1 of graph G 11 15 12 6 13 10 2 7 16 1 3 4 11 17 18 19 16 12 8 13 6 15 1 2 10 5 7 9 10 14 with main node: 1 7 2 1 15 11 6 13 12 16 Edge of type: call F use T use V Node of type: ....
.... types have been defined with different degrees of importance in affecting the quality of a software, including: data, stamp, control, external, and common as coupling strengths; and coincidental, logical, temporal, procedural, communicational, sequential, and functional as cohesion strengths [16]. In a software system consisting of modules, coupling is a measure of the relative interdependence among the modules, and cohesion is a measure of the relative functional strength of a module [16] We approximate the coupling and cohesion metrics among system components with the ....
[Article contains additional citation context not shown here]
R. S. Pressman. Software Engineering, A Practitioner Approach. McGraw-Hill, third edition, 1992.
....a software maintenance point of view single point of control is a very optimal scenario [11] Our design framework also promises data independence, which will help in creating extensible models. Keeping data separate from the application promises more flexibility, extensible and better maintenance [12]. This paper bridges the gap between research and practice. Many researchers propose techniques for managing change in the software architecture for a software system, but few have addressed legacy issues. Our paper seeks to evolve earlier, legacy systems to apply architectural evolution ideas. ....
Roger Pressman, Software Engineering, A Practitioners Approach. Fourth Edition. McGraw Hill 1996.
.... References(M; t)Exports(M; t)g T ; and V = fvjV ariable(v) Contains(M; v) PhiImports(M; v) References(M; v)Modifies(M; v) Exports(M; v)g V: The semantics of the predicates Imports, Exports, Contains, References, Modifies are those presented in the standard Software Engineering literature [41, 71]. The Contains and Imports predicates are module constructors, whereas, the others define the module s properties. Having defined the notion of a module we can define an architecture to be a decomposition of a system into n modules M i = hL i ; F i ; T i ; V i i; i 2 f1: ng, which interact with ....
....engineering is the result of long term experience of the practitioners, engineering 33 techniques from the related domains such as hardware and system engineering, and the state of the technology for automating operations. Research in software engineering is partitioned into three subjects [71]: ffl Process, is responsible for organizing and monitoring different phases of a software development project such as: project planning and estimation, system and software requirements analysis, design, coding, testing, and maintenance. Various processes tend to fall into three well established ....
[Article contains additional citation context not shown here]
R. S. Pressman. Software Engineering, A Practitioner Approach. McGraw-Hill, third edition, 1992.
No context found.
R.S. Pressman, Software Engineering. A Practitioners Approach, third edition, McGraw Hill, 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