Guidelines Based Software Engineering for Developing Software Components

.
DOI: 10.4236/jsea.2012.51001   PDF   HTML     7,456 Downloads   14,187 Views   Citations

Abstract

Software guidelines have been with us in many forms within Software Engineering community such as knowledge, experiences, domain expertise, laws, software design principles, rules, design heuristics, hypothesis, experimental results, programming rules, best practices, observations, skills, algorithms have played major role in software development. This paper presents a new discipline known as Guidelines Based Software Engineering where the aim is to learn from well-known best practices and documenting newly developed and successful best practices as a knowledge based (could be part of the overall KM strategies) when developing software systems across the life cycle. Thereby it allows reuse of knowledge and experiences.

Share and Cite:

M. Ramachandran, "Guidelines Based Software Engineering for Developing Software Components," Journal of Software Engineering and Applications, Vol. 5 No. 1, 2012, pp. 1-6. doi: 10.4236/jsea.2012.51001.

Conflicts of Interest

The authors declare no conflicts of interest.

References

[1] L. Parnas, “Good Program Design,” Prentice-Hall, New Jersey, 1979.
[2] E. W. Dijkstra, “Selected Writings on Computing: A Personal Perspective,” ACM Classic Books Series, 1982.
[3] T. Hoare, “Concurrent Programs,” Prentice-Hall, New Jersey, 1979.
[4] M. Ramachandran and Sommerville, “Software Reuse Assessment,” First International Workshop on Software Reuse, Germany, 1992.
[5] M. Ramachandran, “Software Components: Guidelines and Applications,” Nova Publishers, New York, 2008. https://www.novapublishers.com/catalog/product_info.php?products_id=7577
[6] I. Sommerville and P. Sawyer, “Requirements Engineering: Good Practice Guide,” Addison Wesley, Boston, 1999.
[7] M. Ramachandran, “Knowledge Engineering for Software Development Life Cycle,” IGI Global, Hershey, 2011. doi:10.4018/978-1-60960-509-4
[8] Pressman, “Software Engineering,” 6th Edition, McGraw Hill, New York, 2005.
[9] A. Endres and D. Rombach, “A Handbook of Software and Systems Engineering,” Addison Wesley, Boston, 2003.
[10] W. A. Brown and K. C. Wallnau, “The Current State of CBSE,” The Current State of CBSE, IEEE Software, Vol. 15, No. 5, 1998.
[11] M. Broy, et al., “What Characterizes a Software Component?” Software—Concepts and Tools, Vol. 19, No. 1, 1998, pp. 49-56. doi:10.1007/s003780050007
[12] J. Cheesman and J. Daniels, “UML Components,” Addison Wesley, Boston, 2000.
[13] D’Souza and Wills, “Objects, Components and Frameworks with UML,” Addison Wesley, Boston, 1999.
[14] G. Eddon and H. Eddon, “Inside Distributed COM,” Microsoft Press, Washington, 1998.
[15] G. T. Heineman and W. T. Councill, “Component-Based Software Engineering,” Addison Wesley, Boston, 2001.
[16] IEEE SW, “Special Issue on Software Components,” IEEE Software, Vol. 15, No. 5, 1998.
[17] I. Jacobson, et al., “Software Reuse: Architecture, Process and Organisation for Business Success,” Addison Wesley, Boston, 1997.
[18] K.-K. Lau and Z. Wang, “A Taxonomy of Software Component Models,” Proceedings of the 31st EUROMICRO Conference on Software Engineering and Advanced Applications, 2005.
[19] O. Rob Van, et al., “The Koala Component Model for Consumer Electronics Software,” IEEE Computer, 2000.
[20] R. Sessions, “COM and DCOM,” Wiley, New York, 1998.
[21] C. Szyperski, “Component Software,” Addison Wesley, Boston, 1998.

  
comments powered by Disqus

Copyright © 2020 by authors and Scientific Research Publishing Inc.

Creative Commons License

This work and the related PDF file are licensed under a Creative Commons Attribution 4.0 International License.