• From the e-Activity, speculate as to what the system requirement variables (monitored and controlled) and software requirements (input and output) are for the Nokia portable computer. Determine whether or not you believe that system requirements outweigh software requirements when it comes to usability of this computer. Support your position by writing the functional and non-functional requirement for this.
• Suppose that during the modification of an existing system, the group of the parties concerned include five individuals. Two out of the five members do not agree with the system requirements. Provide a suggestion on what techniques you would use to get members to agree with the system requirements.

Classmates:

From the e-Activity, speculate as to what the system requirement variables (monitored and controlled) and software requirements (input and output) are for the Nokia portable computer. Determine whether or not you believe that system requirements outweigh software requirements when it comes to usability of this computer. Support your position by writing the functional and non-functional requirement for this.

System requirement variables is to protect the linkage in between systems requirement and software requirement thats more likely to bring a situation to variables like monitoring and controlling, input and output for systems requirements. However, the four variable model of software requirements embedded  systems has been used to safety critical applications; with that being said, the model does not explicitly specify the software requirements, but rather bounds the requirements to specifying the system requirements and the input and output hardware interfaces of software systems requirement. To continue, the system requirements are the configuration that a system must have in order for a hardware or software application to run smoothly and efficiently. Failure to meet these requirements can result in installation problems or performance problems. The former may prevent a device or application from getting installed, whereas the latter may cause a product to malfunction or perform below expectation or even to hang or crash (Patcas, Maibaum 2013). System requirement are all of the requirement at the system level that describe the functions which the system as a whole should fulfill to satisfy the stakeholders for the requirements and is expressed in an appropriate combination of textual statements, views, and non-functional requirements; the latter expressing the levels of safety, security, reliability, etc., that will be necessary. On the other hand, it will be a battle to determine which one of each can outweigh one another due to to so many changes that will have to met in a particular subsequence when dealing with usability of computers.

Suppose that during the modification of an existing system, the group of the parties concerned include five individuals. Two out of the five members do not agree with the system requirements. Provide a suggestion on what techniques you would use to get members to agree with the system requirements.

However, if there was any modification to support a system to get better ideas from five people from each group, each individuals will have there different roles and part of an agreement to figure out what the systems that needs system requirements by having techniques to determine to get everyone on the same page of thinking rather then have two out of five agreeing to the modification of the existing system. However with that being said, the techniques that can be used for this existing system are in this following.

Brainstorming

On some projects, the requirements are not “uncovered” as much as they are “discovered.” In other words, the solution is brand new and needs to be created as a set of ideas that people can agree to. In this type of project, simple brainstorming may be the starting point. The appropriate subject matter experts get into a room and start creatively brainstorming what the solution might look like. After all the ideas are generated, the participants prioritize the ones they think are the best for this solution. The resulting consensus of best ideas is used for the initial requirements ( Mochal,2008).

Questionnaires

Questionnaires are much more informal, and they are good tools to gather requirements from stakeholders in remote locations or those who will have only minor input into the overall requirements. Questionnaires can also be used when you have to gather input from dozens, hundreds, or thousands of people  ( Mochal,2008).

Group interviews

Group interviews are similar to the one-on-one interview, except that more than one person is being interviewed — usually two to four. These interviews work well when everyone is at the same level or has the same role. Group interviews require more preparation and more formality to get the information you want from all the participants. You can uncover a richer set of requirements in a shorter period of time if you can keep the group focused  ( Mochal,2008).

One-on-one interviews

The most common technique for gathering requirements is to sit down with the clients and ask them what they need. The discussion should be planned out ahead of time based on the type of requirements you’re looking for. There are many good ways to plan the interview, but generally you want to ask open-ended questions to get the interviewee to start talking and then ask probing questions to uncover requirements ( Mochal,2008).

Lucian M. Patcas, Mark Lawford and Tom Maibaum. (2013). Auto Verification of Critical Systems. Retrieved from Electronic Communication of the EASST : https://pdfs.semanticscholar.org/cb7f/9ae49f8f91a89aa43af6c1852688ee20046f.pdf

Mochal, T. (2008, January 2). 10 Techniques for gathering requirements. Retrieved from Tech Republic: https://www.techrepublic.com/blog/10-things/10-techniques-for-gathering-requirements/