Principles of Software System - Ethics, NFR, Requirements Collection, Software Reuse, Test Case Scenario

Running head: PRINCIPLES OF SOFTWARE SYSTEM
Principles of Software System
Name of the Student
Name of the University
Author Note

1PRINCIPLES OF SOFTWARE SYSTEM
Q1. Read the IEEE/ACM and ACS codes of ethics.
a) Comment on any differences. How to you think these compare?
There is a prevailing major difference between the IEEE/ACM and ACS codes of
ethics. The IEEE/ACM code of ethics does not emphasise much on the details about the rules
and regulations and focuses more on the thoughtful and empathetic part of the fundamental
principles (Punchoojit and Hongwarittorrn 2015). On the other hand, the ACS codes of ethics
lack in flexibility when it comes to deviating from the law on humanitarian grounds.
b) Consider the case when you have been asked to write some software for critical
systems. What ethical issues might arise? How would you deal with them?
The ethical issues that might arise while writing some software for critical systems are
as follows:
 The software may be unauthorized for using in multiple critical systems for
free
 The software may not be compatible with the system requirements of the
computer
 The support and documentation may not be properly done
To solve these issues, the person installing the software needs to authorize the
software use before writing them in critical systems (Turk, France and Rumpe 2014). He
should check for the proper system requirements and documentation.

2PRINCIPLES OF SOFTWARE SYSTEM
Q2. Conduct a brief research on the ways of recording non- functional requirements in
agile environment. Your research should include analysis of the techniques used for
recording non-functional requirements.
Having an agile environment in a workplace implies that the environment is
empowered by the workforce and not the organization norms. Non-functional requirements
are however, the most challenging system development area that deals with the quality of the
software more than the technical aspects (Gupta, Chopra and Chauhan 2017). It is noticed,
that in case of software development non-functional requirements are often overlooked.
While recording Non-functional requirements, it is to be kept in mind that the records should
hold the attributes for security, performance, scalability, reliability, maintenance and usability
(Mojica et al. 2014). In agile environment, NFR or the Non-functional Requirements in an
agile system specifies how a particular entity behaves in the organization.
The methodology for recording the NFRs should be of two types:
 Execution qualities: These are better observed at the runtime, such as
usability and security.
 Evolution qualities: These are measureable during the static structure of the
computer system, such as, extensibility, scalability, maintainability and
testability.
An agile system considers architecture design to come forward with an evolutionary
approach. To record the NFR for the agile system, it is required that the technical
stakeholders of the organizational structure. These include the architects, the user interface or
UI designers, and the operation teams (Ma and Ma 2017). Analysing the procedures, it could
be seen that the recording of the NFRs in execution qualities depicts how user friendly or