Posts

Controls

They write the right stuff, by Charles Fishman 1996, explores the level of control that is exacerbated by the requirements that are used in the deployment of spaceshutlle software. Such a software si portrayed as been perfect by the author, and so it should, this software controls the faith of those aboard the space shuttle. The trouble-free software, is a remarkable feat, it could easily improve the usability of any programme, however we question the usage of this type of documentation in the commercial world of software, as it is seen to be rigid, lack any freedom The author stresses that the success of the group is based due to the process that is in place. The author stresses how such a feat is has not spread to any other section of the industry and offers insight into what comprises this success. The organisation of the specifications for this type of software is seen to be the critical feature. The highly regulated specifications highlight the high level of control that the

Requirements

In this week’s class we looked at the importance of requirements through a practical and theoretical setting. As discussed briefly in my last post Life Cycles: The cycles of life? we explored very briefly the importance of specifications, which are a base of requirements. Requirements are comprised of scope, purpose and a description that will allow the user/client to carry out the specific task that they need address/completed by the product/software programme. The requirements will generally set out the limits and simplifications that are required from the finished product. Requirements will generally consist of goals and scenarios that are required by the finished product and developers are obliged to meet these. The requirements will also look at the risks and deadlines that are a part of the development process. Deadlines are an important aspect as they outline when the product is required and also can determine the cost of the project. It is especially undesirable if the

Life cycles: The cycle of life?

Image
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

Spaghetti, Six Students & Sticky Tape

Image
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.

Design and Evaluate

The focus of discussion in our class this week was in relation to the design aspects of product development and the processes of making a product or service more approachable and usable to customers/users. Following our previous weeks readings of Expressing Experience in Design by Bill Moggridge (1999) & Usability Evaluation Considered Harmful Some of the time by Greenberg & Buxton (2008), we were provided with a basis of knowledge around the ideas of usability, interface design and functionality. Moggridge’s (1999) article on experience through design, provided a suitable background to the area of design and the close relationship that its shares with our senses. I found the article quite helpful in providing a basis background to designing for experiences of the user, although the article was quite outdated. It provided the frameworks and the key themes that can still be seen in design today. It is safe to assume that design on its own is just a process in which a

Systems, systems, systems!

This blog series based on as a series of journal entries will showcase the learning path of a MSc Digital Innovation student. The purpose of the series is to showcase the evolution of knowledge, skills and practices that have been obtained throughout the duration of the module on Design, Development and Creativity. In this week's entry, We will explore the initial thoughts of the areas of systems, showcase my development and the change in my knowledge of the area. So firstly our first exercise of the academic year was to provide the class with what we thought was a system. My response was as a follows, ‘My definition of a system is a network of institutions and processes that are governed by laws that in turn provide a benefit’. So after been asked to define a system, my first idea based on my working experience was to think of a crucial area of society such as the banking sector as a system.The banking sector which provides numerous services to society, have the following inpu