The JCSE asks for stakeholder input
The Joburg Centre for Software Engineering (JCSE) has asked its stakeholders to provide input on subjects that they would like to see included in its 2009 programme.
2 December 2008
The Joburg Centre for Software Engineering (JCSE) has asked its stakeholders to provide input on subjects that they would like to see included in its 2009 programme.
The JCSE is a three-way partnership between government, academia and the software development industry. Based at Wits University, it is multifaceted, with various programmes and facilities positioning it as a focal point of the software development industry in Gauteng.
The JCSE's 2008 programme of activities covered many of the issues related to the software development lifecycle, says JCSE director Barry Dwolatzky. "We started off without a plan and filled the slots with activities as the year unfolded. Looking back, we covered a lot of key areas of concern to the software development community. But, looking forward to 2009, we don't want to leave the programme to chance. We want to get advice from our stakeholder as to what keeps them awake at night."
To gain input from as wide a variety of stakeholders as possible, the JCSE has formed a Stakeholder Advisory Group, which held its first meeting in November.
Members of the group, who include representatives from large corporates, state-owned entities, government departments and small software development companies, were asked to provide input on issues that are of concern to the software development sector.
"We plan to meet twice or three times a year, and to communicate and share insight and input electronically more often," he says.
A considered approach
Dwolatzky says issues the advisory group would like to see addressed in the JCSE's 2009 programme include concerns around the integration of systems and data in large and complex organisations. These organisations need both the right skills and technology to achieve successful integration.
Another crucial concern relates to the management of client requirements. It is a known problem that defining and managing requirements is the toughest challenge affecting most development projects.
"Projects tend to grow bigger and bigger because the customer keeps asking you to answer bigger and bigger problems. The customer gets bolder, asking for more functionality, and in the end, deadlines are missed and the project's resources are depleted."
There is also a clash of cultures between the nature of the client organisation, and the demands that are made on developers, he says. "For example, if you look at some financial institutions, they place a great deal of emphasis on ensuring that strict regulatory rules are observed in their day-by-day operations. Yet, in the same organisations, there is a lot of pressure on software development teams to cut corners and deliver a solution as soon as possible, compromising on quality."
Stakeholders would also like to receive more input on software testing tools, and how to manage the software development process using CMMI, TSP, SCRUM and PSP, Dwolatzky says.
Extracting the metrics to better understand the software development process is also important. "People are also very interested in cloud computing and grids and they are very keen that we do more work on open source and the skills required for open source development. "
He notes that the JCSE will develop a programme out of these broad topics, which will be turned into courses, workshops and seminars as part of the JCSE's annual plan.
"Step by step, as we start to develop the programme, we will keep canvassing our stakeholders to hear if this is what they want. The question of whether we are meeting the needs of our stakeholders will be answered by how well the events are attended," he notes.
If you have any comments for the JCSE please address them to info@jcse.org.za