Approach to Software

I recommend that you follow a more traditional systems development life-cycle model (SDLC) when developing a comprehensive SAS macro-based reporting system. Unlike much of the one-time-only SAS programming that occurs for a clinical trial, you need to ensure that a general-purpose SAS macro system is robust enough to handle any problem it encounters. The systems development life-cycle approach to software development will help you to build strong software applications with SAS. 

If you plan to get into serious applications development, or even if you plan to write comprehensive generic SAS macros, you will want to learn about the systems development life cycle (SDLC). Developed by the Institute of Electrical and Electronics Engineers (IEEE), the SDLC has been the traditional approach to software applications development for a long time. Besides the traditional SDLC, there are many derivative... 

For GMP applications the software development must be based on a fully documented and structured design and formally reviewed to ensure that it is reliable, safe, testable, and maintainable. A modular approach to software design with annotated documentation will provide a better understanding of the system software throughout the relevant life-cycle activities and also during regulatory inspection. Use of standard software should be considered whenever possible. 

MASCOT Modular Approach to Software Construction, Operation, and Test... 

A mechanism to provide some assurance that software development in the long term will not lead to operating difficulties as a result of uncoordinated standards and solutions could be beneficial. Options to approach this might be a more centralized management system, an agreed approach to standards setting, or other alternatives. Similarly, it could be beneficial if a formal as opposed to collegial approach to software development were implemented. 

Early approaches to software effort estimation were based on this principle, a sophistication tending to be an adjustment by means of the application of exponentiation to take account of diseconomies of scale. These diseconomies can be caused by larger projects needing disproportionately more effort to deal with communication and management overheads. 

Component-based software engineering An approach to software engineering based on the acquisition and assembly of components. 

Naeem M, Heckel R, Orejas F, Hermann E (2010) Incremental service composition based on partial matching of visual contracts. In Rosenblum DS, Taenzer G (eds) Eundamental approaches to software engineering. Proceedings of the 13th international conference EASE 2010. Springer, Berlin, pp 123-138... 

We must therefore seek to understand why more formal approaches to software development have not generated the unstoppable momentum of UML or visual programming and, from this, find ways of injecting formality into the earlier stages of the software lifecycle where it will do most good. 

The failure to attempt a more rigorous approach to software development would not matter if the performance of our industry was wholly to be admired. Regrettably that is not the case. On any objective set of measures our industry paints a story of failure. Cancelled systems, late delivery, poor performance and cost overruns are the norm. Martyn Thomas [Thomas 2003] quotes figures from the Standish Group and from the BCS that show ... 

There is general agreement that the essential attributes of the object-oriented approach to software development include the following ... 

Perhaps a change in the approach to software safety standards was inevitable sooner or later. A number of research strands looking at the issue of certifying COTS products for use in safety-related systems (Advantage Technical Consulting, 2000), (Adelard, 2001), proposed an evidential approach. 

There are a number of fundamental problems with process-based approaches to software safety management. While these do not appear to be resulting in safety-related software products of unacceptable quality, there is a difficulty in developing cogent arguments that the risks associated with safety-related software are acceptable or tolerable. 

Also, Dr Ian Brindle, VP Research at Brock University who supported the development of the PAM prototype during the creation of Norton Scientific Inc. and Adrian Snell who facilitated a lexible approach to software development. 

Maibaum, T.S.E., Wassyng, A. A product-focused approach to software certification. IEEE Computer 41(2), 91-93 (2008)... 

A number of current approaches to software structuring fra safety critical systems aim to simplify the software structure as much as possible, with the structure detomined by the available verification techniques. Whilst simplification of software stincture is to be encouraged, simplification of the safety argument should be a stronger guiding principle. Most current verification methods do not allow this to take place because they do not allow natural software and system structures to be adopted. 

Laprie, J.-C. For a product-in-a-process approach to software reliability evaluation. In Third International Symposium on Software Reliability Engineering (ISSRE 1992), pp. 134-139 (October 1992)... 

---