Análisis y Dise˜no

More documents

Recommendations

Info

eferencia principal del capítulo de medición [11], y a los artículos citados enel texto [5] y [2].Referencias[1] Grady Booch, James Rumbaugh, and Ivar Jacobson. Unified ModelingLanguage User Guide, 2nd Edition. Addison-Wesley Professional, 2005.[2] Fernando Brito e Abreu and Walcelio Melo. Evaluating the impact ofobject-oriented design on software quality. In METRICS ’96: Proceedingsof the 3rd International Symposium on Software Metrics, pages90–99, Washington, DC, USA, 1996. IEEE Computer Society.[3] Bernd Bruegge and Allen H. Dutoit. Object-Oriented Software Engineering:Using UML, Patterns and Java, Second Edition. Prentice Hall,September 2003.[4] David Budgen. Software Design. Addison Wesley, 2003.[5] S. R. Chidamber and C. F. Kemerer. A metrics suite for object orienteddesign. IEEE Transactions on Software Engineering, 20(6):476–493,1994.[6] George Coulouris, Jean Dollimore, and Tim Kindberg. Distributed systems(3rd ed.): concepts and design. Addison-Wesley Longman PublishingCo., Inc., Boston, MA, USA, 2001.[7] O. J. Dahl, E. W. Dijkstra, and C. A. R. Hoare, editors. Structuredprogramming. Academic Press Ltd., London, UK, UK, 1972.[8] Tom DeMarco. Structured analysis and system specification. 1979.[9] Edsger W. Dijkstra. Notes on structured programming. Technical Report70-WSK-03, Technological University Eindhoven, 1970.55
[10] Mohamed E. Fayad, Douglas C. Schmidt, and Ralph E. Johnson. ImplementingApplication Frameworks: Object-Oriented Frameworks at Work.John Wiley & Sons, Inc., New York, NY, USA, 1999.[11] Norman E. Fenton and Shari Lawrence Pfleeger. Software Metrics: aRigorous & Practical Approach. International Thompson Press, 1997.[12] Martin Fowler. UML Distilled: A Brief Guide to the Standard. Adison-Wesley, 2004.[13] Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides. DesignPatterns: Elements of Reusable Object-Oriented Software. Addison-Wesley Longman Publishing Co., Inc., Boston, MA, USA, 1995.[14] Chris P. Gane and Trish Sarson.[15] David Harel. Statecharts: A visual formalism for complex systems. Scienceof Computer Programming, 8(3):231–274, June 1987.[16] S. Henry and D. Kafura. Software structure metrics based on informationflow. IEEE Transactions on Software Engineering, 7(5):510–518,1981.[17] C. A. R. Hoare. An axiomatic basis for computer programming. Communicationsof the ACM, 26(1):53–56, 1983.[18] IEEE. IEEE standard glossary of software engineering terminology,1990.[19] M.A. Jackson. Principles of Program Design. Academic Press, Inc.,Orlando, FL, USA, 1975.[20] Ivar Jacobson, Grady Booch, and James Rumbaugh. The unified softwaredevelopment process. Addison-Wesley Longman Publishing Co.,Inc., Boston, MA, USA, 1999.[21] Ralph E. Johnson and Brian Foote. Designing reusable classes. Journalof Object-Oriented Programming, 1(2):22–35, June/July 1988.56
Page 3:
4.3. Diseño por contratos . . . .
Page 6 and 7:
Abstracción de control. Define a u
Page 9 and 10: Figura 1: (a) Acoplamiento débil;
Page 11 and 12: estándar ISO/IEC 42010:2007, defin
Page 13 and 14: Figura 2: Estilo arquitectónico de
Page 15 and 16: Figura 5: (a) Cliente-servidor; (b)
Page 17 and 18: Figura 6: Evolución de los método
Page 19 and 20: Figura 8: Niveles en los diagramas
Page 21 and 22: Regla1 2 3CondicionesEdad > 60 Sí
Page 23 and 24: ases de datos. El modelo Entidad/Re
Page 25 and 26: Al igual que con los métodos estru
Page 27 and 28: Kruchten [23] mediante modelos y di
Page 29 and 30: Figura 13: Diagrama de clasesDiagra
Page 31 and 32: Figura 15: Ejemplos de diagrama de
Page 33 and 34: Resumen del diseño orientado a obj
Page 35 and 36: Finalmente, el paradigma de la orie
Page 37 and 38: solución un millón de veces en el
Page 39 and 40: Figura 19: Patrón Observerclase de
Page 41 and 42: Figura 20: Patrón StrategyAdemás,
Page 43 and 44: Es decir, el framework debe ser lo
Page 45 and 46: nentes, donde la no disposición de
Page 47 and 48: 5. Diseño de sistemas distribuidos
Page 49 and 50: distribuido. Para ello deben de imp
Page 51 and 52: Un tipo de validación, aunque meno
Page 53 and 54: Dentro de la orientación a objetos
Page 55 and 56: Profundidad en árbol de herencia (
Page 57: software y cubre tanto las metodolo
Page 61: [34] James Rumbaugh, Ivar Jacobson,
show all

Análisis y Dise˜no

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?