Fresh Free Thoughts

The topic of discussion in this week’s lecture was based upon life cycle developments. Life cycles are a critical part of any system development, they ensure that processes can be optimised and errors can be mitigated to a degree. They may not always do this in essence but they should technically be tailored to match the organisation that they wish to serve. They may have new phases added or subtracted depending on the scope and purpose of the project in mind. Royce, 1970 asserts that the development of large scale software programmes using a system development approach requires a step by step approach to developing a finished product. This can be seen in the image below, from p.329. Furthermore Royce states that an addition of feedbacks and interactions between the neighbouring steps should be facilitated to reduce costs and ensure that time scales and budgets are adhered too. The feedback process allows for the release of high quality finished programmes that have little or few

This week our class focused on a broad range of topics from design evaluation, team work, software design and design activity mapping. Our base reading for the week provided a basic foundation for Design systems in the areas of software and the importance of teamwork in this process. The paragraphs below summarise our reading activities. Large scale software systems are seen to draw around the basis of the simplest aspect of software development, with focus on the Analysis and Coding stage. Royce, 1970 illustrates that coding and analysis are central to software development no matter what the requirements are for the project in mind. Royce, 1970 goes on to add that the failure of systems to include the testing phase so late has financial, time and customer satisfaction issues due to a failure of the model to allow for repair without costing a lot of time and labour. Royce argues that preliminary work by program designers would allow collaboration between relevant departments.