Spiros Mancoridis
ABSTRACT
Large scale software development is an intrinsically difficult task. Developers use a set of specialized tools to alleviate some of this difficulty. The problem is that most of these tools are not integrated and do little to help developers and managers maintain an overall view of the development by organizing the software entities, created by tools, in a consistent fashion.
Our solution, called the Software Landscape, provides developers with a conceptual framework of integrated tools while providing a metaphor for managing the complexities of large-scale software development.
The Software Landscape is a metaphor of a country-side viewed from above in which each major entity, such as a software project, appears as a large plot of land, and each minor entity, such as a source C module, is contained within a plot. Plots can be libraries of reusable software as well as ongoing developments.
A Software Landscape can be used as a mechanism that allows the developer to navigate around the entities created during the software development process, much the way a flight simulator allows one to “fly” and optionally to dive down to entities of interest. During this flight, and controls their level of visible detail. This model is constructive, allowing the developer to manipulate, as well as view, the entities of the Landscape.
- 1.BOOCH, G. Object-Oriented Design with Applications. Benjamin/Cummings Publishing Company Inc., Redwood City, California, 1991. Google Scholar
Digital Library
- 2.COAU, P., AND YOURDON, E. Object Oriented Analysis, 2nd Edition. Prentice-Hall Inc., Englewood Cliffs, New Jersey, 1990. Google ScholarDigital Library
- 3.ECMA. Portable Common Tool Environment (PCTE) Abstract Specification. Tech. Rep. Technical Report No. 149, European Computer Manufacturers Association, December 1990.Google Scholar
- 4.ECMA. A Reference Model for Frameworks of Computer Assisted Software Engineering Environments. Tech. Rep. Technical Report No. 33, European Computer Manufacturers Association, August 1991.Google Scholar
- 5.GOLDB~rtG, A. Smalltalk-80: The Interactive Pro- #ramming Environment. Addison-Wesley Publishing Company, Reading, Massachusetts, 1983. Google ScholarDigital Library
- 6.HOLT, R. C. The Design of OOT: Object Oriented Turin#. Tech. Rep. CSRI Technical Report, University of Toronto, 1991.Google Scholar
- 7.HOLT, R. C., AND COrtDY, J. R. The Turing Programming Language. Communications of the A CM 31, 12 (December 1988), 1410-1423. Google ScholarDigital Library
- 8.HOLT, R. C., PENNY, D. A., AND MANCORIDIS, S. Multicolour Programming and Metamorphic Programming: Object Oriented Programming-inthe-Large. Tech. Rep. Technical Report No. 74.087, IBM Canada Laboratory, March 1992.Google Scholar
- 9.MANCOKIDIS, S. A Visual Programming Environment for Object-Oriented Turing. Master's thesis, Department of Computer Science, University of Toronto, 1992.Google Scholar
- 10.OSTERWEIL, L. Software Processes are Software Too. Proc. of the 9th lnt'l Conf. on Soft. Eng., IEEE (1988). Google ScholarDigital Library
- 11.PENNY, D. A., HOLT, R. C., AND GoogrtEv, M. W. Formal Specification in Metamorphic Programming. In S. Prehn and W. J. Toetenel (eds.), VDM '9I: Formal Software Development Methods, Proceedings of the 4th International Symposium of VDM Europe, Springer-Verla9 Lecture Notes in Computer Science 551 (October 1991), 11-30. Google ScholarDigital Library
- 12.KEIss, S. P. Graphical Program Development with PECAN Program Development Systems. Proceedings of the A CM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Environments (1984), 324-333. Google ScholarDigital Library
- 13.RF.PS, T., AND T~{TELBAVM, T. The Synthesizer Generator. Proceedings of the A CM SIG- SOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environ. meats (May 1984), 42-48. Google ScholarDigital Library
- 14.tLTMAN, A. The Theory-Model Paradigm in Software Design. Tech. Rep. Technical Report No. 74.048, IBM Canada Laboratory, October 1989.Google Scholar
- 15.TEITELMAN, W., AND MASINTEK, L. The lnterlisp Programming Environment. Computer Science Press, Los Alamitos, California, 1981.Google Scholar
Index Terms
- A conceptual framework for software development
Recommendations
"Leagile" software development
In recent years there has been a noticeable shift in attention from those who use agile software development toward lean software development, often labelled as a shift "from agile to lean". However, the reality may not be as simple or linear as this ...
A conceptual framework for lean regulated software development
ICSSP 2015: Proceedings of the 2015 International Conference on Software and System ProcessA growing number of companies are discovering that their software development processes must be in compliance with some form of regulation. This is particularly so when it comes to safety-critical or business-critical systems such as Automotive ...
Adopting to Agile Software Development
Abstract Agile software development can be made successful, but there is no well-defined way how to achieve this. The problem is that the successful adoption of agile methods and practices is a complex process and this process should be customizable for ...
Comments