Professional Documents
Culture Documents
Christian says:
From North West Sydney, I went to a senior High School with teachers that
specialised in teaching the HSC curriculum. As a result I have study notes that are
in depth, but not too long so they are still readable.
– Code of Conduct. Developers should adhere to a code of conduct specifying what they are
allowed to do.
– Ergonomic issues. Developers should work in an ergonomically safe environment, and the
software they make should be ergonomically sound for the user.
– Inclusivity issues. Software should take into account different cultural backgrounds, economic
backgrounds, genders and disabilities to ensure equal access for all users.
- Intellectual property. Original authors of software can be vague, but should have rights
regarding the use and sharing of their software.
- Malware. Software developers are responsible for ensuring their software is free of malware.
- Privacy issues. Developers should ensure they are only requesting information they require, and
that personal information is used correctly.
– Plagiarism. Code is often reused, but should always be properly acknowledged and should only
be used with permission.
– Copyright laws. Creators of software have a right to benefit from their work. Promotes creative
endeavours.
– License Conditions, which protect intellectual property rights and protect developers from legal
action.
– Types of Software including commercial, open source, shareware and public domain.
– Software privacy prevention methods including non-copyable datasheets, hardware serial
numbers, installation counters, registration codes, encryption keys and back-to-base
authentication.
Use of Networks
– Maintaining market position. Social and ethical issues must be considered when developing
marketing techniques and strategies. Marketing is in terms of product, place, price and
promotions.
– The effect of dominant developers od software
– The impact of new developers of software and new products
Legal implications
– Agile. Based on repeating and incremental development, where requirements and solutions
evolve. Very fast production, uses requirements to aid development. Cycle of Analyse, Develop,
Test done for each feature. Delivered in incremental ‘releases’ and iterating. Each feature
completed fully before doing the next. Timescale is fixed, requirements evolve. Involves
collaboration between self-organising, cross-functional teams. Once released, adds new
features, tests and releases updated version. Low levels of documentation.
– End User Development. Developer is client, no communication issues. User solves his own
problems quickly. Lack of formal stages, small budget and time period. Fourth generation
languages used.