13 April: Overview of Model-based performance improvement – 1 day (Johannesburg)
19 April: Overview of Model-based performance improvement – 1 day (Cape Town)
20-22 April: Introduction to CMMI – 3 days (Cape Town)
20 April:Agile Forum
Speaker: Ahmed Omarjee
Overview: Agile software development applies techniques that aim to amplify the effects of standard development practices such as testing through the use of Test Driven Development (TDD) as well as quality control and early feedback through the use of Pair Programming and Continuous Integration. It is common to hear that “if testing is considered good” then “we should strive to test more often” and “if obtaining early feedback on quality is considered good” then “we should strive to obtain such feedback more often”.
Continuous Integration is an agile software development practice that implements continuous processes of applying quality control – that is small pieces of effort, applied frequently. It aims to improve the quality of software, and to reduce the time taken to deliver it, by replacing the traditional practice of applying quality control after completing all development.
The typical lifecycle includes members of a team integrating their work frequently, usually each person integrating at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including tests) to detect integration errors as quickly as possible. Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly.
Overview: We have seen the use and abuse of the architectural views suggested by different architecture guidelines, but we seldom see the usage of those guidelines yield the desired results. Often the TOGAF guidelines are flouted to present an architecture for the sake of presenting it. But do these views always answer the questions related to all apsects of a system? We have seen many times the architecture views leave too many things to be interpreted subjectively by the implementation team leading to failure during implementation. Can there be a list of architecture views which could serve as a definitive list for all system architectures? How does the Solution and Enterprise Architecture meet the Business Architecture? How do we merge these successfully?
Here is a list of views suggested to see the system architecture from different angles and leave very little for subject to interpretation:
Topic:Report-back from the “SEPG North America” Conference
Speaker: Prof Barry Dwolatzky
Overview: “SEPG North America” is the Software Engineering Institute (SEI)’s big annual process improvement gathering. In March 2010 it was held in Savannah, Georgia, and was attended by nearly 1,000 process experts and software engineers from around the world. Some of the highlights of the conference were papers on Cloud Computing, CMMI and Agile, CMMI for Services and a “multi-model” approach to process improvement. There was also a forum on the upcoming CMMI version 1.3, due for release later in 2010.Barry Dwolatzky, Director of the JCSE was one of the few attendees from Africa.He will present an overview of some of the important papers presented at SEPG 2010.